Cookies policy

1. What this page covers

Cookies are small files a server or script may store in your browser. The browser may also keep data in localStorage. This page describes what collect.md actually does — not cookie categories that are not in use.

2. Public site: what is not used

On public pages (home, services, articles, contact, and similar) we do not install Google Analytics, GTM or Meta Pixel, and we do not set analytics cookies. Language is not a functional cookie: it is the URL prefix (/ro, /ru, /en).

3. Notice preference in local storage

The public notice banner may write localStorage key collect_cookies (values such as accepted, rejected or acknowledged) so the message is not shown again. That is not an HTTP cookie and it does not turn analytics on. Dismissing the notice does not disable tracking that does not exist; it only stores that the notice is hidden.

4. Fonts

Site fonts (Inter, Fraunces, Instrument Sans) are self-hosted in the build and are not loaded from fonts.googleapis.com / fonts.gstatic.com.

5. Google Map on the contact page

The Maps iframe (maps.google.com) loads automatically on the contact page. After it loads, Google may set third-party cookies in its own context.

6. Login and portal

After you sign in, the app may store a technical token in localStorage (including base44_access_token). Session cookies from the login provider were not fully verified in this environment. That storage is not part of ordinary public browsing.

7. Browser controls

You can clear localStorage and cookies in your browser settings. Blocking third-party content may hide the map on the contact page.

8. Contact

Questions: info@collect.md. See also the privacy policy.

Privacy policy