Privacy Policy

Last updated: October 23, 2026

1. Who we are

This Policy explains what data SecurePublish keeps and why, under Brazil's General Data Protection Law (LGPD, Law 13,709/2018). Privacy contact: [email protected].

For published content, you or your company decide what goes on the page. We store it and show it to authorized people in order to provide the service. You are responsible for having a legal basis for any personal data you include in that content.

2. What we store

We store the following:

Account record: email, domain and subdomain.
The published HTML, up to 3 MB per publication, stored on Cloudflare infrastructure (Workers KV).
Each link's title and name.
The list of invited emails for each link.
The email of the person who published.
The email of each person who opened each link.
The date of first and last access for each person on each link.
View counts.
Three first-time events, with a pseudonymized email: account created, first publish and first colleague open. In these events the email is stored as a hash (for first colleague open, the publisher's email). Pseudonymized data is still treated as personal data.
Daily counts with no personal data, such as the number of completed CLI logins (count only, no email).
Login codes and short-lived tickets, valid for up to 10 minutes.
Anti-abuse data, kept for up to 48 hours: counters by IP address, a counter of wrong login codes, and the hash used to count clicks on the "Create account" button on the landing page. The IP used in code login is kept for up to 10 minutes.
CLI token, saved on your own computer in the ~/.secure-publish folder.

In addition, our infrastructure provider (Cloudflare) may keep technical request logs for a limited period.

3. Strictly necessary cookies

We use only strictly necessary cookies and browser storage (localStorage and sessionStorage) that the service needs to work, so they don't require consent. We don't use advertising cookies or trackers.

Name	Purpose	Duration
`__Host-sp_session`	Keep you signed in (session)	up to 7 days without use, and 14 days at most
`__Host-sp_oauth`	Protect sign-in against request forgery (anti-CSRF)	10 minutes
`__Host-sp_handoff`	Hand your sign-in over to the address where the panel is shown	60 seconds
`sp-lang` (cookie, on the site securepublish.work)	Remember your language preference (pt/en) on the site	1 year
`sp-lang` (localStorage, on the console app.securepublish.work; same name, different mechanism)	Remember your language preference (pt/en) on the console	No expiry (stays until you clear your browser data)
`sp-me-view` (sessionStorage, on the console)	Hold the signed-in email, sign-in provider and account host only to render the screen	Cleared when the tab closes or on sign-out
`sp-demo-auth` (browser sessionStorage, not a cookie)	Simulate sign-in on the example/demo pages	Demo pages only, until the tab is closed
`sp-consent` (localStorage, on the site securepublish.work; not a cookie; value only `seen`)	Remember that you've seen the cookie notice. It stores no identifier.	No expiry (stays until you clear your browser data)
`sp-list-view` (localStorage, on the console app.securepublish.work)	Remember whether you prefer the list as rows or cards	No expiry (stays until you clear your browser data)

On your first visit to the site, we show a notice about these cookies. When you click "Got it", we save that choice in your browser so the notice doesn't appear again.

4. Measurement and third-party services

Cloudflare Web Analytics runs on the site and the console. It doesn't use cookies or identify individual visitors. It is not used on published pages.
Google Fonts: the site, the console and published pages load fonts from Google Fonts. When fonts load, Google receives the visitor's IP address and user agent (browser details), under Google's own terms.
We don't add any measurement to pages published by users.

5. What we use it for

To publish links and show them to authorized people.
To check whether a person opening a link is allowed (everyone at your company's domain, or only the people from your company you listed).
To show the publisher who opened a link and how many times.
To understand, in aggregate, whether the product works for new users.
To protect the service against abuse.
To meet legal obligations.

Legal bases (LGPD art. 7): performance of a contract, legitimate interest (security and operation of the service), and compliance with legal obligations.

6. Who can see it

People who open a link see the published content. The publisher sees the emails of who opened it, the access dates and the counts.
Our team may access stored data when needed to run the service, respond to a security issue or meet a legal obligation.
Cloudflare, our infrastructure provider (sub-processor), processes data to host and deliver the service.
Google Fonts receives the IP and user agent of whoever visits the site, the console and published pages, to deliver fonts (see section 4).
Authorities, when required by law.

We don't sell your data.

7. International transfers

Cloudflare and Google Fonts (used on the site, the console and published pages) may process data outside Brazil. In those cases, we aim to follow the LGPD rules on international transfers.

8. How long we keep it

Account, links, invitations and access records are kept until they are deleted.
When you delete a link via the CLI or console, usually it stops opening within about a minute, and the link and its access records are deleted.
There is no automatic account deletion today. Full account deletion (including your email in invitations and metrics records) is done by request to [email protected] and carried out manually within a reasonable time and within legal timeframes.
A person who opened a link and wants their own email removed from our records can make the same request, within the same timeframe.
Login codes, tickets and the IP used in code login: up to 10 minutes. Session and CLI token: up to 7 days without use, and 14 days at most. Anti-abuse counters and the "Create account" click hash: up to 48 hours.
Technical request logs kept by Cloudflare are retained for a limited period.

9. Your rights (LGPD)

You can ask, among other things, for confirmation that we process your data, access, correction and deletion. To do so, write to [email protected] from the email address concerned. We may ask you to confirm your identity first. Deletion requests are carried out manually within a reasonable time and within legal timeframes. You can also file a complaint with Brazil's data protection authority (ANPD).

10. Security

We require sign-in to open links and limit attempts to prevent abuse. No measure removes all risk. If a relevant incident affects your data, we will notify you and the ANPD as the law requires. To report a security issue: [email protected].

11. Changes

We may update this Policy. When a change is relevant, we will give reasonable notice — for example by publishing the new version on this page, in the console or by email.

12. Contact

[email protected]