Placeholder for layout testing only. This sample Cookie Notice is not legal advice and does not represent a completed cookie audit. Replace the sample table, bracketed fields, and descriptions with client-approved information from a final production scan before launch.
Effective date: [EFFECTIVE DATE]
Last updated: [LAST UPDATED DATE]
1. About This Notice
This sample Cookie Notice explains how [COMPANY LEGAL NAME] (“Company,” “we,” “us,” or “our”) may use cookies and similar technologies on the Disney Princess Experience website (the “Site”). It is intentionally long and includes a wide data table to test desktop and mobile layouts. The final version must be based on the technologies actually present in production, including anything added through WordPress, hosting, analytics, embedded media, ticketing, email, advertising, or consent-management tools.
2. Current Staging Configuration
The custom theme does not intentionally add analytics or advertising tags during this staging phase. The video area initially uses a locally hosted preview image; the Vimeo player is requested only after a visitor selects the play control. WordPress, the hosting provider, security systems, or an authenticated administrator session may still use technologies necessary to operate or protect the Site. A fresh scan should be performed in a logged-out browser after all production plugins and vendor integrations are finalized.
3. What Are Cookies and Similar Technologies?
A cookie is a small text file that a website asks a browser to store on a device. Cookies can help a website recognize a browser, maintain a session, remember a choice, or understand how a service is used. Some cookies expire when the browser closes, while persistent cookies remain until their stated expiration or until they are deleted.
Other technologies can serve related purposes. These may include pixels, tags, local storage, embedded scripts, software development kits, device identifiers, and server logs. In this notice, “cookies” is used as a convenient collective term unless a distinction is necessary.
4. Categories of Cookies
Strictly Necessary
These technologies support functions needed to provide a requested service, maintain security, route traffic, prevent abuse, remember privacy choices, or administer an authenticated WordPress session. Because the Site may not work correctly without them, they may not be subject to an opt-in choice in every jurisdiction.
Preferences and Functionality
These technologies may remember choices such as language, region, accessibility preferences, media settings, or form progress. If disabled, some personalized or convenience features may not function as intended.
Analytics and Performance
Analytics technologies may help measure visits, page performance, navigation patterns, errors, and aggregate audience interest. The final notice should identify each analytics provider, the information collected, retention period, configuration choices, and whether consent is required before activation.
Advertising and Social Media
Advertising or social-media technologies may be used to measure campaigns, limit repeated ads, create or use interest profiles, or enable sharing features. They can recognize a browser across different services. These technologies should remain disabled until any consent required by applicable law is obtained and the client has approved the associated vendors and disclosures.
5. First-Party and Third-Party Cookies
First-party cookies are set by the domain a visitor is using. Third-party cookies or comparable requests may be controlled by a separate provider whose content or service appears on the Site. A third party may process information under its own privacy notice. The final implementation should minimize unnecessary third-party requests and should load optional providers only in accordance with the visitor’s choice.
6. Sample Cookie Inventory
The entries below are fictional examples included to stress-test table styling. They are not a representation of the cookies currently deployed.
| Sample name | Sample provider | Category | Illustrative purpose | Illustrative duration |
|---|---|---|---|---|
| consent_preferences_example | [CONSENT PLATFORM] | Strictly necessary | Stores a visitor’s example cookie-category selections so the consent interface can honor them on later pages. | 6 months |
| security_session_example | [HOSTING OR SECURITY PROVIDER] | Strictly necessary | Supports traffic protection, rate limiting, and session integrity for the sample website. | Session |
| language_preference_example | [COMPANY] | Preferences | Remembers a visitor’s selected language or regional version when that feature is enabled. | 12 months |
| analytics_id_example | [ANALYTICS PROVIDER] | Analytics | Distinguishes browsers for aggregate usage measurement after the required consent choice. | 13 months |
| campaign_measurement_example | [ADVERTISING PROVIDER] | Advertising | Measures whether an approved campaign led to a visit or registration after consent. | 90 days |
| embedded_video_example | [VIDEO PROVIDER] | Functionality or analytics | May support playback, settings, security, or measurement after a visitor activates an embedded video. | Provider-defined |
7. Embedded Video
The Site may use Vimeo to provide video. The current design delays the Vimeo connection until the play control is selected. When a visitor activates the player, Vimeo may receive IP address, browser and device information, referring-page information, playback activity, or other data and may set or read cookies according to its configuration and policies. The final notice should link to the provider’s then-current privacy information and accurately describe the selected privacy-enhanced settings.
8. Consent and Preference Controls
Where required, the final Site should display a consent interface before non-essential cookies are used. The interface should provide balanced choices, explain the categories in plain language, and allow a visitor to accept, reject, or customize optional technologies. A visitor should be able to revisit the choice through a persistent “Cookie Settings” link or comparable control.
Withdrawing consent should be as easy as giving it. A changed choice should stop future optional processing associated with that browser, but it may not automatically delete information previously collected by a third party. The final process should explain any additional provider-specific opt-out or deletion step.
9. Browser and Device Controls
Most browsers allow users to view, block, or delete cookies through privacy or security settings. Instructions vary by browser and version. Blocking all cookies may prevent authentication, consent storage, video playback, or other functions from working. Device and operating-system settings may provide additional controls for advertising identifiers, tracking permissions, location, or app-level data.
10. Global Privacy Control and Do Not Track
Some browsers or extensions can send a Global Privacy Control (GPC) or “Do Not Track” signal. The final policy should explain how the production Site responds to legally recognized preference signals and whether the response applies only to the browser or device sending the signal. The Site should not claim to honor a signal until that behavior has been implemented and verified.
11. Data Retention
Cookie durations vary by purpose and provider. Some expire at the end of a session; others may persist to remember a choice or measure activity over time. Providers may also retain server-side records for different periods. The final inventory should identify meaningful retention information and should be reviewed whenever a tag, plugin, or vendor setting changes.
12. Updates to This Notice
This notice may be updated when technologies, providers, purposes, or legal requirements change. The “Last updated” date should be revised whenever a material change is published. A renewed consent request may be required when new purposes or providers are introduced.
13. Contact
Questions about the final cookie practices or preference controls may be directed to [PRIVACY EMAIL] or mailed to [COMPANY LEGAL NAME], Attn: Privacy Team, [MAILING ADDRESS], [CITY, STATE/PROVINCE, POSTAL CODE], [COUNTRY].
End of placeholder cookie copy. Complete a production scan and replace with client-approved language before launch.