Cookie policy
Last updated: 8 September 2026
This page states exactly what is stored in your browser when you use AutoGarage.pro, why, and for how long. The table below is complete.
What a cookie is
A cookie is a small file the site saves in your browser and reads on later visits. Every cookie below is set on our own domain, not on another company's. One of them, `_dd_s`, belongs to our technical monitoring tool and exists only inside the application, after you sign in.
The cookies we use
| Name | Purpose | Duration | When it is set |
|---|---|---|---|
| asvc-consentStrictly necessary | Remembers your cookie choice so we do not ask again on every page. It holds only the accepted category, the version of the question and the moment of the choice. No identifier and no personal data. | 1 year | Only when you press "Accept all" or "Necessary only". |
| NEXT_LOCALEStrictly necessary | Remembers the language you want the interface in. | 1 year | Only when you change the language from a screen in the app. |
| sb-<project-ref>-auth-tokenStrictly necessary | Keeps your account signed in. It is issued by Supabase Auth, our database and authentication provider, on our own domain. It is split into chunks (.0, .1) when it grows too long. | For the session, until you sign out | Only after you sign in to the application. |
| _dd_sAnalytics | Ties together the technical events of one working session (errors, load times and, for a small share of sessions, a screen recording with all text masked) so we can diagnose a fault. It is set by our monitoring tool, Datadog, on our own domain. It contains no name and is not used for advertising. | 15 minutes, extended while you keep working; a session ends after at most 4 hours | ONLY inside the workshop application, once you have signed in: on your account screens and at the initial setup step. Never on the public pages (the landing page, a workshop's public page, order tracking, unsubscribe) and never on the sign-in or sign-up pages, because the tool does not load there at all. |
| referral_codeStrictly necessary | Remembers the code of the workshop that recommended this application, so that your discount is applied when you create your account. It holds only the referral code. No identifier and no personal data. | 90 days | Only when you yourself open a referral link (a /r/code address). Never on a page you merely land on. |
Analytics and marketing cookies
Marketing cookies we use nowhere: there is no advertising pixel, no heatmap and no font loaded from someone else's server. For analytics we use one tool, Vercel Web Analytics, and only on the public pages. It SETS NO COOKIE — it saves nothing in your browser — and it does not load at all until you press "Accept all". If you choose "Necessary only" it never loads; and if you withdraw your consent later it immediately stops sending anything, with no need to reload the page. Its script is served from our own address, so your browser contacts no other company. The one other company your browser does contact is Cloudflare, for the bot check on the sign-in, sign-up, password-reset and resend-confirmation forms, and Cloudflare documents no cookie for that check. The only cookie in this policy that is not strictly necessary remains `_dd_s` in the table above, and it is set ONLY inside the application, after you sign in. A visitor who has not signed in never receives it.
Similar technologies
Inside the workshop application, after sign-in, we store your default invoice series locally in the browser so you do not retype it on every invoice. It stays on your device, never reaches us and is not used for tracking.
Inside your account
The cookie banner appears only on the public pages. In your account and in the admin panel we use cookies strictly necessary to perform the contract, namely the sign-in session and the language, and we do not ask for consent for those. Inside the workshop application (your account screens and the initial setup step) the `_dd_s` session cookie of our technical monitoring tool is added, on the basis of our legitimate interest in keeping the application working and diagnosable. It is set only after you have signed in, never on the public pages, and never on the sign-in or sign-up pages. In the screen recordings all text is masked, so your customers' data does not leave the application by that route.
How to change your choice
The button below reopens the cookie window. A new choice replaces the previous one immediately.
Your choice is remembered separately for each domain (autogarage.pro and autogarage.md), so if you visit both, you're asked again on the second one; the alternative would be sharing your identity across the two domains, which this product deliberately never does.
Deleting them in your browser
You can delete or block cookies at any time in your browser settings. If you block the strictly necessary ones, signing in and switching language will stop working.
Changes
If the cookies we use change, we update this page and ask for your consent again.
Contact
For any question about cookies or about your data, write to us at apolossrl@gmail.com.