Screenbreak privacy policy
1. Who we are
Screenbreak is responsible for your personal data (the "controller"; "we" in this policy).
Write to us at [email protected] about anything in this policy.
2. The browser extension
2.1 Where it works
- The extension works only on the tab where you click its button, its menu item or its shortcut. No code of it runs on a page before you click, and it does not watch your browsing.
- It asks your browser for access to all sites because an article's pictures, styles and frames often come from other sites. It uses that access only on the tab that you clicked.
- Without a click, it does three things only. It opens a welcome page once, when you install it. It asks our print service for an install token (section 2.4). It watches the sign-in tab that it opened for you, to know when you have signed in. It sends nothing about your pages.
2.2 When you click Print
The extension makes a simplified copy of the article page and sends it to our print service (app.myscreenbreak.com/api/v1/print/decide). The service finds the article and picks the design. Your browser then sets the pages and opens its print window.
The copy holds:
- the page's structure and text, also the parts that the page hides (such as menus), the sizes of its elements and the addresses of its pictures;
- its links (without tracking codes), its meta tags and its structured data;
- the page address, without the part after "?" or "#";
- numbers measured from each picture that you see on the page: its size, how many colours it has, how much of it is white, dark or transparent, and a small 16 × 16 map of where its detail is. The pictures themselves are not sent. The extension loads them from their own sites, in your browser.
The copy does not hold what you typed into forms, hidden form fields, passwords, cookies, scripts, or the content of frames from other sites. Pages on your own network (such as a router's page) are not sent.
The request carries your install token (section 2.4) and the extension's version. It does not carry your Screenbreak sign-in, and you need no account to print.
The print service does not store the copy. For each print, it writes one log line: the time, the extension's version, a short code made from your install token, the site's name (not the full address), sizes and counts, and how long the print took. The service uses your IP address only in its memory, to limit how many prints come from one place.
2.3 When you click Save
- Saving needs a Screenbreak account. The extension first sends the page's full address, its title and the size of the copy. If you are not signed in, it opens the sign-in page and sends them again every few seconds until you sign in, for at most 5 minutes. Until you are signed in, our server stores nothing.
- When you are signed in, the extension sends a full copy of the page as you see it: its text, its pictures and its styles, without its scripts. The copy is made by SingleFile, by Gildas Lormeau.
- We keep the copy in your library with its address, its title, the time, the extension's version and your browser's name and version (its "user agent"). Our server takes the article's text out of the copy for your library, its search and its prints.
- With the setting "Also save what I print" on, each print also saves the page.
- Save uses your Screenbreak sign-in, the same cookie as the app (section 6).
2.4 The install token
The extension asks our print service for an install token when you install it, and again when the token is older than 7 days. The token is a random code that our server signs. It is not linked to your account or to your name. The extension sends it with each print, and the print service uses it to limit how many prints one install can make.
2.5 What stays in your browser
The extension keeps these in your browser's own storage:
- your settings (what the button does, "Also save what I print", paper size, pictures, two-sided). If you use your browser's sync, your browser may copy them to your other computers;
- the install token;
- a list of at most 200 pages that you saved, each as a short code made from the page address and the id of the saved article, so that its pop-up window can show "Saved · Open";
- a few small notes, such as whether a tip was shown and when you first printed (never in a private window);
- while a print tab is open, the article and the print service's answer, in memory only (never for a private window).
When you remove the extension, your browser deletes all of these.
2.6 Who is signed in
When you open the extension's pop-up window, its Settings or a print page, the extension asks our app who is signed in, and the app answers with your name, your email address and your plan. If you are signed in, not in a private window, and the page is one that you saved, the pop-up window also asks the app if that article is still in your library. It sends the article's id. So we learn that you opened the pop-up window on that saved page.
2.7 When you remove the extension
Your browser opens our goodbye page, www.myscreenbreak.com/bye/, with the extension's version number in the address. The page sends nothing.
3. Your account
- To create an account, you give your email address, a password and your first name. You can add a last name. We keep your password only in a scrambled form (a hash), never as you typed it.
- If you sign in with Google or Facebook, we receive your name, your email address and the basic profile details that the service shares with us (for example the address of your profile picture). We keep them with your account.
- We also keep when you accepted the terms, when you first signed in, and when you last used the app.
- If you had a Screenbreak account before (2020–2025), your account and the articles that you saved with it move to the new Screenbreak.
- Why: to give you the account that you asked for (our contract with you).
4. Your library, booklets and print settings
- Your library holds the pages that you save (section 2.3), the text taken from them, and what you do with them: your booklets (their titles, articles and design choices), when you removed an article, and when you printed a booklet.
- Your print settings (paper size, two-sided, pictures, greys, design) stay with your account, so they follow you to another computer. Without an account, they stay in your browser.
- When you print from the app (one article or a booklet), our server sends the saved page to our print service, inside our own network, to pick the design. The service does not store it, and the app keeps the answer in its memory for a short time.
- Save PDF. Your browser sends the finished pages to our server, and our PDF service makes the PDF and sends it back to you. We do not store the pages or the PDF. The service's log keeps sizes, page counts and timings, not the text, the title or the address.
- When you remove an article, it goes to the Bin, where you can put it back for a time. Removed articles stay stored until you ask us to delete them. Email [email protected] to delete your account and its data.
- Other people cannot see your library. We look at it only when you ask us to (for example, to fix a problem that you report), to stop abuse, or when the law requires it.
- Why: to give you the service that you asked for (our contract with you).
4.1 Send to Kindle
You choose to connect a Kindle. Until you do, none of this happens.
- What we keep. Your Kindle's email address (the one that ends in @kindle.com), your Amazon store, when you confirmed it, your choices (the Sunday edition, new saves), and the word of your last test letter. You also get your own sending address (k-…@kindle.myscreenbreak.com). Amazon must have it on your approved list.
- What we send. When you send articles or a booklet, or when your Sunday edition is due, our server makes one e-book from the saved pages and emails it from your sending address to your Kindle's address. The email goes through Resend (section 10), and Amazon receives the book. Amazon's privacy policy applies to what it does with it.
- The delivery log. For each send we keep its title, the articles in it, its size, when it was asked for and sent, whether Amazon's mail server accepted it, and, if Amazon sent it back, Amazon's code and sentence. Amazon writes back to your sending address only when it refuses a book. We read those replies to show you what came back.
- Disconnect. Disconnect removes your Kindle's address. We keep your sending address (so that a new connection needs no new step on Amazon) and the delivery log, until you ask us to delete your account.
- Why: to give you the service that you asked for (our contract with you).
4.2 Your newsletter address
You choose to use your newsletter address (n-…@in.myscreenbreak.com). Until mail comes to it, we keep nothing but the address.
- Mail to your address. It comes to us through Resend (section 10). We keep each newsletter issue in your library, as a saved page: its text, the pictures that come inside the mail, the sender's name and address, the subject, the time, and the result of the sender checks (SPF, DKIM, DMARC). A short note of each mail (sender, recipient, subject, time, what we did with it) stays in our mail log.
- Mail that is not a newsletter (for example a receipt) is set aside. We keep it for a short time, then delete it, unless you file it in your library before.
- Confirmation mails. When a newsletter or Gmail asks you to confirm, we show you its link and its code. We never open those links for you. They stay until you press Done.
- Forwarding from Gmail. If you forward mail to your address, we see the Gmail address that it comes from.
- Your choices. Off refuses all mail to your address. A new address stops the old one at once. We keep the old address in your account, stopped, so that mail to it is refused, and for a time we show which newsletters still need the new one. Block keeps the sender's past issues and refuses new ones.
- Pictures. We leave out the pictures that a mail loads from the sender's site, so neither we nor you load them, and opening an issue tells the sender nothing.
- Why: to give you the service that you asked for (our contract with you).
4.3 Reporting a print problem
When you report a print problem, we keep the description, page address, print settings and technical details that you submit. If the report includes a page copy, that copy can contain the whole page, including private text and pictures. The report form tells you that we keep a copy to investigate the problem. These copies are private and are not published.
We keep the copy while the report is open. It becomes due for removal 90 days after closure; until that removal is processed it remains stored. Copies can also remain in database history and backups (section 9). You can contact us to request deletion. Report details and your contact address are kept separately from the page copy.
If you ask for a fix notification, we use your address to email you when the problem is fixed. The email can name the page, site and problem and link to its print page; it does not include the page copy. You can stop these notices from the email.
4.4 Print milestones and review or share prompts
When a supporting extension is used while you are signed in, it can report that you reached your 10th or 25th print, or clicked its review or share prompt. We keep the date when our app first receives each of those four reports, linked to your account. This does not send us an article, its address or title, or a log of every print for this purpose.
We use these dates to avoid repeating prompts and, only with your permission for tips and news and when those emails are enabled, to time optional review and share emails. We also keep whether each of those emails was claimed or sent so that it is not sent again. These records stay with your account; database history and backups are described in section 9. The milestone and click dates are not exported to the email contact list.
5. Emails
- We send account emails: the link to confirm your email address, the link to reset your password, and other messages about signing in to your account. You get them while you have an account.
- We send them through Resend (section 10). Resend also sends the books that you send to your Kindle and receives the mail to your newsletter address (section 4.1 and 4.2).
- If you said yes to hearing from us, we send occasional letters about Screenbreak. Every letter has a one-click unsubscribe link, and you can change your choice at any time.
- Why: account emails run your account (our contract with you). Letters: because you said yes (your consent). You can take it back at any time.
6. Cookies
- The app (app.myscreenbreak.com) sets one cookie,
sessionid, when you open its sign-in pages or sign in. It keeps you signed in for two weeks, unless you sign out (signing out ends the session), and it holds the security code of the app's forms. - The app can also set a short
messagescookie to show a notice on the next page. It is deleted when the notice is shown. - The extension uses the same
sessionidcookie when it saves and when it asks who is signed in. - The website (www.myscreenbreak.com) sets no cookies.
- We use no analytics, advertising or tracking cookies, and no tracking pixels. These cookies are needed for the service that you ask for, so we do not ask for consent.
7. Logs
Our servers keep technical logs to run Screenbreak and to keep it secure. A request can be logged with its IP address, the address asked for, the time and the browser. The app writes its errors to its log, with the method and the address of the request. Section 2.2 and section 4 say what the print and PDF services write to their logs.
Why: our legitimate interest in keeping Screenbreak working and secure.
7.1 Usage measurements
The app and website send a limited set of usage events to PostHog's EU service: actions such as opening a permitted app route or choosing a feature, and bounded counts and technical properties. We do not intentionally send your account identity, article text, titles, full page addresses, query strings or referrers. PostHog receives the network request, including its IP address and browser headers; this is not a promise of anonymity.
Our configuration uses no analytics cookies or browser storage, session recordings, person profiles or automatic page-content capture. The extension's goodbye page sends no analytics events. We use these measurements to understand which features work and where readers encounter problems.
8. Who else handles your data
- We do not sell your data, and we do not share it for advertising.
- Service providers that handle data for us: Cloudflare, Resend and PostHog (sections 7.1 and 10). We answer support email through our email provider.
- Google or Facebook, if you sign in with them. Their own privacy policies apply.
- Google Fonts, when the app's sign-in pages load its fonts (section 10).
- Amazon, when you send articles to your Kindle (section 4.1). Its own privacy policy applies.
- The senders of the newsletters that you receive at your newsletter address (section 4.2).
- The sites of the articles that you print or save. The extension and the app's print pages load an article's pictures from its own site, as your browser does when you read it.
- The authorities, when the law requires it.
9. What we keep, and deleting your account
- Your account, your library and your booklets stay stored until you ask us to delete them. This includes the articles and booklets that you remove in the app: Removed articles stay stored until you ask us to delete them.
- The app has no "delete account" button yet. Email [email protected] to delete your account and its data. Write from the email address of your account.
- Our database keeps a history of its changes, and we keep backups to restore the service after a failure. Deleted data can stay in them.
- The install token: 7 days, in your browser. The print service keeps no list of tokens.
- Logs: section 7.
10. Where your data is
Our application and database are hosted in Greece (European Union). We use Cloudflare for DNS and traffic proxying.
- Resend sends our account emails (section 5), the books for your Kindle and receives the mail to your newsletter address (section 4.1 and 4.2). Its data processing agreement says that its primary processing is in the United States (section 6.1), and it includes the European Commission's standard contractual clauses for transfers out of the EEA (section 6.2).
- You can sign in with Google or Facebook. If you do, that service handles your sign-in under its own privacy policy.
- The app's sign-in pages load fonts from Google Fonts. When they load, Google receives your IP address and your browser's details.
11. Your rights
You can ask us to:
- give you a copy of your data, in a common format;
- correct it;
- delete it;
- stop or limit a use of it, or object to it.
Write to [email protected]. We answer within one month. You can also complain to the Hellenic Data Protection Authority (https://www.dpa.gr), or to the data protection authority of the country where you live.
12. Children
Screenbreak is not for children under 16. We do not knowingly keep their data.
13. Changes to this policy
If we change this policy in a way that matters to you, we tell you by email or in the app before the change applies. The version and the date are at the top of this page.
14. Contact
Screenbreak
Email: [email protected]