Secure document sharing
Secure document sharing, with a link you still control after you send it.
Send a proposal, report or deck as a private link: behind a password or a verified email, set to open once if it should, kept out of search, and tracked, so you know who opened it and when.
Start your 10-day trial. $15/mo after, cancel anytime.
This page is protected
Enter the password to continue
PBKDF2-hashed · enforced at the edge · we can’t read it
The short answer
What makes document sharing secure
Three things. Only the right people can open it, which means an access check that runs before the content is sent, not a script that hides it afterwards. Nobody else can find it, so the link is not listed in search. And you keep control after sending: you can see who opened it, change the password, or take it down.
An email attachment fails the third test the moment you hit send. A public link fails the first two. Pagelive is built to pass all three for the documents you make as web pages: proposals, audits, reports and decks built with AI.
Access control
Six ways to decide who opens it
Use one, or combine them. Each is set per page, when you publish or any time after.
Password
Checked at the edge before the page is served. Passwords are encrypted (PBKDF2), so we can’t read them.
Email gate
The reader enters an email before the page opens. Turn on verification and a one-time code, or signing in with Google, proves the address is theirs.
Recipient links
Give each person their own link. Their opens show under their name and they never see a code.
Allow-list
Limit the email gate to named addresses or a whole company domain, so a forward to the wrong person stops at the door.
View once
The first person to open the link sees the page; later visits get an “already opened” screen. Link previews in chat apps don’t use up the view.
Take it back
Revoke one recipient link and only that person loses access. Archive the page and the link stops working for everyone, at once.
After you share
See who opened it, and when
Every link reports opens, unique viewers, reading time, days and countries, with bots filtered out, and emails you when the document is opened. With a verified email or a recipient link, each open is tied to a person.
9
Opens
3
Unique viewers
6m 05s
Avg. reading time
Tue
Busiest day
Versus a drive link
Drive and Dropbox links share files. Pagelive shares the page.
Cloud drives are built for storing and collaborating on files, and their link settings are worth knowing. In their own help pages:
Google Drive
“Anyone who has the link can use your file, without signing in to their Google Account.”
Dropbox
“You can add passwords to shared links if you’re a Professional, Standard, Advanced, or Enterprise customer.”
If what you send is a spreadsheet, raw assets or a folder, a drive is the right tool. If it is a page you built with AI, a drive means exporting it to a file first, and the interactive parts stay behind. A Pagelive link serves the page itself, on your own domain, with the access controls above and a read signal you can act on. More on what that sharing setting implies: what “anyone with the link” really means.
Our posture
What happens behind the link
Noindex by default
Every page tells search engines not to list it, unless you opt in.
Served separately
Pages are served apart from your account and billing, so a page can’t reach your private data.
No training, no selling
Your documents are never used to train AI models and never sold.
Cloudflare infrastructure
Runs on SOC 2 Type II-ready infrastructure on Cloudflare, with data stored in Western Europe.
Pricing
Which plan includes what
Free covers 2 public pages with a view count. Passwords, email gates, allow-lists, recipient links, view-once links and an alert on every open come with Solo, at $15/mo or $150/yr. Team is $49/mo per workspace for up to 10 people.
Secure document sharing FAQ
Sending a document so that only the intended people can open it, nobody else can find it, and you can still see and change access after it has gone out.
For many client documents, yes: a password checked before the page is served is real protection. When you need to know who read it, or the document may be forwarded, add the email gate with a one-time code, and an allow-list so only people at the client’s domain get in.
You see every open, how long each visit lasted, the country and the day, and you get an email when it happens. With a verified email or a recipient link, each open is tied to a person, so you see who it was.
Yes, on Solo and Team, once you switch comments on for the page. Only identified readers comment: people who verified their email, signed in with Google, or came through their own recipient link. You can keep each reader’s threads private to them, and write internal notes they never see.
The first real visitor sees the page. Everyone after that, including the same person on a second visit, sees an “already opened” screen. Link previews in apps like Slack and iMessage are recognized and don’t consume the view.
Pagelive runs on SOC 2 Type II-ready infrastructure on Cloudflare. Pagelive itself does not claim a separate certification. The details of how pages are stored and served are on the security page.
No. Pagelive shares web pages: the HTML documents you build with AI or by hand. For raw files and folders, a file-sharing tool is the right choice.
Sending proposals? See AI proposal software. Sharing files rather than pages? Read secure file sharing for business.
Send your next document as a link you control.
Password, verified email, recipient links or view once, kept off Google, with a record of every open. Start your 10-day trial. $15/mo after, cancel anytime.