Privacy Policy

1Who is responsible

Quiet Digest is run by Max Luong, an individual based in Vietnam. There is no company behind it and no data protection officer; the operator answers privacy questions personally at support@quietdigest.com.

The service is in a pre-launch private beta. At the time of writing, the only personal data most people have given us is an email address on the waitlist.

2What we collect

Only what the service needs in order to work. There is no advertising and no profiling, and nothing here follows you to other websites.

• Waitlist email address, if you asked to be notified at launch.
• Account email address, used to sign in via a one-time link.
• Your Kindle delivery address. This is a second, separate address, and it is where digests are emailed.
• The links you save, and the content fetched from them: article text, page titles, images, and transcripts of YouTube videos.
• The digests generated for you, stored so you can download them again.
• Your schedule: delivery hour, timezone and cadence.
• If — and only if — you agree to it, which pages you visit and which features you use. Never what you save or read.
• Your plan, credit balance and usage counts.
• Ordinary server logs (IP address, timestamp, request path), kept for security and debugging.

3Your reading list is sensitive, and we treat it that way

A list of what somebody chose to read can reveal their politics, their health, their religion, their finances and who they are worried about. For Quiet Digest that list is not a side effect. It is the entire input.

So: we do not sell it, we do not share it with advertisers, we do not build a profile from it, and we do not use it to train anything of our own. Access is limited to the operator, and only where operating the service or answering your support request requires it.

4Why we process it

Each category has one purpose, and it is the obvious one.

Account and Kindle email

To sign you in and to deliver your digests. Without them there is no service to provide.

Saved links and content

To fetch, rewrite and assemble the EPUB you asked for. This is the service itself.

Schedule, plan, credits

To send digests when you asked and to apply the limits of your plan.

Logs

To keep the service running and to investigate abuse or failures.

Waitlist address

To send you one message when Quiet Digest opens. That is the whole purpose: no newsletter, no marketing, and never passed to a partner.

5Who else sees it

Quiet Digest cannot do its job without sending content to other companies. These are the ones involved, verified against the running production configuration rather than against our own documentation.

OpenAI

Receives the extracted text of the articles and transcripts you save, in order to rewrite them for reading. What OpenAI may do with content sent through its API is governed by OpenAI's own policy. We link it rather than paraphrase it, because it is theirs to change. OpenAI privacy policy

Supadata

Receives the URL of a YouTube video you save, and returns its transcript. Supadata privacy policy

Supabase

Hosts the database and handles sign-in. Holds your account, links, content and digests. Servers in Singapore.

Resend

Sends the email carrying your digest, which means the EPUB passes through it on the way to Amazon. Servers in Tokyo.

Google

If you allow analytics, receives which pages are visited and which features are used, under a name from a fixed list rather than the real address. It never receives your links, your reading, your email or your Kindle address, and nothing sent to it is tied to your account. Servers in the United States. Nothing at all is sent unless you agree. Google privacy policy

Railway

Hosts the application and background workers. Servers in the United States.

Amazon

The final destination you chose. Your digest is emailed to your Kindle address, and from that point Amazon's own terms and privacy policy apply to it.

6Where your data goes

The operator is in Vietnam, but none of the infrastructure is. As the table above shows, your data is stored and processed in Singapore, Japan and the United States. Using Quiet Digest means accepting that it leaves your country and ours.

7How long we keep it

Until you ask us to delete it. Quiet Digest does not yet run an automatic deletion job, and we would rather say so than publish a retention window the system does not enforce.

Write to support@quietdigest.com and we will delete your account, your saved links, the content fetched for them and your generated digests. Deletion is done by hand, so allow a few days. Server logs age out of the hosting provider's own retention and are not kept beyond it.

Building self-service deletion is on the list before launch. When it exists, this section changes and the version at the top of the page changes with it.

8Your rights

Write to support@quietdigest.com to ask for any of the following and we will act on it, wherever you live. They are all reasonable things to want.

• A copy of what we hold about you.
• Correction of anything that is wrong.
• Deletion of your account and everything attached to it.
• Removal from the waitlist, at any time and without giving a reason.
• An explanation of anything on this page that is unclear.

9Cookies and analytics

Reading this site sets no cookies and creates no identifier for you, and the app at app.quietdigest.com has no analytics of any kind — nothing there reports to another company, ever.

On this public site only, and only if you agree to it, we use Google Analytics to see how many people visit and roughly where from. Nothing is loaded from Google and nothing is sent to them until you choose Allow on the bar at the bottom of the page. Choose No thanks and nothing loads at all — not a reduced version, not an anonymous ping. Your answer is kept in one small cookie holding a yes or a no and nothing else.

If you do allow it, Google receives which page you are on, and the coarse things any website sees: approximate location, language, browser, and the link that sent you. It never receives your email, and it is never loaded on the app, so it cannot see a single thing you save or read. We do not use it for advertising and we build no profiles.

We do count pages. When you open the landing page we record that a view happened, along with the campaign tag in the link you followed, if there was one. That record contains no identifier, so it cannot be connected to you or to any other page you open. It tells us a post somewhere sent forty people; it cannot tell us who they were.

If you arrived from a tagged link, that tag is also kept in your browser's session storage until you close the tab, so that it is still attached if you sign up a few minutes later. It is a note about where the visit came from, not about you, and it never leaves your browser unless you submit the form.

If you join the waitlist, that changes, and only then. Submitting the form creates a random identifier — a number that means nothing outside our own database — and stores it in a cookie for 90 days. We use it for one thing: to see which channel a signup came from all the way through to someone finishing their Kindle setup, so we know which places are worth posting in. It is not your email address, it is never shared, and it is not used to follow you to other sites. The cookie covers quietdigest.com and app.quietdigest.com so the two halves of that count line up. Clearing your cookies removes it, with no effect on your place on the list.

Being specific about what that identifier is attached to, since "we count signups" would undersell it: we store one row for each of four things — joining the waitlist, answering the optional questions, downloading a sample edition, and finishing your Kindle setup — and each row holds that identifier, which page it happened on, the campaign tag if there was one, and the time. That is the whole record. There is no page-by-page browsing history, nothing about what you read or save, and no profile assembled from any of it. We keep these while the pilot is running and delete them when it ends; ask us sooner and we will delete yours.

The optional questions after you join — which Kindle you have, how often you read on it, where your unread links pile up — are stored with your waitlist entry. They are genuinely optional: skipping them is a complete signup and changes nothing about your place on the list. We do not ask to interview anyone, and there is no field for it.

The application at app.quietdigest.com sets cookies for one purpose: signing you in and keeping you signed in. That means the session cookie, plus a short-lived verifier cookie that lives from the moment you request a sign-in link until you use it, and proves the link was opened by the browser that asked for it. Both are strictly necessary. Neither is shared, and neither is used to follow you anywhere.

Changed your mind? Clear the cookies for this site in your browser and the bar comes back, so you can answer again.

10Security

Traffic is encrypted in transit. The database enforces row-level security so one account cannot read another's data, and the public waitlist form can add an address but can never read the list back.

No service can promise it will never be breached, and this one is run by one person. If a breach affects your data, we will tell you at the address on your account.

11Children

Quiet Digest is for adults: you must be 18 or older to use it. We do not knowingly collect data from children, and if we learn we have, we delete it.

12Changes to this policy

When this policy changes, the version and effective date at the top change with it, and the superseded text is kept so it stays possible to establish which version applied at a given time.

If a change materially affects how your data is handled, we will email the address on your account before it takes effect.

13Contact

For anything about privacy, whether a question, a request or a complaint, write to support@quietdigest.com. It reaches Max Luong directly.