Security and data
Where your data lives
and who processes it.
Where the data lives, who processes it, how an access is closed and how you take everything with you.
Who touches the data, one by one
The full list of who processes your data and why.
| Provider | What it does | Where |
|---|---|---|
| Hetzner | Servers, database and audio file storage | Germany |
| Stripe | Payments for your subscription and your sales | Ireland, US group |
| Fatture in Cloud | Issues the invoices for your Fonaria subscription (not those for your own sales: you issue those) | Italy |
| Our own mail server | Sending invitation and service emails | Our infrastructure, Europe |
Stripe is the only part of the chain with an American parent company, and it is there because no equivalent European alternative exists for card payments. It does not receive your content: it receives payment data, as your online shop would. The same holds the other way round: your customers' money goes to your own Stripe account, we hold no money of yours and card details never enter our systems. On request we provide the up to date list of sub-processors with their purposes.
How access to a private podcast works
This is the part that really matters, because a podcast app does not log in: it makes a request with an address, and that is all. The whole system is built around that fact.
- Every listener gets an address with a personal token, different from anyone else's
- The token can be revoked at any moment, and from then on the feed stops answering
- Audio files are not directly reachable: every download goes through a signed address that expires
- Drip and expiry do not just hide episodes in the feed: an address saved yesterday will not download what is not unlocked today
- If one address is used from too many countries or apps within hours, we warn the creator, who decides what to do
Your listeners' data
It is yours and we process it on your behalf.
- We do not profile your listeners and we sell data to nobody
- The IP address is used to derive the country and is not kept
- There are no third party cookies on listening pages
- If you add a marketing pixel to your own sign-up and sales pages, it loads only after the person consents
- When one of your customers asks for erasure, we delete their personal data and keep only what tax law requires
If one day you leave
What happens if you cancel.
- Export episodes, feeds and subscribers whenever you want, including while you are a customer
- On cancellation your listeners' feeds stay active for ninety days, so nobody finds the podcast switched off without warning
- Your customers and their emails are yours: we do not contact them, do not reuse them, they are not ours
- Payments already go through your own Stripe account, so there is nothing to unlock or transfer
Where the protection ends
What the protection does not cover.
- Revoking stops requests from that moment on. A file already downloaded stays on the phone of whoever downloaded it, and no system on earth can take it back.
- If you change an intro or an outro, the new version applies to the audio we serve. The copy already downloaded stays as it was.
- Drip, on the other hand, holds even on saved addresses: an episode that is not unlocked yet will not download, not even reusing yesterday’s address.
- If an address starts circulating (too many countries or apps within hours) we tell you. We do not block on our own: the decision stays yours.
Sold content can always be copied. What we can give you is an alert when an address spreads and the revocation of one access at a time.
What we do not do
- We do not sell or pass on your listeners' data
- We do not use your content to train our models or anyone else's
- We do not put advertising inside your feeds
- We do not contact your customers to sell ourselves to them
- We do not hold your data export hostage to keep you
Questions on security and compliance
Are you controller or processor?
Can you provide a data processing agreement?
What backups do you take, and where?
What if someone downloads the episodes and redistributes them?
If something here does not add up, ask
We answer ourselves.
No card required