Cookies
Cookies and browser storage, clearly explained.
This notice explains the necessary cookies used by the WordPress site, the optional Google Analytics controls now active for testing, and the separate browser storage used by the Addienator application.
Draft notice with replace-before-launch fields
This notice is a construction draft. The service operator is [[REPLACE BEFORE LAUNCH: FINAL LEGAL BUSINESS NAME]], with the postal address [[REPLACE BEFORE LAUNCH: FINAL LEGAL BUSINESS POSTAL ADDRESS]]. These fields and the final cookie inventory require legal review before launch.
Current website storage
Necessary cookies and optional measurement have separate controls
Necessary website functions remain available. Analytics cookies require an explicit visitor choice and can be withdrawn later.
Necessary cookies
The live WordPress site uses necessary cookies when a visitor signs in or requests account, membership, security, form, or other protected functionality. These cookies support the requested action and are not used for advertising or remarketing.
Google Analytics after consent
Site Kit places the Google Analytics tag. Analytics cookies remain denied until a visitor chooses Accept all cookies. Site Kit uses advanced Google Consent Mode, so Google may receive cookieless consent signals before a visitor makes a choice. These signals are different from Analytics cookies and do not make advertising storage or personalization active.
No marketing trackers
Ads, remarketing, and other marketing trackers are not authorized for launch. If the approved website configuration changes later, this notice and the consent controls must be reviewed before the change is treated as active.
Accept or reject optional categories
The consent interface provides Accept all cookies, Necessary only, and Choose settings controls. Necessary functions stay available when optional Analytics is rejected.
Change your choices later
Privacy choices in the footer reopens the consent interface so a visitor can review, change, or withdraw a previous choice.
Site Kit and Complianz have separate jobs
Site Kit owns the Google tag and Google Consent Mode. Complianz and the WordPress Consent API provide the visitor-facing banner, category controls, and withdrawal interface. Complianz does not add a second Analytics tag or a second Google Consent Mode implementation.
Separate browser storage
Application storage is not ordinary website-cookie storage
The Addienator application uses browser storage for active project work. The Privacy and Security pages explain how that storage differs from website cookies.
Session storage
Active project state and a direct-plan Gemini API key use browser session storage. The key is not saved in an .addie project file.
IndexedDB
Original PDFs and prepared source artifacts use IndexedDB in the browser profile. Clearing browser data can remove that local project material.
Saved project files
An .addie file may contain project content, original PDFs, and prepared source material. It does not contain credentials and is not encrypted. Store and share it according to the sensitivity of its contents.
The launch cookie inventory still requires final review
The active consent manager is Complianz, integrated with the WordPress Consent API and Site Kit. Google Analytics is the only optional statistics service configured. Exact cookie names, durations, the Analytics retention setting, and the complete necessary-cookie inventory still require a final scan and legal review. The consent behaviour must also pass anonymous English (United States), English (Canada), and French (Canada) testing before launch.
Read the complete information-handling boundary
The Privacy notice covers accounts, forms, project storage, and AI routes. Use the working Contact and Support form if you have a question.
