Heads up: the easy free way to put an AI-built page online usually makes it public and searchable on Google. Pagelive keeps yours private →
+ +

Security & privacy

Your client deck stays private, not searchable on Google.

The quick, free ways to publish a page were never built for confidential client work: most put your page on the public web, where Google can index it by default. Pagelive is built the other way around: unlisted and kept out of search by default, and on Solo and Team behind a password or a verified email when it matters. So a proposal, deck, or dashboard reaches the people you send it to, not a search engine.

noindex by defaultisolated content planePBKDF2 passwordsno AI trainingno data sellingSOC 2 Type II-ready infrastructure on Cloudflare

+ +

Noindex by default

It won’t show up on Google

Every page ships with a robots meta tag and an X-Robots-Tag: noindex, nofollow response header, the two signals search engines use to decide whether to list and follow a URL. Both say no by default, so your client deck stays out of search results. You can opt a page into indexing only if you explicitly choose to.

What a page looks like when a typical free host indexes it:
site:my-test-page.example
https://my-test-page.example › q3-pricing
Q3 Pricing Proposal · Confidential
A test page published on a typical free host. Indexed and searchable within a day: no password, no noindex…
Pagelive serves the same page noindex by default. It never shows up here.

Illustrative demonstration of default behaviour. No real customer data.

+ +

Isolated content plane

Your pages are walled off from your account

Published pages serve from a separate content plane (Pagelive’s own content domains, and your own custom domain with Solo) that’s isolated from the control plane where your dashboard, login, and billing live. A served page can’t reach your account data. If a page were ever compromised, the blast radius stops at that page.

Control plane
app.pagelive.io
  • • Dashboard
  • • Auth & accounts
  • • Billing
isolation boundary
Content plane
content domain
  • • Your published pages
  • • Custom domains (Solo)
  • • noindex · edge-gated
+ +

Password protection

Lock a page with a password even we can’t read

On Solo and Team, any page can be password-protected. The password is PBKDF2-hashed, never stored in plaintext, and not visible to us. The gate is enforced at the edge with signed cookies, so only people who have both the link and the password can open the page. Lose the password? You reset it; we can’t recover the original because we never had it.

Hashed, not stored

PBKDF2-hashed at rest, never plaintext, never visible to us.

Edge-gated

The check runs at the edge before any content is served.

Signed cookies

A verified visitor gets a signed cookie. No shared secret leaks to the page.

+ +

What we never do

No training on your content · no selling your data

No training on your content

We never use your content, or anything inside your pages, to train AI or ML models, ours or anyone else’s. Your work is yours.

No selling your data or recipients’ emails

We never sell your data, and we never sell or rent the email addresses of the people you share pages with. Read the privacy policy →

And we never delete your evidence. Analytics are recorded from day one and never deleted behind a paywall: the full detail for every page keeps accumulating whatever plan you are on, and upgrading unlocks the whole history, back to day one.

+ +

Infrastructure

On SOC 2 Type II-ready infrastructure

Pagelive runs entirely on Cloudflare (Workers, D1, and R2): SOC 2 Type II-ready infrastructure. That means DDoS protection, TLS everywhere with automatic per-domain certificates, and your data on a hardened, globally distributed network.

publish → Cloudflare R2 (object storage) → edge Worker serves on a separate content domain (noindex) → analytics in Cloudflare D1 · app.pagelive.io stays isolated
+ +

For the security lead reviewing this

No. We never use your content, or anything in your pages, to train AI or ML models, our own or anyone else’s. It’s in our terms.

The questions a CTO actually asks before a confidential document goes out, answered plainly.

+ +

Privacy

How we handle viewer data, and a clear takedown path

Analytics are privacy-first: viewer IPs are salted-hashed, never stored raw, with coarse country only. If a page ever needs to come down, abuse and takedown requests have a clear path and we can disable a page from the edge with one flip.

+ +

Send your next deck on a link that stays out of search.

Noindex by default, isolated content plane, a password on Solo and Team. Free to start.