diff --git a/src/faq.md b/src/faq.md
index fd63e71..4ce54b5 100644
--- a/src/faq.md
+++ b/src/faq.md
@@ -12,6 +12,7 @@
 - [How to run TLSNotary with extra logging?](#faq10)
 - [How do I troubleshoot connection issues?](#faq11)
 - [Does TLSNotary Solve the Oracle Problem?](#faq12)
+- [What is a presentation in TLSNotary?](#faq13)
 
 
 ### Doesn't TLS allow a third party to verify data authenticity? { #faq1 }
@@ -96,3 +97,9 @@ If you are connecting through a WebSocket proxy (e.g., in the browser extension)
 No, the TLSNotary protocol does not solve the "Oracle Problem." The Oracle Problem refers to the challenge of ensuring that off-chain data used in blockchain smart contracts is trustworthy and tamper-proof. While TLSNotary allows a Prover to cryptographically authenticate TLS data to a designated Verifier, trust is still required in the designated Verifier when it attests to the verified data on-chain. Therefore, this is not a trustless, decentralized solution to the Oracle Problem.
 
 TLSNotary can be used to bring data on-chain, but when the stakes are high, it is recommended to combine TLSNotary with a dedicated oracle protocol to mitigate these risks. Multiple projects are currently exploring the best solutions.
+
+### What is a presentation in TLSNotary? { #faq13 }
+
+In TLSNotary, a **presentation** refers to data shared by the Prover to selectively reveal specific parts of the TLS data committed to earlier during the attestation phase. By using these earlier commitments, the Prover can choose to disclose only particular segments of the TLS data while keeping other parts hidden or redacted. This enables a flexible and controlled way to share proofs, ensuring that sensitive information remains private.
+
+The term “presentation” is inspired by similar terminology in the [W3C Verifiable Credentials standard](https://www.w3.org/TR/vc-data-model/#dfn-verifiable-presentations).
\ No newline at end of file