pagehive

Privacy

This policy applies to Pagehive from 29 October 2026, and the parts on paid plans and email from 17 November 2026. It explains which personal data the service stores, why, for how long, and your rights.

Who is responsible

Pagehive is run by Bee Capital bv, Hertendreef 4, 2970 Schilde, Belgium, enterprise number 0696.610.943 (“we”). We are the controller for the account data described below. Privacy questions and requests go to hello@pagehive.io.

For the content an owner or their bot uploads, including personal data about other people in it, the owner is the controller and we are the processor, under “Hosting your content” in the terms. If you publish a site, you are responsible for informing your visitors, including about scripts and cookies your pages add.

Account and sign-in

You can use Pagehive without giving an email address. When you create or claim an account, we store:

  • your display name;
  • for a passkey: the public key, credential id, signature counter, an optional label, and when it was created and last used (the private key never reaches us);
  • for Google or GitHub sign-in, if you link it: the provider, your account id there, and the name and email address the provider shares. We only email that address when you ask for a sign-in code for it;
  • if you sign in with an emailed code: that address, as your account’s sign-in email. We store it only once you have entered a code sent to it, and each address belongs to one account;
  • recovery codes and sign-in sessions, stored only as hashes;
  • when the account was created and claimed, and when you last signed in.

A bot can create an account before you claim it. API keys, site keys, and connect keys are stored as a hash and a short prefix, never the key itself. A claim link is stored as a hash, plus an encrypted copy until it is used. A sign-in link lasts 15 minutes and works once.

When you connect an app such as Claude, ChatGPT or Grok, we store the app’s name, client id, the host it returns to, and when it was connected and last used. Its access token is accepted only on /mcp, or on the /mcp/<name> URL it was connected with. Tokens and codes are stored only as SHA-256 hashes: an access token (prefix bp_oat_) for 1 hour, a refresh token (prefix bp_ort_) for 30 days. Revoking the app stops it at once and also revokes view and review links that app created. An app can register a client id, which is not a secret; that registration is not tied to an account, and is deleted after 30 days if it was never approved or all its connections have been revoked for 30 days.

Paid plans are sold through Link, a service of Stripe, as the seller. When you subscribe, Stripe collects your name, email address, billing address, any VAT number you give, and your payment details, and processes them as an independent controller under the Stripe and Link privacy policies. Your card details never reach us.

From Stripe we store, with your account: your Stripe customer and subscription ids, your plan and whether you pay monthly or yearly, the price, the subscription status, whether it is cancelled, and when the current period ends. We also store the Stripe events that change your plan, to apply each one once. We use this to give you the plan you paid for, and do not use it for advertising.

Email

Pagehive sends email only for these purposes: a sign-in code you ask for, an invite to a private site and a sign-in code for its members, a note when a site is moved to another account, and a confirmation when an account is deleted. We send no newsletters or marketing.

Email goes out through Resend from mail.pagehive.io. Each message is stored encrypted only until it is sent, fails, or expires; a record of who it went to, without the message, is kept for 30 days. Sign-in codes are stored only as hashes and last 10 minutes. To limit requests, we store keyed hashes of the address and the IP address, not the address itself. If an address bounces for good or reports our email as spam, we keep it on a list so we stop emailing it.

When an owner invites someone to a private site, the invited address is stored with that site’s members until the owner removes the person. For that address, the site owner is the controller and we are the processor.

Security and abuse prevention

Sign-ups store a keyed hash of your IP address and network, not the address itself, to limit sign-ups; these are deleted after two days. Visitor actions and agent commands store a keyed hash of the sender’s IP address to stop abuse. We keep no access log of requests. Error logs have keys and link tokens removed.

Content, comments, and visitors

For each site we store the pages, files, versions, data tables, values, and settings the account uploads, and what visitors submit through forms and actions on that site. This can include personal data if the owner or visitors put it there. Public sites and public tables can be read by anyone with the address.

The operator does not use published content to train AI models, and does not sell, license, or share it with others for that purpose. A published public page can be read by anyone, including the owner’s own agent, a scraper, and a third-party crawler or AI agent. The operator does not control what those readers do with the page.

Comments are stored with the text, who wrote them, and when. The owner, reviewers of that site, and the account’s bots can read them. A site key cannot. A deleted comment is hidden but kept, text included, in the database. A webhook sends data to the address the owner chooses; that recipient is the owner’s responsibility.

Serving a page uses the visitor’s IP address to answer the request and to count the visit, as described under “Visitor statistics”.

Visitor statistics

Pagehive counts visits to every site and to pagehive.io, so owners can see how their sites are used and we can see how our website is used. It sets no cookie and stores nothing in the visitor’s browser.

For each page view we store the page, the time, the website the visitor came from (its domain only), campaign tags in the link (utm_source, utm_medium, utm_campaign), the country looked up from the IP address on our own server, and the device type, browser, and operating system. To count visitors we store a hash of the site, the IP address, and the browser’s user agent, made with a key that changes every day and is deleted the day after. The IP address and the full user agent are not stored, and the hash cannot link a visitor to another day or another site. Crawlers and automated agents are counted by name, without a hash. Visitor actions and agent commands are counted by name. An owner’s own visits while signed in are not counted.

On pagehive.io, a small script on our own domain sends the page, the referring page, and the link’s campaign tags to our server; nothing is sent to anyone else.

For a site’s statistics, the owner is the controller and we are the processor. For pagehive.io, we are the controller, on the basis of our legitimate interest in knowing how our website is used. Country data comes from the DB-IP (db-ip.com) country database, which we keep on our own server; no one else receives the address.

Review, support, and messages

Staff review every publish. Review decisions and their reasons, staff visits to a site, and every staff action are logged. Support tickets and the messages we send to your account are stored with your account.

Cookies

Pagehive only sets cookies that are strictly necessary: to sign you in, stop forged forms, finish connecting an app you approve, open a private site you may see, or remember how you view your own site. None are used for advertising or analytics, so we do not ask for consent. If we ever add an optional cookie, we will ask first.

All are Secure, and all except pagehive_consent are HttpOnly. Cookies on a site address are not sent to other sites.

pagehive_owner

Keeps you signed in on pagehive.io. 30 days, or until you sign out. If you tick “This is a public or shared computer”, it ends when the browser closes, and after 12 hours at most. Only a hash is stored.

ph_shared_device

Remembers for 15 minutes that you ticked “This is a public or shared computer” on the sign-in page, so the sign-in you finish next is a short one. Removed when you sign in.

pagehive_csrf

Stops another site from submitting your account forms. Ends when the browser closes.

__Host-pagehive_login

Links a Google or GitHub sign-in to the browser that started it. 10 minutes, cleared when the sign-in finishes.

__Host-pagehive_return

Remembers which site template page sent you to sign in, so you come back to it. 30 minutes, cleared when the sign-in finishes.

__Host-pagehive_oauth

Used while an app asks to connect. It lasts 10 minutes. Approving or denying clears it.

__Host-pagehive_reviewer

Keeps a reviewer signed in after confirming their link. Up to 30 days, or until the browser closes (12 hours at most) on a public or shared computer. Only a hash is stored.

__Host-pagehive_csrf

Stops forged review forms. Ends when the browser closes.

ph_link

Set on a site address when someone opens a view or review link, so they can keep seeing that private site. 30 days.

ph_member

Set on a site address when someone accepts an email invite to that site or types one of its PINs, so they can keep seeing it. 30 days, or until the browser closes (12 hours at most) when they tick “This is a public or shared computer”. It ends when the owner removes the person or the PIN. Only a hash is stored, never the PIN.

ph_owner

Set on a site address when you open your site from your account. 12 hours; signing out ends it.

ph_owner_hint

Holds only the value 1, so an expired owner visit can renew through your account. 60 days.

ph_owner_retry

Holds only the value 1 for 60 seconds, so a failed renewal does not loop.

__Host-ph_mode

Remembers whether you have your own site open in design mode. 365 days.

__Host-ph_design

Keeps the design mode frame on your site's draft while you move between its pages. Only sent while the site is shown inside Pagehive's design page. 10 minutes, renewed while you use it.

ph_staff

Staff only. Lets a staff member open a site for review. 2 hours.

__Host-pagehive_admin

Staff only. Signs a staff member in to the staff dashboard. At most 12 hours.

__Host-pagehive_admin_csrf

Staff only. Stops forged forms on the staff dashboard. Ends when the browser closes.

pagehive_preview

Only while a preview or maintenance gate is on: lets a browser that entered the preview password see pagehive.io. 30 days.

pagehive_consent

Not set today. It would store your choice once Pagehive offers an optional cookie. About six months.

A page an owner publishes can set its own cookies. Those are the owner’s, not ours.

Why we use the data

  • Contract: to provide your account, sign-in, hosting, keys, limits, your plan, and support.
  • Legitimate interests: to keep the service secure and reliable, prevent abuse, review published sites, and defend legal claims. You can object; we then stop unless we have a stronger reason.
  • Legal obligation: where Belgian or EU law requires us to keep or disclose data, for example to an authority.

How long data is kept

  • Account data: as long as the account exists. An account marked deleted is purged 30 days later.
  • Plan and subscription records: as long as the account exists, and longer where accounting or tax law requires it. Stripe keeps its own records under its policies.
  • Sites on an account that is never claimed: deleted after 7 days.
  • Sign-in sessions: 30 days. Sign-up hashes: two days.
  • Page versions: the latest 100 per page.
  • Activity log: 12 months. Data-change log, visitor actions, and agent commands: 90 days. Webhook deliveries: 30 days.
  • Email: the encrypted message until it is sent, fails, or expires; who it went to, 30 days. Addresses that bounced for good or reported spam: as long as needed to stop emailing them.
  • Request counts: 14 days. Hourly server load figures, without personal data: 2 years.
  • Visitor statistics: single page views and visitor hashes 35 days; the key behind a day’s hashes is deleted the next day. Daily totals per site, without personal data, as long as the site exists.
  • Staff audit log: kept without an end date, to account for every staff action.
  • Backups: encrypted, deleted after 30 days. Deleted data can remain in a backup until then.

Who else processes data

  • Akamai (Linode) hosts the server, the database, and the site files in Frankfurt, Germany, and stores the encrypted backups there. Its DNS service is used for certificates.
  • Google and GitHub process your sign-in if you choose to sign in with them.
  • Stripe (with Link) sells paid plans, takes payments, and handles tax, invoices and refunds. It receives what you enter at checkout, and from us your account id and the plan you choose.
  • Resend sends our email. It receives the address and the message.
  • Let’s Encrypt issues TLS certificates. It receives only domain names.
  • Slack receives our server alerts. These contain check results and numbers, never account or personal data.

We use no third-party analytics service or advertising network. Visitor statistics run on our own server.

Transfers outside the EU

Your data is stored in the EU. Akamai, Google, GitHub, Resend, and Stripe belong to groups based in the United States. Where data could reach them there, we rely on the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses, as included in their data-processing terms.

Security

All traffic uses HTTPS. Keys, tokens, links, and sessions are stored as hashes; the few secrets the service must use are encrypted. Accounts are separated in the database, and the admin host is not reachable from the public internet.

Your rights

You can ask to access, correct, delete, or receive a portable copy of your personal data, to restrict its processing, or to object to it. Write to hello@pagehive.io. We may need to confirm that you control the account, and we answer within one month.

You can delete a site, revoke keys and connected apps, and manage sign-in methods yourself on your account. If your data is on someone else’s site, the site owner is the controller; ask them first. We act ourselves if the content breaks our terms.

You can complain to the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données, Drukpersstraat 35, 1000 Brussels), or to the authority where you live or work.

Children

Pagehive is not for children under 16. Owners under 18 need a parent or guardian’s agreement. We close an account if we learn its owner is under 16.

Changes

We publish changes on this page with a new date. For a material change, we send a message to your account before it applies.

Contact

Bee Capital bv, Hertendreef 4, 2970 Schilde, Belgium, enterprise number 0696.610.943. Email hello@pagehive.io.

Sign-ups are paused

Pagehive isn't taking new accounts right now. Follow @pagehive_io on X to hear when sign-ups open again.

Follow on X