effective November 2026; the watch app added
Paper is an Android launcher. It contains no analytics, no advertising, no tracking, and no accounts. The app sends nothing to anyone: no usage data, no identifiers, no crash reports. Everything it knows — your favorite apps, your book and reading position, your notes, your settings — is stored only on your device, with one exception you choose: your own watch, described next.
Paper on your watch — if you install the Paper watch app, the launcher sends the book you are reading to that watch: its title, the few lines at your place, the chapter's name, how far into the chapter you are, and the minutes left in it. The Five Lines and Bookmark watch faces show them. They travel over the Wear OS connection between your phone and your watch, which Google Play services provides and which can pass through Google's servers when the two are not near each other. They go to no server of ours, and without the watch app nothing is sent. The Paper watch faces themselves contain no code and collect nothing.
The website counts its visits itself, without cookies and without keeping your IP address; how is under Visitor statistics. Beyond that it collects two things, and only if you ask it to: the email address you type into the signup form, and, if you sign in to the requests board, what the board needs to count your votes. Each has its own section below, and together they are the whole of it.
Query installed apps — Paper is a launcher; listing your apps is its job. The list never leaves the device.
Calendar, contacts, notifications, usage access, location (coarse) — each powers one optional feature (the calendar line, contacts in search, correspondence on the home page, the screen-time line, the weather line). All are off by default, each is read only when you switch its feature on, and none of this data is transmitted or stored off the device.
Internet — used by three things: the weather line (off by default; a keyless request to Open-Meteo with your coarse position), the custom line (off by default; a request to a web address you choose), and the list of feature requests in the welcome and at the top of Settings, read from paperlauncher.app. That request carries no cookie, account or identifier; like any web request, it reaches the server with your IP address. Voting and suggesting happen on the website, not in the app.
The one purchase — after fourteen days, the book and the slowing-down features are a single in-app purchase. Google Play takes the payment under its own terms; Paper only learns whether it was bought, and keeps that one yes or no on your phone.
The form at paperlauncher.app keeps something about you only if you type into it.
What is kept: your email address, the sentence you wrote about why you want to test, the date, and a one-way hash of your IP address — enough to show a signup came from somewhere, not from whom. Also kept is where your visit came in: the page it started on, the site that linked to it (its address only, no path), and any campaign tags in the link. That shows which ways in lead to testers, and it is never added to the visitor statistics below.
What it is used for: one email when Paper goes on sale, and an invitation to the test if there is room. Nothing else. No other sender uses this list, it is not shared, it is not sold, and there is no advertising anywhere near it.
Who else touches it: the list itself lives at Resend, who send the mail, on their servers in the United States; the written records sit in Google Cloud Storage in the EU. Both act only on instructions, and neither may use the addresses for anything of their own.
Getting off it: every email has an unsubscribe link, and one click is the end of it. To have the record deleted as well, write to [email protected] and it goes the same day. Everything is deleted anyway once Paper has shipped and the announcement has gone out.
The legal basis is your consent, given by pressing the button under a sentence that says what you will get. That sentence is stored with your entry, so what you agreed to is a matter of record rather than of memory.
paperlauncher.app/requests is a list of things people want Paper to do. Reading it needs nothing. Asking for something or voting needs a Google sign-in, so that one person counts once.
What is kept: when you sign in, Google hands this site a signed note saying which account you are. The site checks it and keeps one thing from it: the number Google uses for your account. Your name, photo and email address are in that note too, and none of them is stored. Next to that number the board keeps each vote you cast and each request you write, with its date.
The cookie: signing in sets one cookie, which holds that same number and keeps you signed in for twelve hours. Nothing is set if you only read, and signing out removes it.
What others see: a request appears on the board only after it has been read and approved, and it may be shortened or reworded on the way. The board never shows who wrote a request or who voted for it.
Who else touches it: the board is stored in Google Cloud Firestore, in the EU (Belgium, europe-west1). The sign-in button is Google’s own and is loaded from Google, so Google knows you signed in here; that part is covered by Google’s privacy policy. To slow down scripts, the server also counts, in memory and for at most an hour, how often an account or an IP address has posted. That count is never written down.
Getting it deleted: while you are signed in, the board has a “forget me” link. It takes back every vote you cast and deletes any request of yours that is still waiting. A request already on the board stays, because other people voted for it, but nothing links it to you any more. The board stores no email address, so a request by email cannot be matched to an account; the link is the way to do it. For anything else, write to [email protected].
The legal basis is your consent: nothing is stored until you choose to sign in, and “forget me” withdraws it.
Every visit to paperlauncher.app is counted by the site's own server. No analytics company is involved and no cookie is set.
What is sent: the page you opened, the site that linked to it (without anything after a question mark), campaign tags in the link (utm_source, utm_medium, utm_campaign), and your browser's time zone and language. From the browser's User-Agent the server notes the kind of device, the browser and the operating system; from the time zone, a country. No address is ever looked up to find where you are.
Counting people without remembering them: to count visitors rather than page loads, the server hashes your IP address and User-Agent together with a random value that is replaced every day, and the old value is deleted. The same browser looks alike for one day and never again. Your IP address itself is not stored, and nothing is stored in your browser for this.
If you say yes: on a first visit the page asks whether it may keep two random numbers in your browser’s local storage (not a cookie): one for the browser and one for the visit, so that coming back next week counts as coming back. With that yes it also remembers where your first visit came from, for the signup form above. Saying no, or not answering, changes nothing else on the site. The “visit statistics” link at the bottom of the home page, or this one, asks again; saying no deletes the numbers.
Where it goes: Google BigQuery, in the EU, in a Google Cloud project that exists only for this site. Only the developer can read it, on a private page behind a Google sign-in. Rows are deleted after 24 months.
Counting rests on a legitimate interest in knowing how many people read this site and how they found it (Art. 6(1)(f) GDPR); you can object at any time by writing to [email protected]. The numbers kept in your browser rest on your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG), which the link above withdraws.
If a future version changes any of the above, this page changes with it, and the app's listing will link the current version.
Questions: [email protected]
paperlauncher.app