Privacy policy
Polygraph is published by Polygraph, Inc. This policy covers the Polygraph service (the server you connect to your AI agent at mcp.polygraphagent.com, its setup and sign-in pages, and the emails it sends) and this website. Questions go to support@usepolygraph.com.
- Polygraph coordinates a request between two people: a few short questions, each with an agreed form for its answer. The asked person’s own AI agent establishes the answers from their records.
- Polygraph doesn’t connect to, browse or copy anyone’s files, inboxes or accounts. It receives what people write into requests, the questions they agree to, any changes they choose to suggest with any personal note they choose to send, and the answers the person asked approves and sends. An answer is only its value, such as Yes, a number or a short line of text: no evidence, summaries or reasons.
- The answers, and when they were verified, go to the two people in the request, through their own accounts. There are no public result links.
- A request stops accepting decisions and answers 14 days after it is first sent; that is not a deletion date. Requests and their records have no fixed deletion date. You can ask us to delete your information, and we review each request by hand. Some sign-in and notification records expire on their own; the periods are listed below.
What we collect
- Account details. Sign-in is handled by Clerk. Polygraph receives your account ID, your verified email address and your display name. It never receives your password.
- Requests. What you ask and any context you give, who or what it is about, the email address of the person you are asking, anything Polygraph asks you to clarify and your replies, the drafted questions with their definitions, evidence criteria and answer forms, and every version of them. Requests and questions can contain personal information about the person asked.
- Decisions. Approvals, agreements, proposed changes and declines, with the account that made each one and when. A proposed change is in the words of the person who suggested it and may include a personal note they chose to send.
- Answers. The answers the asked person’s AI agent sent once they approved them: each answer’s value in its question’s agreed form, when the answers were published, the version of the questions they answer, the account, the supported route they came from, and the version of Polygraph’s answering standard in force. The submission has no place for evidence, documents, summaries, explanations or reasons, and Polygraph asks for none, though it can’t guarantee that a short text answer holds nothing else. A submission Polygraph refuses is not stored.
- Emails. Copies of the invitations and notices we send (recipient, subject and content), and delivery records: when each was sent, the email provider’s message reference, and the status the provider reports, such as delivered or bounced and, where reported, opened or clicked. Replies to Polygraph emails aren’t read or treated as answers or decisions, but they reach our email provider.
- Connections. Records of each sign-in and of the AI app you connect, with sign-in codes and tokens stored only in hashed form. Sign-in pages use a hashed form of your IP address to limit repeated attempts. Each time your connection reads or acts on a request made to you, Polygraph checks whether it can send answers. It looks at the network address the connection comes from, the AI app’s client details and certificate, and its protocol headers. When answers are accepted, the route is recorded with them. Listing, opening and submitting also write a log entry that describes the route only in fixed categories, such as the kind of AI app and which checks passed; it doesn’t contain your IP address, account or request. If your AI app subscribes to updates, the address it gives for them is stored encrypted.
- Operational records. Daily usage counts per account and request, the status of background work, error codes, AI outputs kept so interrupted work can resume without repeating it, and service logs.
- Earlier requests. Requests made with earlier versions of Polygraph worked differently. In the first, the asked person’s AI agent sent a report (answers, evidence summaries, limitations and dates) which Polygraph reviewed. In the next, the person asked agreed to have specific claims verified, and Polygraph recorded which claims were verified. Those requests, their terms, decisions, reports and results are kept as they were. They are closed and can’t be continued.
- This website. Cloudflare serves it and processes your IP address and browser details to do so. It may also use Cloudflare Web Analytics to count visits. The website sets no cookies of its own.
- Earlier sign-up lists. If you joined our waitlist or early-access list, we keep the email address you entered as a contact in Resend, our email provider. The website no longer collects waitlist sign-ups.
Polygraph never receives the records an AI agent looks at: no source emails, files, screenshots or documents, unless someone writes their content into a request or a proposed change. It processes no payments.
Information Polygraph is not for
Don’t put payment card details, health information, government identification numbers, passwords, API keys and sign-in codes, or other sensitive personal information into a request or a proposed change. Polygraph is not designed to handle them, and its terms don’t allow requests for them.
How we use it
- To run requests: draft and check questions, release them, record decisions, check and publish answers, and show both people the answers and when they were verified.
- To sign you in, keep accounts secure, apply usage limits and prevent misuse.
- To send the emails that belong to a request: the invitation, notices when the requester updates it or the person asked suggests a change, and a completion email to the requester containing the agreed questions, their published answers and the date. Answer values appear in the body, not the subject or preview.
- To send people on the waitlist, and on the earlier early-access list, updates about Polygraph’s launch by email. We use those addresses for nothing else.
- To fix problems, finish interrupted work and answer you when you contact us.
Polygraph uses AI models, currently through the OpenAI API, to draft and check the questions and evidence criteria of a request, and to check that each short text or list answer fits its question and carries nothing else. That check sends those answers, with their questions, definitions, evidence criteria and answer forms, to OpenAI for that one decision, asking it not to store them; OpenAI’s own retention terms apply. It can’t judge whether an answer is true and never changes one. To draft sound criteria it may also search the public web through Exa for general background, such as what a standard means. Those searches are written to leave out names and request details, but Exa receives the search text.
We don’t sell personal information, use it for advertising, or publish results. Polygraph doesn’t train AI models on your information.
Who receives it
- The other person in the request. The person asked sees the requester’s display name and the email address they signed in with, and every version of the questions the requester releases. The requester sees decisions and proposed changes, including a personal note if the person asked explicitly chooses to send one. A personal note is not verified evidence and is not included in Polygraph’s drafting or answer-check context. Both see the answers and when they were verified. The requester’s own wording, drafts, Polygraph’s clarifying questions and each person’s private settings stay with that person.
- Anyone holding an invitation link. The setup link in an invitation shows who asked, the request’s title and its questions with their answer forms to whoever opens it. It doesn’t show the invited address or any answers, and it grants no access to the request.
- Your AI app. Whatever Polygraph returns to your connection passes through the AI app you use (such as ChatGPT or Claude) and its provider, under their own terms.
- Service providers. Cloudflare (hosting, network protection and storing email copies), Neon (the database), Clerk (sign-in), OpenAI (AI models, including the answer check), Exa (public web search) and Resend (email, and the waitlist). Completion emails contain the published answers; the email provider and recipient’s inbox hold copies. Each provider processes data to provide its service to Polygraph, which can include processing in the United States and other countries.
- Update addresses. If your AI app subscribes to updates on a request, the address it gives receives short status messages: a request’s status and version, never its questions or answers.
- When required. We may disclose information if the law requires it, or where needed to protect people from harm or the service from abuse.
How long we keep it
- Requests, questions, decisions, answers, earlier requests’ reports and results, email copies, delivery records, usage counts and other operational records have no fixed deletion date. Polygraph doesn’t delete them on a schedule; they are removed only when we act on a deletion request, as described below. A request’s 14 days limit what can still happen on it, not how long it is kept.
- Sign-in records expire quickly: a sign-in in progress after 10 minutes, a sign-in code after 2 minutes, an access token after 15 minutes. A saved sign-in issued by Polygraph lasts at most 30 days from when you signed in. A connection made before Polygraph issued its own sign-ins may instead keep refreshing under Clerk’s session settings until you disconnect it. Expired records are cleared by a cleanup that runs regularly.
- Update subscriptions last at most one day. When one ends, its delivery address and secret are cleared; a record that it existed remains. Records of completed update messages are removed once they are more than seven days old.
- The waitlist and the earlier early-access list keep your address until you ask us to remove it.
- Service logs are held by Cloudflare under its own log retention.
Deleting something from Polygraph doesn’t reach copies elsewhere. These include questions and answers the other person has already received, anything that passed through either person’s AI app, copies our providers keep under their own retention (including the email provider’s copies of messages and replies), and database backups, until those expire.
Your choices and requests
- Nothing goes out unless you approve it. The requester approves the exact questions before anything is sent. The person asked can agree to the whole request, suggest changes or decline; opening a request agrees to nothing. Their AI agent looks through their records only after they agree and shows them the answers first. Polygraph receives only the answers they approve, all together.
- Disconnect at any time by removing Polygraph from your AI app.
- Ask us for a copy of your information, to correct your account details, or to delete your information. Write to support@usepolygraph.com from the email address on your account, or the one an invitation was sent to.
- Leave the waitlist at any time. Write to support@usepolygraph.com from the address you signed up with, and we’ll delete it from Resend.
- Invited but not interested? You can ignore the invitation, decline it, or ask us to remove your address.
How we handle deletion requests
There is no self-service deletion yet; a person handles each request. We first confirm the request comes from the address involved. We then delete or de-identify the information we hold about you where we can.
Some records may be kept, or kept with your details removed. These include the agreed questions and published answers of a request the other person still relies on, records needed to keep the service secure and prevent misuse, and anything the law requires us to keep. Agreed questions and published answers are never rewritten. Deletion also can’t reach the copies elsewhere described above.
We’ll reply with what we deleted, what we kept and why.
Security
Polygraph uses encrypted connections, keeps sign-in codes and tokens only as hashes, encrypts update addresses and their secrets, and keeps request data in private storage that only the service and the person who runs it are given access to. No system is perfectly secure; if you think something is wrong, tell us at support@usepolygraph.com.
Changes
When our practices change we’ll update this page and the date at the top.