ePrivacy · TTDSG · GDPR

The cookies we actually use.

We rely mainly on browser storage (localStorage) for sign-in and your consent record. Google Analytics loads only if you opt in. No ad pixels, no support-chat widgets on this product.

Last reviewed: 12 March 2026 Essential storage + optional analytics (consent-gated) Zero advertising trackers

01 Your preferences

Plain English
Toggle what you're OK with. Sign-in tokens and your consent record stay available so the Service can work; analytics stays off until you allow it. Click Save and we update right away (same choices as the cookie banner in the app).
Cookie preferences Last saved · 4 minutes ago · this browser only
Strictly necessary Required
After you sign in, session JWTs are stored in localStorage (accessToken, refreshToken) so the app can call our API. Your consent record is stored as JSON in localStorage under cookie_consent so we do not nag you on every page load. The Next.js app may set minimal first-party cookies where the framework or hosting requires them for routing or security.
localStorage + any host cookies·first-party
Functional
When enabled, we may store optional UI state in localStorage (for example your last selected project, draft forms in the dashboard, or similar convenience keys). This category matches the Functional toggle in our cookie banner.
localStorage·until you clear it·first-party
Analytics
Google Analytics 4 (measurement ID G-5PJP8S8KJX) via gtag.js, loaded only after you opt in on this site or in the app. Google may set _ga / _ga_* cookies. See Google's privacy policy and our Privacy Policy.
Google cookies when on·per Google defaults·third-party provider

02 What is a cookie?

A cookie is a small text file a website asks your browser to store. The next time you visit, the browser sends the file back, so the site can recognize you (still logged in), remember a setting (dark mode), or count visits. The same applies to similar technologies, local storage, session storage, pixels, which we treat under this policy as "cookies".

03 Cookies we use

Name / technologyPurpose · Notes
accessToken, refreshToken (localStorage) Required for signed-in use. JWT credentials issued by our API after authentication. Removed when you sign out or clear site data.
cookie_consent (localStorage) Required for consent UX. JSON with essential, analytics, functionality, and accepted_at. Read by the banner, this page, and GoogleAnalytics to know whether GA may run.
Other localStorage keys (e.g. project selection, drafts) Functional (optional). Only when the Functional toggle is on; used for convenience inside the product.
_ga, _ga_* (cookies, Google) Analytics (optional). Set by Google Analytics when you have opted in. Not placed if you reject analytics or use Essential only.

We do not use advertising or retargeting pixels. We do not embed a third-party support chat that sets cookies on this site.

04 Third-party cookies

The only third-party analytics technology we use on the marketing site and signed-in shell is Google Analytics, and only when you have turned analytics on. Google's tags may set cookies and send events according to Google's cookie information.

Stripe is used for billing; when you go through checkout, Stripe may set its own cookies under its privacy policy. Other sub-processors (hosting, email, AI inference) are listed in our Privacy Policy; they are not loaded for basic page views solely to profile you for ads.

06 Change your mind

Three ways to revoke or change consent:

  • Use the toggles at the top of this page.
  • Click "Cookie settings" in the footer of any page.
  • Clear cookies in your browser settings, the banner will reappear on next visit.

Most browsers also let you block all cookies globally. Note that doing so will sign you out of the Service and disable functional preferences.

07 Contact

Data Protection Officer
[email protected] · For any cookie or privacy question.