‹ back to amblewave
Privacy
Last updated 21 July 2026
Amblewave is made by Everydaylives SRL (VAT BE 0723.477.567), Genval, Belgium. This page explains what we collect when you use the app, why, and how to reach us about it.
What we collect
- Email address — asked for the first time you start a real listening session (not when scanning a venue/QR card, which stays anonymous). Used to keep your listening history in sync across devices so the app can avoid repeating content you've already heard, and to verify an active subscription.
- Listening topic history — the topics of clips you've heard, tied to your email, so we can avoid repeating them for roughly the next 20 sessions.
- Session count — how many listening sessions you've had, stored the same way.
- Local device storage — your session profile, lifetime clip count, and saved email are also cached on your own device (localStorage) so the app works smoothly offline and between visits.
We don't use third-party advertising trackers, analytics pixels, or cookies for tracking purposes. The in-app "ad" slots are our own house content, not third-party ads.
Who else sees it
- Supabase — hosts the database that stores your email and listening history.
- Cloudflare — hosts the app and the backend functions that generate and serve content.
- Anthropic and OpenAI — process the text and audio of the stories themselves (the topic/prompt text and clip text), not your email or identity.
- Stripe — handles subscription payments directly. We don't see or store your card details; Stripe's own privacy policy covers that data.
How long we keep it
Listening topic history rolls off after roughly 20 sessions. Your email and subscription status are kept until you ask us to delete them.
Your rights
Under GDPR, you can ask us to access, correct, or delete the data we hold about you at any time. Email us and we'll action it.
Children
Amblewave isn't directed at children under 16.
Changes
If this policy changes materially, we'll update the date at the top of this page.