Official documents
Cookies
1. Policy scope
The policy applies to the domains autocare.md, autobuse.md and autobuze.md, as well as the web pages associated with Autocare. The mobile application mainly uses device storage and notification identifiers, not all web cookies described below.
2. What a cookie is
A cookie is a small text file saved by the browser. Cookies may be "session" or persistent, may originate from the visited domain or from an external provider, and may serve authentication, security, preferences, or usage measurement.
We also use similar technologies, such as localStorage and mobile app identifiers. These are not cookies, but they may store information on the device and are described separately.
3. How consent works
- the banner allows accepting all categories, accepting only the necessary ones, or choosing optional categories;
- the choice is stored in first-party cookies for one year;
- Google Consent Mode starts with analytics_storage, ad_storage, ad_user_data and ad_personalization set to "denied";
- Analytics storage is enabled only if you choose the analytics category;
- as of this version, there are no active cookie categories for behavioral advertising or social network integration.
4. Confirmed web cookies and identifiers
| Name | Provider | Category/purpose | Duration | Requires optional choice? |
|---|---|---|---|---|
| ncc_c | Autocare | Confirms that the cookie choice has been saved. | 1 year | No; it is required to remember the choice. |
| ncc_e | Autocare | Stores the list of categories allowed by the user. | 1 year | No; the content reflects the user's choice. |
| user_hub | Autocare | Remembers the hub/region relevant for displaying content and routes. | 30 days | No, when it is necessary for the requested function. |
| Session/authentication cookie (the name may vary by domain) | Autocare | Session, security, authentication and prevention of unauthorized requests. | Session or configured technical period; it is deleted/invalidated on expiration or logout, as applicable. | No. |
| _ga | Google Analytics | Distinguishes users for statistical analysis. | By default up to 2 years; the browser may apply a shorter limit. | Yes — analytics category. |
| _ga_<container-id> | Google Analytics | Preserves session state for the GA4 property. | By default up to 2 years; the browser may apply a shorter limit. | Yes — analytics category. |
| reCAPTCHA cookies/identifiers, if set | Security and prevention of abusive automated requests when sending the OTP code. | Set by Google and the browser; may vary. | Treated as security for the requested OTP function. | |
| Google Maps cookies/identifiers, if set | Displaying maps, stops and routes when the user opens the function. | Set by Google and the browser; may vary. | External functionality activated when using the map. |
Google durations represent the provider's published default values and may be shortened by the browser. The list is updated if the implementation or active services change.
5. Local storage and similar technologies
| Type of information | Purpose examples | Duration |
|---|---|---|
| Site preferences | Language, theme, selected date, map center, hub and hiding certain messages. | Until replacement, user deletion, or browser reset. |
| Searches and routes | Recent searches, favorite routes and selections used to simplify a future search. | Until deletion or the internal list limit. |
| Cart and flow recovery | Temporary preservation of the selection and resumption of checkout. | Until completion, replacement, or deletion. |
| Mobile app authentication | Tokens needed to maintain the session and refresh it, protected through the mechanisms available on the device. | Until logout, revocation, expiration or deletion of the app/its data. |
| Mobile notifications | FCM/APNs token associated with the device for transactional messages and requested alerts. | Until revocation, replacement, disabling or technical clearing. |
6. Google Analytics
Google Analytics helps us understand site usage and flow performance, including interactions with the offer and checkout. Analytics storage is allowed only after consent. Data may include the page, event, time, browser/device information and identifiers generated by Analytics. We do not intentionally send the passenger's name, phone number, email or card details as Analytics parameters.
7. reCAPTCHA and Google Maps
reCAPTCHA v3 is used to protect OTP code requests against bots and fraud. Google Maps is loaded in the functions that display stops or routes. When using them, the browser communicates directly with Google, which may receive technical data according to its own policies. If you do not want the map loaded, do not open the component and use the available text address.
8. How to change or withdraw the choice
You can refuse optional cookies in the banner. To reset the choice later, delete the ncc_c and ncc_e cookies (or all site data) from the browser settings and reload the page; the banner will ask for the choice again. You can also block cookies in the browser, but some necessary functions, authentication or choice storage may stop working.
Withdrawing consent stops future optional storage. To delete cookies already present, the browser settings must also be used.
9. Updating the list
We periodically review the active services and update this policy before activating a new non-essential tool. The existence in the code of an unloaded file or package is not sufficient to declare the service active. Services not listed in this policy are not included in the active services list of this version.
10. Contact
For questions regarding cookies or personal data: [email protected]. Details about the other processing operations are in Privacy Policy.
