Privacy Policy
Last updated: · TIDURDURTI SRL
Bitesday is operated by TIDURDURTI SRL ("we", "us"), a company registered in Romania, which is the data controller for the processing described here. This policy covers the Bitesday iOS app, bitesday.com, and temporary meal-plan links on share.bitesday.com and viewer.bitesday.com.
TIDURDURTI SRL, registered office: Bulevardul Iuliu Maniu nr. 7, Corp I, birou nr. 2.11, compart. 14, etaj 2, Sector 6, București, Romania · Trade Register no. J2012006916405 · Tax ID (CUI) 30324173 · Phone: +40 750 274 148. Write to support@bitesday.com with any privacy question or request.
If you live in a US state with a consumer health data law, such as Washington or Nevada, our Consumer Health Data Privacy Policy also applies to you.
You can browse our marketing website without an account. We do not sell personal data, run advertising trackers, or use children's information for advertising. Health-data consent and optional app analytics are separate choices.
Information we process
- Website visits and service requests: hosting and infrastructure providers receive technical information needed to deliver and protect the service, such as IP address, request time, requested page, browser or device information, and security or error information.
- Account and household: your email address, authentication information, caregiver display name, household membership, measurement units, and other settings. Supabase handles authentication; passwords are not stored in plain text.
- Sign in with Apple or Google: if you choose one of these instead of a password, the provider confirms your identity and sends us an identity token. With Sign in with Apple we ask for your name and email address; you can share Apple's private relay address instead of your real one, and Apple sends the name only the first time. With Google, Google shares your name, email address, and profile picture link. Supabase stores the identity details the provider returns together with your account.
- Children's profiles: the name you enter, birth month and year, selected emoji, allergies, dietary-health needs, food and feeding preferences, structured safety choices, snack settings, and, if you choose to enter it, which milk the child drinks (for example breast milk, formula, or whole milk) and roughly how much. These details can reveal health information.
- Plans and feedback: generated meal plans, preparation guidance, grocery-list state, meal status, liked or disliked feedback, and amount eaten, used to provide your plan and inform future planning.
- After-meal notes: only if you choose to save one. A note holds what you noticed after a meal, picked from a short fixed list (skin, tummy, swelling, breathing, or something else), roughly when, an ingredient you suspect, and whether you asked us to keep that dish or that ingredient out of the child's plans. There is no free text. These notes are health information.
- Sharing records: the audience, expiry, creation and last-opened time of a link, and a hash of its access token. Pediatrician sharing can also contain your questions, saved responses, overall reviews, meal observations, save times, and an optional reviewer name. We do not verify the reviewer's identity or professional qualifications.
- Subscriptions: purchase and entitlement information, subscription status, and app-scoped identifiers handled with Apple and RevenueCat. Bitesday does not receive your payment-card or bank details.
- Choices and correspondence: your separate health-data choices, the document versions presented when you create an account, and contact details, messages, and attachments you send us. Please avoid emailing passwords, share links, medical records, or unnecessary information about a child.
- Optional app analytics: limited app-operation events and a pseudonymous account identifier, only after you allow analytics and are signed in.
The app also keeps local preferences, sign-in state, and cached plans. Onboarding progress stays on the device for up to 30 days, is excluded from device backups, and does not sync between devices. Home-screen widgets read a local snapshot rather than making their own network requests.
Children's information and health-data consent
Bitesday is for adults; children do not create accounts. To give health-data consent, you must confirm that you are at least 18 and are the child's parent or legal guardian with authority to make that choice. Receiving a shared link does not give its recipient authority to consent on your behalf.
Before sending a child's health and feeding information for personalized planning, we ask for a separate, initially unselected explicit choice. Accepting the Terms, opening a legal page, purchasing, or allowing analytics does not give that consent. We rely on consent under GDPR Article 6(1)(a), together with explicit consent under Article 9(2)(a) for special-category health information, for these purposes:
- A preview before account creation: Supabase receives birth month and year, allergy and dietary-health choices, safety selections, feeding and setup preferences, and, if you entered it, the child's milk type and amount to select a preview day. It does not receive the child's name for this preview. The job and its consent receipt expire within 48 hours.
- A saved child profile: after account creation, we store the child's name with their health and feeding profile so you can view and edit it.
- Personalized planning: we apply age, allergy, and food-form filters, create meal plans and groceries, and use saved feedback in future planning. If you save an after-meal note, we store it with the child's profile and keep the dish or ingredient you chose out of that child's future plans until you allow it again.
- Temporary sharing: each new link requires an additional explicit choice identifying its audience, disclosed information, and expiry. This is not part of the consent given during onboarding.
You can refuse; features needing the corresponding information will be unavailable. You can withdraw later in Settings → Health Data & Legal. Withdrawal stops new covered processing and queued work, revokes active shares, deletes that child's profile, plans, groceries, raw feedback, sharing records, and ordinary consent receipts, and clears related local caches. Your caregiver account and subscription remain. A later consent starts fresh and does not restore history.
Withdrawal does not affect the lawfulness of earlier processing or retrieve copies already held by recipients. A limited withdrawal record may remain as explained below. We request a new explicit choice before materially changing the purposes or information covered by health-data consent.
Other purposes and legal bases
- Providing your account, subscription, and service support: performance of our contract, or steps you request before entering one, under GDPR Article 6(1)(b).
- Website delivery, security, and general enquiries: our legitimate interests in reliable delivery, protecting accounts, preventing abuse, resolving technical problems, and responding to you, under Article 6(1)(f). This does not replace consent for child-health processing or optional analytics.
- Legal duties: responding to privacy requests and maintaining necessary consent, security, and legal records under Article 6(1)(c), where required by applicable law.
- Optional app analytics: your separate consent under Article 6(1)(a), which you can withdraw without losing product features.
Meal suggestions are selected automatically using the profile and preferences you provide. They are general planning guidance, not a medical diagnosis or a decision about treatment, eligibility, or legal rights. Caregivers decide what is suitable and when to seek professional advice. An after-meal note changes plans only through the choices you make when saving it. Bitesday does not interpret notes, look for patterns across them, or change the child's allergies because of one.
Optional analytics and cookies
Analytics are off until you choose Allow analytics in Settings and are signed in. Choosing Don't allow has no effect on your subscription, features, or personalized plan. You can change this choice at any time; Don't allow stops new analytics events.
If enabled, PostHog receives your account UUID and restricted events about purchases, generation reliability, navigation, account actions, and notification operation, with limited technical context such as platform, device class, and build configuration. The UUID is a pseudonymous identifier, not anonymous data. Events are sent to PostHog's United States endpoint.
We do not send PostHog children's names or profiles, birth or age data, allergies, safety details, food preferences, meals, plans, groceries, feedback, after-meal notes, review text, or share tokens. Saving an after-meal note sends no analytics event at all. We do not enable session recording, automatic screen capture, or advertising identifiers. Providers can still process technical request information, such as IP addresses, when delivering network requests.
Our marketing website and sharing viewer do not run product analytics, advertising trackers, social widgets, or embedded third-party content. We do not add advertising or analytics cookies. Essential hosting or security measures are separate from optional product analytics.
Because our websites do not track visitors across sites or over time, they do not respond differently to browser Do Not Track or Global Privacy Control signals; there is no such tracking for those signals to turn off.
Temporary sharing links
Sharing starts only when you create a link. Anyone holding a valid link can access its permitted information, so send it only to someone you trust. Caregiver links last from 4 hours up to 3 days; pediatrician links can last up to 7 days. You can revoke a link in Settings → Shared links. Expired or revoked links no longer authorize access.
Both audiences can see the selected child's first name, emoji, age in months rather than date of birth, snack setting, allergens, structured safety selections, and, if you entered it, the child's milk type and amount as drinks guidance; measurement settings; and the shared week's meals, ingredients, allergen information, toddler adaptations, guidance, status, and saved feedback. Caregiver links also provide preparation steps and groceries and permit saving liked or disliked feedback and amount eaten.
Both audiences also see which dishes and ingredients you are avoiding for now and which planned meals are on hold because of an after-meal note, so whoever feeds the child knows. What you noticed, roughly when, and any ingredient you suspected are shown only on a pediatrician link you created after agreeing to include after-meal notes, next to that meal's saved report. Pediatrician links created before that and caregiver links never show them, and link holders cannot write a note.
Pediatrician links provide available nutrition estimates and their serving basis, your questions, and the saved review exchange. Recipients may save a reviewer name, an overall review, meal observations, and responses. Caregivers can read saved sharing records in the app. Neither type of link permits replacing meals or editing recipes. A saved name or response is not proof of a particular professional's identity or clinical approval.
We store a token hash in the database, not the reusable token itself. The viewer sends the token to authorize service requests and may retain it in that browser tab's session storage for refreshes. It does not put the token in cookies or persistent local storage. Removing it from the visible address does not erase browser history, bookmarks, synced browser state, or recipient copies. Revocation cannot delete those copies.
Service providers and other recipients
- Supabase: authentication, database storage, and APIs for accounts, profiles, plans, consent records, and temporary sharing.
- Vercel: hosting, delivery, and security for our websites.
- RevenueCat: subscription and entitlement management. We do not send child profiles, meals, feedback, or review content to RevenueCat.
- Apple: App Store payments, subscriptions, and related platform services under Apple's own terms and privacy practices. If you use Sign in with Apple, Apple confirms your identity; when you delete your account, we ask Apple to disconnect Bitesday from your Apple ID.
- Google: if you choose Google sign-in, Google confirms your identity and learns that you signed in to Bitesday. Google acts under its own privacy policy. Google receives no child, meal, or health information from us. You can remove Bitesday's access at any time in your Google Account under Third-party apps & services.
- PostHog: optional app analytics as described above.
- Resend: delivery of sign-in, confirmation, and other account emails. It receives your email address and the message it delivers, not child profiles or meal data.
- Fastmail: hosting of our support mailbox, including the messages and attachments you send us.
- Authorized personnel: handling support messages and privacy requests.
Every provider that processes personal information on our behalf does so under a written agreement and must protect it at least as well as this policy describes and as applicable law and the App Store rules require. Providers may use it only to provide their service to us, not for their own advertising or other purposes. Apple and Google act under their own privacy policies for their sign-in and App Store services.
Information is also disclosed to recipients you choose through sharing, or where necessary to comply with applicable law, protect rights, or respond to a valid legal request. We do not disclose personal information to advertisers or data brokers. External services, including the App Store, apply their own privacy notices when you follow a link to them.
International processing
Our providers operate internationally. Information may be processed outside Romania and the European Economic Area, including in the United States. Optional PostHog analytics use its United States service. We do not promise EU-only storage.
Providers publish information about their data-processing terms and transfer safeguards, including standard contractual clauses and applicable adequacy frameworks: Supabase, Vercel, RevenueCat, PostHog, Resend, Fastmail, and Apple. Contact support@bitesday.com for information about transfers affecting your data or to request a copy of applicable safeguards. These providers do not all receive the same information or have the same role.
Retention and deletion
Access expiry and database cleanup are different: an expired link stops working even while its record is waiting for scheduled deletion. Our product retention rules are:
- Preview data: jobs and consent receipts expire within 48 hours; expired records are scheduled for hourly cleanup.
- Accounts and profiles: account information remains while you have an account. Child profiles delete on withdrawal, child removal, or account deletion. The account's Terms acceptance record deletes with the account.
- Plans, groceries, and raw meal feedback: history is scheduled for daily cleanup once it is 12 months old, or deletes earlier with the child or account.
- After-meal notes: deleted 12 months after the meal's date. A note that is still keeping a dish or an ingredient out of plans stays until you allow that food again or delete the note, so an excluded food never comes back without warning. Notes also delete with the child's profile, on health-data withdrawal, and with the account.
- Share links: expired or revoked metadata becomes eligible for deletion after 24 hours and is removed by daily cleanup.
- Sharing notes and questions: when a link is purged, saved review records detach from it. Detached records that are at least 30 days old are removed by daily cleanup. Child, plan, or account deletion can remove them earlier.
- Consent evidence: ordinary receipts delete with the child. A limited withdrawal record remains for up to three years before scheduled cleanup, or until earlier account deletion. It contains timing, version and deletion information and derived identifiers, not child names, health values, free text, IP addresses, or share tokens.
- Product-controlled security records: expired abuse-prevention records are scheduled for cleanup after 90 days. Information needed for a specific incident or legal obligation may be retained for that purpose.
- Support: correspondence is retained for handling and follow-up, normally no longer than 24 months after closure unless a legal obligation or dispute requires longer.
- Optional analytics: provider-held events are separate from the app database. Turning analytics off does not erase earlier events. Contact us to request erasure or information about retention applying to your records.
You can delete your account in Settings. After verification, deletion removes the Bitesday account and its linked household, child, plan, grocery, feedback, and sharing data. The app clears related local records. The analytics deletion integration requests PostHog erasure when available; external deletion may require follow-up and does not block deletion of the Bitesday account. Contact us if you need confirmation of external erasure.
Account deletion and health-data withdrawal do not cancel an Apple subscription; manage subscriptions through your Apple account. They cannot erase recipient copies, browser-owned records, or Apple's purchase records. Provider backups, security logs, and purchase records have separate retention requirements and deletion cycles. Removal from the active app database does not promise immediate erasure from every backup or external system.
Your rights and choices
Depending on applicable law and circumstances, you can request access, correction, deletion, restriction, or portability of your information, and object to processing. You can withdraw consent without affecting earlier lawful processing. Profile changes, consent choices, link revocation, and account deletion are available in the app.
Email support@bitesday.com to exercise a right or ask about a child's information. We may request information reasonably needed to verify identity and authority before disclosing or changing data. We respond within the applicable statutory period, normally one month under the GDPR, and tell you if a permitted extension is needed.
You may complain to a data protection authority. In Romania, this is the National Supervisory Authority for Personal Data Processing (ANSPDCP). You can also contact the authority in the EU country where you live, work, or believe an infringement occurred. Outside the EU, you can contact your local authority, for example:
- United Kingdom: the Information Commissioner's Office (ICO);
- Australia: the Office of the Australian Information Commissioner (OAIC);
- Canada: the Office of the Privacy Commissioner of Canada, or your provincial commissioner;
- New Zealand: the Office of the Privacy Commissioner;
- Mexico: the federal authority responsible for personal data protection.
These rights also apply to people who receive a sharing link. If you opened a link or saved a name, feedback, or review through one, you can contact us at support@bitesday.com to access, correct, or delete that information. Because a link identifies a child rather than you, we may ask for details of the link or the saved entry so we can find it, and we may tell the parent who created the link about a change to their child's records.
Security and changes
We use access controls, authenticated account access, limited temporary sharing, and other technical measures to protect information. No service can guarantee absolute security. Keep credentials and share links private and contact us if you believe information has been exposed improperly.
We update this policy when practices change and show the revised date above. For material changes, we provide additional notice where appropriate and request new consent when required. Questions and privacy requests: support@bitesday.com.