Data handling in the staging preview.
Updated 3 October 2026. This describes the current build. The operator identity, support contact and final retention terms must be supplied before a paid release.
What the workspace stores
Account records include your name, email, password hash and sessions. Project records include brand details, permitted members, prompts, retrieved evidence, source facts, content revisions, approvals and activity. Connected integrations add their authorized property or site and encrypted connection credentials.
Cloudflare hosts the application and D1 records. Raw evidence is stored in private R2 storage. Evidence downloads and workspace operations require server-side account and project permission.
When data goes to another service
A configured AI run sends its selected prompts and bounded context to the selected provider. Draft generation sends the reviewed facts and sources. Connecting Search Console uses Google authorization; a WordPress operation sends the selected approved revision to its connected site. Transactional email sends account verification, recovery or invitation messages through Resend when configured. Configured billing uses Stripe-hosted account flows.
These integrations are optional or currently gated in staging. Their disconnected state is shown in the application. Staging setup does not authorize autonomous publication of customer content.
Browser and credentials
The application uses a session cookie to keep you signed in. This build loads its fonts locally and has no configured advertising or third-party analytics. Connection credentials are encrypted with a separately stored key. Raw credentials and account recovery tokens are excluded from ordinary application logs and data exports.
Affiliate links
The affiliate programme is off unless the operator switches it on. When it is on and you open a page through an affiliate's link (an address ending in ?ref= and a code), we log the click with the affiliate's code, the time and the page only (no IP address or browser details) and set a first-party cookie, promptmentions_ref, that remembers the code for the programme's cookie period (60 days by default). If you create an account while it is set, we note which affiliate referred the account for the same period, and if your workspace subscribes, the affiliate's commission records keep the Stripe customer reference, payment amounts and dates. Affiliates see only totals, never your name, email or workspace. People who apply to become affiliates give us their name, email, website, audience size and how they will promote PromptMentions; we use these only to review the application and run the programme. Your personal export includes any affiliate attribution on your account, and account erasure removes it.
Ad landing pages
Pages under /for/ are landing pages for advertising. When you open one, we add one to a daily count for that page, kept with the campaign's utm_source and utm_campaign tags only (no IP address, browser details or referrer), and set a first-party cookie, promptmentions_utm, that remembers the page and its campaign tags for 30 days. If you create an account while it is set, we note that page and those tags against the new account so we can tell which campaigns lead to sign-ups. Your personal export includes this note, and account erasure removes it.
Export and erasure
Account settings separates your personal export from a workspace export. Workspace export requires owner permission. Personal erasure and workspace erasure have different scopes and explicit confirmation. Some shared authorship references are replaced by pseudonymous identifiers so another member's work retains its history.
Erasure revokes access and uses bounded background cleanup of the recorded D1 and R2 inventory. Unresolved jobs, publication uncertainty or billing obligations can prevent a request from proceeding. Financial and minimal erasure-control records have separate retention requirements. Backups can retain earlier data until their retention period expires; restoration must honor erasure records.
Before using real client data
This is a staging preview. Final business details, integration acceptance and recovery checks are still open. Use explicitly named test data until the operator completes those release checks. A final privacy notice and service terms will identify the operator, support route and applicable retention periods.