# Cookie and Similar Technologies Notice

**Version:** [VERSION]  
**Effective date:** [EFFECTIVE_DATE]

## 1. Scope

This notice explains how [COMPANY_NAME] uses cookies, pixels, SDKs, local
storage, device identifiers, and similar technologies on [DOMAIN] and the
following products or applications:

[[REVIEW: LIST THE WEBSITES, SUBDOMAINS, APPS, EMBEDS, AND EMAIL TECHNOLOGIES IN SCOPE]]

## 2. Actual Technology Inventory

[COOKIE_INVENTORY_TABLE]

For each technology, verify its exact name, provider, purpose, data collected,
first- or third-party status, lifespan, domain/path, trigger, and whether it is
blocked until the required choice is obtained. Include dynamically created and
server-side tracking where relevant.

Do not call a technology “strictly necessary” merely because it is useful to the
business. Document the legal exemption and technical necessity for the service
requested by the user.

## 3. Purposes and Categories

Explain only categories actually used:

- **Strictly necessary:** technology required to deliver a service explicitly
  requested by the user, maintain security, or preserve a requested setting,
  where the applicable law provides an exemption.
- **Preferences/functionality:** optional personalization or convenience.
- **Analytics/performance:** measurement, diagnostics, experimentation, or
  product analysis.
- **Advertising/targeting:** advertising selection, measurement, profiling, or
  cross-context behavioral advertising.
- **Other:** describe the specific purpose rather than forcing it into an
  inaccurate category.

[[REVIEW: MAP EACH INVENTORY ITEM TO ITS VERIFIED PURPOSE, LEGAL CONDITION, AND CONSENT/OPT-OUT BEHAVIOR]]

## 4. Your Choices

Cookie and privacy settings: [COOKIE_SETTINGS_URL]

Describe the deployed choice flow accurately:

[[REVIEW: EXPLAIN WHICH TECHNOLOGIES ARE OFF BY DEFAULT, HOW USERS ACCEPT OR REJECT BY PURPOSE, HOW THE CHOICE IS STORED, HOW OFTEN IT IS RENEWED, AND HOW TO WITHDRAW OR CHANGE IT]]

Where prior consent is required, nonessential technologies must remain blocked
until a valid affirmative choice. Rejecting should be as easy and prominent as
accepting. Withdrawal must take effect for future processing and propagate to
the relevant vendors.

Browser controls may supplement but should not replace an in-product choice
mechanism when the law requires one. Browser deletion may also remove the stored
preference and cause the banner to reappear.

## 5. Opt-Out Preference Signals

[[REVIEW: EXPLAIN WHETHER AND HOW THE SERVICE PROCESSES GLOBAL PRIVACY CONTROL OR OTHER LEGALLY RECOGNIZED OPT-OUT PREFERENCE SIGNALS. DO NOT CLAIM SUPPORT UNTIL IT HAS BEEN TESTED END TO END]]

## 6. Vendors and Cross-Site Processing

[VENDOR_TABLE]

Link to current vendor privacy information and explain each vendor's role. A
vendor contract or “service provider” label does not by itself determine whether
processing is a sale, sharing, joint controllership, or exempt processing.

## 7. Email and Mobile Technologies

[[REVIEW: DISCLOSE EMAIL PIXELS/LINK TRACKING, MOBILE SDKs, DEVICE IDENTIFIERS, APP PERMISSIONS, AND PLATFORM PRIVACY CHOICES IF USED; OTHERWISE REMOVE THIS SECTION]]

## 8. Consequences of a Choice

Explain any genuine feature impact of disabling optional technology. Do not
suggest that core service access will fail unless that is technically true and
lawful.

[[REVIEW: DESCRIBE VERIFIED FEATURE EFFECTS BY CATEGORY]]

## 9. Retention

[RETENTION_SCHEDULE]

The inventory's lifespan and the server-side retention of data derived from a
technology are different concepts. State both where relevant.

## 10. Updates

Explain how the inventory is monitored, how material changes trigger renewed
choice or notice, and how the version history is maintained.

[[REVIEW: INSERT THE ACTUAL COOKIE-AUDIT AND CHANGE-NOTICE PROCESS]]

## 11. Contact

- Privacy/legal email: [CONTACT_EMAIL]
- Postal address: [COMPANY_ADDRESS]
- Privacy notice: [DOMAIN]/privacy
- Cookie settings: [COOKIE_SETTINGS_URL]

[[REVIEW: ADD JURISDICTION-SPECIFIC COMPLAINT OR REGULATOR INFORMATION IF REQUIRED]]