ZIAZI public document
ZIAZI Cookie Policy
What cookies and similar technologies ZIAZI uses on its web surface.
1. About this policy
This policy describes how ZIAZI uses cookies and similar technologies on the website, on the legal pages, and in the web app.
The operator is ZIAZI DIGITAL GROUP S.R.L, IDNO 1026023041407, with its registered office at MD-6801, str. Nucarilor 53, or. Ialoveni, Republic of Moldova.
This policy is written in relation to the applicable legal framework in the Republic of Moldova, including the relevant rules on data protection and electronic communications.
2. What cookies and similar technologies are
Cookies are small files stored in the browser to allow a web surface to work or to remember certain preferences.
Besides cookies, ZIAZI may also use similar technologies such as:
localStorage;sessionStorage;- technical session tokens;
- other local mechanisms needed for the interface to function.
3. What ZIAZI uses in the current configuration
In the current public configuration, ZIAZI uses:
- cookies and tokens that are strictly necessary for session handling, authentication, security, and protection of technical requests;
- local technical preferences, including the selected language or the state of certain UI elements;
- Google Tag Manager as the shared layer that loads technical analytics and technical tags published in the active container.
- Meta Pixel as a measurement tag for visits, campaign attribution, and basic conversions on the web surfaces where it is mounted.
According to the current implementation, Google Tag Manager and Meta Pixel may be loaded on:
- specific web surfaces where tracking is explicitly enabled;
- the legal pages;
- the public share page of a worker offer;
- the web app shell.
The main public landing page runs without loading these third-party scripts.
ZIAZI also declares the use of a campaign-measurement tag through Meta Pixel. This does not mean that every profiling mechanism or every personalized ad feature is active at all times.
4. Categories of technologies used
| Category | Main purpose | Example uses | Strictly necessary? |
|---|---|---|---|
| Session and authentication | keeping the session and authentication state | active session, access protection | Yes |
| Security and technical protection | protecting forms and reducing abuse | CSRF, abuse prevention, session checks | Yes |
| Technical preferences and language | keeping the chosen language and local UI state | selected language, hiding the public notice | Usually yes, in the context of the active function |
| Technical analytics | understanding basic traffic and general technical signals | Google Tag Manager and the analytics services published through the active container | No, not usually strictly necessary |
| Public campaign measurement | attributing visits and basic campaign conversions | Meta Pixel | No, not usually strictly necessary |
The table above describes the real categories used in the product and should not be read as an exhaustive list of internal technical names.
5. Google Tag Manager, technical analytics, and Meta Pixel
ZIAZI uses Google Tag Manager as the shared layer that loads technical analytics and other technical tags published in the active container.
ZIAZI also uses Meta Pixel as a campaign-measurement tag for visit attribution and basic conversions associated with Meta platforms.
These mechanisms may collect signals about traffic, page loading, visits, and basic conversions on the web surfaces where they are mounted.
These tags are not strictly necessary for the basic functioning of the website.
6. The current information and control model
ZIAZI currently shows a public cookie notice with an informational role.
In the current configuration:
- closing the notice may store locally only the preference not to show the notice again;
- the public notice does not function as a granular accept/reject panel by category;
- separate consent settings by category are not yet exposed through a public dedicated manager.
The user can control most cookies and similar technologies from the settings of their own browser.
Blocking strictly necessary cookies may lead to incorrect behavior in authentication or other basic functions.
7. Third-party providers
In the current configuration, the relevant third-party providers for loading technical analytics and campaign measurement are Google Tag Manager and Meta Pixel, together with any services published through the active container or loaded directly on the approved web surfaces.
Besides those providers, the platform infrastructure may involve providers for hosting, content delivery, security, email, or other operational services.
8. How you can manage cookies
The user can:
- review cookies in the browser;
- delete existing cookies;
- block certain cookies;
- block all cookies;
- delete locally stored data such as
localStoragefrom the browser.
The exact instructions depend on the browser and device being used.
9. Link to the Privacy Policy
The use of cookies and similar technologies may involve processing technical data such as:
- IP address;
- user agent;
- session identifiers;
- language preference;
- local interface state;
- data about technical requests and navigation.
For details about the processing of personal data and the user rights, please consult the ZIAZI Privacy Policy.
10. Policy changes
We may update this policy to reflect technical, operational, or legal changes, including the introduction of a new consent model or a change of relevant technical providers.
11. Contact
For questions about cookies or about this policy, you can contact us at:
- ZIAZI DIGITAL GROUP S.R.L
- IDNO: 1026023041407
- Registered office: MD-6801, str. Nucarilor 53, or. Ialoveni, Republic of Moldova
- E-mail: support@ziazi.app
- Website: ziazi.app