Privacy Policy
What CareVentory stores, where, and why — written from what the app actually does.
Last updated: 2026-11-12
Privacy Policy
Who we are
CareVentory (“the app”, “we”, “us”) is provided by Oğuzhan Kırlı, an individual (natural person) resident in Türkiye, Girne Mahallesi, Eser Sokak, Meriç Sitesi, A Blok, Kat 1, Daire 5, Maltepe, İstanbul, Türkiye. Oğuzhan Kırlı is the data controller for the personal data described in this policy.
Privacy contact: [email protected].
EU and UK representative: none appointed (see “Representatives by region”). No data protection officer is designated.
Representatives by region
We have not appointed a representative in the EU or the UK. Questions about territorial scope and representation are kept under review.
- Switzerland: we have not appointed a representative in Switzerland; this is kept under review and a representative will be named here if one is appointed.
- Türkiye: the controller is resident in Türkiye, so no representative under the Turkish Personal Data Protection Law (KVKK) applies. The controller is exempt from registration with the Data Controllers’ Registry (VERBİS) under decision No. 2025/2393 of the Personal Data Protection Board.
What the app is
CareVentory helps parents and caregivers log baby care (feeds, diapers, sleep), pumping sessions and supplies, and share them in a family. It records what you enter. It gives no medical advice and is not a medical device.
Without an account, everything stays on your device and nothing is sent to us. Data reaches our servers only if you sign in, to sync between phones or to share with other caregivers.
Data kept only on your device
- App settings (appearance, units, reminder settings), running timers, low-stock alert state.
- Local reminders scheduled by your operating system. We use no remote push notifications.
- Your sign-in session, in the device’s secure storage.
- Without an account: all care logs and supplies, in the app’s local database.
- Device backups: Android backups do not include the care database. An iPhone backup you turn on (iCloud or computer) includes it. Those backups are controlled by you and Apple.
Data on our servers after you sign in
- Account data: email address and a random account id. Other caregivers see your display name, not your email.
- Sign-in provider data, only if you use Sign in with Apple or Google. Apple: the provider’s account id and the email it gives us (possibly a private relay address), and an encrypted refresh token used to revoke Apple access when you delete your account. Google: the app does not ask for your name or photo, but Google’s sign-in token can contain claims such as name, profile picture and email, and our authentication provider (Supabase Auth) stores them in the account’s identity and user metadata. Household members do not see them.
- Display names, household and baby names, optional baby birth date, household membership with relationship label and permission settings, invites (only a hash of the code). A membership is removed when the person leaves, is removed or deletes their account; the care entries they logged stay in the household without attribution.
- Baby-care logs (feeds, diapers, sleep, who logged them), pumping logs, supplies (stored milk portions, diaper counts). The account id of the person who archived a baby stays in that baby’s record, and a deleted baby’s deletion marker keeps the account id of the person who deleted it.
- “Recent changes”: who added, edited or deleted an entry and when, never what it said; pumping is not recorded. Visible to household members.
- Technical sync records (they stop a change from being applied twice when a phone re-sends it): a change id, the household id, the account id of the person who sent it, the kind of change, whether it was applied or rejected, a result code and small outcome flags or counts, and the time. They hold no baby-care, supply or pumping content and no names.
- Subscription status: trial dates, plan, expiry, store, store purchase identifiers and tokens, which household it pays for. A household-level access record, if one is set, carries a short free-text note written by us.
- Trial eligibility: a keyed one-way hash of your verified email address and, for Apple or Google sign-in, of your provider account id, recorded when a trial starts.
- Consent records: which consent, its version, the time and whether it was given or withdrawn.
- Server logs of our providers: IP address and user agent, time and endpoint, in the logs of Supabase Auth, its API gateway and server functions, our website host, and delivery logs of our email provider.
Who in your household sees what
- Only you: your email address and the store purchase identifiers.
- Nobody, not even household members: sign-in provider data, technical sync data and trial-eligibility hashes.
- Household members: display names, household and baby names, baby birth date, membership and role, baby-care logs, pumping logs (editable or deletable only by their author), supplies, “Recent changes”, and whether the subscription is active and who pays.
Trial eligibility (one trial per person)
To offer one trial per person we record, when a trial starts, a keyed one-way hash (HMAC-SHA256) of your verified email address (never a private relay address) and, if you sign in with Apple or Google, of your provider account id. Your account id is kept with the record only while the account exists. The hashes stay after account deletion (with, if the household continues, the link to that household) and are still personal data. No retention period is set: a daily purge job exists in the database but deletes nothing while the retention setting is empty. A second household, or a new account with the same email address, gets no new trial.
Sign in with Apple and Google
These optional sign-in methods are offered only when they are available in your version of the app. If you choose one:
- Our sign-in request to the provider contains the app’s client id; for Apple it also contains a hashed nonce.
- The provider’s account id and email are not shown to household members. The app does not request or show a name, photo or other profile detail; see “Data on our servers” for what Google’s token can still contain.
- For sign-in, Apple and Google act as independent controllers.
Security check (CAPTCHA)
The sign-in screen (through a hidden in-app web view of our helper page) and the account-deletion page can support an optional security check by Cloudflare Turnstile. It is currently switched off: no Cloudflare script runs for it and Cloudflare receives no data through it. We will update this policy before we switch it on. If it is on, a script from challenges.cloudflare.com runs, so Cloudflare receives your IP address and the browser signals needed to tell people from automated traffic, and content from Cloudflare may set cookies or use storage inside that web view. Cloudflare states that it processes only data strictly necessary for this security function and does not read what you type. We set no cookie ourselves.
Health-related data
Pumping logs describe the caregiver’s lactation and are health data. Baby-care logs describe an infant’s feeding, diapers and sleep; whether routine infant-care logs are health data is debated, and we treat them as health-related data as a precaution and protect both the same way.
Before health-related data is synced to our servers, the app asks for explicit consent, separately from this policy and the Terms:
- Household health data (baby-care logs, supplies, baby profile): given by the household owner, or by a member recorded in the household as the baby’s mother or father. Whoever gives it confirms in the app that they are the baby’s parent or legal guardian, or are authorised by them to manage the baby’s data. Other caregivers are not asked.
- Pumping logs: each caregiver for their own entries; this consent is the user’s own. Without a grant nothing of that kind is synced (“consent required”); the records wait on your device. Withdrawing stops syncing for that purpose. When the household consent is withdrawn, cloud sync stops for all members of that household. Data already on the server stays until it is erased by leaving or removal from the household, account deletion or household dissolution; there is no separate in-app action to erase only your pumping entries. If the consent wording changes, the app asks again. Pumping entries are visible to household members who have view access, and can be edited or deleted only by their author. Consent events (which consent, version, time, given or withdrawn) are kept as proof; after account deletion your account id in them is replaced by a one-way hash. How long: no fixed period has been set.
We do not collect location, contacts, photos, advertising identifiers, analytics or crash-reporting data, or data from Apple Health or Google Health Connect. The app has no advertising and no third-party tracking, and we do not sell personal data. Error diagnostics stay on your device unless you share them from Settings.
Why we use data and on what legal basis
- Account and sign-in, sync and sharing, subscription: performance of the contract (GDPR Art. 6(1)(b)).
- Pumping logs and baby-care logs on our servers: Art. 6(1)(b) together with your explicit consent under Art. 9(2)(a), recorded in the app (see “Health-related data”).
- “Recent changes”, security and abuse prevention, trial eligibility: legitimate interest (Art. 6(1)(f)).
- Legal obligations: Art. 6(1)(c). Consent records (proof that consent was given): Art. 6(1)(c) with Art. 7(1). You can withdraw consent in the app; withdrawal does not affect earlier processing.
Legal basis by purpose, continued
- Sign in with Apple or Google: Art. 6(1)(b) (the sign-in you ask for).
- “Recent changes” and sharing with caregivers you invite: Art. 6(1)(b) or (f); shared health data rests on the consent described above.
- Providing the subscription: Art. 6(1)(b).
- Other jurisdictions (UK GDPR, US state privacy and health-data laws such as the Washington My Health My Data Act and CCPA/CPRA, Türkiye KVKK): we apply the legal bases above and have not added country-specific bases.
- There is no sync-off switch other than not giving, or withdrawing, the consent above.
Who processes data for us
- Supabase (Supabase Pte. Ltd., Singapore, per its data processing terms) runs the database, authentication and server functions. The production database is hosted on Amazon Web Services in Germany (Frankfurt,
eu-central-1). A separate development project (Ireland,eu-west-1) is used for testing and is not used by app users. - Resend (United States) sends the sign-in code emails from
[email protected]over SMTP; it handles your email address and the message. - Cloudflare (United States) hosts the website (Cloudflare Pages) and forwards mail sent to our support and privacy addresses (Cloudflare Email Routing).
- Apple and Google are independent controllers for purchases and, if you choose Sign in with Apple or Google (when available), for sign-in. They process purchases under their own terms and tell us the subscription status and purchase identifiers, never payment details.
Our providers’ data processing terms include the EU Standard Contractual Clauses for transfers of personal data from the EU. For the Turkish side see “International transfers”.
Logs, encryption and clean-up
- Server logs (IP address, user agent) are kept by our providers (Supabase Auth, API gateway and server functions, website host); how long depends on their plans. Delivery logs of our email provider are kept by that provider.
- A daily clean-up job enforces the 30 and 90 day periods where the database supports scheduled jobs. It is active on the production database.
- Subscription records kept by Apple and Google follow their own policies.
How long we keep data
- Logs and supplies: while the household exists, until deleted. Deleting an entry erases its contents (data, times, author, stock link); a minimal row (id, baby, kind, timestamps) stays for the life of the household, until the baby is deleted or the household is dissolved, because devices need it to drop their copy. Edits keep only the latest version.
- “Recent changes”: 90 days. Technical sync records and ended invites: 30 days. This short technical period is separate from any retention required by law. Technical sync records of other members of a household that was deleted remain until they pass the 30 days; they hold no care content.
- Backups of our hosting provider: we do not restore deleted data from backups except to recover from a security or availability incident; any provider backups are deleted on the provider’s schedule.
- Trial-eligibility records (a one-way hash of your email address and, for Apple or Google sign-in, of your provider account id; if the household continues, also the link to that household) are kept after account deletion for as long as needed to offer one trial per person; no fixed period has been set.
- Records of your consent choices are kept after your account is deleted, without your account id (replaced by a one-way hash), to prove that consent was given, for as long as that proof may be needed; no fixed period has been set.
- The account ids stored on a baby’s archive record and on a deleted baby’s marker stay after the person deletes their account until the baby or household is deleted.
- Apple revocation queue (Apple sign-in only): an encrypted token without your user id, until Apple confirms, at most 30 days or 20 failed attempts.
- Sign-in codes expire after 10 minutes and work once.
More information for users in the EU, EEA and UK (GDPR Arts. 13-15)
- Source of data: from you. Data about an infant is entered by a parent, guardian or caregiver. Other caregivers’ display names are entered by them or by the household owner. Subscription status comes from the store.
- Providing data: an email address is needed for an account; without an account the app works on your device only.
- Automated decisions: none with a legal or similarly significant effect. Trial eligibility is checked automatically against the hashes above; if you think the result is wrong, write to [email protected] for a human review.
- You can object to processing based on legitimate interest, withdraw consent at any time without affecting earlier processing, and complain to your supervisory authority.
- Transfers outside the EEA: see “International transfers”; you can ask [email protected] for information on the safeguards.
Consumer health data (Washington and other US states)
What you enter about a baby’s feeding, diapers, sleep and pumping can be consumer health data. We collect it only from you, to provide the features of the app (logging, family sharing, sync, export). We share it only with the providers that run our service (see “Who processes data for us”) and with the household members you choose. We do not sell it and do not use it for advertising. You can ask us for access to it, withdraw your consent or have it deleted through the app (export and account deletion) or by writing to [email protected].
Your rights
Depending on where you live, you can ask for access, correction, erasure, restriction, objection, portability and withdrawal of consent. In the app you can view and correct your logs, export your data, delete entries, leave a household and delete your account. For other requests write to [email protected]. You may complain to the data protection authority of your country.
Children
The app is for parents and caregivers aged at least 18. It stores information about infants that their parents or caregivers enter; the infant is not a user. If you believe a child has created an account, contact us and we will delete it.
Security
Server data is reachable only through checked functions that verify household membership and role. Data is encrypted in transit. Sign-in uses one-time codes or a provider token; the app uses no passwords. No method is completely secure.
If a personal data breach occurs, we notify the Turkish Personal Data Protection Board within 72 hours of becoming aware of it and inform the people affected as soon as reasonably possible. For users in the EU, the UK and Switzerland we also notify the competent data protection authorities and inform affected users where their law requires it.
Changes
We will announce material changes in the app before they apply and update the date above.
Cookies and device storage
Cookies and device storage
- Website: our pages set no cookies, use no browser local or session storage, and contain no analytics, advertising, social-media or tracking scripts. Fonts and images come from our own site. Nothing optional is used, so there is no cookie banner.
- Account-deletion page: your request goes directly from your browser to our Supabase backend, which receives your IP address and browser details like any request. Your sign-in session is kept only in the page’s memory (no cookie, no storage) and ends when you close or reload the page. If the optional Cloudflare Turnstile security check is switched on, the page loads its script from challenges.cloudflare.com (see “Security check”).
- App: we set no cookies, and the app has no advertising identifier and no analytics. It keeps settings, running timers and, without an account, your records in its private local database, and your sign-in session in the device’s secure storage. If the optional sign-in security check is switched on, the app opens a hidden web view that loads our helper page and the Cloudflare Turnstile script; content from Cloudflare may set cookies or use storage inside that web view. We will update this page before any other security-check provider is used.
- We treat the storage above and the security check as strictly necessary for the app and security you asked for, so no consent banner is shown. Cloudflare’s documentation names only an optional pre-clearance cookie, which we do not use.
- Hosting server logs (IP address, time, page) are kept by our hosting provider; retention depends on its plan.
- If we ever add optional cookies or trackers, we will ask you first and update this page.
Deletion and retention
Deleting your account (Delete account)
- Households where you are the only active member are deleted with all their data.
- In other households your membership is removed and your pumping entries are erased (soft-deleted, their data emptied). Baby-care entries you logged stay with the household without attribution (the author is cleared); the change-history actor tied to you is cleared and your command log is removed.
- Invites you created are revoked and removed after 30 days.
- Your email, account, memberships, your own technical sync records and subscription record are deleted.
- When a household is deleted (you were its only active member, or you chose to delete it for everyone), the baby-care entries, shared household records, pumping records of all members and invites in it are deleted with it. The technical sync records that other members’ phones sent for that household are not deleted at that moment: they hold no care content and are removed by the daily clean-up once they are older than 30 days (see “How long we keep data”).
- If you own a household with other members, ownership passes to the successor you choose, otherwise to the member who joined first. If you were the paying owner, the household’s store subscription link is removed and the household returns to the trial or expired rules (no family sharing) until a member subscribes. Deleting it for everyone is a separate option you must confirm.
- If you used Apple sign-in, our server asks Apple to revoke access.
- Deleting your account does not cancel a store subscription; cancel it in your store account. Two residues remain: the household’s change log keeps a membership marker containing your account’s internal identifier (a random UUID, no name or email) for the household’s sync history; and the trial-eligibility record keeps its keyed hash and, if the household continues, the link to that household. Consent records remain with your account id replaced by a one-way hash. The trial-eligibility hash and the consent records are kept as legal and audit evidence, not as care data. Gift and promotional subscriptions are redeemed through the App Store or Google Play and belong to your store account; a household-level access record, if one exists, belongs to the household, not to your account, and goes when the household is deleted. We do not restore deleted data from backups except to recover from a security or availability incident; any provider backups are deleted on the provider’s schedule. See “How long we keep data”.
- You can also delete your account without the app at /account-deletion/.
Leaving or being removed
You stop seeing the household and its data leaves your device. Your membership is removed and your pumping entries there are erased; baby-care entries you logged stay with the household without attribution. The only member who leaves deletes the household. An owner must first choose a new owner (“Make owner”).
What stays when someone’s access ends
- “Recent changes” entries caused by a member who leaves, is removed or deletes their account stay until they are pruned after 90 days. The person who caused them is cleared from them.
- Milk portions already in storage stay, because they are the baby’s food supply, without a link to the deleted pumping session.
- Baby-care entries stay with the household. A deleted entry leaves a minimal row (id, baby, kind, timestamps) for the life of the household, until the baby is deleted or the household is dissolved.
- The deleted account’s membership record is removed; no row with a relationship label or permission settings is kept. The household’s change log keeps a membership marker containing the deleted account’s internal identifier (a random UUID, no name or email) for the household’s sync history.
- The account id of a person who archived a baby, or deleted a baby (in its deletion marker), stays in those records after the person deletes their account.
Archiving and deleting a baby
A baby can be archived: the history is kept and the baby is shown as archived, and can be restored. A baby can also be deleted permanently after you confirm it. Deletion removes that baby’s records, can be done only by roles that are allowed to, and cannot be undone.
Signing out
Signing out removes the app’s data from that device; data already synced stays in your account. It also cancels the reminders scheduled for the account on that device. Reminders are planned again only after you sign in.
When access ends
When a trial, subscription or promotional offer ends, nothing is deleted. You can still view your records, delete your own entries, export, manage the family and its security, subscribe or restore a purchase, contact support and delete your account. Logging and changing records needs an active plan.
Export and portability
Export your data (Export my data)
At no charge, at any time and also after access has ended:
- From this device: a JSON file with your household, baby profile, caregivers (names and roles), your complete history of feeds, diapers and sleep, your own pumping sessions and supplies; and a CSV file of the entries.
- From your account (when signed in): a JSON file with your email, memberships, subscription status and the data of each household you belong to, including your own “Recent changes” entries, your consent records (consentEvents), the invites you created (without the code), your store purchase identifiers (for Google Play, the purchase token) and trial records (without the hash).
Limits of the export
- The owner can restrict export. Then a member’s export holds only their own membership and pumping sessions.
- Not included: pumping sessions of other caregivers, their email addresses, households you left, deleted entries and their minimal markers, other people’s change-history entries, invites created by others, permission bookkeeping, notes on manual access grants, server and email logs, internal technical data.
- The file contains health data. Once saved or shared it is outside the app’s protection. Other requests: [email protected].
More about the export
- While the owner’s export restriction is on, a member’s export holds only their own membership and pumping sessions. Baby-care history, other caregivers’ names and the household’s stock are left out; account data and subscription status are always included.
- Files already exported cannot be recalled.
- The file is shared through your device’s share sheet, or downloaded in a browser.
- For any other copy of your data, such as technical sync records, write to [email protected].
- We answer requests within one month.
International transfers
International transfers
Our production database is stored in the EU (Germany, Frankfurt, Amazon Web Services) and operated by Supabase Pte. Ltd. (Singapore). Resend and Cloudflare are based in the United States, and Apple and Google may process data outside your country. For data of people in the EU, the UK and Switzerland, our providers’ data processing terms include the EU Standard Contractual Clauses (with the UK and Swiss addenda where they apply). Our controller is established in Türkiye, so storing data with these providers is a transfer abroad under Article 9 KVKK. Our providers’ data processing terms apply to these transfers; KVKK Article 9 standard contracts have not been concluded.
Transfer safeguards
For people in the EU, the UK and Switzerland, transfers to our processors (Supabase, Resend, Cloudflare) rely on the providers’ data processing terms, which incorporate the EU Standard Contractual Clauses (with the UK and Swiss addenda where they apply). Apple and Google act as independent controllers under their own terms. Türkiye: standard contracts under Article 9 KVKK have not been concluded with our providers; this is kept under review.
Country-specific information
Country-specific information
- European Union and EEA: offered. Representation: see “Representatives by region”.
- United Kingdom: offered. Representation: see “Representatives by region”.
- Switzerland: offered. No representative in Switzerland has been appointed; this is kept under review.
- Türkiye: offered. Controller resident in Türkiye; the VERBİS registration exemption applies under KVKK Board decision 2025/2393.
- Brazil: contact for data protection matters (LGPD): [email protected].
- United States (state privacy and health data laws): see “Consumer health data (Washington and other US states)” in the Privacy Policy.
- Japan and South Korea: no country-specific disclosure has been added.
- India, Indonesia and other launch markets: no country-specific disclosure has been added.