Privacy Policy

Vyne works fully offline and needs no account. Everything you create is stored on your device:

• Branches, habits and their check-ins, due dates and amounts
• Notes, lists and reminders
• Calendar items, time clock entries and your hourly rates, the money you log and plan in Budget and No-spend days (spending, income, savings, subscriptions, goals and debts), your flashcard decks and study history, and the water and other amounts you log
• Your daily journal and weekly diary
• The people you add and their birthdays
• Your profile name
• If you turn on cycle tracking, the health data it keeps; see "Cycle tracking" below.
• If you allow it, the days your Steps habit reached its goal and the sleep nights you save after filling them from Apple Health or Health Connect; see "Apple Health and Health Connect" below.

Nothing you create leaves your device unless you turn on Cloud Backup, share a profile or export a backup file yourself. Crash reports and update checks, which carry none of your content, are described below.

• If you turn on Cloud Backup, the email address you sign up with is handled by Firebase Authentication (a Google service), so you can sign back in and restore your data on another phone. Your password is handled by Firebase; I never see it.
• Your content (everything listed above, except cycle data, which goes to the cloud only with end-to-end encryption on, as described under "Cycle tracking") is then also stored in Firebase Firestore (a Google Cloud database), linked to your account. Along with it, Vyne stores a random ID for each installation of the app and the platform (iOS or Android), so it can tell which phone wrote a backup. That ID is created by Vyne, isn't tied to your hardware or to any advertising ID, and changes if you reinstall.
• If you share a profile, its content and the member details described under "Shared profiles" are stored in a shared space that the other member can see.
• Crash and performance diagnostics are sent to Sentry, as described in the next section.
• When Vyne starts, it asks Expo, the service that delivers Vyne's app updates (servers in the United States), whether a newer version is available. That request carries the app version, the platform, a random ID for the installation and, like any internet request, your IP address. It carries none of your content. When your phone talks to Firebase or Sentry, they also see your IP address and basic device information, as any internet service does, and use them only to run and secure their service.

Vyne does not collect your location, contacts, photos, microphone or browsing activity, and never asks for your real name. People you add on the People page are typed in by you; Vyne does not read your phone's contacts. Vyne shows no ads and contains no advertising or analytics SDKs. If that ever changes, this policy will be updated before the change takes effect.

Vyne uses Sentry, a crash-reporting service, to find and fix bugs. When the app runs into an error, Sentry receives:

• the error message and the screen it happened on
• the device model, OS version and app version
• a random identifier for the device, not linked to your account
• a short trail of the most recent taps and screens before the problem

Vyne also sends Sentry basic performance timings, such as how long a screen took to load. This data is not linked to your name or email, it is used only to diagnose problems, and Sentry does not use it for advertising or for its own purposes. Sentry stores it on servers in the United States, keeps it for 30 days and then deletes it automatically. Sentry is set not to store your IP address. You can turn crash reports off at any time in Account, under Privacy, with Send crash reports; while it is off, your phone sends nothing to Sentry.

Typing in the book form's "Find it" box searches Open Library, a free book catalogue run by the Internet Archive (servers in the United States). Each search is one HTTPS request to openlibrary.org that carries only the words you typed (3 to 120 characters) plus fixed search settings. As with any web request, it also carries your phone's IP address, a User-Agent of "Vyne/1.5 (vyneapp.help@gmail.com)" and the standard headers your phone's operating system adds, such as preferred language and accepted compression. Nothing else goes: no account, device or advertising ID, no shelves, reading log, notes, mood or sleep data. Vyne sends no cookies and does not keep cookies from Open Library. Searching is limited to one request per second and starts only after you have typed 3 characters and paused briefly. If you keep a result that has a cover, your phone fetches that picture from covers.openlibrary.org by its cover number. The picture is stored only in your phone's cache; it is never uploaded and never part of Cloud Backup or exported files. The book itself keeps only the cover number, the Open Library work key and the ISBN. Search is optional: typing a book by hand never uses the network, and the Goodreads or StoryGraph import reads a file on your phone and sends nothing.

If you allow notifications, Vyne schedules them on your device, at the times you choose:

• reminders for due dates, list items and reminders
• a habit's own reminder time
• the birthdays of people you add
• an optional daily check-in
• a short weekly note on Monday mornings

They are created on your phone and never involve sending your data to a server. You can turn them off in the app or in your phone's settings.

If you tap "Add to Calendar", Vyne opens your phone's own new-event screen with that item filled in, and you decide whether and where to save it. If you allow it, Vyne reads your phone's calendars to show them next to your plans. It only reads them: events are never copied into Vyne or uploaded. A countdown you turn on keeps only a pointer to that event, on this phone.

This is optional. On iPhone Vyne can read Apple Health, and on Android Health Connect, for two things only, and only after you allow each one: your daily step count, for a Steps habit, and your sleep times, when you tap "Fill from Health" on a Sleep habit. Vyne asks the first time you use each one, never when the app opens.

Read only. Vyne never writes anything to Apple Health or Health Connect, and reads nothing in the background. What it reads is shown on your phone while the screen is open. It is not stored, not sent to Vyne's cloud, and not put in a backup file, an export, a widget or an error report.

What Vyne keeps. Two things you could also enter by hand: the days your Steps habit reached its goal (a day marked done, like a tick, without the step count), and a sleep night you save after "Fill from Health" (the bed and wake times you saved, noted as filled from Health). They are kept and synced like your other habits: on your phone, and in Vyne's cloud if you turn on Cloud Backup, end-to-end encrypted if you turn that on. Steps and Sleep habits are never placed in a shared profile.

Never shared. Data from Apple Health or Health Connect is not used for advertising, marketing or analytics, not sold, and not shared with anyone.

Turning it off. iPhone: Settings → Privacy & Security → Health → Vyne. Android: Settings → Health Connect → App permissions → Vyne. Days already marked done and sleep nights you saved stay in Vyne until you delete them.

Vyne can export your data as a backup file, and you choose which profiles go into it. The file is created on your device and handed to your phone's share sheet, so it goes wherever you send it; I never receive a copy. When you import a file, you choose:

• "Add": only what is missing is added.
• "Replace": a profile that is already on the phone is overwritten by the file's copy.

Your last 3 imports can be undone, and profiles that aren't in the file are never touched.

Cycle tracking is off until you turn it on. When you turn it on, Vyne keeps the health data you enter or import: temperatures, period and bleeding, cervical mucus, cervix observations, LH and pregnancy test results, symptoms, how you feel, sex, things that may have affected a reading, your own marks on the chart, and your notes.

Where it is kept. On your phone, in Vyne's own storage. Your phone's own backup (iCloud Backup on iPhone, Google backup on Android) may include the app's local files, cycle data among them, depending on your device settings. Apple or Google run those backups under their terms, not mine.

Vyne's cloud. Cycle data reaches Vyne's cloud only if you have turned on end-to-end encryption for your account. It is then encrypted on your phone, like the rest of your backup, with a key that only your devices hold, before it leaves the phone. I cannot read it, and I cannot hand it to anyone in readable form. Without end-to-end encryption, cycle data stays on your phone and is not sent to Vyne's cloud. If you turn end-to-end encryption off, the encrypted cycle copies are deleted from Vyne's cloud and your data stays on your phones.

Never shared. I do not share, sell or rent cycle data. It is never placed in a shared profile. It is not used for advertising, analytics, research or to train any model, and Vyne has no advertising or analytics tools.

Files you make. Import reads a file you choose on your phone. Export (Vyne file, spreadsheet) and the PDF for a clinician are made only when you ask, and go only where you send them through your phone's share sheet.

Error reports. Vyne sends crash reports to Sentry to fix bugs. While a cycle screen is open no activity trail is recorded, cycle terms are removed from every report, and a crash inside a cycle screen is reported as one fixed message without content.

Deleting it. Settings → Cycle tracking → Delete all cycle data removes every day from your phone and from the encrypted cloud copy. Deleting your account deletes your cloud data and offers to delete cycle data from your phone too. Uninstalling Vyne removes the data from the phone (a copy may remain in your phone's own backup until that backup is replaced).

Not medical advice. Vyne shows what you logged. It does not predict, does not tell you when you are fertile or safe, is not medical advice and is not birth control. Optional rule helpers, off until you turn them on, show what one named, published rule says about the days you logged, for example where Sensiplan's coverline falls. They are not a fertile-window calculation and must not be used to avoid or plan a pregnancy.

Consumer health data (for example Washington's My Health My Data Act). The categories of consumer health data in cycle tracking are listed above; I collect them only to show them back to you; they come only from you (what you enter or import); I share them with no one. You can see all of it in the app, export it, and delete it at any time as described above; to ask me anything about it, write to vyneapp.help@gmail.com. Health-related things you log or type elsewhere in Vyne, such as a water habit, are covered by the Consumer Health Data Privacy Policy.

Consumer Health Data Privacy Policy (Washington and Nevada) →

You can share one of your profiles with one other person. This needs Cloud Backup to be on, and it only starts when you send an invite and they accept it.

While a profile is shared, everything in it (branches, habits and their history, notes, lists, journal, calendar items and time clock entries) is stored in a shared space in the same Firebase database as Cloud Backup. Both of you can see, change and delete everything in it, including what was in the profile before the other person joined. Members are equal: neither of you can remove the other. Your other profiles, notes and settings stay in your private backup and are not shared.

About its members, a shared profile stores your account ID, the date you joined, and the name you chose to show to the other member (it starts as your profile name; you can change it or leave it empty, and then you appear as "Other member"). For each habit day, it stores which member marked it and when; the other member sees this as "Done by". Like everything Vyne syncs, each item also carries when it was last changed and the random installation ID of the phone that changed it. The other member does not see your email address. Vyne does not record when you open the app, what you look at, or where you are.

An invite is a code and a link that you send yourself, through the app you choose (for example Messages). It includes the profile's name, works once and expires after 24 hours. The invite record (the code, the profile it is for, your account ID and, once used, the account ID of the person who joined) is kept until it is cancelled or replaced, or until you leave the profile or delete your account.

The other member can see everything in the shared profile. A shared profile lives in a separate shared space that both members read, stored by Google on my behalf and protected by access rules that stop anyone other than its two members from reading it. It can be end-to-end encrypted too: when both members have end-to-end encryption on, either of you can encrypt the shared profile, and its content is then encrypted on your phones with a key that only the two members' devices hold. Until then, it is encrypted in transit and at rest but not end-to-end encrypted. Anything the other member can see, they can also keep: for example by keeping a private copy when they leave, by exporting a backup file, or with a screenshot. Copies like these are outside my control, so only share a profile with someone you trust.

When a branch, note, list, calendar item or time clock entry is removed from a shared profile, a copy goes to "Recently removed", where either member can restore it for 30 days. After that it is deleted the next time either of you opens Vyne, so it can stay longer if neither of you opens the app. Entries inside a list, log lines and single ticks are not kept there (they have the usual Undo), and neither is an item moved to a private profile.

You can leave a shared profile at any time (Shared space screen → "Leave this shared profile"), and you can choose to keep a private copy of it. The copy goes into your private backup, without the record of who did what. When you leave:

• the shared profile is removed from your phones;
• your name, account ID and join date are removed from its member list, and your account ID is replaced by a random ID in its items and in Recently removed; the shared profile keeps that random ID and the date you left;
• the random installation ID on items you changed stays, and does not tell the other member who you are;
• invites you made for it, and the one you used to join, are deleted;
• the other member keeps the shared profile and everything in it, including what you added, and sees "Former member" where your name was.

This does not change text anyone typed into the profile: if you wrote your name or other details into a note, they stay there until someone edits or deletes them. If the other member's phone is offline, it can keep your name and account ID in its own copy until it next connects; then it removes them, keeping only a scrambled, one-way form of your account ID, used only to make sure your ID is never written back. If you are the last member, leaving deletes the shared profile and everything in it, including Recently removed, from the servers.

If you delete your account, Vyne first takes you out of every shared profile as described above, without keeping a private copy, and removes them from your phone. A shared profile with no other member is deleted with all its content, and your invites are deleted. Only after that are your private backup and your sign-in deleted. If Vyne cannot finish leaving a shared profile (for example, you are offline), nothing in your private backup or account is deleted and you can try again; shared profiles you have already left stay left.

After you leave or delete your account, what you added to a profile that another member still uses stays with them, because it is their profile too, without your name or account ID. If you want something you added gone, delete it from the shared profile first; it then stays in Recently removed for 30 days, where the other member can still restore it, and is deleted after that.

Cloud data is linked to your account, and the database's access rules stop other users from reading it, except the other member of a profile you chose to share. Google encrypts it in transit and at rest. Without end-to-end encryption, that is how your backup is protected, but it is not end-to-end encrypted. I don't look at your content, except when you ask me for help with your own data or when the law requires it.

End-to-end encryption is an optional Cloud Backup setting for your account. When you turn it on, the content of your whole cloud backup (branches, habits, notes, journal, lists, calendar items, time clock entries, cycle data and everything else in it) is encrypted on your phone, with a key that only your devices hold, before it leaves the phone. I cannot read it, and I cannot recover it if you lose your recovery code and all your signed-in devices. Even with it on, your email address, how many items are stored, their approximate size, when they changed and the random installation ID on each item stay visible on the server. In an end-to-end encrypted shared profile, the member list (each member's account ID, shown name, join date and a public key Vyne uses to pass the profile's key between your phones) and the record of former members stay readable too; the content does not. Cycle data goes to the cloud only with end-to-end encryption on, as described under "Cycle tracking". A shared profile has its own key and is encrypted separately, as described under "Shared profiles".

Cloud Backup and shared profile data (Google Firebase) and crash reports (Sentry) are stored, and app update checks (Expo) are handled, on servers in the United States; if you use Vyne from outside the US, this data is transferred there. For people in the EU, UK and Switzerland, I rely on the EU-U.S. Data Privacy Framework (and its UK and Swiss extensions) where the provider is certified under it, and otherwise on the European Commission's standard contractual clauses in the provider's data processing terms. On your phone, your data is protected by the operating system's app sandbox.

If something goes wrong: if I learn that someone got access to your data who should not have, I will tell you by email without undue delay, explain what happened and what you can do, and tell the authorities where the law requires it (for example within 72 hours under the GDPR, and under the FTC's Health Breach Notification Rule for health data). End-to-end encrypted data stays unreadable without your key.

If I receive a legal demand for your data, I will check that it is valid, hand over only what the law requires, and tell you unless the law forbids it. For end-to-end encrypted data, including all cycle data in the cloud, I can only hand over encrypted data I cannot read.

I don't sell, rent or share your data with advertisers or data brokers. The only services that handle data for me are Google Firebase (Google LLC: sign-in and backup storage), Sentry (Functional Software, Inc.: crash and performance diagnostics) and Expo (650 Industries, Inc.: app updates). None of them uses your data for its own purposes. Apple and Google, as the app stores, may collect information about downloads and purchases under their own privacy policies. If you share a profile, its content is also visible to the person you invited (or who invited you), as described under "Shared profiles".

The person responsible for your data (the "data controller") is Hasan Kalkan, the independent developer of Vyne, reachable at vyneapp.help@gmail.com. I use your data only on these grounds:

• Cloud Backup: to give you the service you asked for, keeping your data and returning it to you (performance of a contract; GDPR Art. 6(1)(b), KVKK Art. 5(2)(c)).
• Shared profiles: to give you the sharing you asked for (performance of a contract, as above). When you leave or delete your account, what you added stays for the other member, with your name and account ID taken out: their and my legitimate interest in keeping their profile whole (GDPR Art. 6(1)(f), KVKK Art. 5(2)(f)).
• Crash and performance data: my legitimate interest in keeping the app working and fixing bugs (GDPR Art. 6(1)(f), KVKK Art. 5(2)(f)). You can object by emailing me.
• Cycle tracking: this is health data, including data about your sex life, so I process it only with your explicit consent, which you give on the "Before you start" screen when you turn cycle tracking on (GDPR Art. 9(2)(a), KVKK Art. 6). Most of it never reaches me: it stays on your phone, and its cloud copy, if there is one, is end-to-end encrypted. You can withdraw your consent at any time: turn cycle tracking off and choose Settings → Cycle tracking → Delete all cycle data. Withdrawing does not affect what was done before.
• Nothing is used for advertising, profiling or automated decisions about you.

Cloud data is kept only as long as your account exists; there is no separate archive. The exception is a shared profile: what you added stays with the other member after you leave or delete your account, as described under "Leaving a shared profile". You can permanently delete your account and cloud data any time from the More tab → Cloud Backup → "Delete My Account & Cloud Data" (the button appears once you are signed in). It takes effect immediately. You can also email me and I'll delete it for you, taking the same steps for shared profiles. Uninstalling the app removes the data stored on your phone.

Depending on where you live (for example under the GDPR in the EU and UK, Turkey's KVKK, or US state privacy laws), you may have the right to access, correct, export (portability) or delete your data, to restrict or object to how it is used, and to withdraw any consent you gave, without affecting what was done before. You can do most of this yourself in the app: edit anything, export a backup file, or delete your account. For anything else, email me; I answer within 30 days.

If you think I have handled your data wrongly, please write to me first so I can fix it. You also have the right to complain to a data protection authority: in the EU, the authority in the country where you live or work; in the UK, the Information Commissioner's Office (ico.org.uk); in Turkey, the Personal Data Protection Board (kvkk.gov.tr), after you have applied to me.

Together with the sections above, this is the information notice under Turkey's Personal Data Protection Law No. 6698 (KVKK). The data controller, the data, the purposes and legal grounds, and who receives the data are described above, in "What Vyne collects", "Shared profiles", "Sharing with third parties" and "Why I can use your data".

• How it is collected: electronically, through the app, when you sign up, when you use Cloud Backup or sharing, and automatically when the app runs into an error.
• Transfer abroad: Cloud Backup and shared profile data are stored by Google, and crash reports by Sentry, on servers in the United States. Cloud data goes there only if you turn on Cloud Backup, and for that I rely on your explicit consent, which you give by turning it on; you can withdraw it at any time by deleting your account. Crash reports are not linked to your name or email.
• Your rights under KVKK Art. 11: to learn whether your data is processed and, if so, to ask for information about it; to learn the purpose and whether it is used for that purpose; to know the third parties in Turkey or abroad it is transferred to; to ask for incomplete or wrong data to be corrected, and for it to be deleted; to ask that a correction or deletion be passed on to those third parties; to object to an outcome against you that arises only from automated analysis; and to ask for compensation if unlawful processing causes you damage.

To use these rights, email me at vyneapp.help@gmail.com from your account's email address. I answer free of charge within 30 days at the latest.

Vyne is not directed at children under 13, and I don't knowingly collect data from them. If you believe a child under 13 has created a Cloud Backup account, email me and I'll delete it.

When this policy changes, the date at the top changes too. If a change is significant, for example a new kind of data or a new service that receives it, I will tell you in the app before it takes effect, and I will ask for your consent again where the law requires it.