A cookie is a small text record a website asks a browser to store and return on later requests. Local storage keeps a similar value inside the browser. Pixels, tags and device identifiers can also write or read information without being called cookies. Each can be first-party, belonging to this domain, or third-party, set by another organization.

These are the only records this site writes itself. Each is first-party, holds a preference value rather than a profile, and is not sent to an advertising or analytics network. Providers the publisher configures may add their own.

When the publisher activates analytics, an advertising network, an embedded player or a spam filter, that provider — not this site — decides what it stores and for how long. Names and lifetimes change whenever a product is updated, so this page describes categories rather than a list that would soon be inaccurate.

Any such provider can also read what a browser sends with an ordinary request: the page address, the referring page, an Internet Protocol address and device characteristics. Depending on the technology and the jurisdiction, that may be described as targeted advertising, cross-context behavioral advertising, sharing or a sale.

1. You decide

   Where the notice is enabled, “Reject optional” and “Accept optional” sit side by side. Neither is hidden behind an extra menu and neither is preselected.

2. The decision is stored

   Your selection is written to the r34c8_consent cookie and the local-storage records in section 2, so the notice stays out of the way on later pages.

3. The signal is broadcast

   This site announces the recorded value through a browser event and a small JavaScript interface, so a consent-aware tag can read the current choice instead of assuming one.

4. Connected scripts respond

   Whether a particular third-party tag acts on that signal depends on how the publisher connected it. A tag that ignores the choice should be reconfigured or removed.

There is more than one way to withdraw a choice already made:

• Reopen the notice with the review control near the top of this page, where that control is shown, and pick the other option; the new decision replaces the earlier one.
• Clear this site’s data in your browser, which deletes the stored record and returns the site to its unanswered state.
• Block storage at the browser level, as described below, which applies to whatever any site requests.
• Use a provider’s own opt-out when a specific advertising or measurement company is involved.

Withdrawal applies to future optional processing. It does not undo processing that was lawful beforehand, and it does not switch off strictly necessary storage, which may continue to deliver a requested feature, remember the refusal or protect the service.

Every major browser can list stored cookies, delete them for one site, block third-party cookies or clear site data on exit. Menu wording differs between versions, so the routes below describe where the controls usually sit rather than exact clicks.

Advertising organizations also publish their own controls, which apply to their services whether or not those services run here:

• Google My Ad Center for Google ad personalization, and the Google Analytics opt-out add-on for Google Analytics measurement.
• Digital Advertising Alliance and Network Advertising Initiative opt-out pages for participating companies in the United States.
• Your Online Choices for participating companies across Europe.

Those tools store an opt-out record of their own, so clearing all cookies can erase it. Some browsers and extensions also send an automated signal such as Global Privacy Control; where applicable law treats that signal as a valid opt-out request, the services receiving it are expected to act on it.

A cookie policy is only useful while it matches the live site. We scan for active storage, compare it against the table and categories above, remove tools that no longer serve a purpose, and revise this page when a service is added, replaced or reconfigured.

The “Last reviewed” date at the top is refreshed whenever these policy pages are rebuilt. Where a new purpose goes beyond what an earlier choice covered, a fresh choice should be requested rather than assumed.

If a cookie or script appears that is not explained here, send its name, the page where you saw it and the provider domain to info@amomana.com. That detail makes the technology far easier to identify, document or switch off. Broader information about personal data is in the Privacy Policy.