Privacy
Last updated 24 October 2026
ashare.net is run by a private person, the operator, not a company. The operator decides what the service stores and why, and is the controller of your personal data under the GDPR. Write about anything to do with your data to abuse@ashare.net. There is no data protection officer: a service run by one person does not need one.
What is stored and why
- Documents: every version and file as published, the title, dates, a view counter and the settings of the document. To host and show them: the service you asked for. Everyone who opens a document sees the name on its publisher's profile and their email next to the title.
- Comments: who wrote it, the text, the quoted fragment and the time. You comment signed in: a comment goes under the name on your profile, or under your email when there is none, and keeps your email too. Everyone who can open the document sees the name and, on pointing at it, the email, as in Google Docs. To show them with the document and to its owner.
- Reports: the reason, your email if you leave one, and your IP address, so the operator can tell a real report from a flood.
- Support messages: what you write on the Support page goes by email to the operator's mailbox with your email and name, so the operator can answer you; ashare itself does not keep it. A letter to support@ashare.net goes to the same mailbox.
- Accounts: your email, when you signed up, and your API keys as one-way hashes with their names and dates. Apps you connected with Sign in, like claude.ai: their name, when you connected them, when they last worked, and their tokens as one-way hashes. A sign-in code is kept as a signature for 10 minutes. If you sign in with Google or Microsoft: which of the two, the account id it gives ashare, the email it confirmed the first time, and your name from it when your profile has none. ashare never sees your password there. Your notification settings: whether to email you, and the Slack or webhook address you entered. The name you set on your profile, which signs your replies, and your defaults for new documents. Where you came from, if your browser kept it (see Cookies): the tags of the link of your first visit, such as
utm_source, or the site that linked to ashare. - Access lists: for a private document, the emails its owner let in; the owner gives them to ashare, not the people on the list. To open it, a reader signs in with a code sent to their email, as above, and comments under that email. A reader off the list may ask the owner in: their email, message and the owner's answer are kept with the document.
- Organizations: the name and short name of an organization, its members with their emails and roles, its company domains, and invitations: the invited email and when, for 7 days or until accepted. Whoever signs in with an email on a company domain joins that organization as a member automatically; when no organization holds the domain, ashare creates one named after it with them as its owner. Its other members then see their name, email and role, and they open its company documents.
- Who viewed: when you open a private or company document signed in and you are not its owner, ashare records your account, the first and the last time and how many times. The owner of the document sees your email with those times on the document's page, in the API and through their agent. The viewer tells you so in the comments panel: “The owner sees that you opened this document”. Public documents record nobody, only the total count of views.
- Billing: your plan, and if you pay for Pro, the ids Stripe gave your customer record and subscription, its status and when the paid period ends. For a company: the same ids, its trial and billing status, the currency it pays in, and how many domains and storage packs it pays for, which ashare sends to Stripe as the quantities of its subscription; the billing page shows the members the company's domains, its storage and its monthly bill. Card details, the billing address and invoices stay with Stripe, which takes the payments under its own privacy policy. The country Cloudflare reports for your connection picks euros or dollars for the prices; ashare does not store it.
- IP addresses also limit how often one address can comment, try a password, sign in or send a report. For that they are not saved.
- Technical logs: Cloudflare, which runs ashare, logs requests to the service (time, address, path, errors), which may include your IP address.
Your email is needed for an account and to open a private document: without it ashare cannot sign you in. Everything else is up to you: the name on your profile can be any name, the email on a report is optional.
Legal bases
- The service you use, Article 6(1)(b): accounts, sign-in, documents, comments, sharing, notifications, organizations, plans and payments. The terms apply to everyone who publishes, opens or comments.
- Legitimate interests, Article 6(1)(f): the interest of a document's owner in sharing it with the emails they choose and in knowing who opened what they shared privately; the interest of a company in giving its people its documents and paying for them; the interest of the operator in knowing which links and sites bring new accounts; the interest of everyone in a service without abuse: reports, rate limits, bans and technical logs. You may object to these, see your rights below.
- Legal obligations, Article 6(1)(c): payment records that tax and accounting law requires Stripe to keep, and answers to lawful requests of authorities.
Nothing is based on consent: there is no tracking to consent to.
Who sees what
A private document and its comments are visible to its owner and the emails the owner listed; a company document also to the members of the owner's organization and the emails on its domains; a document the owner made public is visible to anyone with the link, comments and names included. The owner of a document may get every new comment, with your name and the quoted fragment, by email, in their Slack or at a web address they chose. The operator sees everything listed above. Nothing is sold or shared with anyone else, unless the law requires it.
Service providers and transfers outside the EU
- Cloudflare hosts ashare: the Worker that runs it, the database (D1), the file storage (R2), the letters ashare sends (Email Service), forwarding of abuse@ashare.net to the operator's mailbox, and the libraries Markdown documents and the version comparison load from cdnjs.cloudflare.com.
- Stripe takes payments for Pro and for companies.
- Google and Microsoft, only if you choose to sign in with them. They then know you signed in to ashare, under their own privacy policies.
Cloudflare and Stripe process data for ashare under their data processing agreements. Cloudflare serves every request from its global network, close to where you are, and the database and files may be stored outside the European Union, including in the United States. Cloudflare, Stripe, Google and Microsoft are US companies certified under the EU-US Data Privacy Framework, for which the European Commission adopted an adequacy decision in July 2023; the data processing agreements of Cloudflare and Stripe also include the Standard Contractual Clauses of the European Commission. Their texts are on the providers' sites; ask at abuse@ashare.net if you cannot find them.
A document itself may load scripts, fonts or images from other sites, for example a chart library from a CDN; those sites then see your request. That is up to the document's author.
How long
- A document stays until it is deleted. If the owner set an expiry, the link stops working at that time, and 30 days later the document is deleted for good with all its versions, comments and reports.
- Comments, reports, access lists, access requests and the record of who viewed are deleted together with their document.
- An account stays until you delete it on your profile page, and the deletion is immediate: its sessions, keys, connected apps, Google and Microsoft sign-ins, notification settings, every document of yours with all its versions, files and the rows above, the record of what you viewed, your place in an organization and an organization you are alone in. The files leave storage in the same step. You can also ask at abuse@ashare.net. Leaving a company deletes your account the same way, and so does the owner or an admin of your company removing you.
- Comments and access requests you left on other people's documents stay with those documents, as part of their threads. Ask at abuse@ashare.net to have them removed.
- A sign-in code lives 10 minutes; the email of a sign-in that was never finished is deleted within a day. A session lasts 30 days or until you sign out. The tokens of a connected app expire within 30 days unless the app keeps using them; revoked and expired ones are deleted daily. Invitations to an organization last 7 days.
- The record of the letters ashare sent about an account, a company or a share (which letter, about which account, document or email, and when), which keeps each from going twice, is deleted after 30 days, and at once with the account.
- Stripe event ids, which keep a payment event from being applied twice, are deleted after 30 days. Stripe keeps payment records as long as tax and accounting law requires.
- Cloudflare keeps technical logs for up to 7 days. The database keeps a recovery history for 30 days (Cloudflare D1 Time Travel): the operator uses it only to restore the service after a failure, and deleted data leaves it after 30 days.
- A document taken down after a report is out of view but stays stored until it is deleted.
- A revoked key stops working at once.
Cookies
ashare sets only the cookies it needs to work, all on ashare.net only, all HttpOnly, none for tracking:
| Name | What for | How long |
|---|---|---|
ashare_session | Keeps you signed in. Holds a random token; ashare keeps only its hash. | 30 days or until you sign out |
ashare_pw_<id> | Lets you into a document with a password after you enter it. Holds a signature, not the password. | 7 days |
ashare_auth_google, ashare_auth_microsoft | A one-time check while you sign in with Google or Microsoft, against forged sign-ins. | 10 minutes, deleted when you come back |
Documents open on c.ashare.net, which sets no cookies: a private or password-protected document gets there with a signed link that works for 10 minutes. Other sites set their own cookies under their own policies: Stripe on checkout.stripe.com and billing.stripe.com while you pay or manage billing, Google and Microsoft on their sign-in pages. Cloudflare may set a security cookie such as __cf_bm when it screens traffic for bots.
That is why there is no consent banner: every cookie above is strictly necessary for something you asked for, and the law needs no consent for those. Should ashare ever add a cookie that is not strictly necessary, it will ask first.
Pages of ashare.net also keep one entry in your browser’s local storage, ashare_src: the tags of the link you first came by (utm_source, utm_medium and the like) or the name of the site that linked here, and when, for 30 days. It is not a cookie and is never sent with your requests. When you create an account, the sign-in form sends it once and it is saved with the account, so the operator knows which links bring people. Clear it with your browser’s site data for ashare.net.
Your rights
- Access and portability: download everything your account holds on your profile page, Download my data: a ZIP with your profile, settings, comments and access requests as JSON and every version and file of your documents as published, once an hour. For anything not in it, write to abuse@ashare.net.
- Rectification: change your name on your profile page and your documents through your agent or the cabinet. Your email is your account: another email is another account. Anything else, write to us.
- Erasure: delete your account on your profile page, at once and for good. A comment, a report or an access request about you elsewhere: write to us.
- Restriction and objection: write to us. Processing based on legitimate interests stops unless the operator shows compelling grounds, for example a report of abuse that has to be handled.
- Complaint: you may complain to a data protection supervisory authority, in particular the one of the EU country where you live, work or think the problem happened.
Write from the email of your account, so the operator knows it is you. The answer comes within one month.
Age
ashare is not for anyone under 16. If you are under 16, do not create an account or send personal data. An account found to belong to someone under 16 is deleted.
No tracking, no automated decisions
No third-party analytics, no ads, no tracking cookies on ashare pages, no profiling. The one thing ashare notes about how you found it is the link or site of your first visit, kept with your account, see Cookies. There is no automated decision-making with legal or similarly significant effects on you. The one automatic step is joining the organization of your email domain, and it goes by the domain alone.
Changes to this policy
The date at the top shows the last change. A significant change is announced on this page and on the sign-in page before it takes effect. Using the data for a new purpose comes only after such a notice.
Contact
To have a comment, a report or anything else about you removed, and for any question about this page, write to abuse@ashare.net.