Privacy Policy

Last updated: 2 November 2026

This policy explains what personal data we process when you use the Osira app for iPhone, iPad and Android (the “app”) and the website osira.tv, why we process it, who helps us, and what rights you have.

1. Who is responsible

The controller responsible for your data is:

Osira Labs, Inc.
838 Walker Road, Suite 21-2
Dover, DE 19904
USA
Email: hello@osira.tv

For any privacy question or request, write to the address above. We answer within one month.

2. The website osira.tv

Hosting and server logs

The website is hosted on Cloudflare Pages (Cloudflare, Inc., USA). When you open a page, Cloudflare processes technical access data (your IP address, date and time, the page requested and your browser’s user agent) to deliver the page and protect it against attacks (legal basis: our legitimate interest in a secure, working website, Art. 6(1)(f) GDPR).

Cloudflare Web Analytics

We count visits with Cloudflare Web Analytics, which records pages viewed, referrer, device type, browser, country and load times in aggregate. It sets no cookies, reads nothing from your device and does not track you across websites (Art. 6(1)(f) GDPR).

Watching episodes on the website

Episodes on osira.tv are streamed by Mux, Inc. (USA). To stream to you, Mux receives your IP address and technical data about the request and the player (Art. 6(1)(f) GDPR: our legitimate interest in showing you the episode you opened).

Rating episodes

After an episode you can rate it with one to five stars and, if you like, add a short note. Below five stars you can also tap what could be better, from a fixed list (for example "Too slow"). We store the stars, the options you tapped, the note, the show and episode, the language of the page and a random ID that exists only while the page is open, so that a second tap replaces your first rating instead of counting twice. We do not store who you are. A note contains only what you type, so please leave out personal details; notes are read only by the Osira team and never shown on the website. Ratings are kept in a database at Cloudflare (stored in the EU) and deleted after 14 months. To stop abuse we count ratings per internet connection for one hour, as described for the waitlist below. Legal basis: our legitimate interest in learning what viewers think of our episodes (Art. 6(1)(f) GDPR).

One question about the app

After you have finished three episodes, we may ask once what would make you get the Osira app, with a few fixed answers and a Skip button. We store the answer you tap, the show and episode where we asked, the language of the page and a random ID that exists only while the page is open. We do not store who you are. Your device remembers that you were asked, so we do not ask again; if the answer could not be sent, your device keeps it until it can. Answers are kept in a database at Cloudflare (stored in the EU) and deleted after 14 months. To stop abuse we count answers per internet connection for one hour, as for ratings. Legal basis: our legitimate interest in learning what would make our app worth getting (Art. 6(1)(f) GDPR).

When your visit is counted

The two analytics tools below count visits only as described here. If you visit from the EEA, the United Kingdom or Switzerland, or if we cannot tell where you are, nothing is loaded and nothing is stored on your device until you choose “Allow” in the cookie banner. If you visit from anywhere else, the tools count your visit by default, unless you have chosen “No thanks” or your browser sends a Global Privacy Control signal, which we treat as a “no”. Under “Cookie settings” at the bottom of every page you can switch counting off or on at any time.

To tell which case applies, the page asks our server which country your request comes from. Cloudflare works the country out from your IP address when the request arrives; we do not store the country or the IP address for this, and your device does not keep the answer.

Google Analytics

With your consent, or by default where described above, we use Google Analytics 4 (Google Ireland Limited, Ireland) to understand how the website is used: which pages and episodes are viewed, how long episodes are watched, where visitors come from (for example a link in a social media post), and actions such as joining the waitlist, rating or sharing an episode. Google Analytics sets two cookies (_ga and _ga_ followed by our property ID) that hold a random ID and expire after 13 months. It receives your IP address to work out your approximate location (country and city); Google Analytics 4 does not store the IP address. Google signals and ad personalisation are switched off, and we do not use this data for advertising.

Legal basis: if you visit from the EEA, the United Kingdom or Switzerland, or we cannot tell where you are, your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG); without it, Google Analytics is not loaded at all. Where you are counted by default, our legitimate interest in understanding how the website is used (Art. 6(1)(f) GDPR, where that law applies). You can withdraw your consent or switch Google Analytics off at any time under “Cookie settings” at the bottom of every page; it then stops and its cookies are deleted. Google processes the data on our behalf under a data processing agreement. Data may be transferred to Google LLC in the USA, which is certified under the EU–U.S. Data Privacy Framework. We keep Google Analytics data for 14 months.

PostHog

With your consent, or by default where described above, we also use PostHog (PostHog Inc., USA) for product analytics: which pages and episodes are viewed, and actions such as joining the waitlist, rating or sharing an episode. We use PostHog’s US cloud, so the data is stored on servers in the USA. With each request PostHog receives your IP address, the address of the page you are on, the page you came from, and technical details of your browser and device. PostHog keeps a few entries in your browser’s local storage and session storage (their names start with ph_ followed by our project token). One holds a random ID together with the page you first arrived on and where you came from; the session storage entries identify the current window and visit and disappear when you close the tab. We switch off automatic capture and session recordings, we do not create person profiles for anonymous visitors, and we do not use this data for advertising.

Legal basis: if you visit from the EEA, the United Kingdom or Switzerland, or we cannot tell where you are, your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG); without it, PostHog is not loaded at all. Where you are counted by default, our legitimate interest in understanding how the website is used (Art. 6(1)(f) GDPR, where that law applies). You can withdraw your consent or switch PostHog off at any time under “Cookie settings” at the bottom of every page; it then stops and its entries are deleted. PostHog processes the data on our behalf under a data processing agreement. Because PostHog Inc. is based in the USA and the data is stored there, the agreement includes the EU Commission’s standard contractual clauses (Art. 46(2)(c) GDPR), which are the basis for this transfer. We keep PostHog data for 12 months.

Cookies and storage on your device

Apart from the Google Analytics cookies and the PostHog entries above, the website sets no cookies and contains no advertising trackers. It keeps a few entries in your browser’s local storage so that it works as you expect: your cookie choice, which episodes you have watched (for “Continue”), whether you have already joined the waitlist, and whether we have already asked you the question about the app and what you answered (an answer that could not be sent waits there until it can). They stay in your browser and you can delete them in your browser settings at any time (§ 25(2) no. 2 TDDDG). They are not sent to us, except an answer that could not be sent the first time, which is sent again later.

Waitlist

If you join the waitlist, we store your email address, the language of the page, the country your internet connection comes from (as our host Cloudflare reports it; not your IP address), when you signed up and where on the website you did (the page and, on an episode page, the show and episode). We use it to tell you when Osira launches. Your consent is the legal basis (Art. 6(1)(a) GDPR); withdraw it any time by emailing us.

The list is kept in a database at Cloudflare (Cloudflare, Inc., stored in the EU) and with Resend (Resend, Inc., USA), which also sends our emails. We delete your address when you withdraw, or once the launch announcement has gone out.

To stop automated signups, we count signups per internet connection for one hour. For this we store a one-way hash of your IP address, made with a key that changes every day, never the IP address itself; the counts are deleted after a day (Art. 6(1)(f) GDPR: our legitimate interest in a waitlist free of abuse).

Emailing us

If you email us, we use what you send to answer you (Art. 6(1)(b) or (f) GDPR) and delete it when it is no longer needed.

3. The Osira app

Using the app without an account

You can watch without signing up. When you first open the app, it creates an anonymous guest account with Firebase Authentication so your favourites and watch progress are kept. For this we process a random account ID, which shows and episodes you open, how far you watch or listen, your favourites and settings, and technical data such as app version, device model, operating system and language. We need this to provide the app you asked for (Art. 6(1)(b) GDPR).

A guest account is anonymous. It holds no personal details such as a name or an email address, only the random account ID, your watch history, favourites and likes, a push token if you turned notifications on, and the app’s usage events. We keep guest data for up to 12 months after you last use the app; usage events are kept as described under “Our own usage analytics” below. To have guest data deleted sooner, email hello@osira.tv.

Our servers also log technical request data, including your IP address, to keep the service secure and to fix errors (Art. 6(1)(f) GDPR). These logs are kept for up to 30 days.

Signing in

You can sign in so your library follows you across devices:

Sign in with Apple: we receive an account ID and the email address you choose to share (possibly an Apple relay address), and your name if you share it.
Sign in with Google: we receive your name, email address, profile picture and a Google account ID.
Email code: we send a one-time sign-in code to the email address you enter. The email is delivered by Amazon Simple Email Service (Amazon Web Services, Frankfurt region). We keep the code only in hashed form; it expires after 10 minutes.

Legal basis: providing your account (Art. 6(1)(b) GDPR).

Deleting your account

You can delete your account in the app (You tab → Delete account). This deletes your account and sign-in record, your profile, favourites, watch history and, if you turned notifications on, your device’s push token. Usage events already collected keep the IDs they were sent with, including your account ID, and are deleted automatically after 14 months. The app starts a new analytics ID on your device, so what you do afterwards is not joined to the deleted account. Records of your consent choices are kept as proof of those choices. The app then carries on as a guest.

If you no longer have the app, email us from the address linked to your account (or tell us that address). We delete the same data and confirm when it is done.

Streaming

Videos and audio stories are delivered by Mux, Inc. (USA). To stream to you, Mux receives your IP address and technical data about the request and the player (Art. 6(1)(b) GDPR).

Our own usage analytics

The app sends usage events (for example screens viewed, episodes started and finished, searches and taps) to our own servers. These events carry a random analytics ID that is created on your device and, when you are signed in, your account ID, so that we can see how Osira is used, find faults and decide what to build next. Our legitimate interest in running, securing and improving the app is the legal basis (Art. 6(1)(f) GDPR).

You can switch this off in the app (You tab → Share usage data). When you do, the analytics ID is deleted from your device and further events no longer carry any ID that identifies you or your account. They still carry a session ID (a random value that groups the events of one app session) along with a count of how many sessions this installation has had, your device model, app version, language and time zone, so that we can count sessions and usage. Switching usage data off also switches off personalised recommendations, because they are built from the data that stops being collected.

On iPhone and iPad the analytics ID is stored in the iOS keychain, so it survives deleting and reinstalling the app. On Android it is stored in the app’s private storage, which Android’s own backup can restore when the app is reinstalled. Switching off “Share usage data” is what deletes it; deleting your account gives you a new one.

The first time you open the app, it asks a separate question: whether we may use what you watch or listen to in order to personalise your recommendations. That one is your choice, and consent is the legal basis (Art. 6(1)(a) GDPR). If you say “Not now”, we still collect the usage events described above, but we do not use what you watch or listen to in order to pick what we show you (the app stops asking our servers for recommendations altogether), and we do not use these events for advertising measurement. What Meta receives is governed separately (see “Meta (Facebook SDK) and tracking” below). You can change your answer at any time (You tab → Personalised recommendations). We keep a record of each choice (for personalised recommendations, for sharing usage data and for the iOS tracking prompt) with the date, which control you used, and the analytics ID (and account ID, if you are signed in) it applied to, as proof of your choices.

Our content delivery provider (Cloudflare) tells our servers which country the request came from; we store only that country (and, where the network provides it, the region) with the event, never the IP address itself. Events are stored with Google Cloud in the European Union. The raw event store deletes them automatically after 14 months.

Google Firebase

The app uses Google Firebase (Google Ireland Ltd. / Google LLC, USA) for sign-in (Firebase Authentication), usage statistics (Google Analytics for Firebase), crash reports (Crashlytics), performance measurement (Performance Monitoring), remote settings (Remote Config), in-app messages (In-App Messaging) and push notifications (Cloud Messaging). These services process app-instance and installation IDs, device and app data, usage events, crash reports and performance data. On iPhone and iPad, Google Analytics for Firebase and Crashlytics run from the first launch, independent of both “Share usage data” and the personalisation choice above, and if you allow tracking in the iOS prompt (see below), Google Analytics for Firebase may also receive your device’s advertising identifier. On Android, Google Analytics for Firebase, Crashlytics and Performance Monitoring run only while “Share usage data” is on, stop when you switch it off, and never receive your device’s advertising ID. Legal basis: our legitimate interest in a stable, secure app and in understanding its use (Art. 6(1)(f) GDPR); for the advertising identifier, your consent.

Meta (Facebook SDK) and tracking

We use Facebook and Instagram to advertise Osira. To measure whether these ads work, the app uses the Facebook SDK (Meta Platforms Ireland Ltd.; Meta Platforms, Inc., USA), which sends app events such as installs and app launches to Meta.

Only if you choose “Allow” in the iOS tracking prompt does Meta also receive your device’s advertising identifier, which it can link to your Meta account to measure and optimise our advertising. Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). You can change this at any time in iOS Settings → Privacy & Security → Tracking. Without that permission, Meta receives the app events without the advertising identifier (Art. 6(1)(f) GDPR). For ad measurement Meta acts as a joint controller with us; Meta’s privacy policy explains how it uses the data.

On iPhone and iPad, the Facebook SDK sends these app events from the first launch. Switching “Share usage data” or “Personalised recommendations” off stops our own usage analytics but not these Meta app events; the advertising identifier stays governed by the iOS tracking prompt.

On Android, the app does not send anything to Meta at present. If that changes, we will update this policy first.

We do not show ads in the app and we do not sell your data.

Push notifications

If you turn on Notifications in the app (You tab → Notifications), we store a push token for your device, together with the platform (iOS or Android), the app’s language, the app version, your account, and the date and version of your consent. While notifications are on, we also record when the device was last seen, updated at most once a day when you open the app. We use this to send you the notifications you opted into: new stories and chapters, and what’s coming to Osira. Legal basis: your consent (Art. 6(1)(a) GDPR).

Notifications are sent through Google Firebase Cloud Messaging (see “Google Firebase” above) and delivered to your device by Apple’s Push Notification service on iPhone and iPad, and by Firebase Cloud Messaging itself on Android.

You can withdraw your consent at any time: turn Notifications off in the app, or turn off notifications for Osira in your phone’s settings, which the app treats as a withdrawal the next time you open it. Either way we delete the push token and the details stored with it. Deleting your account deletes them too. We also delete them when Apple or Firebase reports that the token is no longer valid, for example after you uninstall the app.

Purchases

Osira is free during launch. If we offer an Osira Pass subscription, you buy it through Apple’s App Store or, on Android, Google Play, and Apple or Google handles the payment. We receive a transaction ID, the product, the purchase and expiry dates and the renewal status (never your payment details) to unlock access (Art. 6(1)(b) GDPR).

Voice search

If you tap the microphone in Search, the app asks for access to your microphone and turns what you say into text on your device, with the phone’s own on-device speech recognition (Apple’s on iPhone and iPad, Google’s on Android). The recording is not sent to us and is not stored; only the resulting search text is used, exactly like a typed search.

Test versions

If you test pre-release versions through Apple TestFlight or Google Play’s testing tracks, the app connects to our normal servers, and Apple or Google may share your feedback and crash reports with us. TestFlight versions from before 10 October 2026 connect to a test server hosted by Oracle Cloud Infrastructure in Mumbai, India, which keeps the data sent to it.

4. Who helps us

We use these providers. Those marked “processor” handle data only on our instructions under a data processing agreement; the others are responsible for their own processing.

Google Cloud: servers, database and analytics storage in Belgium and the EU (processor)
Google Firebase: sign-in, app analytics, crash and performance reports, messaging and push notifications (processor)
Amazon Web Services: sign-in code emails, Frankfurt region (processor)
Mux: video and audio streaming, USA (processor)
Cloudflare: website hosting, web analytics, the database for the waitlist and ratings (EU), and the network in front of our app API, USA (processor)
Resend: waitlist emails, USA (processor)
Google Ireland: Google Analytics on the website, with your consent or by default outside the EEA, UK and Switzerland (processor)
PostHog: product analytics on the website, with your consent or by default outside the EEA, UK and Switzerland, USA (processor)
Oracle Cloud Infrastructure: test server, India (processor)
Apple: Sign in with Apple, App Store purchases, TestFlight, delivery of push notifications
Google: Sign in with Google, Google Play purchases and testing
Meta: advertising measurement (joint controller, see above)

5. Transfers outside the EU

Osira Labs, Inc. is based in the United States, and some providers process data in the United States or India. Where a recipient is certified under the EU–U.S. Data Privacy Framework, the transfer relies on the European Commission’s adequacy decision; otherwise we rely on the Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR). Ask us for a copy.

6. How long we keep data

Account, favourites and watch history of a signed-in account: until you delete your account.
Guest data (an anonymous guest account with its watch history, favourites, likes and push token): up to 12 months after you last use the app, or until you ask us to delete it.
Our usage analytics events: 14 months in the raw event store, then deleted automatically.
Records of your consent choices: kept for as long as we may need them to prove what you chose.
The analytics ID on your device: until you switch off “Share usage data” or delete your account (on iPhone and iPad it survives reinstalling the app; on Android, Android’s backup can restore it).
Sign-in codes: usable for 10 minutes; the stored code is deleted when it is used.
Push token and the details stored with it: until you turn notifications off (in the app or in your phone’s settings, see “Push notifications”), delete your account, or Apple or Firebase reports the token invalid.
Server logs: up to 30 days.
Waitlist addresses: until you withdraw, or until the launch announcement has gone out.
Signup and rating counts for stopping abuse: one day.
Episode ratings and notes from the website: 14 months.
Answers to the question about the app: 14 months.
Google Analytics data from the website: 14 months. Its cookies: 13 months, or until you withdraw your consent or switch it off.
Data held by Firebase and Meta: according to those services’ retention settings.

7. Your rights

You have the right to access your data (Art. 15 GDPR), to have it corrected (Art. 16) or deleted (Art. 17), to restrict its processing (Art. 18) and to receive it in a portable format (Art. 20). You can withdraw any consent at any time, which does not affect processing before the withdrawal.

Right to object: where we rely on legitimate interests (Art. 6(1)(f) GDPR), you can object at any time for reasons arising from your particular situation (Art. 21 GDPR). For our own usage analytics you can act on this yourself in the app (You tab → Share usage data); emailing us is not necessary.

To use these rights, email hello@osira.tv. You can also complain to a data protection supervisory authority (Art. 77 GDPR), in particular the one in the EU country where you live.

8. Children

Osira is not intended for children under 16, and some shows contain violence and mature themes. We do not knowingly collect data from children under 16. If you believe a child has given us data, contact us and we will delete it.

9. Security

Data is encrypted in transit (TLS), and access to our systems is restricted to the people who need it.

10. Changes to this policy

We update this policy when our app or our providers change. The date at the top shows the latest version; for significant changes we will also tell you in the app.