Coparenta · Privacy
Privacy Policy
Last updated: November 5, 2026
Citește în română →This English version is a translation provided for your convenience. In case of any discrepancy, the Romanian version at coparenta.ro/privacy prevails as the legally binding text.
1. Who we are
Coparenta is an app for coordinating child custody and daily life between separated or divorced parents. Data Controller within the meaning of the General Data Protection Regulation (GDPR, EU Regulation 2016/679):
COPARENTA S.R.L. (formerly PACSUNA CARTIE S.R.L.), a limited liability company registered in Romania.
Trade Register no.: J2021003293220 · Unique registration code (CUI): 44983034 · Share capital: RON 200
Registered office: Str. Iazului nr. 17M, sat Horpaz, com. Miroslava, jud. Iași, Romania
Contact: contact@coparenta.ro
This policy explains in plain language what data we collect about you and the children in your family, why, with whom we share it, and what rights you have.
2. The data we collect
2.1 Data about parents (adult users)
- Email — for authentication with a code sent to your email (passwordless)
- Display name (which you choose)
- Identification colour in the calendar
- Preferences — time zone, quiet hours for notifications
- Push notification tokens (the device identifier used for notifications) — to send you notifications
- Payment details, if you choose to fill them in — IBAN and account holder name, or your Revolut username. They are optional and serve a single purpose: letting the other parent settle an expense. Coparenta does not initiate or process payments; the details are shown to the other parent in your family so they can copy them into their own banking app.
2.2 Data about children (GDPR-K data)
Data about children is entered by you, as the legally responsible parent. Coparenta does NOT collect data directly from children and does NOT allow children to register as users.
- Child’s first name
- Date of birth (day, month and year), required when adding a child
- Optional avatar (child photo)
- Journal notes — observations, moments and events you share with the other parent
- Photos uploaded to the journal (of what happens in the child’s life)
- The child’s routine, if you fill it in — wake, nap and bedtime, meal habits, foods to avoid, free-text notes
- The child’s wishes, if you record them — a title, an optional note and who bought the item
- The recorded residence — which parent it is registered with, and since when. When there are two parents in the family, changing it requires the other parent’s agreement.
2.3 The child’s health record (special category, Art. 9 GDPR)
This is sensitive data.The health record is optional — the app works fully without it. You fill it in yourself, as a parent, and only if you want the other parent to have it at hand while the child is with them. The record is visible only to the parents in the shared space — not to people with viewer access (for example grandparents). We process it on the basis of your explicit consent, within the meaning of Art. 9(2)(a) GDPR: the app asks you for it separately, before the first save with data, and records it with the date and the version of the text. Records filled in before this step was introduced remain. Saving new data requires explicit consent in the app; older versions without this step can no longer save the record until they are updated. Clearing the record stops the data from being shown; earlier versions stay stored in the shared space's internal change log, which only parents with consent can access, for as long as the shared space exists and at least one parent has consent. If you delete your account, the record stays in the shared space with the other parent (see section 6). You withdraw your consent in the app, from Settings, as easily as you give it, or by writing to us at contact@coparenta.ro. Withdrawal stops only your access to the health records; the records remain unchanged for the other parent. A child's record and its history are deleted when all remaining parents in the family have withdrawn consent. Filling in a record does not replace explicit consent: if the family has no recorded explicit consent, the records are hidden until a parent gives it. Hiding them is not deletion. New consent does not retrospectively validate earlier processing. You can give consent again at any time; if the record still exists, you can see it again.
- Blood type
- Allergies
- Chronic conditions
- Current medication
- The doctor’s name and phone number
- An emergency contact
- Free-text notes about the child’s health
The health record is never sent to analytics services and is not part of the events in section 2.6. We do not use it for profiling, advertising or automated decisions.
2.4 Data about custody coordination
- The custody schedule (the days the child is with each parent)
- Swap requests between parents
- Expenses + photo receipts + settlements
- Child support, if you set it up — the payer, the recipient, the amount, the currency, the day of the month, and the payments you record as made
- The conversation in the shared space — messages and the files attached to them: photos and documents (PDF, Word, Excel, text)
2.5 Automatic technical data
- IP address — for security; it may appear in our providers' technical logs (for example at sign-in). On the website, the IP address reaches Vercel, which hosts the site, and on the home page also Cloudflare (the anti-bot filter), see 9
- App version + operating system
- Errors and crash reports — configured not to include your name, email or the content you enter
2.6 Usage analytics (optional, off by default)
If you turn it on, the mobile app sends ten events that record ONLY that a step happened — never what it contained. This is not automatic collection: nothing is sent until you explicitly opt in. The full list of events, the identifiers involved and what is never sent are in section 4.4.
2.7 The website suggestion form
If you send a suggestion, we receive its text, your selected role (parent, specialist or other) and your email only if you provide it for a reply. We use them to review your suggestion and, where appropriate, reply to you. The message is sent through Resend, the email processor already described in section 4, and kept in the contact@coparenta.ro mailbox according to the retention period in section 6; you can request deletion at the same address. We use Cloudflare Turnstile, an anti-bot filter, described in sections 4.2 and 9. To limit abuse, we temporarily use a fingerprint of your IPv4 address or IPv6 /64 prefix in server memory within a one-hour window; it is removed on the next request after expiry, on restart or earlier when capacity is reached. The IP address is not included in the message. Do not include names, diagnoses or case-file details.
2.8 Data about a parent who is not connected in the application
If the other parent uses Coparenta, we may receive information about you from them even if you do not have an account or do not accept the invitation to connect. Depending on what is actually entered, this may include information about the parenting schedule and child handovers, organisational proposals, expenses or payments attributed to you and references in uploaded content. The source of these data is the parent who entered them; the entries represent that parent’s statements, not information automatically confirmed by you.
For non-health data strictly necessary to organise childcare, we assess processing on the basis of the legitimate interest in enabling family responsibilities to be recorded and coordinated, with due regard for your rights and the child’s rights. This basis does not authorise the collection of any information whatsoever about you. Health data require an additional applicable condition under Article 9 GDPR; the other parent’s consent on behalf of the child does not cover your health data.
Not accepting the invitation does not mean accepting the Terms and Conditions, schedule, expenses or other entries and does not constitute consent to data processing. Without creating an account, you may request information about the data processed and their source, access, rectification, erasure or restriction, and object to processing based on legitimate interests, subject to the conditions explained in this policy. You can contact us at contact@coparenta.ro. Recipients, retention periods and your other rights are described in the relevant sections of this policy.
3. Why we collect this data (purpose and legal basis)
We process your data for the following purposes, based on the GDPR legal bases:
- Providing the service (Art. 6(1)(b) GDPR — performance of a contract): schedule coordination, custody swaps, expenses, journal — everything that makes Coparenta work for you
- Authentication and security (Art. 6(1)(f) GDPR — legitimate interest): the sign-in code, sessions, abuse prevention
- Push notifications (Art. 6(1)(a) GDPR — explicit consent): only if you grant the notification permission on your device
- Data about children (Art. 6(1)(b) GDPR): the name, date of birth, school, photo and other information you enter, so that you can coordinate the child’s care. Children have no account in the app; you, the parents, enter their data. You, as a parent, hold legal responsibility for the data you enter about your child. The medical record has its own regime, below
- The child’s health record (Art. 9(2)(a) GDPR — explicit consent, on top of the Art. 6 basis): this is special-category data. We do not ask for it and do not assume it — we process it only if you choose to fill the record in, and for a single purpose: making it available to the other parent. What happens when the record is cleared or an account is deleted is described in 2.3
- Settlement details (Art. 6(1)(b) GDPR — performance of a contract): your IBAN, account holder name or Revolut username, if you fill them in, so the other parent can send the money. We do not pass them to any payment processor; they do not leave your family
- Suggestions submitted through the website (Art. 6(1)(f) GDPR — legitimate interest): improving the service and responding to your request. Email is optional, provided voluntarily for a reply.
- Data about a parent who is not connected in the application (Art. 6(1)(f) GDPR — legitimate interests): the non-medical data strictly necessary to organise the child’s care, entered by the other parent; details in 2.8.
- Product improvements (Art. 6(1)(f) GDPR — legitimate interest): crash reports to fix bugs
- Product usage analytics (Art. 6(1)(a) GDPR — explicit consent): the ten events described in section 4.4, only if you turn the feature on. You can withdraw consent at any time, as easily as you gave it.
4. Who we share data with
Your data stays within Coparenta. We share it ONLY with:
4.1 The other parent in your family (within Coparenta)
Data about the schedule, swaps, expenses and child journal is shared AUTOMATICALLY with the other parent you share a family with in Coparenta — this is the purpose of the app.
4.2 Technical providers (sub-processors)
- Supabase Inc. (USA, with EU servers in Frankfurt, Germany) — database and authentication. Data stored in the EU.
- Vercel Inc. (USA) — hosting for the coparenta.ro website
- Cloudflare, Inc. (USA) — anti-bot filter (Turnstile) for the sign-up forms on the home page and in the holiday calculator, as well as the suggestion form; Cloudflare is a processor for bot filtering and a controller for improving Turnstile, see 9
- Resend Inc. (USA) — sending emails: the sign-in code; email alerts when the app cannot send you a push notification (they carry the same content as the notification, so they can include the start of a message — you can turn them off in the notification settings, under «Email updates»); the weekly «Your weekly summary is ready» email, only if you don’t have Coparenta notifications on your phone — it contains only the week’s dates and a link to the summary, nothing about the children; you can stop it from the unsubscribe link in the email or in the notification settings, under «Weekly summary by email» (see 4.3); and questions sent from the app to specialists (see 4.6)
- Google Firebase Cloud Messaging (USA) — delivering push notifications on Android
- Apple Push Notification Service (USA) — delivering push notifications on iOS
- Expo, Inc.(USA) — building and updating the app, and the service push notifications are sent through. A notification for a new message says only «New message», without the sender's name or any text, as long as «Discreet» is chosen in the notification settings under «New messages» (the default); if you choose «Full», it contains the sender's name and the start of the message (up to 80 characters). The same content then passes through Google (Android) or Apple (iOS)
- Functional Software, Inc. (Sentry) (USA, with EU servers in Germany) — the error and crash reports mentioned in 2.5. Configured with no default personal data and no session tracking.
Transfers to providers outside the European Union rely on the Standard Contractual Clauses (SCC) approved by the European Commission or on the provider's certification under the EU-US Data Privacy Framework.
4.3 AI processors (Anthropic, Google)
Coparenta offers two AI-based features: Weekly AI Summary (summarises the child’s journal notes) and Rewrite with AI (rephrases a message before you send it). Both send text to an external AI processor, ONLY to generate the summary or the rewrite — for no other purpose.
- Processors: Anthropic and Google (Gemini API). Each feature has a primary processor and a backup, used automatically if the primary fails to process the request (technical error, unavailability, or an invalid response) — so content may reach either one, regardless of the exact reason for the failure.
- Weekly AI Summary sends ONLY journal notes marked as shared AND for which you gave explicit consent — by default from Settings → Privacy → «New notes in AI Summary», or chosen individually per note. It sends the note’s text, the child’s name and age, and the note’s category (e.g. “school”, “activities”). Private notes never leave. Photos never leave.
- Notes in the “Health” category NEVER enter the AI Summary, regardless of consent — they are technically excluded before reaching any processor. They remain normally visible to the other parent, as a regular journal note.
- Rewrite with AI sends the message text ONLY when you explicitly choose to use the feature, at that moment — nothing is sent automatically.
- The content of the AI Summary is never sent by email. If you don’t have Coparenta notifications on your phone, on Mondays you get an email that only says the summary is ready, with a link to it; you see the summary only after signing in. We don’t record whether the email was opened, and the other parent can’t see whether it was sent to you.
- You can change your preference for the AI Summary anytime from Settings → Privacy.
Neither of these processors uses the content Coparenta sends to train their models — Anthropic does not train on data from its commercial API; Google does not train on data from the Gemini API for users in the European Economic Area (including Romania). The transfer to these processors (USA) is covered by the same Standard Contractual Clauses (SCC) mentioned above.
4.4 Product usage analytics (PostHog)
To see where people get stuck in the app, we can send a small number of events to PostHog. The feature is off by default: until you switch it on yourself, the app does not even start the analytics component and sends nothing at all.
- Processor: PostHog, Inc. (USA), running on PostHog Cloud EU — servers in Frankfurt, Germany (the AWS eu-central-1 region). The events stay stored in the European Union; our relationship with PostHog, Inc. is covered by the same Standard Contractual Clauses (SCC).
- Purpose: measuring the journey through the app and nothing else — how many people finish a step and where they stop. Not for advertising, commercial profiling or targeting.
- The ten events, and no others: onboarding completed · family invitation share sheet opened · family invitation accepted · expense created · Expenses screen opened · Coordination guidelines screen opened · Support for parents screen opened · «Talk to an EFT therapist» screen opened · agreement proposed to the co-parent (swap, schedule or settlement) · agreement accepted by the co-parent (swap, schedule or settlement). Each one records only THAT the action happened.
- What travels with an event: your internal account identifier and, where one exists, the family identifier — two system-generated codes (UUIDs), with no name, email or other profile field. The two events about agreements also carry the type of agreement: swap, schedule or settlement. We do not call them anonymous: on our side they remain linkable to your account, which is why we treat them as personal data and ask for your consent. Beyond that, only technical fields belonging to the analytics library travel along — its name and version, our public PostHog project key, and two internal processing flags.
What never leaves, even with analytics on: message content · journal note text · health notes and medical records · expense amounts, descriptions and receipts · photos · your name, email or any other profile field · addresses and location data. This is not a promise on trust: the app passes every event through a filter that keeps only the fields listed above and discards everything else before sending.
We have explicitly disabled, at configuration level: session replay · automatic error and exception capture · deriving location from the IP address (GeoIP) · automatic device and app properties (model, operating system, version) · automatic app lifecycle events · push-notification events · in-app surveys · feature flags.
How to give and withdraw consent: in the app, under Settings → Privacy → «Send usage data». This consent is separate from the one for the AI Summary and the one for notifications — none of them inherits from another. You can turn the switch off at any time, in a single tap: from that moment the app sends no further events and shuts the analytics component down. Declining or withdrawing changes nothing about how the app works. If you want the events already sent deleted, write to us at contact@coparenta.ro.
4.5 Legal authorities
Only where the law requires us to — for example, at the request of a court or a criminal investigation authority, within the limits set by law.
We do NOT sell your data. We do NOT use it for advertising. We do NOT share it with data brokers.
This stays true after the introduction of usage analytics (section 4.4): those events serve only to understand how the app is used. The Coparenta app contains no advertising pixel, no ad network and no marketing attribution tool. If you join the waitlist, we store next to your email address the page you signed up from and, if the link had them, the utm_source and utm_campaign parameters.
4.6 Questions for specialists
If you send a question from «Ask a specialist», its text reaches us by email (through Resend). We pass it on to the therapists of the EFT network, our partner, without your name or address. If you ask for an answer by email, we use your account address to send it; the therapist does not see it. Some questions may become articles for all parents, without identifying details — so please don't include names or details by which you or your child could be recognised. When you delete your account, the question is deleted from the app; we delete the copy in our email on request, at contact@coparenta.ro.
5. Where data is stored
Your data is stored on Supabase servers in Frankfurt, Germany (the AWS eu-central-1 region) — within the European Union.
Usage analytics events, if you have turned the feature on, are stored separately on PostHog Cloud EU — also in Frankfurt, Germany (AWS eu-central-1). Error reports go to Sentry’s EU region, in Germany.
International transfers (to the USA for email, push and hosting) are made ONLY with GDPR safeguards (Standard Contractual Clauses). Supabase, PostHog and Sentry are US companies that keep Coparenta’s data on EU servers — our relationship with each is governed by those same clauses.
6. How long we keep data
- Active account — for as long as you use Coparenta
- After account deletion — Your account, email, profile, IBAN, and notification tokens are deleted. Notifications from Coparenta stop. Journal notes marked private are deleted. Files are deleted in a separate step: we try, but if we can't, a file can remain on the server. This can't be undone. Database backups are kept for 7 days, then they expire. They hold only the database, not the photos or documents.
- What stays in the shared space: the schedule, holidays, vacations, handoffs, expenses, shared journal, wishes, health record, the child's routine, events, child support, the conversation (with the photos and documents sent in it), and the reminders you shared. Your days, shared notes, expenses, and events stay under your first name. Some open requests can stay open for the other parent. If you're the last remaining member, the shared space is deleted too.
- Audit log (actions) — The action log stays as long as the shared space exists and is deleted together with it. We don't delete it after a fixed number of days.
- Usage analytics events — stop the moment you withdraw consent. Those already sent stay with PostHog; you can ask us to delete them by writing to contact@coparenta.ro.
- Website visit statistics collected until November 1, 2026 — the page views and actions recorded by Vercel Web Analytics stay in the statistics for at least 12 months (our plan's reporting window), each with a visitor identifier; Vercel may keep them longer.
- Data about a person without an account, entered by a parent — kept while the shared space in which they were entered exists, or until they are deleted on request (see 2.8).
- The holiday calculator counter — the daily totals contain no data about people and have no deletion period.
- Website suggestions — 12 months from receipt, then we delete them from the contact@coparenta.ro mailbox; earlier on request.
7. Security
- HTTPS / TLS 1.3 connection for all data in transit
- Supabase database with Row Level Security (RLS) — each family sees ONLY its own data
- Children’s avatars — signed URLs expiring in 15 minutes (private bucket)
- Passwordless authentication — a one-time code sent by email, valid for 10 minutes (security through possession of the email address)
- Immutable audit log for critical actions
- For security bugs, contact us at contact@coparenta.ro
8. Your rights (GDPR)
You have the right to:
- Access — to receive a copy of your data
- Rectification — to correct inaccurate data
- Erasure (“the right to be forgotten”) — to delete your account and the associated data
- Portability — to receive your data in a structured format (JSON / CSV)
- Objection — to object to processing based on legitimate interest
- Restriction — to temporarily restrict processing
- Withdrawal of consent— for push notifications, for the AI Summary and for usage analytics. Each has its own switch in Settings and is independent of the others. Withdrawing is as easy as consenting, and does not affect the lawfulness of processing carried out beforehand. You can withdraw consent for the child's health record in the app, from Settings, as easily as you give it, or by writing to contact@coparenta.ro. Withdrawal stops only your access; the record and its history are deleted when all remaining parents in the family have withdrawn consent (see 2.3).
- Complaint to the National Supervisory Authority for Personal Data Processing (ANSPDCP): dataprotection.ro. If you live in another European Union member state, you can also contact the data protection authority in your country.
To exercise any of these rights, write to contact@coparenta.ro. We respond within a maximum of 30 days.
9. Cookies
The coparenta.ro website has no user accounts and does not set tracking, analytics or advertising cookies. The only cookie it writes is locale: it remembers the language you pick (RO or EN), appears only if you press the language switch, lasts one year and holds nothing but the language code, with no identifier.
For automatic language selection without the cookie, we use the country inferred by Vercel from your IP address, without storing it for this purpose: Romanian for Romania, otherwise your browser’s language, with Romanian as the default.
The website no longer uses Vercel Web Analytics, removed on November 1, 2026. What was recorded until then stays with Vercel, as described in section 6.
On the holiday calculator page we have an aggregate counter, so we know whether the page is used. For each day we keep two totals: how many times the page was loaded and how many times the displayed result changed, with rapid changes counted once. Each total is split by the link’s source: the value of the utm_source parameter, if it is on a fixed list of ours (for example facebook or presa); any other value counts as «direct». The counter uses no cookies and saves nothing in your browser. We do not keep your IP address, identifiers or your choices in the calculator in it, and the totals contain no person or visit identifiers. The totals are stored in our Supabase database (see 4.2). The request to the counter passes through Vercel, like any request to the website (see 2.5).
Links to Google Play on the website carry coparenta.ro as the source, web as the medium and the badge’s position, and those in our emails carry the email’s source, medium and campaign name, so we can see where installs come from. These parameters contain no data about you.
The waitlist sign-up forms on the home page and in the holiday calculator, as well as the suggestion form, use Cloudflare Turnstile, an anti-bot filter: when the page loads, your browser sends Cloudflare technical signals about the browser and the connection — among them its IP address, its TLS connection fingerprint, the User-Agent header and the site’s address. Cloudflare uses them to tell humans from bots and, according to Cloudflare’s Turnstile addendum, also to improve its own service; Cloudflare acts as a processor for bot filtering and as a controller for improving Turnstile (see 4.2).
The mobile app does NOT use cookies (data is stored locally on the device). If you turn usage analytics on, the app keeps a local technical identifier for that feature. It never leaves the device except alongside the ten events, and it stops being used the moment you withdraw consent.
10. Children’s data
Coparenta is NOT intended for children. The minimum age to be a user (parent) is 18.
Data about children is entered by parents, as legal representatives. Children have no account and do not use the app. The legal bases for the child’s data are those in section 3, and for the medical record, those in section 2.3.
If you are the other parent and believe the shared child’s data is being processed without your consent, contact us at contact@coparenta.ro and we will resolve the situation within a maximum of 7 days.
11. Changes to this policy
We will announce significant changes by email and via in-app notification. The current version is marked with the date above.
Version history: 28 May 2026 — first public version (beta) · July 20, 2026 — added disclosure for AI processors (Anthropic, Google) used by the Weekly AI Summary and Rewrite with AI, with the exact data sent and guarantees on model training (no-training) and SCC · August 25, 2026 — added disclosure for usage analytics in the mobile app (PostHog Cloud EU): the analytics events, the identifiers involved, the list of what is never sent, the legal basis (explicit consent) and how to withdraw it; added Sentry to the sub-processor list, for the error reports already mentioned in 2.4; clarified that each consent (push, AI Summary, analytics) is withdrawn separately · September 2, 2026 — analytics event list aligned with the app registry (seven, without a check-in event); account-deletion policy aligned with the tombstone (what stays in the shared space, under the first name); removed the mention of a custody-papers feature the app does not provide; APNs is no longer marked as forthcoming · September 8, 2026 — declared the categories of data the app actually stores that were missing from “what we collect”: the child’s health record, in a section of its own (2.3), because it is special-category data within the meaning of Art. 9 GDPR; the routine, the wishes and the recorded residence; child support; the IBAN and settlement details. Added the missing legal bases — Art. 9(2)(a) for the health record and Art. 6(1)(b) for the settlement details · September 18, 2026 — the data controller becomes COPARENTA S.R.L. (formerly PACSUNA CARTIE S.R.L.), replacing the app's founder; the company's identification details are in section 1 · September 25, 2026 — section 9 (Cookies) corrected to say what the website actually does: the locale cookie (the chosen language), the visit statistics (Vercel Web Analytics — what is recorded and how long it is kept) and the Cloudflare Turnstile anti-bot filter; removed the incorrect mention of a Vercel session cookie and the claim that the site runs no analytics; sections 2.5, 4.2, 4.5 and 6 completed accordingly · October 1, 2026 — aligned with what the app does: what push notifications and fallback emails contain (Expo, Resend); the health record is visible only to parents, and its history stays while the shared space exists; new section 4.6 (questions for specialists); the analytics event list has ten entries and the agreement type; removed the claims about anonymising the IP address, «anonymous» error reports and a 5-year retention on tax grounds; clarified the basis for transfers outside the EU, requests from authorities and your right to complain in your own country · October 4, 2026 — the Cloudflare Turnstile anti-bot filter is also used for the sign-up form in the holiday calculator (sections 4.2 and 9) · October 5, 2026 — removed the reference to Art. 8 GDPR and the wording about «implicit» parental consent for children’s data (sections 3 and 10): Art. 8 concerns services offered directly to children, and Coparenta is not aimed at children; section 10 is now called «Children’s data»; section 9: added the action «confirming your waitlist signup» (five actions on the website, not four); message notifications are now «Discreet» by default (section 4.2); medical record: the app asks for explicit consent separately, before the first save, and records it; withdrawing it is described in 2.3 and 8 · October 12, 2026 — consent for the health record can be withdrawn from Settings or by email; withdrawal stops only the requesting parent's access, without changing the other parent's record. The record and its history are deleted only when no parent in the family has consent anymore, including consent recognised for records filled in before the consent step was introduced. These records remain; saving new data requires explicit consent in the app, and older versions without this step must be updated to save the record. Consent can be given again at any time; if the record exists, access resumes (sections 2.3 and 8) · October 13, 2026 — section 9: added the action «clicking a store badge» (six actions on the website, not five; the store, the badge’s position and the page language are sent); links to Google Play carry the source, the medium and the badge’s position or the email campaign, with no data about you, to attribute installs; the page language is also chosen automatically from the country inferred by Vercel from your IP address, without storing it for this purpose · October 26, 2026 — the weekly «Your weekly summary is ready» email, for parents without notifications on their phone: it contains only the week’s dates and a link, nothing about the children; it can be stopped from the email or from the notification settings (sections 4.2 and 4.3). · October 29, 2026 — website suggestion form: data, purpose, delivery through Resend, mailbox retention and abuse prevention (section 2.7). · November 1, 2026 — removed Vercel Web Analytics from the website (sections 2.5, 4.2, 4.5, 6 and 9); added the holiday calculator’s aggregate counter (sections 6 and 9); added section 2.8, for a parent who is not connected in the application, with its legal basis in section 3. · November 5, 2026 — the child's date of birth is required when adding a child (section 2.2); filling in the health record does not replace explicit consent, and records without explicit consent are hidden (sections 2.3 and 8).
12. Contact
Questions, GDPR requests, suggestions?
We respond in Romanian or English, within a maximum of 7 business days.