What we collect
- Account information: name, email address, password hash, workspace name, role, and which projects you can reach.
- Workspace data: the domains you add, crawl results, tracked keywords and their positions, keyword research you save, backlink snapshots, Search Console and Analytics history once you connect those accounts, AI-search prompts and answers, content tasks, work items, workflows, reports, and client portal settings.
- Page content: when you put a URL under Content Monitor we store the readable text of that page at each check, so a later check can say what changed.
- Billing data: plan, credit balance, and a line for every credit spent — what ran, when, and what it cost. Card details are handled by our payment processor and never reach our servers.
- Technical data: IP address, browser, request logs, and error reports.
What we send to AI models
- Xavier and every AI-assisted feature send your question and the project data needed to answer it to a model provider. That can include domains, URLs, keywords, rankings, crawl findings, Search Console figures, and whatever you type into the chat.
- We use more than one provider and route each request to whichever model suits it: Anthropic, OpenAI, Google, Perplexity, and xAI, some of them through OpenRouter. All are United States companies.
- We do not send your workspace data for model training, and the providers we use make the same commitment for API traffic. We cannot promise a provider will never change that. If one does, this page changes.
- AI features are optional. A workspace that never opens Xavier and never runs an AI-search check sends nothing to a model provider.
Who else receives data
- Cloudflare (United States) hosts the application and stores workspace data and files at rest.
- Our managed Postgres provider holds the same workspace data as the primary database.
- DataForSEO (Cyprus) receives the domains, URLs, and keywords needed to return rankings, search volume, backlinks, and SERP results. It receives no account or billing information.
- Google returns Core Web Vitals field data for the URLs we check, and — only if you connect them — Search Console and Analytics read under the permissions you grant.
- Stripe processes payments and holds your card details.
- Loops sends transactional email: verification, password reset, invitations, and billing notices.
- Slack, Notion, WordPress, Webflow, ClickUp, and Monday receive data only for workspaces you deliberately connect, and only what the connection needs.
- Reddit's advertising pixel runs on our marketing pages and reports that a visit or a signup happened. It does not run inside the application and never sees workspace data.
Accounts you connect
- Connecting Google Search Console or Analytics stores an access token for the properties you pick and nothing else from your Google account. Disconnecting revokes the token and stops the sync; history already imported stays in the project until you delete it.
- Connecting Slack stores the workspace ID, the token issued at install, who installed it, and the channels you map to projects. The app can see messages that mention it, post messages, and receive its slash commands. It cannot read channel history, list members, or open files.
- Notifications you turn on post project data into the channel you choose. Everyone in that channel can read them, including people added later and, in a shared channel, your client.
Client portals
- A portal link is a token in a URL. Whoever holds it can read the sections you shared, with no account and no sign-in, until you revoke the link.
- We record that a portal was viewed and when. We do not identify the viewer.
- Choosing which sections a portal shows is how you control what a client sees. Treat the link as a credential, because it is one.
Data about your clients
- When you add a client domain we collect data about that website from public sources and from the accounts you connect. You are responsible for having the right to analyze the properties you add.
- Everything in your workspace is yours. We do not sell it, and we do not use one customer's workspace data to serve another.
How long we keep it
- Site audits: the ten most recent per project, and never less than ninety days of history.
- Content Monitor snapshots: up to two years, or forty versions of a page, whichever comes first.
- Search Console and Analytics history: kept while the project exists, so year-on-year comparisons stay possible.
- Deleting a project deletes its data. Closing an account deletes the workspace within thirty days, apart from records we must keep for tax and accounting.
- Backups are held for thirty-five days and then overwritten.
Security
- Traffic is encrypted in transit and data is encrypted at rest. Passwords are hashed and never stored in a readable form.
- Access is decided per person and per project. A viewer cannot change anything or spend credits, and that is enforced on the server rather than by hiding buttons.
- Every action an agent takes is written to the project activity log with the evidence behind it, and a workspace can require a person to approve any change before it happens.
- If a breach affects your data we will tell you what happened, what was reached, and what we are doing, without waiting until we have a complete answer.
Your choices
- Export what is on screen, delete a project, or close your account from inside the product.
- Ask for a copy of your data, a correction, or deletion at support@pageoptimized.com. We answer within thirty days.
- If you are in the UK, the EU, or a US state with its own privacy law, those rights apply to you and this is how to use them.
Why we are allowed to process it
- If the GDPR or UK GDPR applies to you, these are our lawful bases.
- Performance of a contract: running your workspace, storing your projects, processing credits, and providing support. Without this we cannot deliver the service you bought.
- Legitimate interests: keeping the service secure, preventing abuse, debugging errors, and understanding which features are used. We balance these against your interests and use the least data that answers the question.
- Legal obligation: tax records, accounting, and responding to lawful requests.
- Consent: the advertising pixel on our marketing pages, and any marketing email you opt into. You can withdraw consent at any time and nothing else stops working.
- Where you upload or connect data about other people — your client's Search Console, a colleague's email address — you are the controller of that data and we process it on your instructions.
Where the data goes
- Page Optimized operates from Delaware, United States and our infrastructure is in the United States. If you are in the UK, the EU, or Switzerland, your data is transferred there.
- For those transfers we rely on the European Commission's Standard Contractual Clauses and the UK Addendum, incorporated into our data processing agreement. Vendors that hold data on our behalf are bound by the same clauses.
- Cloudflare serves the application from the location nearest your users, so a request may be handled in your region even though the database is not.
- You can ask us for a copy of the transfer safeguards at any time.
Your rights, and how to use them
- Access: ask for a copy of the personal data we hold about you.
- Rectification: correct anything wrong. Most of it you can edit yourself in the product.
- Erasure: delete a project from inside the product, or ask us to close the account and remove the workspace.
- Portability: export what is on screen as CSV from any table, or ask us for a full export.
- Restriction and objection: tell us to stop a particular use, including any processing based on legitimate interests.
- Withdraw consent: decline the advertising pixel, or unsubscribe from marketing email using the link in it.
- Email support@pageoptimized.com from the address on your account. We reply within thirty days and we do not charge for it.
- If you are unhappy with the answer you can complain to your supervisory authority. We would rather you told us first, but that right is yours regardless.
If you are in California
- We do not sell personal information and we do not share it for cross-context behavioural advertising as the CPRA defines those terms. We have never done so.
- Categories we collect: identifiers, commercial information, internet activity, and inferences drawn from product usage. The section above lists what each of those means here.
- You have the right to know what we collect, to delete it, to correct it, and not to be discriminated against for asking. Use the same address as everyone else.
- The advertising pixel on our marketing pages reports that a visit or signup happened. It does not run inside the product and never sees workspace data. Turning it off changes nothing about your account.
Cookies
- Strictly necessary: a session cookie that keeps you signed in, and a security cookie that resists cross-site request forgery. These cannot be turned off without breaking sign-in.
- Preference: your theme, sidebar state, and rows-per-page choice, stored in your browser rather than sent to us.
- Analytics and advertising: only on our marketing pages, and only with consent. Declining leaves every part of the product working.
- We set no advertising cookie inside the application. A signed-in workspace is not tracked for advertising.
Children
- The service is for business use and not directed at anyone under sixteen. We do not knowingly collect data from children, and we delete it if we discover we have.
Security incidents
- Report a vulnerability to support@pageoptimized.com. We will confirm within two business days and will not pursue anyone who reports one in good faith and does not access other customers' data.
- If a breach affects your personal data we notify you and, where required, the supervisory authority within seventy-two hours of becoming aware. We tell you what happened, what was reached, and what we are doing, without waiting until every answer is complete.
Changes to this policy
- We post the effective date at the top of this page and keep the previous version available on request.
- For a change that materially reduces your rights we email account owners at least thirty days before it takes effect.
Questions?
Contact Page Optimized through the contact form.
Review pricing