Blingo privacy policy
The controller of the personal data described here is the developer of Blingo, operating under the Atlascope name, based in New Zealand. Contact: support@getatlascope.com; it reaches a person.
1. What we store
- Account: your email address, a display name, your language and time zone, your settings (daily goal, reminder hour, keywords to follow). Authentication is handled by Supabase; your password is stored only as a hash. If you sign in with Google, we receive your email and name from Google.
- Your work: themes, the sources you add (titles, abstracts, extracted text of your PDFs and notes), the generated material (sheets, cards, quizzes, podcast scripts, briefs, discussion messages), and your review history (which card, when, which grade), used to schedule reviews and to show your progress and streak.
- Podcast audio: the MP3 of each episode, stored on our server until you delete the episode.
- Credits: your balance and the history of credits received and spent (which action, when). Blingo sells nothing, so no payment data is collected.
- Technical logs on our server (time, route, status, IP address), kept for 30 days to keep the service running and to protect it.
Your personal Anthropic API key, if you enter one, is kept in your browser only and sent with your requests; it is never written to our database or logs.
2. What we send to whom, and why
- Anthropic (model provider): the sources you select, your questions, and your answers to open questions, to produce the material. Under Anthropic's API terms this content is not used to train their models. Servers in the United States.
- Microsoft Azure Speech (voices): the text of podcast scripts, to produce the audio. Alternative open-source voices run on our own server and send nothing.
- PubMed, Europe PMC, arXiv, Crossref, Semantic Scholar (public databases): your search words and the identifiers of the papers you add, to find papers and fetch open-access text. These are public services with their own policies.
- Supabase (database and authentication) and our own server: where your account and your work live.
We do not sell personal data, show advertising, or run third-party analytics or tracking scripts.
3. Cookies and local storage
Blingo uses a session cookie to keep you signed in (shared with Atlascope on the same domain) and the browser's local storage for conveniences: language, an interrupted session, your personal API key if any, and, without an account, your local data. No advertising or analytics cookies.
4. Legal bases
Running the service you asked for (contract), keeping it secure and improving it (legitimate interest), and your consent where it is needed, for example for reminders. Where the GDPR applies, you can withdraw consent at any time.
5. Retention
Your work stays as long as your account exists. Deleting a theme deletes its sources, cards and material; deleting an episode deletes its audio. Deleting your account deletes everything within 30 days,. Logs are kept 30 days.
6. Your rights
You can access, correct, export and delete your data. Most of it is directly in the app; for anything else, write to support@getatlascope.com and we will answer within 30 days. Where the GDPR applies, you can also complain to your data protection authority.
7. Security
Data travels over HTTPS. Each account can only read its own rows in the database (row-level security). Secrets live on the server, never in the browser, except your own API key, which you choose to keep there.
8. Changes
If this policy changes in a way that matters, we tell you in the app before it applies.