Privacy

The feed is built to know as little about you as possible. You don't need an account, and you never give your name unless you make a profile.

What the feed stores

An anonymous ID for this device. The first time you open the feed, your browser gets a random ID, kept in a cookie. It isn't linked to your name, email or anything else about you. Each device and browser gets its own.
When you visit, so the feed can mark the papers added since your last visit.
The papers you save and the filters you follow, so you can come back to them. They're kept with this device's ID, so another device or browser won't have them, unless you make an account.
Whether you chose “Top journals only” or “Past 2 weeks” for the front page, in two more cookies on this device.
Your sections, if you choose them: the topics in the bar at the top of the front page. They're kept in a cookie on this device and with this device's ID, or your account, so they follow you when you sign in elsewhere. Forgetting the device or deleting the account deletes them.
On your device only, if you use the app: its scripts and styles and a “You're offline” page, so it opens quickly, and whether you said “Not now” to it. None of this is sent to the feed.
Later, your notification settings, when that feature arrives.
Only if you allow it: which filters you use and follow, and which papers you open or save (abstracts, links to the publisher or PubMed, shares and saves), with the time. It shows what readers find useful. Nothing else is recorded: not what you type, not your device.

Your email and password, kept by Supabase, the database service. The password is stored scrambled, so nobody can read it.
Your email is your account's name. The feed never shows it or shares it, and writes to it only for what you ask: a link to confirm it when you make the account, and a link to choose a new password if you forget yours.
Your saved papers and followed pages are kept with the account, on every device you sign in on. Signing in adds the device's own to it.
If you allow sharing, what you share is linked to your account.
Deleting the account deletes all of it.

Your name, role, institution and country, as you enter them, a photo if you add one, and whether the profile is private. Your sections show on it as your interests.
A photo is made a small square, which strips anything else the file held, such as where it was taken. It's kept in Supabase's file storage, and only people who can see your profile get a link to it.
Everyone with an account can see it, unless you make it private, when only your colleagues can. It isn't on the open web, so search engines never see it.
Your colleagues, requests, invite link and the people you've blocked are kept with your account. Anyone with your invite link can see your name, role and institution.
Your messages to colleagues, with any paper you send in them, and when you wrote and read them, are kept until you delete them, or your account. Deleting a message deletes it for both of you. Deleting your account deletes your messages; the other person keeps theirs. Messages aren't end-to-end encrypted.
A report you make goes to the site's owner, with your name and what you wrote, and the message you're reporting if it's about one.
Deleting the account deletes your profile and all of these.

A device's anonymous ID is deleted after 90 days without a visit, with its visits, unless you saved papers or followed pages with it.
What you share, if you allow it, is deleted after 12 months.
An account and everything kept with it stay until you delete it.
A copy of the database, encrypted, is made each week, in case something goes wrong. Each copy is kept for 90 days, on GitHub and on the site owner's own computer, so a deleted account is gone from them within 90 days.

Vercel hosts the website. Its pages are made in Washington, D.C., and served from data centres near you.
Supabase keeps the database and runs signing in, in Northern Virginia, on Amazon Web Services.
Resend sends the site's two emails, from no-reply@dailypapule.com, in the United States. It sees the address each goes to.
GitHub keeps the site's code, and the weekly copies of the database, encrypted.

No name unless you make a profile, and no email unless you make an account.
No ads, and no tracking by other companies.
No IP addresses in the feed's own records. Like every website, the services that run it (Vercel and Supabase) keep their own security logs.

Nothing is stored for this device yet.