Sloppod › privacy

Privacy

What Sloppod keeps, who else handles it, and how to have it removed. Last changed 15 September 2026.

Who is responsible

Sloppod is run by Refleksion · Planlægning · Handling, a small Danish company (CVR-no. DK45818659). It decides what is collected and why, and it is who you ask about anything on this page.

Write to inbox@sloppod.app. A person reads it.

If you only read or listen

Nothing about you is kept. There is no analytics script, no advertising, no tracking pixel, and no cookie. The same goes for a podcast app fetching a feed.

Cloudflare, which runs the site, writes every request to its own log, with the address it came from. That log exists whether or not anybody reads it. This site asks it for counts and nothing else: how many times each page was fetched on each day, and which countries the page views came from. Every count is added up across everybody. Nothing about a person, such as an address or a browser, is ever asked for. The daily counts are kept, so the site's owner can look back further than Cloudflare's own week. Nothing here counts a listen.

If you ask for an account

Sign-up is closed while Sloppod is small, so there is a waiting list. It keeps the address you give and the note you add, if you add one, and uses them to let you in. The entry goes when your account is made, or when you ask.

If you have an account

• Your e-mail address. The account is the address; there is no password. A sign-in code is e-mailed to you and kept only as a scrambled hash, for ten minutes.
• One cookie. It keeps you signed in and does nothing else.
• What you make. For each episode: the thread it came from, the script, the transcript, the audio, the choices you made, and what it cost to make.
• Your balance and settings. How many tokens you have used, any bonus you were given, whether your episodes are public by default, and the feeds you follow.
• Your private feed address. It contains a secret, so that a podcast app can fetch your episodes without signing in. Anybody you give that address to can listen.

The owner can see how many episodes each account made and what they cost. The admin pages do not show episode titles. Like the operator of any service, the owner could read what is stored, and does not go looking.

What becomes public

An episode is public unless you choose private, on the form or later from your episodes. A public episode has a page with its title, audio and transcript, and a link to the thread it came from, and it appears in the public feeds. Your address is never shown with it.

A thread about a private person's own situation comes out private whatever you chose, and you can share it afterwards if you judge it fair.

The people in the threads

Sloppod only reads posts that are public. The thread is kept as it was captured, in the episode's working files, which are never published. On Reddit and Instagram that includes the usernames. From Facebook no name is kept at all: the extension scrambles each one inside your browser before anything leaves it, and a thread fetched from a link has its names dropped before it is saved.

Before any language model sees a thread, every username is replaced with a stand-in such as u1 or u2. No episode names a commenter, and no page shows a username. If a thread you took part in was made into an episode and you want it gone, write to inbox@sloppod.app.

Who else handles it

Sloppod does not sell data or share it with anybody for their own use. Making an episode takes a few services, and each receives only what its step needs:

• Cloudflare runs the site and stores everything on this page. Its request log records the address a request came from, as every web server does, and keeps it for a few days.
• Google (Gemini API) reads the thread - its text, and the images in the post - and writes the script.
• Google Cloud Text-to-Speech speaks the script, for episodes made with Studio voices.
• OpenAI speaks the script, for episodes made with Deluxe voices.
• Microsoft speaks the script, for episodes made with Free voices, through the read-aloud voices built into Edge.
• Apify fetches a public thread when you paste its link rather than sending it from the extension. It is given the link, not you.
• Resend sends the e-mails: your sign-in code and your invitation. It is given your address and the message.

Only Cloudflare and Resend ever receive your e-mail address. The others receive the thread, or lines of the script, and nothing that says whose episode it is. Several of these companies are in the United States, so data can be handled there, under their own terms for business customers.

The browser extension

The Sloppod extension reads a page only when you click its button, and only the tab you clicked it on. It sends that post and its comments to Sloppod, or to the address you set in its options. It does not read your browsing history. It never reads your login cookies for the sites it reads, and never sends them to Sloppod.

It keeps its settings, a build in progress, and a count of what it has lent, in your browser's own extension storage. The counts stay there.

Its options page can also lend the browser to Sloppod: to read public Reddit threads in the background, and to make Free voices through Microsoft's read-aloud service. Both are off unless switched on, and each asks for its own permission. A browser that lends identifies itself with a random id made the first time it lends, so the queue can tell browsers apart. At present lending works only for the owner's own account.

How long it is kept

• Sign-in codes: ten minutes. Sessions: thirty days, renewed while you keep using the site.
• The waiting list: until your account is made, or you ask.
• Your account and your episodes: until you ask for them to be deleted.
• Cloudflare's request log: a few days, on Cloudflare's own schedule.
• The daily counts of pages and countries: kept. They say nothing about a person.

Your rights

You can ask to see what is kept about you, to have it corrected, to have it deleted, or object to how it is used. Write to inbox@sloppod.app. Deletion is done by hand, so allow a few days, and the account and everything in it goes.

Under the GDPR, an account is kept because you asked for the service, the waiting list because you asked to be on it, and the request log and the public threads under legitimate interest - keeping the site running, and making episodes out of what people chose to post in public. If you think this is handled wrongly, you can complain to the Danish Data Protection Agency, Datatilsynet.

Changes

When this page changes in substance, the date at the top moves. Nothing collected under an older version is used in a way the newer one does not describe.