Cookie policy
Last updated: April 2026
We use a small set of strictly-necessary cookies. None of them tracks you or sells anything — so the Site shows no cookie-consent banner.
A cookie is a tiny file your browser stores on behalf of a website. Because every cookie we set is strictly necessary to deliver a service you request, prior consent isn't required under art. 22.2 of Spain's LSSI-CE — we only need to inform you, which this page does. We classify ours by purpose and lifetime below.
| Name | Purpose | Duration | Type |
|---|---|---|---|
| session | Keeps you logged in. Session · Strictly necessary | Session | Strictly necessary |
| refresh_token | Lets us re-issue your access token without asking you to log in again. 30 days · Strictly necessary | 30 days | Strictly necessary |
| base_app.guest | Identifies your browser so guest edits and saved files survive a refresh. 30 days · Strictly necessary | 30 days | Strictly necessary |
| i18n_locale | Remembers your language choice. 1 year · Technical / functional | 1 year | Technical / functional |
Local storage (not cookies)
Beyond cookies, the editor uses your browser's local storage and IndexedDB to work: your in-progress documents and uploaded fonts stay on your device — never uploaded unless you save them to your cloud library — and, if you arrive from an ad, the click identifier (gclid) is kept for up to 90 days to attribute the sign-up. This data lives in your browser; clearing the site's data removes it.
Managing cookies
All major browsers let you delete cookies and block them per site. Strictly-necessary cookies can't be turned off without breaking the editor — we don't track you with them, they only carry your session.
Third-party cookies
We run no advertising or analytics that drop third-party cookies. Our website analytics use a self-hosted Plausible instance whose snippet is cookieless and sets nothing on your device. Ad-campaign conversions are reported to Google Ads server-to-server via its API, with no ad tags or pixels on the page. Stripe (payments) and Google sign-in set their own cookies on their own domains when you use those features; those policies live with them.