Privacy Policy
What we collect, why, and what you can do about it.
Effective date: October 3, 2026
Contact: support@pagehub.dev
This page explains what PageHub collects, why, who helps us run the service, how long we keep things, and what you can do about it.
"PageHub", "we" and "us" mean the PageHub service at pagehub.dev. "You" means someone with a PageHub account. "Visitors" means people who visit a site built with PageHub.
There are two roles here:
- Your account and your sites: we decide how that data is handled. This policy covers it.
- Your visitors' data (form submissions, store customers, analytics on your site): you decide what to collect on your site, and we store and process it for you. If you run a site on PageHub, you're responsible for telling your visitors what you collect. Your own site's privacy policy should cover that.
We don't sell your data.
What we collect
Your account
- Email address. You sign in with a one-time link or code sent to your email.
- Name and profile image, if you add them or sign in with Google.
- Phone number, only if you add one to get text-message alerts. We verify it before sending anything.
- Plan and billing status. Stripe handles card details. We keep your Stripe customer ID, plan and billing period, not your card number.
- Usage counts: form submissions per month, published sites, storage used, and AI credits.
- Notification and email preferences, including whether you've opted out of marketing email.
Your sites
- Site content: pages, text, images, video, files, collections, forms, theme and settings you create in the editor or through the API.
- Uploaded media. Images go to Cloudflare Images. Other files (video, audio, PDF, zip) go to Cloudflare R2.
- Site history: saved versions of your pages so you can restore them.
- Custom domains you connect.
- Credentials for services you connect to a site, such as your Stripe keys, your own mail server, a Google Sheet or a Shopify store. We store these encrypted.
- Collaborators you invite, and their role on the site.
Data from your visitors
When someone visits a site you built on PageHub, we may collect the following for you:
- Form submissions. Whatever your form asks for: often a name, email and message. We store the form name, the page it came from and the fields submitted.
- Store customers. If your site sells through Stripe, a visitor who buys something or signs in gets a customer record: email, name, order count, total spent and whether they agreed to marketing email.
- Customer sign-in links. Visitors can sign in to your site with an emailed link.
- Site analytics. Page views, time on page, scroll depth, referrer, campaign tags (UTM), device type, browser, operating system, screen size, page speed scores, and country, region and city. Location comes from our host's request headers.
- We don't store the visitor's IP address for analytics. We turn IP address and browser details into a short code using a random value that changes every day, so the same visitor can't be linked from one day to the next.
- Our analytics script doesn't set cookies. It keeps a session start time in the browser tab only.
- Review comments. When you share a draft for feedback, a guest types their name and email to leave comments. We store the comments, where on the page they were pinned, and who wrote them.
- Chat with visitors. If you turn on chat for your site, we store the conversation and give the visitor an anonymous cookie so the conversation continues across messages. If the visitor leaves their details for you, they're saved as a form submission along with the conversation.
When you use our marketing site
- On pagehub.dev's marketing pages (not the editor, and not sites you build), we use Google Analytics, loaded through Google Tag Manager, which sends page views and clicks to Google.
- If you sign up for our newsletter, your email goes to our newsletter list.
API keys, OAuth tokens and AI requests
- API keys (they start with
ph_) let scripts and tools act on your account. - OAuth tokens are issued when you connect an app, such as an AI assistant, to the PageHub MCP server. We store a hash of each token, not the token itself.
- AI request logs: which feature you used, which model, how many tokens, whether it worked, and the prompt you typed.
Why we use it
- To run the service: sign you in, save and publish your sites, serve your pages, send your form submissions and alerts.
- To bill you: track your plan, usage and AI credits.
- To keep things safe: rate-limit abuse, block suspended accounts and take down sites that break our rules.
- To fix problems: debug errors and failed AI requests.
- To improve the product: see which marketing pages people visit.
- To send email you asked for: sign-in links, receipts, alerts and, only if you opted in, product news.
API, OAuth and the MCP server
PageHub has a REST API and a hosted MCP server at https://pagehub.dev/api/mcp. MCP lets an AI assistant (like Claude) build and edit your sites.
- You connect an app by signing in and approving it, or by giving it a
ph_API key. - A token acts as you. Every tool call runs with your account's access. The app can see and change any site you can see and change: read and edit pages, upload files, manage collections, publish and unpublish, delete sites, connect domains and invite collaborators. There's one permission level today,
mcp:tools, and it covers all of this. - Changes go to your draft first. Edits from an app don't reach your live site until someone publishes, unless the app calls publish.
- Content you read through MCP goes to that app's AI provider. When an assistant reads your site, the text is sent to whichever company runs that assistant, under their privacy policy, not ours.
- Access tokens last 1 hour. Refresh tokens last 30 days. You can revoke an app's access.
- API keys don't expire. Anyone with your key can act as you. Keep it secret, and replace it if it leaks.
- To stop a tool call running twice when an app retries, we briefly keep the result of calls that create something.
AI features send content to AI providers
When you use an AI feature — the editor assistant, AI drafting, image descriptions, image generation — we send your prompt and the relevant site content to an AI model. Requests go through Vercel AI Gateway to the model provider. The providers we use today:
- Anthropic (Claude models) for text and image understanding.
- OpenAI for image generation.
Who helps us run PageHub
We share data with these companies only as needed to run the service.
| Company | What they do for us | What they get |
|---|---|---|
| Vercel | Hosts the app and your published sites. Handles rate limiting and custom domains. Routes AI requests (AI Gateway). | Every request, including IP address; site content; AI prompts |
| MongoDB (Atlas) | Our database. | Everything we store |
| Cloudflare (Images and R2) | Stores and serves uploaded images and files. | Your uploads |
| Stripe | Takes payments for PageHub plans. Also runs checkout for stores on your sites. | Billing details; your store customers' purchase details |
| Amazon Web Services (Amazon SES) | Sends our email: sign-in links, alerts, form notifications. | Recipient email and message content |
| Anthropic | AI models. | Prompts and site content you use with AI features |
| OpenAI | Image generation. | Image prompts |
| Inngest | Runs background jobs, like sending notifications and running imports. | Job data, which can include form submissions and import content |
| Browserless | Takes screenshots of your draft site when you or your AI assistant ask for one. | The page being screenshotted |
| Telnyx | Sends text-message alerts, if you turn them on. | Your phone number and the alert text |
| Google Analytics (through Tag Manager) on our marketing pages. Google Fonts on sites and emails. Page speed checks. Google sign-in (currently turned off). Google Sheets, if you connect one. | Marketing page activity; visitor IP address when fonts load; the URL being tested; your Google profile; the sheet you connect | |
| Sendy | Our newsletter list. | Your email, if you subscribe |
| Shopify | Imports your store when you connect it. | Access to the store you approve |
| Figma | Imports a design when you ask. We use your Figma token for that one request and don't keep it. | Your token and file ID |
| Unsplash and Pexels | Stock photo and video search. | Your search words only |
Services you add to your own site. You can add tools like Google Analytics, Google Ads or other tracking to a site you build. Those send your visitors' data straight to that company. That's between you, your visitors and that company.
We may also share data if the law requires it, or to protect people or the service from harm.
Where your data lives
PageHub runs in the United States. The app and your published sites are hosted by Vercel in its Washington, D.C. region, and our database is MongoDB Atlas on AWS in the eastern US. Our email goes through Amazon SES in the US. Uploaded images and files are served from Cloudflare's worldwide network. Our other providers may store or process data in the US and other countries.
We encrypt the credentials you give us for connected services, like Stripe keys and mail server passwords. Connections to PageHub use HTTPS.
How long we keep it
Most things are kept until you delete them, or until you delete your account. That includes your account details, site content, uploaded files, collections, form submissions, store customer records and review comments.
Some things are deleted on a timer:
| What | How long |
|---|---|
| Raw site analytics events | 7 days |
| Daily analytics totals | 1 year |
| Daily random value used to make visitor codes | 3 days |
| Your sign-in link or code | 15 minutes |
| Your sign-in session | 30 days |
| Visitor sign-in link (store customers) | 15 minutes |
| OAuth approval code | 5 minutes |
| OAuth access token | 1 hour |
| OAuth refresh token (the record is deleted when it expires) | 30 days |
| Registered OAuth app not used | deleted after 90 days |
| MCP retry records | 2 to 5 minutes |
| AI request logs | 7 days |
| Visitor chat conversations | 30 days after the last message |
| Website and WordPress import jobs | 30 days |
| Collection webhook delivery logs | 30 days |
| Collection sync logs | 30 days |
| Security (CSP) reports | 30 days after last seen |
| Site history versions | Newest 15 (Free), 75 (Pro), 100 (Business) or 500 (Agency) per page |
Your choices and rights
-
See and change your data. Most of it is in your dashboard and editor.
-
Download your data. You can export form submissions and customer lists as CSV from the dashboard. For anything else, email us.
-
Delete things. You can delete sites, pages, files, collections and submissions yourself.
-
Delete your account. Go to your dashboard's account settings. This:
- cancels your active subscription,
- deletes the sites you own, their pages and their analytics,
- removes you from sites other people own,
- signs you out everywhere and deletes your account.
It doesn't yet remove form submissions, store customer records, review comments, collections, site history or uploaded files. To have those deleted too, email us at support@pagehub.dev.
-
Stop marketing email. Use the unsubscribe link in any marketing email, or turn it off in your settings.
-
Disconnect apps. Revoke OAuth access, or replace your API key.
Depending on where you live, you may have more rights, such as asking us to correct your data, limit how we use it, or send you a copy. Email us and we'll help. We may need to confirm it's you first.
If you're a visitor to a PageHub site and want your data changed or deleted, contact that site's owner first. They control it. If you can't reach them, email us.
Cookies
We use a few cookies to keep you signed in and make features work. We don't use advertising cookies on the editor or on sites you build. Google Analytics on our marketing pages sets Google's own cookies.
| Cookie | What it does | How long |
|---|---|---|
next-auth.session-token | Keeps you signed in to PageHub | 30 days |
next-auth.csrf-token | Protects sign-in forms | Browser session |
next-auth.callback-url | Sends you back where you were after signing in | Browser session |
mcp_oauth_params | Remembers an app's request while you approve it | 10 minutes |
ph-customer | Keeps a store customer signed in to a site | 30 days |
ph-review | Keeps a guest reviewer signed in to leave comments | 30 days |
ph-review-mode | Remembers you're in review mode on a draft | 30 days |
ph-chat-visitor | Keeps an anonymous visitor's chat together | 90 days |
ph-agency-preview | Lets an agency's client preview a site | 15 minutes |
ph_theme | Remembers a theme while you preview templates | 5 minutes |
Children
PageHub isn't for children under 13, and we don't knowingly collect their data. If you think a child has given us data, email us and we'll delete it.
Changes to this policy
When we change this policy, we'll update the date at the top. If a change is significant, we'll tell you by email or in the dashboard before it takes effect.
Contact
Questions, or want to use any of your rights? Email support@pagehub.dev.