Privacy policy
Broadcast · broadcast.roud.cz · last updated 1 September 2026
Who is responsible
Broadcast is operated by Tomáš Roud, roud.cz, Czech Republic. For anything in this document, write to tomas@roud.cz. The service runs on a private server in Lauterbourg, France, operated on rented hardware from Contabo GmbH.
Broadcast is a private sending service, described on the home page. It has no public users and no sign-up: the only parties involved are the operator, the operator's own applications, and the people those applications write to.
Data from connected Google accounts
Broadcast's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
The operator connects one Google account and grants a single permission,
https://www.googleapis.com/auth/gmail.send. That permission is used solely to send
the messages that the operator's applications submit to Broadcast.
- Broadcast has no permission to read, search or download mail, and it does not do so.
- Nothing obtained from Google is used for advertising, profiling, or to train any model.
- Nothing obtained from Google is sold, and it is not shared with anyone apart from Google itself while a message is being delivered.
- No human reads this data, except the operator when investigating a delivery failure.
What is stored from the connection: the address of the connected mailbox, the OAuth refresh and access tokens, and the granted permissions. Tokens are kept so that messages can be sent without repeating the sign-in, and they are removed when the connection is revoked.
Data submitted by applications
Applications submit the material of the message itself. For e-mail that is recipient addresses, subject, body and any attachments; for a notification it is the title, the text and the Pushover recipient key. Broadcast also records who submitted it, when, and what happened to it.
How long it is kept
| Attachments | Deleted immediately after the message is sent. |
|---|---|
| Message content | 30 days, then erased from the record. |
| Delivery record (recipient, subject, status) | 90 days. |
| Access log (which key called, when, result) | 30 days. |
| Google tokens | Until the connection is revoked. |
Deletion is automatic; nothing has to be requested for it to happen.
Who else sees the data
- Google — delivers e-mail through the Gmail API.
- Pushover (Superblock, LLC) — delivers push notifications, and only for messages sent through that channel.
- Contabo GmbH — provides the server the service runs on.
There are no other recipients. Nothing is sold, rented or used for advertising.
Security
Everything is served over HTTPS. Applications authenticate with API keys, of which only a one-way hash is stored, so the keys cannot be recovered from a copy of the database. Configuration secrets are stored encrypted. Message content and attachments live outside the public directory of the web server and are never served to the web.
Your choices
- The owner of the connected Google account can revoke Broadcast's access at any time in Google account permissions. Sending stops immediately.
- Anyone who receives a message from an application using Broadcast can ask that application to stop writing to them, or write to tomas@roud.cz.
- To ask what is held about you, or to have it erased sooner than the periods above, write to the same address.
Changes
If this policy changes, the date at the top changes with it. Because the service has no registered users, there is no one to notify individually; the current version is always here.