Privacy policy
Last updated 6 October 2026
This policy explains what CertRevisit does with personal data. It covers three kinds of people: visitors to this website, customers who hold an account, and the vendors whose certificates a customer collects.
1. Who is responsible
The operator named in the imprint is the controller for this website and for customer accounts.
For everything a customer uploads or collects about their own vendors, the customer is the controller and CertRevisit is a processor acting on their instructions. If you are a vendor and want your data corrected or removed, ask the company that requested your certificate — they decide, and we act on what they tell us. You can also write to us and we will pass the request on.
2. What we collect
From a customer: the email address used to sign in, the company name they enter, and the times they signed in. Payment is handled by Stripe; we store the Stripe customer and subscription identifiers and the plan, never card details.
From a customer about their vendors: vendor name, contact name and email address, notes the customer writes, and the certificate files uploaded, together with the carrier, policy numbers, coverage limits and dates read out of them.
From a vendor directly: the file they upload through their link, and the fact and time of the upload. We do not ask a vendor for an account, a password or anything else.
A photographed certificate is read on the vendor's own device. When a vendor uploads a photo instead of a PDF, the text is recognised in their browser, on their own phone or computer, and only the file and the fields read out of it reach us. The image is never sent to a text-recognition service, and the software that reads it is served from this site — not from anyone else's.
From every visitor: usage events for a small set of product actions, and standard server logs held by our hosting provider.
3. What we do not keep
The full extracted text of an uploaded document is deliberately not stored — only a short excerpt, capped at 4,000 characters, so a parse can be audited. We do not sell personal data, and we do not use customer or vendor data to train models.
4. Why we are allowed to
For a customer's own account data: performance of the contract, Article 6(1)(b) GDPR, for everything needed to give you an account and run it; our legitimate interest, Article 6(1)(f), in keeping the service secure and working; and a legal obligation, Article 6(1)(c), for invoicing records that tax law requires us to keep.
For everything about a customer's vendors: the customer is the controller and relies on their own legitimate interest, Article 6(1)(f) — verifying that the contractors they engage carry the insurance they were asked for. We process it only on their instructions, as a processor under Article 28, and for no purpose of our own.
Where consent is the basis for anything, you may withdraw it at any time, and withdrawing it does not affect what was lawful before.
5. Who else sees it
We use these processors, and no others:
- Supabase — database, authentication and file storage.
- Vercel — hosting and server logs.
- Stripe — payments and subscription management.
- PostHog — product analytics, US region.
- Google — advertising measurement. When you arrive from one of our ads, Google's tag records that the visit led to an account being created. It sees the pages of this site you visit and sets cookies for that purpose. It receives no email address, no account identifier and nothing about your vendors.
- Sentry — error reports and a sample of performance traces, so faults can be found and fixed. It is configured to receive no cookies, no request headers or bodies, no query strings and no account identifiers, and a vendor's upload link is removed from everything sent to it. A stack trace is enough to fix a bug.
- Resend — sending email, from our own domain.
Data is processed in the United States, where the customers are. Each processor above is engaged under its own data processing agreement, which includes the European Commission's standard contractual clauses where a transfer needs them. We will name the agreement that applies to any of them on request.
6. Cookies and analytics
We set a cookie to keep you signed in, and PostHog stores an identifier so repeated visits are not counted as new people. There is no advertising, no tracking across other websites and no automatic capture of everything you click — only the handful of product events we chose.
7. How long we keep it
Account data for as long as the account exists, and then for 30 days after it is closed — long enough that an account closed by mistake can be brought back, and no longer. Certificates and vendor records for as long as the customer keeps them, since they are the customer's records to keep. Invoicing records for as long as tax law requires.
8. Your rights
You can ask for a copy of your data, ask us to correct or delete it, object to processing, or ask for it in a portable form. Write to the address in the imprint and we will answer within a month. If you are in the EEA you may also complain to your data protection authority.
Deletion on request. A customer can ask us to delete their account and everything in it, including uploaded files, and we will do so.
9. Security
Data is encrypted in transit and at rest by our processors. Access to the database is restricted per organization at the database level, so one customer cannot read another's records. A vendor's upload link is a secret: anyone holding it can upload for that vendor, which is why the link should not be posted publicly.
10. Changes
We will update this page when the service changes and move the date at the top. Material changes will be sent to account holders by email.