What they are
A cookie is a small file the site stores in your browser and the browser returns with every request. Local storage is a similar space that only the site itself reads and that never travels to the server. We use both for what is described below, and for nothing else.
Local storage
The application and these pages keep data in your browser's local storage, under the reitur prefix. Preferences: the light or dark theme, the language, whether you turned analytics off, the active client, the projects view, the library filters, the sections chosen for the PDF and the render settings. Work: a copy of the project you are editing, the client's asset library, saves left pending while offline, the projects you keep only in this browser, the view and form each tab had open so that a reload takes you back to the same place and, for a day, the form you were filling in when a feature asked for a plan. None of it is sent to anyone, and clearing the site's data removes it; whatever you had not sent to the server is lost with it.
Third-party services
- Network and security. A service in front of the site protects it. It may store a cookie of its own to tell automated traffic apart, and on the create account, resend confirmation and password recovery forms it loads a check that does the same without asking you to solve anything.
- Payments. Payment and the billing portal happen on the payment processor's pages; its cookies are created there, not on this site.
- Maps. The venue view requests map tiles and satellite imagery from the map providers directly from your browser. They create no cookies on this site, but they receive your IP address while the map is open.
- Errors. A monitoring service receives the application error reports, without cookies or personal data.
- Web analytics. Only on these public pages, unless you turn it off: the analytics service loads its script from its own server, creates the cookies in the table and receives which pages you visit, what you open on them (tools, examples, questions), where you came from, your IP address, browser and device. If you then create an account, our server also tells it about some steps (creating and confirming the account, signing in, your first project, AI requests, sharing and payments) together with the random identifier in its cookie, without your name or e-mail. It is set up without advertising signals or ad personalization.
Apart from analytics, these public pages load no third-party resources: fonts and images are served from this same site. The application and the account pages load no analytics: the steps above are reported by our server.
How to control them
You can delete or block cookies and local storage from your browser settings; if you block the essential cookies you will not be able to sign in. You can turn analytics off at any time with “Cookie preferences” at the foot of every page, or with this button. Once it is off we stop measuring and delete its cookies.
Changes
This policy is updated when the cookies we use change; the date at the top shows the latest version. Questions: [email protected].