Privacy controls
Effective 28 September 2026. This policy explains storage used by ADJODO and the choices available to website visitors. It should be read with our Privacy Policy.
These support authentication, account security, language and interface preferences, consent records, and support conversations that you request. Disabling them in your browser may prevent login or other requested features from working.
Examples and retention: ADJODO session authentication (browser session), public support-chat visitor reference (up to 30 days), and cookie-choice record (up to 180 days).
When you consent, Google Tag Manager may load analytics tags that help us understand visits, page usage and technical performance. ADJODO does not load GTM for analytics before this choice is granted.
Examples and retention: Identifiers and retention depend on the analytics tags enabled in our GTM container and must follow the selected consent state.
When you consent, advertising measurement or personalization tags may be enabled. Ad storage, ad-user-data and ad-personalization consent remain denied when this category is off.
Examples and retention: Campaign measurement tags configured through Google Tag Manager.
Use the “Cookie settings” control at the bottom of any page to change your optional choices. A withdrawal updates Google consent signals immediately and prevents optional tags from loading on future page views. You can also clear site data in your browser.
Questions or privacy requests can be submitted through Contact. Never include passwords, OTP codes or full payment credentials.
Legal notice: this operational policy describes the current implementation. Final jurisdiction-specific wording and retention requirements should be reviewed by qualified legal counsel.
Cookie choices are recorded for the browser in which you make them. Visiting through another device, using a separate browser profile or clearing site data can mean that the website asks for a choice again. This is why a preference seen on a laptop may not automatically appear on a phone.
Necessary storage supports requested functions such as account access and the preference record itself. Optional categories concern additional measurement or advertising behavior. Read the category descriptions above to understand the distinction before changing browser-wide controls that could affect ordinary sign-in behavior.
The settings control provides separate choices for optional analytics and marketing categories. Accepting one should not be interpreted as an obligation to accept the other. A useful way to decide is to consider the purpose of each category: aggregate usage analysis answers a different question from advertising measurement or personalization.
The implementation uses the selected consent state when deciding whether optional tags may load. A tag's precise identifiers and duration depend on the enabled configuration, so this policy does not substitute a single invented lifetime for every possible external tag. The examples describe categories rather than an exhaustive promise about third-party naming.
Updating the website preference changes the consent state used for subsequent behavior. Clearing site data through the browser removes stored values and can also remove information needed for requested features. For example, losing a saved visitor reference can affect continuity in a support conversation.
Decide which action matches your intention instead of using both interchangeably. If you withdraw an optional choice, use the settings control and then revisit the relevant page to observe the new preference. Existing browser information and future tag loading should be considered separately when checking what happened.
If you notice an unexpected preference or storage item, record the page, browser and choice you made. Indicate whether the visit was in a private window or a different profile. That context is more useful than a screenshot of unrelated account data.
A technical inquiry can be sent through the contact page with the specific concern and the steps needed to reproduce it. Do not send authentication values or full payment credentials as evidence. Questions about a named third-party tag may require checking its current configuration in addition to the website's consent record.
This page concerns browser storage and optional tag choices. The privacy policy describes broader handling of information, while the terms explain conditions for using the service. Reading the documents together helps distinguish a preference control from an account or data request.
If your concern is about a submitted form or a support message, describe that concern directly rather than assuming a cookie change will remove the record. Keep any request specific enough for the team to identify the relevant process. The contact route provides a practical starting point for clarifying which control or request fits the situation.