Privacy Policy
Effective November 13, 2026
sharable.link turns HTML files into public links. This page explains what we collect and how it's handled. Plain English, no surprises.
What you publish
When you share a page, we store the HTML content, an auto-generated slug, a timestamp, and an optional title and password. If you set a password, it is stored hashed — not in plain text. If you share a page with specific people, we store the email addresses and company domains you list, and use them only to decide who can open it. When you publish from the upload page, sharable.link/free-html-hosting, you can also tell us who the page is for (a client, your team, or just you); we keep the answer with the page and delete it with the page.
Anyone with the URL can view a public page. For password-protected pages, anyone with the URL and the password can view. For pages shared with specific people, only visitors who sign in and show that an email address on the list is theirs can view: with a Google or Microsoft account for that address, or for an address at a company domain on the list, or with a sign-in link sent to an address named on it. We may access stored content to investigate abuse reports, respond to support requests, or comply with legal obligations.
When you use the connector
When Claude or another app uses the sharable.link connector for your account, we record each thing it does — publishing, updating, listing or removing pages, or sending feedback — with the time, which app it was, whether it worked, and if it didn't, a short reason such as “page too large”. For a page, we record its size, not its content. When a file is sent to us from Claude's environment, or from the upload area in a Claude or ChatGPT chat or on sharable.link, we also record whether it got through to us and whether the file was published. We also record when Claude or the app loads the connector's tools in a conversation or uses one of the connector's prompts, with the time and which app it was. We use these records to find and fix what goes wrong when you publish from Claude or ChatGPT, and to see whether people who connect go on to publish. We keep them for 90 days, and delete them with your account.
An app you connect can tell which sharable.link account it's connected to. It can also ask to see your name and picture, and your email address. The screen where you approve the connection lists each thing the app asks for, and it gets those only if you approve. What the app does with them afterwards is covered by its own privacy policy.
If you ask Claude, ChatGPT or another app to send us feedback, we keep what it sends — what went wrong, what you needed, or what you liked, and which page it was about — with your account, and email it to the person who builds sharable.link, who may write back to you. We keep feedback for 90 days and delete it with your account.
How long we keep it
Pages stay live until you remove them with /unshare and your delete key. We may also remove pages that violate our terms of use.
Deleting your account deletes every page you published from it, straight away. The one exception is a page we took down for breaking our terms: we keep it, no longer linked to any account, so its link can't be reused for something else.
What we collect about visitors
We count page views in aggregate to understand traffic. We do not store visitor IP addresses or browser fingerprints, and we set no tracking cookies on shared pages and don't identify individual visitors — with one exception, below. If you use the assistant on our own site, see “The assistant on our site”.
To open a page shared with specific people, a visitor signs in with Google or Microsoft, or with a link sent to their email address. That creates a sharable.link account holding their email address and, when they use Google or Microsoft, their name and the account ID that provider gives us — the same kind of account used to publish pages. We use the email address to check it against the page's list, and to send the emails described under “Email we send”. We don't record which pages a signed-in visitor opens, and we don't tell the person who shared a page who viewed it, or who tried to and was turned away. The one exception is a request you choose to send: if you can't open a page and click “Ask for access”, we store your request (your email address, the page, and when you asked) and email your address to the page's owner so they can add you. Nothing else you write goes with it. We delete the request once your address is on the page's list (within two days of the owner adding you), and otherwise 30 days after you asked.
If you ask for a sign-in link by email, we keep the address you typed with the link until the link is used. A link nobody uses expires after 15 minutes and is deleted within about an hour of that. To limit how many links can be sent to one address, we also keep a scrambled form of the address for 24 hours; it can't be read as an address. That applies whether or not the address has an account. When a link signs you in, we note that the session started from a link, for as long as that session can open a page shared with you. The page that says a link was sent has buttons that open your mailbox on the web. The Gmail one includes the address you typed, so Gmail opens the right account; it reaches Google only if you press the button.
IP addresses are processed to apply rate limits and prevent abuse, and aren't stored for visitors who don't sign in. When anyone signs in — to publish, or to open a page shared with them — the session we create records the IP address and browser it was created from.
Abuse reports
When you report a page with our report form, we store the link you reported, the email address you give us, and what you tell us about the page. We use them to review the report and, if we need more detail, to contact you about it. Each report also reaches our team by email, through Resend.
When we refuse to publish a page because it sends a password to another site, we keep a copy of the page and which account sent it, as a record of the decision. Deleting your account unlinks the copy but doesn't delete it.
The assistant on our site
Our marketing pages have an assistant that answers questions about sharable.link. When you ask it something, we store your question, the answer, and which of our pages you were on, and keep them for 90 days after your last message. Then they're deleted. We use them to see what people ask and to improve our guides. The answers are written by Anthropic's Claude, so Anthropic processes the conversation to write each answer. For questions about Claude, HTML or publishing that our own pages don't cover, the assistant may search the web; the search runs through Anthropic and is built only from what you typed, never your IP address or account.
Your first question sets a cookie, sl_assistant, that holds a random ID for 30 days. It keeps the conversation going as you move between pages, and it lets us count whether people who asked a question went on to create an account. If you then create an account, we record only the day that happened, not which account it was, and we don't store your name, email address or IP address with the conversation.
If the assistant can't answer, you can choose to send your question to our team, and add your email address if you'd like a reply. It reaches our team by email, through Resend. We don't store your address with the conversation. To have a conversation deleted sooner, email nazar@sharable.link with what you asked and roughly when.
Email we send
When you create an account to publish, we send a welcome email to the address your provider confirmed. If your account still has no pages a day later, we send one reminder. If you created your account only by signing in to open a page shared with you, we send neither. If someone asks for access to a page you shared with specific people, we email you their address, at most 5 of these emails a day. If you ask for a sign-in link, we email it to the address you typed, whether or not it has an account; Resend keeps a copy of that message and records whether it was opened. All of these come from nazar@sharablelink.com, through our email provider, Resend. We keep a record of that reminder (when we sent it, and which version) so it's never sent twice, and the record is deleted with your account. The reminder asks why you haven't published yet. If you pick an answer, we store it with your account, along with anything you add, so we know what to fix; it's deleted with your account too. Some emails that bounced were sent once more, and we keep a record of each of those too, deleted with your account. Resend records when these emails are opened and, for some of them, which links are clicked, along with the IP address and device that opened them. We use this only to see whether our emails arrive and get read. Replies to nazar@sharablelink.com are stored with Resend.
Now and then we also email people who created an account to publish about what's new: features, guides and posts from our blog. They come from nazar@sharablelink.com, through Resend, which records opens and clicks on them in the same way, and we use that only to see whether they arrive and get read. We choose who gets them only from your account details, such as that you created the account to publish and when, never from what you publish. If you created your account only by signing in to open a page shared with you, you don't get them. Every one has a link to stop them, or you can reply and ask. We keep a record that you opted out, so you don't get them again, and it's deleted with your account.
Cookies and analytics
We set no cookies on shared pages and add no third-party trackers to them. A shared page is its author's own content, though: it can keep data in your browser, and anything its author put in it, such as a YouTube video, comes from that service and follows its rules. Signing in to open a page shared with specific people sets a session cookie on sharable.link, so you stay signed in. Opening a sign-in link sets one more, __Host-sl_press, for an hour: a random value that lets only the browser that opened the link use it.
Our marketing pages (homepage, blog, use cases, install guide) use Google Analytics and Vercel Analytics for aggregate traffic statistics, and so do the rest of sharable.link's own pages (not shared pages), including the ones where you sign in, approve a connection to Claude or another app, and manage your pages. These services may set cookies. If you block analytics cookies, the site still works. Asking the assistant on our marketing pages sets the sl_assistant cookie described above.
Our marketing pages also set one cookie of our own, sl_src, for 30 days. It notes how you first found us: the name of the site you came from (not the page), the campaign tags in the link you followed, if any, the first page you saw here, and when. We use it to see which channels bring people to sharable.link. If you create an account while you have it, we keep what it noted with your account, and delete it with your account. Sign-in, your dashboard and the pages people publish never set it.
Liking a use case or one of its examples sets one more, __Host-sl_like, for a year. It holds a random ID, and we keep that ID with what you liked and when, so one browser counts once and you can take a like back. It isn't tied to an account or an IP address, and it's only set when you like something.
Where data is stored
Page content and metadata are stored on infrastructure operated by Vercel Inc. (United States). Email is sent through Resend, which processes it in the United States and the EU (Ireland). Questions to the site assistant are processed by Anthropic (United States) to write the answers. By using sharable.link you consent to data being processed in the United States and, for email, the EU.
Sharing with third parties
We do not sell, rent, or trade your content or any data we collect. We share data only with the infrastructure providers we use to run the service (Vercel, Resend for email, and Anthropic for the site assistant's answers), with a page's owner when you ask them for access to it (your email address, nothing else), with an app you connect (what you approved when you connected it), with Google when you press “Open Gmail” after asking for a sign-in link (the address you typed, nothing else), with Google through Google Analytics on our own pages (see “Cookies and analytics”), and when required by law.
Your rights
You can remove any page you published at any time using your delete key. Lost the key? Contact us and we'll help.
You may also have rights under your local data protection law (GDPR, CCPA, etc.) to request access, correction, or deletion of personal data. For most visitors we hold no identifiers, so these requests mostly apply to content you yourself published — which you can delete at any time without contacting us. If you asked the site assistant something, your conversation is tied only to the random ID in its cookie, so email us what you asked and roughly when, and we'll find and delete it. If you signed in, your account holds your name and email address. You can delete it yourself from your dashboard — that removes your account, the pages you published, and any connection to Claude or another app.
Changes to this policy
We'll update this page if our practices change. The effective date at the top will reflect the latest version.
Contact
To report a page, use our report form. Questions or requests: email nazar@sharable.link.