1. In short
Suitra uses the cookies it needs to sign you in, keep your session secure and run the demo you open. It also measures how the product is used, with PostHog, to improve it: without your consent this measurement is anonymous and stores nothing on your device; session recordings, heatmaps and click capture run only if you accept them in the cookie banner. Suitra uses no advertising and no social-media cookies.
2. The cookie banner
Article 82 of the French Data Protection Act (loi Informatique et Libertés), which transposes article 5(3) of the ePrivacy Directive, requires consent before information is stored on or read from your device, except when this is strictly necessary to provide an online service you have expressly asked for.
In its guidelines and recommendation on cookies (délibérations n° 2020-091 and 2020-092 of 17 September 2020), the CNIL lists cookies used for authentication, and those that secure it, among the trackers exempt from consent. The demo cookie only serves the demo you asked to open. The cookies in section 3 fall into one of those cases: they are set without asking, and disclosed here.
Session recordings are not strictly necessary, so when product analytics is turned on, a banner asks for your consent to one optional category, Analytics and session recordings. Refuse is as easy as Accept: both buttons sit side by side and look the same, and continuing to browse without choosing is not consent. Your choice, accepted or refused, is kept for 6 months; then the banner asks again. The Cookie settings link in the footer reopens it, so you can change your mind at any time.
3. The cookies Suitra uses
All of them are strictly necessary. Accounts are handled by Suitra itself, on its own servers and database (with the open-source Better Auth software): no third-party sign-in script runs on its pages. A cookie name carries the __Secure-prefix when Suitra is served over HTTPS.
| Cookie | Set by | Purpose | Lifetime |
|---|---|---|---|
suitra.session_token__Secure-suitra.session_token | Suitra | Your signed-in session: a random token Suitra’s server looks up in its own database to open your workspace. HttpOnly and SameSite=Lax: page scripts cannot read it and other sites cannot use it. The __Secure- name is used over HTTPS. | 14 days, renewed while you use Suitra; deleted when you sign out or the device is signed out |
suitra.two_factor | Suitra (when two-factor authentication is on) | Between your password and your authenticator code: which sign-in waits for its second step. Signed, HttpOnly. | 10 minutes |
suitra.passkey | Suitra (when you use a passkey) | The one-time challenge of a passkey sign-in or registration. Signed, HttpOnly. | A few minutes |
suitra_sandbox | Suitra | Only if you open the public demo: remembers which demo sandbox is yours. It holds a random identifier that only our server can read (httpOnly). | 24 hours; deleted when you leave the demo |
4. Local storage
cleverai_consent_v1(local storage, set by Suitra): your answer to the cookie banner and when you gave it, so the banner does not reappear on every page. It contains no identifier and is never sent to our servers. Kept 6 months. Strictly necessary.- Only if you accept Analytics and session recordings: PostHog stores entries in local storage and session storage whose names start with
ph_or__ph_: a random device identifier, a session identifier and a record of your consent. They are deleted when you withdraw your consent or when your choice expires.
5. Product analytics and session recordings (PostHog)
To understand how Suitra is used and improve it, we use PostHog, a product analytics service operated by PostHog, Inc. and hosted on its EU Cloud in Frankfurt, Germany. PostHog acts as our processor (GDPR Art. 28). It works in two modes:
- Before you choose, or if you refuse: cookieless mode. PostHog receives the pages you view and a few named product events, such as a first quotation sent, a report opened or a view switched, never their content, amounts or names. There is no automatic click capture, no heatmap and no recording. Nothing is stored on or read from your device: no cookie, no local or session storage, no identifier. To count visitors, PostHog computes an anonymous value on its servers from your IP address, your browser's user agent and a salt that changes every day, so visits cannot be linked from one day to the next. As nothing touches your device, this needs no consent; it rests on our legitimate interest in measuring how Suitra is used (GDPR Art. 6(1)(f)).
- If you accept. PostHog also records sessions (a replay of the page layout, mouse movements, scrolling and clicks), builds heatmaps, captures clicks, including repeated “rage” clicks, and links events into funnels. If you are signed in, you are identified only by a keyed hash (HMAC-SHA256) of your account identifier: your name and email address are never sent. Legal basis: your consent (GDPR Art. 6(1)(a); article 82 of the loi Informatique et Libertés).
Safeguards that apply in both modes:
- Your workspace stays unreadable. Inside the signed-in app, recordings mask all text and every form field, so they keep only the layout and the clicks, never your customers' names, amounts or emails; images loaded from other sites are left out. On the public pages and the demo, which holds only sample data, every form field is masked.
- Clean addresses: record identifiers in page addresses are replaced with
[id], and query strings are removed except campaign parameters (utm_*,ref,from). - Never recorded: the print pages of quotations and invoices, member settings, the Account & data page, exports and API routes. PostHog never loads on a team's public support form (
/support), which its customers fill in. - Retention: session recordings are deleted after 30 days, events after 13 months.
6. What Suitra does not use
- No Google Analytics and no Vercel Web Analytics.
- No advertising, retargeting or social-media cookies or pixels.
- No third-party fonts loaded from other servers: the Inter typeface is served by Suitra itself.
7. Your choices
Accept or refuse session recordings in the banner, and change your mind at any time with the Cookie settings link in the footer: withdrawing stops the recordings and deletes PostHog's entries from your browser. You can also delete or block cookies and browser storage in your browser's settings. Blocking Suitra's session cookie stops you from signing in, and blocking suitra_sandbox stops the demo from working; refusing or blocking PostHog changes nothing in how Suitra works.
8. More information
For how Suitra handles personal data, see the Privacy Policy. For your rights in France, see the CNIL's guidance on cookies. Questions: privacy@cleverai.ai.