Privacy Policy
Everything that applies to Ebb is here. The general part below covers the website and all apps.
Effective from November 2, 2026
This document is translated from the Czech version for your convenience. In case of any discrepancy between language versions, the Czech version is binding.
What the app does
Ebb uses data in Health (sleep, resting heart rate, heart rate variability and respiratory rate) to calculate a simple daily state against your own normal. It also offers a Journal, moods, breathing exercises and widgets. Ebb is not a medical device and diagnoses nothing.
Core principle: your data is processed only by your device. Ebb has no account or ads. Only what you send to support yourself (section 7), survey answers and anonymous usage counts (section 8) go to a server.
What is stored and where
- Nightly values and the states calculated from them
- Journal entries (day tags and a short note)
- Moods and breathing records
- App settings and whether you have Ebb Plus
Everything is stored only on your device and in the app's shared storage (App Group) so widgets and complications can read the state. Ebb does not sync data through iCloud. I have no access to this data and am not its controller. Device backups are managed by Apple.
The Health app
Ebb reads sleep, resting heart rate, heart rate variability and respiratory rate from Health. Optionally (only if you allow it in the app) it reads state of mind and menstruation records. It only writes the state of mind you choose in Ebb. You can remove access at any time in iPhone Settings → Privacy & Security → Health → Ebb.
Data from Health is not sent to any server, is not used for advertising, is not shared with anyone else, and nothing you write to support includes it. Mood and cycle do not enter the daily state calculation.
Sensitive entries
The Journal contains tags that may say something about health or personal life (for example Illness, Medication or personal entries). These are special categories of data under Art. 9 GDPR. They stay on your device only and do not enter the state calculation. Sensitive entries and cycle do not appear in graphics you can create and share in the app (for example the permission slip or weekend invoice). A shared image is created on your iPhone and you send it yourself; the app sends it nowhere.
Apple Watch, widgets and notifications
The state goes from the iPhone to the watch directly through Apple Watch Connectivity, without a server. Widgets and complications read the state from the app's on-device storage. Notifications are local: iOS schedules them on the iPhone, without a server and without a push service.
Purchases
Ebb Plus is bought through Apple In-App Purchase as a subscription. Only Apple sees payment details. The app verifies the purchase directly with Apple (StoreKit), without third-party services and without a user account.
Contact and support
The contact form (Settings → Contact) is optional. Only the text you write, the e-mail you enter and, if you leave it on, the device model and system and app version are sent. The message is stored as a ticket in the Neologos Development support system (Firebase, region europe-west3) and section 4 of the general part applies to it. The app never attaches Health data, the Journal or moods. If you put sensitive information in a message, I will use it only to answer your request and delete it on request.
Anonymous usage measurement and survey
To improve Ebb, the app anonymously counts how it is used: which screens were opened, which screen you close the app on, how long a session lasted (in coarse bands), at what hour you open it, where it was opened from (icon, widget, notification), which features you use, how far you got in onboarding, a coarse data status (e.g. "learning") and whether you opened or dismissed the Ebb Plus offer. Counts are summed on your device and sent once when you leave the app, as daily totals with no device identifier, no IP address and no account. This never sends Health values, Journal content, moods, notes or the day's state linked to you.
You can turn measurement off at any time in Settings → Data and privacy → Anonymous usage measurement. Nothing is sent after that.
The in-app survey (Settings or the card on Today) is optional. Answers (ratings, choices and any free text you write) are stored anonymously, without e-mail or identifier. If you want a reply, contact me separately through the contact form (section 7). Please do not put health or other personal data in free text; if you do, I will use it only for evaluation and delete it on request.
The legal basis is the legitimate interest in improving the app (Art. 6(1)(f) GDPR); because this is anonymous aggregate data, it is not profiling or tracking. Only I see the results, in an internal app; I do not pass them to third parties and they are not used for advertising. I keep the totals for at most 24 months.
What the app does not collect
- Health data, the Journal or moods on my servers
- Name, e-mail or account (e-mail only if you give it to support)
- A personal profile or history of your use (only anonymous daily totals, section 8)
- Location, contacts or photos
- Advertising identifiers (IDFA) or cross-app tracking
Retention and deletion
You can delete the Journal, moods and breathing records in the app under Settings → Data and privacy. Deleting the app removes everything stored on the device. Data in Health is unaffected; you manage it in the Health app. I keep support tickets and survey answers for at most 24 months. You can ask for earlier deletion under section 7 of the general part.
Contact
Write via Support or directly from the app (Settings → Contact).
General part (applies to the website and all apps)
Data controller
The data controller is Vojtěch Landa, a private individual, contact: vojtajess@gmail.com. Neologos Development is not a legal entity or a registered business — it's the name under which Vojtěch Landa, as a private individual, develops and runs neologos.dev and the apps listed below.
What this page covers
This privacy policy is shared across neologos.dev, vejce.neologos.dev, and the apps Blackout, Blurt, Limi, and Ebb. Each app also has its own section below, since it processes different data depending on what it does — the general part applies to all of them, and the app section adds to it.
Website traffic
neologos.dev collects basic, aggregate traffic statistics (visit counts, pages visited, approximate geographic area from IP address) via Vercel Analytics and, if enabled, PostHog. This data only exists to show whether the site is being used at all — it isn't sold, isn't shared with ad networks, and isn't linked to a name or email unless you provide one yourself (e.g. via the support chat).
Support chat and tickets
The Support section on the website and the support chat inside the apps let you report a bug, suggest an app improvement, ask about legal information or ask a general question. Chat messages are saved as a ticket in Firestore (Google/Firebase, see point 5). I answer every message personally — no AI or other automated system processes them.
When you report a bug directly from an app, a technical app log (error messages and app state) is attached to the ticket so the problem can be traced. An email or name is stored only if you type it into the form yourself — it is never collected automatically.
Blackout, Blurt and Limi also include a short, optional in-app survey. At the end we ask whether you'd like us to get back to you. If you choose "No", your answers are sent without an e-mail address or any contact detail, i.e. anonymously. If you choose "Yes", your answers are sent the same way and the app opens the support chat with your answers pre-filled in the message and the e-mail address you enter yourself. The message and e-mail are then stored as a ticket as described in this section, and the e-mail is used only to reply to your feedback. The survey record itself stays without an e-mail address.
Shared infrastructure
The website and apps run on Firebase/Google Cloud (Firestore, Cloud Functions, Cloud Messaging) — the servers for the apps and site are set to a European region (europe-west3) wherever Firebase allows it. Google acts as a processor there under its own privacy policy (firebase.google.com/support/privacy).
Push notifications (where an app offers them) use the Apple Push Notification service — Apple only needs an anonymous device token for this, not personal data.
Cookies
The website shows no ads and uses no advertising or tracking cookies. Your browser only stores what the site needs to work (for example your chosen language).
Your rights
Under GDPR, you have the right to:
- access your data
- correct inaccurate data
- erasure ("the right to be forgotten")
- restrict processing
- data portability
- object to processing
- withdraw consent at any time, where processing was based on it
- lodge a complaint with the Office for Personal Data Protection (uoou.gov.cz)
You can exercise any of these rights simply — write to vojtajess@gmail.com or via Support (category "Legal information").
What to expect from me: I'll reply no later than 30 days after receiving the request — either sending, correcting, or deleting the data right away, or explaining why (and on what grounds) that isn't possible. For a more complex request this deadline can be extended once by another two months, which I'll tell you about within the first 30 days. To verify identity I may ask for extra information (e.g. the email or nickname used in the app), so the data doesn't end up with someone else under your name.
Data retention
Tickets and incidents are kept for as long as needed to resolve the request, plus a reasonable period after for traceability (typically up to 24 months), then deleted. Data stored directly in the apps (see the app sections below) follows each app's own rules — most of it can be deleted immediately right in the app.
A conversation with the assistant where you leave no email is kept on the server only as a hidden draft, so it can still be handed to a person if you add an email. Nobody reads it, and it is deleted automatically after 7 days.
Changes to this policy
This policy may change as the site and apps evolve. The current version is always on this page; the date of the last change is shown in the header.
Change history
- First version
Where next