Privacy
Privacy notice
What TieProof collects, why, where it is kept, for how long, and who else handles it. It describes the system as it is built today. TieProof is not yet in service, and no customer's file has been processed.
Draft for the founders' review. This page is not yet approved and is not yet in force. Each passage in square brackets is for the founders to write. Drafted on 7 November 2026.
Who is responsible
TieProof is provided by [the company's legal name], [its legal form and registration number], of [its registered address].
For your account and for how the website and the service are run, TieProof decides how your personal data is used. For the files your organization checks and their results, TieProof acts for that organization, which decides what is uploaded. A data processing agreement for organizations is not available yet.
Questions and requests about this notice go to [the address for privacy requests].
What TieProof collects
- Your account
Your email address and a hash of your password, held by the identity service, or, if you sign in with Google, the address and the profile details Google shares at sign-in, such as your name. The sessions of your sign-ins.
- Your organization
Its name, its members' addresses and roles, its projects and settings, and each invitation: the address invited and a digest of the invitation's token.
- The files you check
The files you upload, which hold personal data only if your documents do. They are deleted after the number of days your organization keeps them.
- Results
What a check found: the figures it read, its findings and their evidence excerpts, which are short passages of your files: the values, their locations and the text around them. Also the decisions your team records on findings.
- The audit log
Who did what, and when: decisions on findings, changes to settings and members, and deletions. It holds no text of a reason.
- Technical records
The services log request and check identifiers, routes, status codes, durations and counts, never a file's content. To enforce rate limits, the API counts a signed-in user's requests by user and by network address. The web app's host keeps request logs of the pages it serves.
- Email
Address confirmations, invitations and notices that a check has finished are sent to your address. Not yet in service: no email provider is chosen for a deployment.
- Help
The Help form sends nothing itself: it opens your own email app, or copies your message for you to send.
What TieProof does not collect
The website sets no cookie for a visitor who does not sign in, loads no script from any other site, and records no visit. There is no analytics, no advertising and no tracking.
TieProof does not sell personal data, and does not use your files or results to train any model.
Why it is used
To run your checks and show their results; to keep accounts and organizations secure, through the rate limits and the audit log; to send the emails the service needs; and to answer what you ask.
The legal basis of each use: [the legal basis of each use, once the governing law is chosen].
AI
No external AI model is used today. Matching uses an embedding model that runs inside TieProof's own worker and sends nothing out.
Not yet in service: when external models are added, they will receive only the excerpts one task needs, never a whole file, under terms that bar training on your data, and nothing from an organization whose admin chose Local only. This notice and the security page will name them first.
Who else handles it
Three services handle data for TieProof: Google Cloud, Supabase and Vercel. The subprocessor list says what each does, what it holds, where, and under which terms.
If you choose to sign in with Google, Google confirms who you are, under its own privacy policy.
Where it is kept
The staging environment runs in northern Virginia, in the United States. The production region is not chosen yet.
Transfers between countries: [how transfers of data between countries are protected].
How long it is kept
- Uploaded files
7 days after the check ends, unless an admin chooses from 1 to 30 days.
- Working copies
Deleted at the end of every attempt to run a check, whether it succeeded or failed.
- Results and evidence
Until someone deletes the check or its project. They are never deleted for their age.
- Label vectors
The numerical forms of labels read from your files, used in matching, are deleted once unused for your organization's number of days.
- Rate-limit counts
Deleted once their minute or hour has ended.
- The audit log and your account
Kept as long as the organization and the account are.
- Logs
Not yet in service: how long logs are kept is not set yet.
Your choices and your rights
- Deleting a check
An analyst deletes their own finished checks, and a reviewer or an admin any finished check, with its results, its evidence and any file still stored.
- Deleting a project
An admin deletes a project and every check in it.
- Retention and AI
An admin chooses how many days files are kept, and whether the organization's checks may use external AI once it is added.
- Your account, your organization, your data
Not yet in service: deleting an account or an organization, and exporting your data, are not offered on a screen yet. Ask at [the address for privacy requests].
- Your rights
[the rights the governing law gives, and the regulator to complain to].
Cookies and browser storage
TieProof sets only what the service needs in order to work, so it shows no cookie banner. Anything else would be set only after you agree to it.
- __Host-tieproof-session
Cookies whose names begin with this hold your session once you sign in, in numbered parts when it is long, and, while a sign-in is in progress, the value that ties it to this browser. No script can read them, they are sent only over HTTPS to TieProof's own pages, they last 7 days after their last use, and logging out removes them.
- tieproof-invitation
Kept in this browser's storage, not a cookie: the token of an invitation you opened, so that it survives a sign-in. It is sent once, when you accept, and then forgotten.
- tieproof-completion-notices
Kept in this browser's storage, not a cookie, only if you turn on the notice that a check has finished: that you chose it in this browser. It is never sent to TieProof, and turning the notice off removes it.
Changes to this notice
A change is published on this page with its date. Notice of a change: [how much notice a change is given].
Contact
[the company's legal name], [its registered address]. Privacy requests: [the address for privacy requests].