Informativa sulla privacy
Quali dati personali tratta MAWCast, perché, per quanto tempo, chi li riceve e quali diritti hai su di essi.
Questo è il testo in bozza, pubblicato qui per la revisione. Descrive che cosa fa oggi MAWCast con i dati personali, ma non è ancora l’informativa che la legge richiede: 8 campi sono ancora da compilare — tra questi, chi è il titolare del trattamento e dove lo si può contattare — e il documento non è stato esaminato da un legale esperto di protezione dei dati, come richiedono le regole del documento stesso prima della pubblicazione.
L’Informativa sulla privacy è fornita in inglese, la lingua in cui è redatta.
Version: 1.4-draft Last updated: [DATE] Effective: [DATE]
1. Who we are
MAWCast is operated by [OPERATOR NAME], [SERVICE ADDRESS] ("MAWCast", "we"). For the personal data described in sections 3, 5 and 6 we are the controller.
For anything about your data, write to contact@mawcast.com. It is the only address, for privacy as for everything else, and a person reads it.
This policy goes with the Terms of Service. The Terms say what the service is and who is responsible for what; this document says what happens to personal data.
2. Two roles, kept apart
MAWCast holds personal data in two different capacities, and they work differently.
- About you, our customer. Your account, sign-in, subscription, security, support and use of MAW Assistant. We decide why and how, so we answer for it. That is sections 3 and 5 to 11.
- About the people around your station. Your listeners and the guest DJs you invite. You decide to run and publish the station and whom to let broadcast on it, so you are the controller and we are your processor, as section 11 of the Terms sets out. That is section 4.
3. What we collect about you, and why
3.1 Your account and your stations
Your email address, your name, a profile picture if you upload one or sign in with a provider that has one, a password hash if you set a password (never the password itself), your language, your account ID, how far you went through the welcome tour, and the dates your account was created and last used.
What you put into MAWCast: your stations and their settings, time zone, descriptions and images, schedule, playlists, the audio and artwork you upload, and the history of your broadcasts. Audio you upload in a format other than MP3 is converted to MP3 at 320 kbps when it arrives, and the MP3 replaces the file you uploaded; an MP3 is kept as you uploaded it.
Why: to give you an account and run the service.
Legal basis: contract, Art. 6(1)(b) GDPR. An email address is required to hold an account; without it we cannot provide one. Everything else in this section is yours to give or leave out.
Your first language and time zone. When you create an account, the IP address your request comes from is looked up, in the server's memory, in the same geolocation database we use for listeners (section 4), to find the country you are in. The country is used only to choose the language MAWCast starts in, unless you already picked one in your browser, and, when your browser does not send its own time zone, the time zone of a country that has only one. Your browser's time zone and the language you picked travel with the sign-up itself, never in a cookie. Neither the address nor the country is stored: what is kept is the language and the time zone, and you can change both at any time in Account. This happens once, when the account is created.
Legal basis: legitimate interests, Art. 6(1)(f): starting you in a language you can read and on your own clock.
3.2 Signing in with Google or Discord
If you choose to, the identifier, email address, name and picture address that Google or Discord send us, and the sign-in tokens they issue, stored encrypted. If you connect Discord to add MAW Assistant to a server, Discord also shows us the list of your servers, so that you can choose one.
Why: to let you sign in with that account and use the Discord features.
Legal basis: contract, Art. 6(1)(b). Google and Discord are independent controllers of your account with them; their own policies apply.
3.3 Security
Your sessions: when each started and was last used, how you signed in, and the browser identification string your browser sent (for MAWCast Studio, the app version and the name you gave the device). We do not store an IP address with a session. Sessions end after 30 days without use.
Your multi-factor authentication (MFA) set-up: the secret is encrypted and the recovery codes are stored only as hashes. The one-time codes and links we send you are stored only as hashes and expire within 30 minutes.
To stop abuse of password resets, email links and guest DJ invitations, the server counts requests per IP address in its memory, over periods of 10 to 15 minutes. Those counters are never written to disk; the addresses in them are cleared when the server restarts, not at the end of each period.
Why: to keep your account yours and to show you where you are signed in.
Legal basis: contract, Art. 6(1)(b), and legitimate interests in security, Art. 6(1)(f).
3.4 Subscription and billing
Your plan, its status and dates, and the trial.
MAWCast takes no card payments today and holds no card data, billing address or tax number. No payment provider is connected yet. When one is, it will hold the card, we will keep a reference and the record of each payment, and this policy will name the provider before the first charge.
Why: to provide the plan you chose and, once payments exist, to take payment and meet our accounting duties.
Legal basis: contract, Art. 6(1)(b); legal obligation for invoices, Art. 6(1)(c).
3.5 One free trial per card
Not collected today. When trials that ask for a card open, we will keep a SHA-256 hash of a fingerprint of that card, supplied by the payment provider, with the ID of the account that used it. It cannot be turned back into the card. How long it is kept will be stated here before that happens.
Why: so the free trial is used once, not once per new account.
Legal basis: legitimate interests, Art. 6(1)(f).
3.6 Emails we send you
Emails about your account, security and billing only: a welcome message, verification codes, password resets, changes of email address or password, security alerts, confirmation that your account was deleted, receipts and billing notices. We keep a delivery log (recipient, type, delivery status and date; never the content) so we can tell you whether a message reached you and stop writing to an address that bounces or complains.
Why: to run the account and prove what we sent.
Legal basis: contract, Art. 6(1)(b), and legitimate interests, Art. 6(1)(f). We send no marketing email. Station alerts go to Discord, never to email.
3.7 MAW Assistant on Discord
MAW Assistant is a Discord bot. It reads the direct messages you send it and the commands and buttons you use; it does not read the conversations of a Discord server.
- Your Discord account. Your Discord user ID, with the language, time zone, station, notification, report and answer-style choices you make in the Assistant and which of its introductions and tips it has already shown you; a log of which notices and reminders it sent you; and the highest storage warning it has sent you.
- Your Discord server, if you add the Assistant to one: the server's ID and name, the channels and roles you choose for notices and for the station panel, and the Discord ID of the person who added it. The Assistant also keeps its own list of the servers it is in: their ID and name, and when it joined and left.
- Your messages. No transcript of your conversations is kept. Your messages, as you wrote them, are held only in the Assistant's working memory, never on disk, until the Assistant restarts; to follow the conversation it uses only your last three messages from the last five minutes. When a message about MAWCast is kept so the Assistant can learn how people phrase things, it is stored under a keyed code instead of your Discord or account ID, in three forms: a copy stripped of passwords, keys, tokens, email addresses, web addresses, IP addresses, phone numbers and long numbers, which is deleted after 30 days; the same copy with the names of your stations, shows, playlists and guests also replaced by placeholders; and a word form used to compare phrasings, in lower case, without punctuation or filler words and with those names replaced by placeholders, but not stripped of email addresses, web addresses or phone numbers. A message that contains a password or a key is not kept at all, and nothing more you write is kept until the Assistant restarts. A record that teaches the Assistant nothing is deleted after 30 days; the others after 365 days, or later while a phrasing rule built on them is still being tested or reviewed. Examples in the form with placeholders, and the words that define a group of similar phrasings, are copied into those groups and into the rules the Assistant learns, and can be kept with no time limit; so can a short name you use for one of your stations or shows, kept under your account's keyed code. Names you type that the Assistant does not recognise as yours are not removed.
- Answers that need AI. Most questions are answered by the Assistant itself, from your MAWCast data and from the documentation, partly with a language model that runs on our own server and sends nothing anywhere. Where the documentation has a page close to what you asked, it usually shows you that page first and asks an AI provider only if you tell it that was not the answer. When the Assistant cannot answer and your plan includes AI answers, it sends the stripped message, with the names of your stations, shows, playlists and guests replaced by placeholders, to an AI provider (section 7): to Groq first, and to Google only when Groq cannot answer. With it go the date, your workspace's time zone, the number of stations you have, the documentation pages that seem relevant, the language and answer style you chose, and what kind of request the Assistant thinks it might be and what kind you made just before (the kind, never the text). It does not send your plan, your subscription, your Discord ID, your username, your email address, the names of your stations or the earlier conversation, and it never sends images or attachments. Names you type that the Assistant does not recognise as yours go as you wrote them. A short question that is not about MAWCast is sent stripped in the same way but otherwise as you wrote it, names included, with nothing else at all; you can ask up to five of those every 30 minutes (a number MAWCast can change), counted under your keyed code.
- Answers reused. An answer from an AI provider is kept in the Assistant's memory for up to six hours, under a code worked out from the question and everything sent with it, so that the same question is not sent twice: for a question about your MAWCast it is reused only for your account; for a short question that is not about MAWCast, for anyone who asks exactly the same thing in the same language. It holds the answer, not your message, and it is never written to disk.
- Security. Requests that look like attempts to extract secrets or misuse the Assistant are logged: the time, the keyed codes of your Discord user and of your account, the kind of request, a risk score, and a fingerprint of the text (a hash of it) so that the same message sent again is recognised. The text itself is not stored. Section 10 explains the automatic pause this can cause. When something the Assistant tries to do for you fails for a reason it cannot explain to you, it gives you a reference (MWA-…) and keeps, under the same keyed code, a technical description of the error.
We do not use your conversations to train AI models. What an AI provider does with a question it receives is set by its own terms, which section 7 describes.
Legal basis: contract, Art. 6(1)(b); legitimate interests in security and in improving the Assistant's answers, Art. 6(1)(f).
3.8 Counting visits to our public website
For the public pages of mawcast.com (the home page and the documentation), one counter per day, per page and per kind of site the visit came from: search engine, AI assistant, social network, another site, a campaign link, or none.
What is not collected: no IP address, no identifier, no browser or device details, no cookie, nothing stored in your browser. The counter cannot tell one visitor from another. If your browser sends Do Not Track or Global Privacy Control, the visit is not counted at all. Pages inside your account are never counted. So that one browser cannot inflate the counts, the server counts each address's views per minute in its memory, under a hash salted with a random value that changes whenever the server restarts; that is never written to disk.
Why: to know which pages are useful and which kinds of sites bring visitors.
Legal basis: legitimate interests, Art. 6(1)(f). The counts are aggregate and identify no one.
3.9 Where a new account came from
When you create an account, we note the visit that led to it: the name of the site that linked to us (for example google.com, never the full address), the kind of site, the first page you opened, and campaign tags (utm_*) if the link carried them. We also note how you signed up (password, Google or Discord) and the date you reached a few steps: created the account, created a station, first went on air, started a trial, first paid. No IP address or device data is kept with these.
While you browse before signing up, this is held in the page's memory only, never in a cookie or in browser storage.
Why: to know which channels bring people who actually use and pay for MAWCast.
Legal basis: legitimate interests, Art. 6(1)(f). You can object at any time (section 10); it is deleted with your account.
3.10 Broadcast credentials
The source passwords of your stations and the credentials of the guest DJs you invite, stored encrypted and apart from the rest of your data.
Why: to let you, and only the people you choose, broadcast to your station.
Legal basis: contract, Art. 6(1)(b).
3.11 Writing to us
If you write to contact@mawcast.com, we keep your message and our answer for as long as the matter needs.
Legal basis: contract or steps before a contract, Art. 6(1)(b), and legitimate interests in answering, Art. 6(1)(f).
4. Your listeners and your guest DJs: we are your processor
A public station involves people who are not our customers. We handle their data on your instructions and for your station only.
Listeners. To deliver the stream, the streaming server has to receive each listener's connection. MAWCast's audience figures are counts, not people: how many listeners are connected at a time, the highest number each day, how many connections there were and how long they lasted in total, and the same figures for each broadcast. We keep no list of listeners.
Where listeners connect from. So that a station can see which countries and cities its audience is in, the IP address of a listener's connection is looked up in a geolocation database while the listener is connected. The lookup happens in the server's memory: the address is turned into a country and, where the database knows them, a region, a city and that city's approximate position, and is then discarded. The address is not written to our databases, and neither is anything derived from it that could identify a listener: no hash, no identifier. What is kept is a count per country and per city, for each broadcast and for each day.
The player's identification string (its User-Agent) is treated the same way: it is reduced to a family of browser, device and operating system, counted, and not kept.
Because nothing kept identifies a listener, MAWCast cannot tell whether two connections came from the same person, and it does not report "unique" or "returning" listeners.
The geolocation database is DB-IP's "IP to City Lite" (IP Geolocation by DB-IP). It is a file on our own server: no listener data is sent to DB-IP, or to anyone else, to work out a location.
The streaming server itself keeps a technical access log, as web servers do: for each connection, the IP address it came from, the time and length of the connection, the player's identification string and the page it came from. A listener who reaches it through our web server, as the station page and the web player do, is logged with our own server's address rather than their own; a connection made to the streaming server directly is logged with its IP address. We use the log only to operate and secure the streaming service, not to build audience figures, and it is kept for [STREAM LOG RETENTION].
Station pages and the web player set no cookies. They load their typefaces from Google Fonts, so a listener's browser contacts Google's servers and Google receives the listener's IP address, as it would for any web request.
Guest DJs. When you invite a DJ who has no MAWCast account, we keep the name they give (it is shown to you and in your station's notices), the times they connect, a record of what was done with their access and by whom, and their broadcast credentials, encrypted. We ask a guest for no email address and store no IP address for them.
For all of this:
- You are the controller. You need a lawful basis for it, you tell your listeners and your guests, and you answer their requests.
- We help you as Article 28 GDPR requires, on the terms of section 11 of the Terms of Service.
- Listeners and guests: a request about your data on a station goes to that station. If you write to us, we pass it on to the station and help it answer.
5. Cookies and browser storage
We use only what the service needs to work. No advertising cookies, no analytics cookies, no tracking scripts. That is why there is no consent banner.
| Name | Kind | What it does | How long |
|---|---|---|---|
maw_session | Cookie | Keeps you signed in | 30 days after you last used MAWCast, or until you sign out |
maw_pending | Cookie | Holds a sign-in half done while you enter an MFA code | 10 minutes |
mawcast_admin | Cookie | Keeps MAWCast staff signed in to the administration console. Never set for customers | 8 hours |
mc-language | Browser storage | Remembers the language you chose | Until you clear it |
mc-signed-in | Browser storage | Notes that someone is signed in on this browser, so that mawcast.com opens Control straight away. It says nothing about who | Until you sign out, or clear it |
mawcast-docs-lang | Browser storage | Remembers the language you read the documentation in | Until you clear it |
mawcast-docs-theme | Browser storage | Remembers light or dark mode in the documentation | Until you clear it |
mc-rail | Browser storage | Remembers whether Control's side menu is collapsed | Until you clear it |
mc-media-per-page | Browser storage | Remembers how many files the Media Library shows per page | Until you clear it |
mc-tour-closed | Browser storage | Notes, with your account ID, that you finished or skipped the welcome tour, in case the server could not be told at that moment | Until the server has recorded it, usually at once |
mc-after-sign-in | Browser storage, this tab only | Takes you back to where you were after signing in, for example to connect MAWCast Studio | Until you close the tab |
mc-guest-onboarding | Browser storage, this tab only | Keeps a guest DJ's invitation open while they set up | 30 minutes, or until the tab is closed |
The administration console also remembers two layout choices of MAWCast staff in their own browser.
Two things your browser fetches from someone else. The typefaces of mawcast.com, Control, station pages and the web player are loaded from Google Fonts, so your browser contacts Google's servers and Google receives your IP address as it would for any web request; no cookie is set by it. And if your profile picture, or the icon of a Discord server, comes from Google or Discord, your browser loads that image from them.
6. What our own servers log
The web server in front of MAWCast keeps no log of the pages you request, and the application does not write your IP address or your email address to its logs. The exception is the streaming server's access log described in section 4.
To keep the service running, MAWCast's monitoring records, for each station, its number of listeners and its traffic, per minute and per hour; and, per hour, how many sign-ins failed and how many requests were refused, with no address, account or browser detail. Its alerts and incidents can name a station. MAWCast staff can be told of them by email or in a Discord channel of ours; those messages can name a station, never your email address or your IP address.
Authorised MAWCast staff can see your account's email address, name, dates and plan, and your stations, when they operate the service or answer you. In the Assistant's learning records (section 3.7) they see the form with names replaced by placeholders, the words the Assistant did not know and the short names it learned for stations and shows, never the copy that keeps your names. What staff do in the administration console is recorded in an audit log, which is built so that it cannot be altered or deleted.
7. Who else receives your data
We do not sell your data and do not share it for advertising. It reaches others only where the service needs it:
| Who | What for | Role |
|---|---|---|
| Contabo | The server MAWCast runs on, and the object storage that holds a copy of uploaded files and of backups | Our processor |
| Resend | Sending account, security and billing email: your address and the message | Our processor |
| Groq | Answering the questions MAW Assistant cannot answer itself: the stripped message described in section 3.7. Asked first | Our processor |
| Google (Gemini API) | The same, only when Groq cannot answer | Our processor |
| Discord | The platform MAW Assistant works on: your messages to it, its answers, and the notices it posts where you asked for them. Also sign-in, if you use it, and MAWCast's own operations alerts (section 6) | Independent controller |
| Sign-in, if you use it; and the typefaces of the site, Control, station pages and the web player (sections 4 and 5) | Independent controller | |
| Authorities | Only where the law obliges us, and only what it obliges | — |
Notices that MAW Assistant posts in your Discord server are visible to that server's members, and can include the station's name, listener numbers and the name of whoever is on air.
The two AI providers receive a question only to answer it. Groq states that it does not keep the content of requests by default, and that it may log requests and answers for up to 30 days to keep its service reliable and to investigate abuse; what it keeps is stored in the United States. Google [GOOGLE DATA USE]. Neither is told who you are, though what you type goes as section 3.7 describes: it lists what is sent and what is not.
No payment provider receives anything today (section 3.4).
8. Transfers outside the European Economic Area
MAWCast's server and object storage are in the European Union. Resend, Discord, Groq and Google may process data outside the EEA, in particular in the United States. Where they do, the transfer is protected by [TRANSFER SAFEGUARD]. Write to us for a copy of the safeguard that applies.
9. How long we keep it
| Data | Kept |
|---|---|
| Your account, sign-in methods, sessions and MFA set-up (3.1 to 3.3), the signup source (3.9) and broadcast credentials (3.10) | While your account exists. Deleted when you delete it. A session is deleted 30 days after it was last used |
| Uploaded audio after a paid subscription ends | 14 days after the renewal date (or the day it ended, if it ended early), then deleted |
| Uploaded audio after a trial ends | 5 days after the trial ends, then deleted |
| Stations, schedule, broadcast history and audience counts | While your account exists |
| The songs AutoDJ played on each station, with the number of listeners as each began | 400 days, also after the account is deleted |
| Monitoring (6): each station's listeners and traffic; counts of failed sign-ins and refused requests; alerts and incidents | Per minute 8 days and per hour 400 days, also after the account is deleted; counts 90 days; alerts and incidents with no time limit |
| Guest DJs: name, connection times and access record | While your account exists |
| Station events the Assistant turns into notices, such as who went on air or changed the schedule | 30 days |
| Invoices and payment records, once payments exist | [INVOICE RETENTION], as tax law requires, even after the account is deleted |
| Email delivery log (3.6) | 12 months, then the address is removed, also when the account was deleted earlier. A complaint ("this is spam") is kept, so that address is never mailed again |
| Discord server links (3.7) | While your account exists |
| The Assistant's own list of the servers it is in (3.7) | No time limit |
| Assistant settings kept under your Discord ID (3.7) | Until you disconnect in the Assistant's settings, or ask us to delete them. The log of notices sent, 30 days; of reminders, 7 days; the storage warning, until your storage use drops back below it |
| Your messages and AI answers in the Assistant's memory (3.7) | Messages until the Assistant restarts; answers up to 6 hours. Never written to disk |
| Assistant learning records (3.7) | A record that teaches nothing, 30 days. Otherwise the stripped copy 30 days, and the record, with its other two forms, 365 days, or longer while a rule built on it is being tested or reviewed. Examples and words copied into groups of phrasings and learned rules, short names learned for your stations and shows, and the count of your questions not about MAWCast: no time limit |
| Assistant security events and error references (3.7), and the staff audit log (6) | [SECURITY LOG RETENTION] |
| Streaming server access log (4) | [STREAM LOG RETENTION] |
| Error messages of the server | 14 days |
| Visit counts (3.8) | Aggregate, identify no one |
| Backups | 14 days. Data you delete can remain in backups until they expire |
10. Your rights
You can, at any time:
- Get a copy of your data. Account → Your data → Export your data gives a JSON file with your stations and their public pages, the details of the files in your Media Library (not the files themselves), your schedule, playlists, broadcast history, recent activity, settings and subscription. Analytics → Export gives each station's figures as CSV files. Your audio is downloaded from the Media Library, with Download or Download original file: a file you uploaded as MP3 comes back as you uploaded it; a file in another format, once converted, comes back as the MP3 that replaced it (section 3.1), because the file you uploaded is no longer kept. For anything else we hold about you, write to us.
- Correct it. Most of it you can edit yourself in Account.
- Delete your account. Account → Your data → Delete account. It deletes your account, sign-in methods and sessions, your stations and their credentials, broadcast history, uploaded audio and images, guest DJs, Discord server links and the information in section 3.9, at once. What outlives it is what section 9 lists: the email delivery log for up to 12 months, payment records where the law requires them, the staff audit log, the Assistant's settings under your Discord ID, which you can delete in the Assistant or we delete when you ask, its learning and security records, which carry a code instead of your identity, the songs AutoDJ played and the monitoring history of your stations, under the stations' internal IDs, and backups until they expire. An account with a subscription that would renew has to cancel it first.
- Object to what we do on legitimate interests (sections 3.3, 3.5 to 3.9).
- Restrict processing, or take your data to another service.
- Withdraw consent, where we rely on it. Today nothing in this policy does.
Write to contact@mawcast.com for any of these. We answer within one month. We may ask you to prove the account is yours, and we will not charge you.
If you think we have got it wrong, you can complain to a data protection authority, in Spain the Agencia Española de Protección de Datos (aepd.es), or the one where you live. We would rather you told us first.
Automated decisions. MAWCast makes no automated decisions with legal or similarly significant effects on you. One thing does happen without a person: if many requests in a short time look like attempts to misuse MAW Assistant, it stops giving AI answers and making changes for that Discord user for 60 minutes. Your account, your subscription and Control are not affected, and a person at MAWCast can lift it; write to us if it happens to you by mistake.
11. How we protect it
Passwords are stored as hashes, never in readable form. Broadcast credentials, sign-in tokens and MFA secrets are encrypted. Multi-factor authentication is available for every account and applies to Google and Discord sign-in as well. Connections to mawcast.com are encrypted. MAWCast runs on its own server under an account without administrator rights. Uploaded files are deleted on the schedule in section 9 by an automated job.
12. Age
MAWCast accounts are for people aged 16 or older. If you believe a younger person has given us their data, write to us and we will delete it.
13. Changes
When this policy changes in a way that matters, we tell account holders by email before the change takes effect. The date at the top shows the current version.
14. Contact
| Purpose | Contact |
|---|---|
| Privacy, and everything else | contact@mawcast.com |
Controller: [OPERATOR NAME], [SERVICE ADDRESS].
Ti serve ancora aiuto? Scrivi a contact@mawcast.com.