Privacy
How information moves around Addienator.
This notice explains the current website, account, form, consent, browser-storage, and AI-routing boundaries. It remains a construction draft until the launch configuration and replace-before-launch legal fields receive final review.
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 complete notice require legal review before launch.
Website information
Information used to provide the website and member access
The public website and protected application use separate systems for accounts, inquiries, consent, and project work. Public checkout and the protected Addienator launcher are not open during construction.
Accounts and memberships
WordPress and MemberPress use account identifiers, email addresses, membership and subscription state, and technical information needed for sign-in, security, and protected access. No live payment gateway is connected. Final payment and account data flows must be documented against the launch configuration.
Contact and support requests
The Contact and Support form processes the information you enter and requires consent before submission. Sales requests route to sales. Support, Billing, Privacy, Accessibility, and General requests route to support. Form notifications use the existing transactional mail connection.
Form safeguards and provisional retention
The form warns against sending passwords, API keys, other credentials or secrets, payment-card information, and confidential source materials. It uses honeypot and no-entry spam controls and does not save the submitter’s IP address in the form entry. Entries provisionally move to WordPress Trash after 30 days. Trash is not permanent deletion, and 30 days is not final legal-retention approval.
Project work stays in your browser until needed
Active project state uses browser session storage, while original PDFs and prepared source artifacts use IndexedDB. An .addie file may contain project content and source files. It does not contain credentials and is not encrypted.
Standard and Pro use direct Gemini
You provide your own Google Gemini API key. Selected content and provider file operations go from your browser to Google. The key stays in browser session storage and is not saved in an .addie project file. Google service availability and usage charges are separate.
Enterprise uses the organization route
Enterprise AI traffic goes from the member’s browser through the organization-controlled proxy to its configured provider. The organization controls that provider account, credentials, logs, retention, and deletion. Addienator serves the launcher but is not in that AI request path.
Choices and controls
Privacy controls and remaining launch work
Consent and Analytics controls are active for testing. Payment, final retention, legal identity, and launch configuration details still require review before launch.
Cookies and consent
The site uses necessary cookies for security, sign-in, account access, membership checkout, and other functions a visitor requests. Complianz and the WordPress Consent API provide a worldwide opt-in interface. Site Kit places the Google Analytics tag and is the only system that controls Google Consent Mode. Analytics cookies remain denied until a visitor chooses Accept all cookies. Site Kit may send cookieless consent signals before that choice. Advertising storage, advertising personalization, Ads, remarketing, and other marketing trackers remain denied or disconnected.
Mail transport evidence
Testing has proved that corrected form notifications were accepted by the site’s mail transport. A sent transport record does not prove that a message reached an inbox. No mailbox configuration was changed during form testing.
Privacy and accessibility requests
Select Privacy or Accessibility on the Contact and Support form so the request routes to support. You may also contact support@addienator.com. Do not include credentials, payment-card information, or confidential source materials.
Launch legal and retention review remains required
The current consent stack is Complianz, the WordPress Consent API, Site Kit, and Google Analytics. Visitors can reopen or withdraw their choice through Privacy choices in the footer. Final retention periods, permanent-deletion behaviour, future payment flows, technical logs, processor and subprocessor details, and rights language must still be verified against the complete launch stack and legal requirements. The replace-before-launch legal fields remain placeholders.
Review the current security boundary
Read how project files and AI requests move through Addienator, or use the working Contact and Support form for a privacy request.
