1. The essentials
- The content of your PDF is not stored: it is passed to the analysis engine for as long as it takes to produce the report, which is displayed in your browser.
- We keep data about the analysis: the file’s digital fingerprint (SHA-256), status, score, page count and sign codes, along with your analysis balance.
- The Service uses neither advertising nor audience-measurement tools.
- Our providers are Clerk (sign-in), Supabase (database), Vercel (hosting) and Stripe (payment).
- You exercise your rights by writing to [to be completed].
2. Data controller
The controller of account and usage data is [to be completed] ([to be completed], [to be completed]), [to be completed]. Contact for any question or request: [to be completed].
3. Data processed
| Data | What it is used for | Legal basis (GDPR, article 6) |
|---|---|---|
| The PDF you submit (content) | Producing the report, without storing it | Performance of a contract (6.1.b) |
| Analysis summary: file SHA-256 fingerprint, status, score, page and analysed-page counts, sign codes, counting mode, date | Keeping count of analyses (free, credits, Firm quota), not counting a re-submission twice, preventing abuse | Performance of a contract (6.1.b); legitimate interest (6.1.f) |
| Clerk account identifier, plan, subscription status and period end, credit balance and history | Managing your account, your access rights and your balance | Performance of a contract (6.1.b) |
| Stripe customer identifier and payment events processed (identifier, type, date) | Linking payments to your account, crediting reports, activating the subscription without double processing | Performance of a contract (6.1.b) |
| API keys: name given to the key, display prefix, key fingerprint (SHA-256 hash), creation, last-use and revocation dates; per-minute request counters | Authenticating your calls, limiting rates, protecting the Service | Performance of a contract (6.1.b); legitimate interest: security (6.1.f) |
| Sign-in data managed by Clerk: e-mail address and other information depending on the sign-in method chosen | Creating and securing your account | Performance of a contract (6.1.b) |
| Payment data (payment method, billing address, e-mail) collected and kept by Stripe (via Link) | Collecting payment, invoicing, applying VAT, handling refunds and disputes | Performance of a contract (6.1.b); legal obligations (6.1.c) |
| Technical logs kept by the host, for example IP address, date and requested address | Security and proper operation of the site | Legitimate interest (6.1.f) |
| Your e-mails and messages to the Publisher | Answering your requests | Legitimate interest (6.1.f); performance of a contract (6.1.b) |
| Light or dark theme preference, stored in your browser | Remembering your display choice | Exempt from consent (see “Cookies”) |
4. Messages sent through the contact form
When you write to the Publisher from the Contact page, or from the “Any feedback, any need?” field on the Analyse, Pricing and Account pages, we record:
- your message and its category (feedback, need, bug, question or other);
- your e-mail address, only if you provide one: the field is optional;
- your account identifier, if you are signed in;
- a salted fingerprint of your IP address (computed with a secret held by the Service: the address itself is never stored) and the date of sending.
This data is used to reply to you, to improve the Service and to prevent abuse (the number of messages is limited per hour and per day). Legal basis: legitimate interest (6.1.f). It is kept for 24 monthsto be confirmed, then deleted. You can ask for access to, correction of or erasure of a message by writing to [to be completed]. Please do not paste the content of a confidential document into this form: it only accepts text.
5. Your documents
The PDF is sent from your browser (or through the API) to the Service’s server, then to the analysis engine, which runs on the same hosting platform. Its content is read in memory to produce the report; it is not written to our database.
Archiving: option not enabled
The Service’s code includes an option to archive PDFs on Google Cloud Storage. This option is not enabled as of this version. If it were to be enabled, this policy would be updated before activation (purpose, duration, location, provider).
Third-party documents
A document may contain third parties’ personal data or sensitive data. Only submit it if you have the right to examine it. For this content, the Publisher only acts to produce the report you ask for.
6. What we do not do
- The Service uses no advertising, no audience-measurement tool and no profiling tracker.
- No solely automated individual decision within the meaning of GDPR article 22 is taken about you: the report is a technical sign, the decision remains human.
- We do not ask for your bank card number: it is entered on Stripe’s payment page.
7. Providers and recipients
We use the following providers. They process data on our behalf or, in Stripe’s case, on their own account as the seller of record.
| Provider | Role | Data concerned | Location and safeguards |
|---|---|---|---|
| Clerk, Inc. (United States) | Authentication and account management | Identity and sign-in data | Processing in the United States; Clerk states it is certified under the EU-US Data Privacy Framework and provides standard contractual clauses |
| Supabase (Supabase Pte. Ltd.) | Database | Analysis summaries, accounts, credits, key fingerprints | eu-west-3 region (Paris), AWS infrastructure; standard contractual clauses for any transfers |
| Vercel Inc. (United States) | Hosting and running the site and the engine | PDF content (in transit and in memory), technical logs | Functions configured in the cdg1 region (Paris); Vercel states it relies on the Data Privacy Framework and standard contractual clauses |
| Stripe (via Link) | Payment, seller of record, invoicing, VAT | Payment data, e-mail, billing address, customer identifier | Stripe’s Irish entities for Europe; Stripe, Inc. certified under the Data Privacy Framework; standard contractual clauses |
| Google Cloud Storage (Google) | PDF archiving | None | Not enabled as of this version |
8. Transfers outside the European Union
Clerk, Vercel and Stripe are US groups: data may be processed in the United States. These transfers rely on the EU-US Data Privacy Framework where the provider is certified, and on the European Commission’s standard contractual clauses. The Service’s database is located in the Paris region.
9. Cookies and local storage
The Service only uses what is necessary for it to work. It sets no advertising or audience-measurement cookie.
| Name | Issuer | Purpose |
|---|---|---|
| __session | Clerk | Session: recognising you once signed in |
| __client_uat | Clerk | Indicates the browser’s sign-in state |
| _cfuvid | Cloudflare, via Clerk | Infrastructure: managing traffic to Clerk’s services |
| vd-theme (local storage, not a cookie) | Veritas-Doc | Remembering the light or dark theme, until you clear it |
Clerk states that its cookies are required for it to function and do not store personally identifiable information by default. These trackers fall under the consent exemptions (article 82 of the French Data Protection Act: the CNIL cites authentication and interface personalisation): the Service therefore shows no consent banner. The payment page, hosted by Stripe, may set its own trackers, governed by Stripe’s policy.
10. Retention periods
We keep data for as long as each purpose requires:
| Data | Period |
|---|---|
| PDF content | Not kept: it is not stored |
| Account, plan, balance and credit history | As long as the account exists, then deletion within 30 daysto be confirmed of a deletion request |
| Analysis summaries | As long as the account exists (they are used to count free analyses and quotas); when the account is deleted, they are pseudonymised (the link with your account is removed, the file fingerprint is kept) and then erased within 12 monthsto be confirmed |
| Payment data and invoices | Kept by Stripe (via Link) under its legal obligations; we only hold the Stripe customer identifier and the events processed |
| API keys | Fingerprint kept while the key exists, then 12 monthsto be confirmed after revocation |
| Rate-limit counters | One-minute windows, purged after about one hour |
| Host’s technical logs | Period set by the host according to its plan |
| Messages sent to the Publisher | 3 yearsto be confirmed after the last exchange |
| Messages from the contact form | 24 monthsto be confirmed after sending |
11. Your rights
Under the General Data Protection Regulation (GDPR) and the French Data Protection Act, you have the following rights:
- access to your data and a copy (article 15);
- rectification of inaccurate data (article 16);
- erasure (article 17);
- restriction of processing (article 18);
- portability of the data you gave us (article 20);
- objection to processing based on legitimate interest (article 21);
- setting instructions for what happens to your data after your death.
How to exercise them
Write to [to be completed]. We reply within one month, extendable by two further months for a complex request (GDPR article 12). We may ask you to prove your identity. To delete your account, give the e-mail address you sign in with: we delete your data from our database and ask for your account to be deleted at Clerk.
Payment data held by Stripe (via Link) is Stripe’s responsibility: for a request about it, contact Stripe or Link. Stripe states that it handles deletion requests for data tied to Managed Payments transactions and the associated Link account.
Complaint
If you believe your rights are not being respected, you may lodge a complaint with the French data protection authority (CNIL): cnil.fr/fr/plaintes.
12. Security
Measures in place as of this version:
- Exchanges with the site are encrypted with HTTPS, provided by the host.
- The database is only reachable by the Service’s server: no direct access from a browser is intended.
- API keys are never stored in clear: only their fingerprint is, and a key is shown once.
- Stripe’s payment notifications are verified by signature before any processing.
- The analysis engine only accepts calls authenticated with a secret shared with the Service’s server.
13. Changes to this policy
This policy may change, notably if the Service changes (for example when archiving is enabled). The version date appears at the top of the page; significant changes are notified to you by e-mail or in the Serviceto be confirmed.