Privacy Policy
Last updated 22 August 2026.
The short version
Eidovelle does not send anything you do to us or to anyone else. There is no account, no sign-in, no analytics, no advertising and no tracking. Your screening outcome and your voyage log are written to your phone and stay there. There is nothing on our side to read, because the app has no way of sending it.
That has a cost, and it is not hidden here. A new phone starts with an empty log. Your voyages are not in your iCloud backup, on purpose.
The longer version below says exactly what is stored, where it sits, and what happens when that changes.
1. Who we are
Eidovelle is made by Eidovelle Labs. You can write to us at [email protected] about anything on this page.
2. What the app writes to your phone
Everything in this section stays on the phone it was written on.
| What is written | Where it lives | In your iPhone backup | How you remove it |
|---|---|---|---|
| Your screening outcome, your consent record, your preferences, and your voyage log including any note you typed | One file in the app's Application Support folder, written with iOS complete file protection, so it cannot be read while the phone is locked | No. The file is flagged to be left out of iCloud and computer backups | Delete individual entries in the Atlas, or delete the app. Starting screening again does not remove the dated record of previous outcomes. See section 6 |
| A technical record of each voyage: the date and time, which world, how long it was set for, why it ended, timing accuracy figures, which audio output was in use, and the audio latency your phone reported | A second file beside the first, holding the last 400 voyages and no more. It carries no note and nothing you typed | No. Also flagged out of backup | Delete the app |
| Which audio outputs you have set a listening level on, and whether you have seen the notice about using the phone speaker | The ordinary iOS preference store for the app | Yes, like any app preference | Delete the app |
The third row is the only thing here that travels in an iPhone backup, and it is two lists of audio output names. It says nothing about you, your health, or what you did in a voyage.
2.1 Screening answers are not written down
The app asks you a set of questions before it will run light. Your answers to those questions are not stored. What the app records is the outcome and the date: either that you passed, or which single category stopped you. Those categories are the whole vocabulary, and this is all of it:
Age · Seizure history · Photosensitivity · Proxy symptoms · Eye-closure symptoms · Family history
The screening decides one thing only, which is whether this app will run light for you. It is a set of questions, not a test. Passing it is not an assurance that flicker will not affect you, and around half of the people who react to flicker have never been told they are photosensitive.
If you screen again later, the previous outcomes stay on the phone as dated entries. That record is what lets the app tell you that you have been through this before. It is on your phone, it is not sent anywhere, and starting screening again does not erase it.
2.2 What is in a voyage log entry
A world name, a date and time, the length you chose, whether it ran its length or ended early, whichever of the fixed shape words you picked, one of five words describing how you felt afterwards (Fine, Dizzy, Queasy, Headache, Unsettled), and any note you typed. The note is free text and it is yours. It is not read by us and it is not transmitted.
2.3 The camera permission
The app asks for camera access because iOS will only hold steady torch timing while a camera session is open. That is the only reason. No image is captured, no video is recorded, no frame is analysed, and nothing from the camera is written to disk or sent anywhere. If you refuse the permission the light will not run and the audio worlds still play.
3. What leaves your phone
3.1 From the app itself: nothing
This version of the app sends nothing and fetches nothing of its own. There is no analytics library, no crash reporting library, no advertising library, no attribution library and no software development kit belonging to anybody else. Which worlds are free in a given week is worked out on your phone from the date rather than fetched from us, so even that costs no request.
Two things the app will one day do over the network are built into it and switched off, with no address to send to: downloading new worlds, and the anonymous daily counts described in section 9. Neither happens in this version, and the counts have an off switch in Settings for when they do.
The only traffic the app causes is StoreKit asking Apple about prices and about what you own, which iOS performs on the app's behalf. That traffic carries nothing about you, your screening outcome or your voyages.
3.2 Purchases go through Apple, not through us
If you buy inside the app, Apple takes the payment. We never see your card, your Apple Account, your name or your email address. Apple gives us sales and subscription figures in aggregate, the same way it does for every app on the store. Your purchase is governed by Apple's own privacy policy and terms, not by this page.
The app asks Apple what you currently own each time it needs to know. It does not keep its own copy of that answer.
3.3 If you export or share your log, that is you
The Atlas can produce a plain text copy of your log and hand it to the iOS share sheet. Where it goes then is your choice and outside our reach. It is worth thinking about it the way you would think about any note about your own health before sending it to anybody.
3.4 Why there is no symptom form on this website
If something happens during or after a voyage, the route for telling us is on the Support page. There is no form on this website that asks you to type symptoms into it, because we do not want that detail sitting in a web server's logs and database.
Email is the route we offer instead, and it is not private either. What you write will sit on your mail provider's servers and on ours. Send only as much as you are comfortable sending.
The Report screen in the app currently does one thing, which is to explain the route and point here. It does not compose anything and it sends nothing. A sealed on-device route is described in section 9 and is not built yet.
4. Tracking and advertising
There is none. Version 1.0 contains no code that could produce any: no advertising identifier is read, no advertising network is present, and no profile is built. The app's bundled privacy manifest declares no tracking and no tracking domains, and that is true of the code as shipped. The same manifest declares the four kinds of anonymous diagnostic count described in section 9, marked as never linked to you, ahead of the day they are switched on; nothing of the kind is sent by this version.
No advertising or tracking is planned. If that ever changed, section 9 is where you would be told, and section 9 commits us to telling you before it happened rather than afterwards.
Sending information about somebody's health to an advertising network is the specific failure that turns a privacy problem into a reportable one. The way to not do it is to not build the pipe.
This website is the same shape. It carries no script of any kind, no analytics, no cookies, no embedded third-party content, and no font or image loaded from another host. There is nothing here to consent to, which is why there is no consent banner.
5. Who Eidovelle is for
Eidovelle is sold to adults. You must be 18 or over to use it. The app asks before anything else and stops there if the answer is no. We do not knowingly collect anything from anyone under 18, and since we do not collect anything from anyone at all, there is nothing about a minor for us to hold, sell or disclose. If you believe a minor has this app, take the phone off them and write to us at [email protected].
6. Your control over what is on your phone
- Delete one voyage. Open the Atlas, open the entry, delete it. The note goes with it.
- Export your log. The Atlas will produce it as plain text and hand it to the share sheet.
- Start screening again. Settings, then screening. It starts from the first question. This does clear your consent record, your audio-only preference and your per-world voice settings, and you will answer the consent stage again. It does not clear the dated record of previous outcomes, and it does not clear a hold placed after an uncomfortable voyage. Those are not the sort of thing that should be clearable by answering differently.
- Remove everything. Delete the app. iOS removes the app's Application Support folder with it. Nothing survives on our side, because nothing ever reached our side.
There is no account to close and no data request to make, because there is no file anywhere with your name on it. If you would like us to confirm that in writing for your own records, ask and we will.
7. Consumer health data
Some US state laws, Washington's My Health My Data Act among them, attach specific duties to anyone who collects consumer health data.
Eidovelle Labs does not receive, hold, share or sell consumer health data. Screening outcomes, log entries and notes are processed by the app on your own device and are never transmitted to us, so there is nothing on our side to access, disclose or delete. We do not sell personal information and we do not share it for cross-context advertising.
If that ever changes, section 9 describes how you would be told, and this section will be rewritten rather than quietly left standing.
8. How what is on your phone is protected
The file holding your screening outcome and your voyage log is written with iOS complete file protection, which means it is unreadable while the phone is locked. That protection depends on your phone having a passcode. If your phone has no passcode, iOS cannot enforce it, and a person holding your phone can open the app and read your log.
The second file, holding the technical record of each voyage, has ordinary app file protection rather than complete protection. It carries no note and nothing you typed.
Both files are flagged to be excluded from iCloud and computer backups. That is why a new phone starts empty.
9. What is planned, and how you will be told
The following are decided and not yet built. Each one changes what this policy says, and when each ships this page is amended and re-dated before or on the day the change reaches you, never afterwards.
- Anonymous daily counts. The app will send us, once a day, a message containing whole numbers: how many voyages ran and for how long, which world, whether the light was on, why each one ended, and how well the phone kept the timing. It carries the app version, the build, and the model and iOS version of the phone. The same daily message can include Apple's standard crash and hang reports, which describe what the code was doing and nothing that you were. What is never in it: your screening answers and whether you passed, anything you wrote in the Voyage Log, how you said you felt afterwards, and any note you recorded. There is no identifier of any kind, no account, no install number and no timestamp finer than a calendar day, so nothing that arrives can be traced to a phone or to a person, by us or by anyone we could be compelled to help. A switch in Settings called "Send anonymous counts" turns it off; turning it off deletes everything waiting to be sent, right now. What has already gone cannot be withdrawn, and the reason we cannot pull it back is the same reason it was safe to send: there is no identifier to find it by. Your IP address reaches our server because every message on the internet carries one; it is used to stop abuse and is never stored. The counting code is in the app today and is switched off at our end, with no address to send to, so this version sends none of it. When a build turns it on, this page will be re-dated and the sentences above about "no analytics" will change with it, on or before that day.
- A sealed report route in the app. A report of something that happened during a voyage would be structured and encrypted on your phone before it is sent, and the alert that reaches Eidovelle Labs would carry none of what you wrote until it is opened on the one machine that holds the key. Nothing of this exists today, and today the app sends nothing.
- An account. An account would exist so that a purchase can follow you to another phone. It would hold an email address and what you are entitled to. That is the whole of it. It would not hold your screening outcome, your voyage log or your notes.
- A subscription platform. Entitlements would be handled through RevenueCat, which would process purchase identifiers and subscription state on our behalf. This is billing plumbing and it would not carry health information.
- A payment processor, if purchases are ever taken anywhere other than the App Store. We would not hold card numbers at any point. Today the App Store is the only place Eidovelle is sold.
Diagnostic reporting, when it arrives, is the anonymous daily counts item above and nothing more: screening outcomes, log entries and note text are excluded from it by construction rather than by configuration. There is no separate crash-reporting company and no third-party diagnostic kit, and if that ever changed this list is where you would read it first.
Three things will not change, and they are the point of the design:
- Screening outcomes and voyage log content stay on your device.
- No advertising, no tracking, no advertising identifier.
- An account is a receipt, not a profile.
10. Changes to this policy
The date at the top is the date this version took effect. When it changes materially we will say what changed and when, at the foot of this page, and we will keep the previous wording available so you can see what it used to say.
11. Contact
The terms you buy under are on the Terms of Use page. Anything about a voyage that left you feeling unwell goes somewhere else and is handled differently: see Support.
Eidovelle is not a medical device and does not diagnose, treat, cure, or prevent any medical condition.
For medical advice, diagnosis, or treatment, consult a healthcare professional.