Privacy Policy

Last updated: 10 November 2026

This policy explains what personal data we process when you use Kidli, why and on what basis, who we share it with, how long we keep it and what rights you have. It applies to parents and other customers, to venues and the people who work for them, to guests invited through a wish list, to people on the waitlist and to anyone who visits the site.

1. Who we are and how to contact us

The controller is Theta One Digiplex SRL, tax ID RO46462008, J40/13360/2022, registered at Str. Verzișori nr. 6, bl. D, ap. B118, Sector 4, București 040301, Romania (“Kidli” or “we”).

For any question or request about your data, write to us at privacy@kidli.ro or use the personal data request form.

2. In short

The table below summarises this policy. The details are in the sections that follow.

  • Parent or other customer

    What we process: Account, bookings, payment, invoice, messages, reviewsLegal basis: Contract; legal obligation (invoices); consent (marketing)How long: Booking: at least 30 days after the visit, as the venue sets; payments and invoices: 10 years; account: for as long as you keep it
  • Venue, company and its people

    What we process: Owner account, company, the people who represent or own it, the teamLegal basis: Contract; legal obligation (invoices, DAC7); legitimate interest (checking the company)How long: For as long as we work together, then as the law requires, usually 10 years
  • Guest invited through a wish list

    What we process: Your answer to the invitation and the gift you choseLegal basis: ContractHow long: For as long as the list exists
  • Person on the waitlist, or who sent a report or request

    What we process: Email address; the report or requestLegal basis: Consent; legal obligationHow long: Waitlist: up to 30 days after opening; reports: 3 years
  • Site visitor

    What we process: Technical data; cookies and advertising measurementLegal basis: Legitimate interest (security); consent (cookies)How long: Logs: short periods; cookies: as the Cookie Policy says

3. Who is responsible for the data: Kidli and the venues

The activities on Kidli are offered by venues, businesses independent of us. That is why some data is processed by us and some also by the venue you book with:

  • Kidli is the controller of the platform’s data: accounts, searches, bookings made through the platform, payments, messages, reviews, reports, content checks, the waitlist, wish lists, advertising measurement and security.
  • The venue you book with is a separate controller of the data it needs to welcome you: your name, contact details, booking details, check-in attendance, the invoice and, if you gave it, your photo consent. You see the company that operates the venue on its page and before you pay.
  • For data a venue enters or manages itself in our tools (for example bookings taken by phone or at the front desk, and its employees’ data), the venue is the controller and we are its processor, under a data processing agreement.

You can send us any request about your data, including data a venue holds: we answer for our part and pass the venue’s part on to it.

4. Parents and other customers

When you book or create an account, we process the data below. The legal basis is the contract (art. 6(1)(b) GDPR), unless we state another.

  • Account: email address, name, phone number confirmed by SMS and sign-in method. If you sign in with Apple, Google or Facebook, we receive your name, email address and an account identifier from them.
  • Booking: name, email and phone, the venue, activity, date and time, number of participants, price, payment status and, for parties, the birthday child’s age and the expected number of children. Notes for the venue are optional; do not write health data about children in them, such as allergies, but tell the venue directly.
  • Children saved in your account, if you choose to save them: first name, date of birth and, optionally, gender, so we can fill in bookings faster and show you activities suited to their age.
  • Payment: the Stripe payment identifier, amount, date, card or wallet type and the card’s last four digits. Only Stripe sees the full card number. Cards you choose to save are kept by Stripe, in a customer profile for your account.
  • Billing details: name and address or, for a company, its name, tax ID, registration number and registered office. We ask for them on bookings paid online, because the venue must issue the invoice (legal obligation, art. 6(1)(c) GDPR).
  • Documents accepted: the version of the Terms and the venue’s house rules, the supervision statement, the optional photo consent and, for parties, the signed contract, for which we keep, as evidence of the signature, the typed name, date and time, device, IP address and the fingerprint of the signed text.
  • Features you use: saved venues, discount codes received and used, sign-ups to a full time slot’s waiting list, requests sent to venues not yet on Kidli, messages (section 8) and reviews (rating, text, chosen name and the booking they relate to). We send last-minute offers from saved venues only if you accepted marketing messages (consent, art. 6(1)(a) GDPR).
  • Bookings a venue makes for you: if venue staff hold a place for you by phone or at the front desk, they enter your name and mobile number, and we send you the payment link by SMS and email. The venue is the controller of this data.
  • Support and safety: our team may open your account for support, a dispute, fraud prevention or at an authority’s request, choosing the reason, and every opening is logged. If we restrict an account, we keep the reason and the explanation we send you (legitimate interest, art. 6(1)(f) GDPR).

5. Venues, companies and their teams

When a company joins and lists its venues, we process the data below. The legal basis is the contract with the company, the legal obligation for invoices and DAC7 reporting, and, for checking the company and its people, our legitimate interest in letting only checked companies receive payments (art. 6(1)(b), (c) and (f) GDPR).

  • Owner account: name, email address, mobile number, language and password, kept only irreversibly encrypted. The email and mobile are confirmed with codes.
  • Company: the data in the application (legal form, tax ID, name, registration number, VAT status, registered office, contact details, IBAN and bank, description of activity, website, the invoicing system chosen) and the company documents you attach or we ask for. We do not ask for identity documents.
  • The company’s people: the legal representative, shareholders with at least 25% and the directors, each with name, date of birth, nationality, email, home address, role and shareholding, and for the representative also their phone. The owner enters them and must tell these people that they are sharing their data with us and where to find this policy. To check them, we obtain from ListaFirme (listafirme.ro), from the trade register’s public data, the company’s directors, shareholders and beneficial owners, with name, nationality, role and shareholding, and the company’s status. We keep the people’s data encrypted; only the owner and our team reviewing the application see it, and we pass it to Stripe, which checks the company before it can receive payments. We do not ask for or keep personal numeric codes.
  • Application history: each version submitted, the public registers’ answers, corrections requested, decisions, declarations ticked (with the time, IP address and browser) and the findings of the AI-assisted check, which only our team sees (section 9).
  • The venue’s team: name, email address, phone if you add it, role, sign-in methods (including the second factor), sessions and a log of important actions such as cancellations, refunds or access changes.
  • Measuring campaigns for venues: if you accept the marketing category, we report to advertising networks the moment an owner account is confirmed and the moment the company becomes active, under an opaque identifier, without name, email or phone (consent, art. 6(1)(a) GDPR).
  • Sales to venues: when a venue replies to an email about Kidli or leaves a phone number on the venues’ page, we use what it sends us to contact it about joining. Our internal sales tool receives that reply, visits to the page from the email, a request to remove an unlisted page, the email and mobile of a confirmed owner account and the company’s steps (submitting the application, with tax ID and name, and activation). The legal basis is our legitimate interest in presenting Kidli to businesses (art. 6(1)(f) GDPR). The tool receives no data about parents, and an erasure request is passed on to it too.
  • Venues not yet on Kidli: we may publish, from public sources, a page with the name, address, the business’s contact details, description and photos of a venue that has not joined, marked “Not on Kidli yet”. The legal basis is our legitimate interest in showing parents where they can go (art. 6(1)(f) GDPR). The venue can ask us at any time, through the form on the page, to remove it; we forget the details of whoever sends the form 90 days after the decision.

6. Guests, the waitlist and people who write to us

  • Wish lists: the host gives us the child’s first name, the date, the party’s place and the wishes. Guests see the list through a link; the address of a party held at home is shown only to those who said they are coming. When you answer an invitation we keep the name you typed, how many children and adults are coming and the optional note, and to take a gift you sign in with an account. The host sees how many units of a wish were taken, never by whom. The legal basis is the contract (art. 6(1)(b) GDPR).
  • Content reports: what you report and why and, if you leave them, your name and email, so we can tell you our decision (legal obligation, Regulation (EU) 2022/2065).
  • Personal data requests: your email address, the type of request and our answer (legal obligation, art. 12–22 GDPR).
  • The pre-launch waitlist: your email address, whether you signed up as a parent or a venue, the language, the consent wording you ticked, when you signed up and confirmed and, after opening, the welcome discount code and whether you used it. We use it to send you a few emails about the launch, based on your consent (art. 6(1)(a) GDPR and art. 12 of Law no. 506/2004). Your address joins the list only after you confirm it from the email you receive, and every email has a link that takes you off the list.

If you accept the marketing category, signing up to the waitlist is reported to Meta and the other advertising networks configured, noting whether you signed up as a parent or a venue, without your email address. If you refuse, nothing is reported.

7. Site visitors: technical data, cookies and advertising

Our hosting provider processes the IP address, browser and time of each request in server logs, for security and operation (legitimate interest, art. 6(1)(f) GDPR). Cookies and similar technologies are described in the Cookie Policy; we use those that are not necessary only with your consent, which you can withdraw at any time from “Cookie settings”.

If you accept the marketing category in the cookie banner, we report to advertising networks the steps you take (a search, opening a venue, choosing a time, submitting the booking form and, before opening, signing up to the waitlist) from the browser, and every confirmed payment also from our servers, so we know which campaigns bring bookings. The legal basis is consent (art. 6(1)(a) GDPR).

Events sent from the browser to Meta, TikTok and Google describe the action, not the person: the step taken, the venue’s public address, the order identifier and, for bookings, the amount in RON. Each carries an identifier derived from the action, so the network counts it once even if it receives it twice. Name, email address, phone number, billing details, the child’s age and notes are never included. If you refuse or withdraw your marketing consent, no event is sent.

After each payment is confirmed (the deposit and the final payment alike), we report it to Meta (Conversions API), TikTok (Events API) and Google Ads (Data Manager API) from our servers. The payment page loads no tag; the page that then confirms the booking reports the same payment from the browser too, through our tags and the venue’s, with the same event identifier, so the payment is counted once. Our report contains our commission on the payment, without VAT, in RON, the payment number, the venue’s public address, the click identifier received from the ad and, so the network can match the payment to an account, the email address and phone number irreversibly turned into SHA-256 codes. With the same consent, the report also contains the IP address and browser you paid from, the networks’ own cookies (_fbp, _fbc, _ttp) and a customer identifier irreversibly turned into a SHA-256 code; we keep these only until the report has gone, 7 days at most, and delete them with the booking. Name, billing details, the child’s age and notes are never sent. The legal basis is the marketing consent given when booking; without it nothing is sent, and every sending is recorded in our audit log.

Our Google tag may load from a Kidli address (/kt) instead of Google’s servers. In that case its measurements reach Google through our servers, which pass on the IP address, browser, language, the page you came from, Google’s cookies (_ga, _gcl, FPID, FPLC) and your approximate country and region. Google thus receives what it would receive directly, and we keep none of it. The tag follows the same choices made in the cookie banner, and venues’ tags never take this route.

Paid bookings that carry a click identifier may be exported by our team to the advertising account the click came from. The export contains the click identifier, the conversion name, the time, the value in RON and the currency, without name, email, phone or data about children, and concerns a single advertising account.

Venues may set up their own advertising tags (Google Analytics 4, Google Ads, Meta, TikTok). These load only on that venue’s pages and in the steps of a booking with it, only if you accept the marketing category, and never on the payment page or on the email link you use to cancel or move a booking. They receive the same booking events we send, with the amount that reaches the venue, without your name, email or phone. A venue can only set its accounts’ identifiers, which we check, never its own code. For the data collected through its tags, the venue is a separate controller. Legal basis: consent (art. 6(1)(a) GDPR).

A venue may also give us a key to report conversions from the server to its Meta (Conversions API) or TikTok (Events API) account. Then, after each payment confirmed with it and only if you accepted the marketing category, we report the payment to it from our servers, under the same rules as our own report: the amount that reaches the venue, in RON, the payment number, the click identifiers received on its page, the email address and phone as SHA-256 codes, the IP address, browser, the network’s cookies and the customer identifier, also as a SHA-256 code. A venue’s Google account receives nothing from our servers. For this data, the venue is a separate controller. We keep the key encrypted. Legal basis: consent (art. 6(1)(a) GDPR).

8. Messages

From your account you can write to us in Help and to venues that accept messages. Messages are text only.

  • What we keep: the text of each message, who wrote it and when, the booking it is about if you choose one, and how far you have read the conversation. The venue sees your first name, the initial of your surname and your bookings with it, never the email or phone in your account.
  • Who reads them: in Help, our team and Oaki, our AI assistant (section 9), and if we add the venue for a booking, it sees only the messages written from then on; in a conversation with a venue, the venue, as a separate controller, and our team when you or the venue call us in.
  • The Kidli team may read any conversation for safety, to resolve disputes and to prevent fraud, never for advertising. When it reads a conversation it was not called into and that was not flagged or reported, it chooses the reason from a list, and the reading is logged. Legal basis: legitimate interest in keeping the platform safe (art. 6(1)(f) GDPR).
  • A message containing a card number is refused and not kept. A message to a venue containing a phone number, an email, a link, an IBAN or an offer to pay outside Kidli reaches the recipient but is flagged to our team, and its author is reminded to pay only through Kidli. The rules are fixed and decide nothing about you: they only bring the message before a person.
  • If you do not read a reply within a few minutes, we send you an email with the venue’s or Kidli’s name and a link to the conversation, never the text of the messages. Web notifications that venue staff and our team can switch on carry no content and pass through the browser’s notification service.
  • If you delete your account, Help conversations are deleted straight away, and your messages and name are deleted from conversations with venues; the venue keeps its own messages. If a conversation is flagged, reported or the subject of an open dispute, your messages stay until the review ends. Conversations are included in the copy of your data you download from your account.

9. Artificial intelligence

We use artificial intelligence (AI) models to quickly check what is published on Kidli and to answer you quickly in Help. The AI decides nothing against you on its own: it approves only what raises no issue, and the rest goes to a person. Your data is not used to train models. We use it in these cases:

  • What venues publish: every change to what parents see (texts, products, house rules, contracts, photos) is checked before it becomes public, with fixed rules and an AI model. A photo in which a child can be recognised is published only after the venue confirms it has the parents’ written consent. Content that could endanger a child is blocked, and if there are signs of a crime we report it to the authorities. Legal basis: legitimate interest in keeping the platform safe for families (art. 6(1)(f) GDPR) and, for reporting, legal obligation (art. 6(1)(c)).
  • Reviews: the text is read with fixed rules and by an AI model. A review without problems is published automatically, and a flagged one is read by a person, who decides; the AI rejects no review. Legal basis: legitimate interest in moderating reviews (art. 6(1)(f) GDPR).
  • Venues not yet on Kidli: the public data taken about them is checked once, on import, and a photo in which a child can be recognised is not published. Legal basis: legitimate interest in not publishing unsuitable content (art. 6(1)(f) GDPR).
  • Companies’ applications: each version is also read by AI models, which flag what does not match. They receive the application’s fields (company data, the domain of its email address, bank and account holder, description of activity, website and, for each person, name, role, shareholding and age) and the registers’ findings, but never the company’s documents, the IBAN, personal numeric codes, dates of birth, or a person’s address, email or phone. Only our team sees what they find, and a person takes the decision. Legal basis: legitimate interest in checking companies before they receive payments (art. 6(1)(f) GDPR).
  • Oaki, the Help assistant: when you write to us in Help, as a parent, a venue employee or an owner, Oaki may answer first and tells you from the first message that it is an AI; with “Talk to a person” you switch to a colleague straight away. Oaki reads the conversation, the help articles and, without being able to change anything, your data: your account’s bookings, refunds, invoices and requests, the day and bookings of the venue you work at, or your company’s application, payments and monthly statement, without contact details, children’s names or booking notes. It can also write draft answers for our team, which a person sends, changes or discards. Legal basis: the contract (art. 6(1)(b) GDPR) and, for venue employees, the legitimate interest in offering them the help included in their company’s service (art. 6(1)(f)).
  • Wish lists: if you choose the AI drawing or text for an invitation, the drawing is made from the description you write in Oaki’s workshop (up to 200 characters) and the background colour you pick; an AI model reads the description before anything is drawn, and the child’s first name, if it appears in it, is replaced before it is sent. The text is proposed by an AI model from the tone, theme, child’s age and kind of place. Neither gets the child’s name, the date or the address. What guests see may be checked by an AI model, after the child’s first name has been replaced; a flagged item is not shown to them, and the host sees why. Drawings are checked before you see them, are marked as made with AI and are kept, with their descriptions, with the list until you delete it. Legal basis: the contract (art. 6(1)(b) GDPR).
  • Messages between parents and venues, where we switch this check on: an AI model reads a message after it is sent only to flag abuse, threats, sexual content, discrimination or scams to our team. It does not block, hide or decide anything: a flag brings the conversation before a person. Legal basis: legitimate interest in keeping the platform safe (art. 6(1)(f) GDPR).

We do not take decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (art. 22 GDPR): any decision against you (a rejected change, an unpublished review, an application with corrections or refused) is taken by a person.

Requests to the models go through Vercel AI Gateway (Vercel Inc., USA), which sends them, as its sub-processors, to Amazon Web Services (Amazon Bedrock, Anthropic’s Claude models) and, for invitation drawings, to Google Cloud (Vertex AI, the Gemini model). For each request we ask for processing in data centres in the European Union and zero retention, and we discard an answer that came from outside the EU. Before a request leaves, we replace card numbers, IBANs and personal numeric codes in it. The point at which a request enters Vercel’s network may be outside the EU, before the model processes it in the EU (section 11).

One limit you should know about: a model provider may, under its own rules, keep a request that its abuse-prevention systems flag, even though we asked for zero retention.

You may object to this processing at any time and ask for a person to handle it: in Help, with “Talk to a person”; for a change held at the check, with “Ask a person”; in any other case, at privacy@kidli.ro. You can challenge any decision, and a person reviews the challenge.

10. Who we share data with

We share data only as far as needed: with the venue you book with, with authorities when the law requires it, and with providers who work for us under data processing agreements, or as separate controllers where we say so:

  • The venue you book with: name, email, phone, booking details, payment, billing details, invoice and documents accepted, so it can welcome you and invoice you. It does not see your account or your bookings at other venues.
  • The venue’s invoicing provider (for example Oblio, SmartBill, FGO, factureaza.ro or Facturis), if the venue connected its account: the billing details, with the booking reference, products and amount, so the venue can issue the invoice and send it through RO e-Factura. The provider works for the venue, not for us.
  • Authorities: ANAF receives invoices through RO e-Factura and, each year, the DAC7 report on venues’ income; ANAF’s public register receives a company’s tax ID when we check it. Other authorities receive data only on a request based on law.
  • Stripe Payments Europe, Limited (Ireland): payments on behalf of venues, refunds, disputes and saved cards. It receives the payment data, email address and device information, and for venues the company’s data, bank account and its people’s data, to check the company; Stripe may ask these people directly for an identity document. For fraud prevention, checking companies and its legal obligations, Stripe is also a separate controller.
  • SC Oblio Software SRL (Romania): issuing our commission invoices to venues (legal obligation, art. 6(1)(c) GDPR).
  • ListaFirme (listafirme.ro, Romania): the trade register’s public data on joining companies and their people (section 5).
  • Amazon Web Services EMEA SARL (Luxembourg), through Amazon SES, in Frankfurt: sending emails. It receives the address and content of the message and tells us whether the email arrived, bounced or was marked as spam.
  • sendSMS Solutions SRL (Romania): SMS codes and, if you choose them, booking messages by SMS or WhatsApp. It receives the phone number and message content; WhatsApp messages also pass through Meta’s WhatsApp platform (WhatsApp Ireland Limited).
  • Apple, Google and Meta (Facebook), only if you sign in with their account: they send us your name, email and an account identifier and learn that you signed in to Kidli. Each is a separate controller.
  • Amazon Web Services EMEA SARL (Frankfurt): file storage, such as venues’ photos and booking documents.
  • Neon (Frankfurt): the database.
  • Vercel Inc.: hosting the application, with its functions in Frankfurt; server logs may temporarily contain the IP address, browser and time of a request.
  • Vercel Inc. (AI Gateway), with Amazon Web Services (Amazon Bedrock) and Google Cloud (Vertex AI) as sub-processors: running AI models, in the EU, with zero retention (section 9).
  • Vercel Inc. (Vercel Web Analytics), only with analytics consent: counting visits from aggregated data, without cookies and without identifiers stored on your device. Legal basis: consent (art. 6(1)(a) GDPR).
  • Meta Platforms Ireland Ltd. (the Meta pixel and Conversions API), only with marketing consent: measuring ads on Facebook and Instagram, from pseudonymous browser identifiers and conversion events, and the report of payments from our servers (section 7). Legal basis: consent (art. 6(1)(a) GDPR).
  • TikTok Technology Ltd. (the TikTok pixel and Events API), only with marketing consent: measuring ads on TikTok, from pseudonymous browser identifiers and conversion events, and the report of payments from our servers (section 7). Legal basis: consent (art. 6(1)(a) GDPR).
  • Google Ireland Limited (Google Analytics 4, Google Ads and Data Manager API): measuring traffic and ads. The Google tag loads with all storage and advertising signals denied and, in that state, sends only cookieless data; it uses cookies only with analytics or marketing consent. With marketing consent it also receives the report of payments from our servers (section 7). How Google uses data is explained at business.safety.google/privacy. Legal basis: consent (art. 6(1)(a) GDPR).
  • Cloudflare, Inc. (Turnstile): checks, on a booking without an account, the waitlist or a report, that the request comes from a person, from the IP address and browser signals (legitimate interest in preventing abuse, art. 6(1)(f) GDPR).
  • Upstash, Inc. (Frankfurt): rate limiting and the task queue; short-lived counters may be linked to the IP address.
  • Functional Software, Inc. (Sentry, EU region): error monitoring, without name, email or other contact details.
  • Browsers’ notification services (Apple, Google, Mozilla, Microsoft): delivering content-free web notifications to venue staff and our team who switch them on.

11. Transfers outside the European Economic Area

Some providers are based outside the European Economic Area (EEA) or may process data there: Vercel, Stripe, Cloudflare, Sentry, Apple, Meta, TikTok, Google, Mozilla and Microsoft. Transfers rely on a European Commission adequacy decision, including the EU-US Data Privacy Framework for certified companies, or on the Commission’s standard contractual clauses. Neon, Upstash and Amazon Web Services process data in Frankfurt, and sendSMS, Oblio and ListaFirme in Romania. The AI models run in the EU, but Vercel is a US company, and Amazon Web Services and Google belong to US groups.

12. How long we keep data

We keep data only as long as needed, then delete or anonymise it:

  • Booking (name, email, phone, notes, child’s age, documents accepted): for its duration and then as long as the venue sets, at least 30 days; the signed contract is deleted with it.
  • Payments and invoices, with billing details: 10 years, as accounting and tax laws require.
  • Account: for as long as you keep it. After you close it, we delete or anonymise it within 30 days, except data the law obliges us to keep, and delete the Stripe customer profile with the saved cards.
  • An owner account not confirmed within 7 days, with no company and no access: deleted. Email codes expire after 15 minutes.
  • Companies’ and venues’ data, with the application and the company’s people: for as long as we work together, then as long as the law requires for tax documents and DAC7 reporting, usually 10 years, the company’s people remaining only encrypted, in the application’s versions.
  • Team accounts: for as long as they are active.
  • Conversations: 5 years after the last message; sooner when an account is deleted (section 8).
  • Reviews: for as long as the booking they relate to is kept.
  • Content reports and decisions: 3 years after the decision.
  • Sign-ups to a time slot’s waiting list: 30 days after that time. Requests sent to venues not yet on Kidli: your details, 90 days.
  • Wish lists and guests’ answers: for as long as the host keeps the list; deleted with it or with the host’s account.
  • The pre-launch waitlist: an unconfirmed address, 7 days; a confirmed one, up to 30 days after opening and at most 12 months after signing up; on request, straight away.
  • AI: we do not keep requests to the models and their answers as such, only the result of the check, for as long as we keep the content checked, and a record of each call, without any text, for 24 months.
  • Ad attribution values: 30 days in the browser and, after a booking, on the booking until it is anonymised.
  • The audit log of important actions: 10 years for money, invoicing and promotions, 5 years for the rest; the data of a person who deletes their account is pseudonymised in it.
  • Server logs: short operational periods, at the hosting provider.

13. Children

Kidli is for adults. About children we process only what is necessary: the birthday child’s age and the number of children, for parties, the first name and date of birth of children saved in an account, with optional gender, and the first name on a wish list. We do not ask for children’s health data.

Photos taken at the venue are the venue’s responsibility. The photo consent you may give when booking is optional, given to the venue, and you may withdraw it at any time. A photo published on Kidli in which a child can be recognised appears only after the venue confirms it has the child’s parents’ written consent.

14. Your rights

Under the GDPR, you have the right:

  • of access: to receive a copy of your data (you can download it directly from your account);
  • to rectification: to ask for inaccurate data to be corrected;
  • to erasure: to ask for your data to be deleted, except what the law obliges us to keep;
  • to restriction: to ask us to limit the processing;
  • to portability: to receive your data in a structured, machine-readable format;
  • to object: to processing based on our legitimate interest;
  • to withdraw your consent at any time, as easily as you gave it (for example from “Cookie settings” or the unsubscribe link), without affecting the processing until then.

You exercise your rights through the personal data request form or at privacy@kidli.ro. We answer within one month, and pass any part concerning a venue on to it.

15. Complaining to the authority

If you believe we have infringed your rights, you can lodge a complaint with the National Supervisory Authority for Personal Data Processing (ANSPDCP):

ANSPDCP — National Supervisory Authority for Personal Data Processing

Website: www.dataprotection.ro

Email: anspdcp@dataprotection.ro

Phone: +40.318.059.211

16. Changes to this policy

We update this policy when our services, providers or the law change. The date at the top shows the last change. If you have an account, we tell you by email about important changes before they apply.