Privacy policy

Who is behind this policy

KidLoop is a pre-launch project without a registered company yet. This means there is no legal entity named here as data controller, and no supervisory-authority contact, because neither exists yet. Once we incorporate and register kidloop.be, this section will carry that information. Until then, read this as a statement of intent from the team building KidLoop, not a binding commitment from a legal entity.

Account data

To create a KidLoop account we collect an email address, a display name and a password. The password is stored only as a salted hash, never in a form anyone here can read. We send verification, resend and password-reset emails when you request them, and you cannot sign in until your address is verified. We also keep the session records needed to keep you signed in. We do not ask for a phone number as part of account creation.

Optional identity verification

An adult can choose to verify through Stripe Identity for a public identity-verified badge. KidLoop sends Stripe the account email and an opaque family reference, then Stripe collects and checks a government-issued identity document and a matching selfie on its own hosted pages. KidLoop's application does not retrieve the document, selfie, legal name, birth date, address or VerificationReport. We store only the Stripe session reference, status, an error code when another attempt is needed, and the verification time. Other families see only the badge. Skipping or failing the check blocks no KidLoop feature. You can request redaction from the account page; KidLoop removes the badge first and keeps the request pending until Stripe confirms its asynchronous redaction. Stripe processes and retains the evidence under its own terms; this draft policy and that provider arrangement require legal review before launch, especially because selfie matching can involve biometric data.

Your postcode and city, not your address

We ask for your postcode and city and turn them into an approximate map point so we can show listings near you and sort search results by distance. We do not ask for or store a street address as a profile field. If you type an exact meeting place into KidLoop chat, that message is stored as part of the conversation and visible to the other participant, so share only what is needed for the hand-over.

What we store about your child

A child profile can hold the following information, all entered or selected by you, never by the child:

• A nickname you choose, never their legal name
• Their birth month, not their exact birth date
• Clothing size, shoe size, and when each size was last confirmed
• Item-style preferences used to filter clothing
• Interests you select, such as dinosaurs, building or drawing

Why this is minimal, and why we're allowed to hold it (lawful basis)

We ask for a birth month instead of a birth date, and a nickname instead of a full name, because that is enough to project a likely next clothing size and power matching while collecting less identifying data. The private child profile is not shown to other families. A wishlist is separate: if it is explicitly marked as a public registry, its title and active wish details, including any query, category, size or age range, are visible to anyone who has its unlisted link. The profile itself is not included. You, as the account holder, enter this data as a parent or guardian to use a feature you requested. This draft currently states contract performance (GDPR Article 6(1)(b)) for matching and legitimate interest (Article 6(1)(f)) for related alerts; those bases still require legal review before launch.

Listings, photos, and transaction history

We keep the text, category, price or swap terms, and photos of anything you list. Listing photos must show the item itself: clothing laid flat or on a hanger, a toy, a book, a piece of gear. Never a photograph of your child; we don't build features that ask for or expect one. A photo removed before publication is queued for immediate deletion; an automated cleanup deletes any still-unreferenced draft photo after a 24-hour grace period, which covers a crashed browser or interrupted request. We also keep a record of your purchases, sales, swaps and give-aways (what, when, with whom, and for how much) for as long as your account exists. We also expect Belgian accounting and consumer-dispute rules to require us to keep transaction records for a period after your account closes, likely around seven years, pending confirmation from an accountant.

AI-assisted listings, translation and search

When the corresponding provider keys are configured, KidLoop sends normalized copies of listing photos to the MiniMax API to suggest a draft, and sends the listing title and description to MiniMax for translation. It sends listing title and description text, and the words a visitor searches for, to the Google Gemini API to create numeric search vectors. It does not send a child profile, account email, session token or private chat in those calls. Without a MiniMax key, photos are not sent anywhere, the seller completes the listing manually, and its text stays in the language they wrote. Without a Gemini key, KidLoop creates search vectors locally, with same-language rather than cross-language matching. Provider processing, retention and any transfer outside the EEA are governed by their terms; the processor agreements and transfer safeguards must be completed and legally reviewed before real-family use. Do not upload photographs containing a child or other personal information.

Who sees your data

The other party to a transaction sees your display name, city and rating, never your email address or a stored street-address field. If you complete the optional Stripe Identity check, they also see the identity-verified badge, never its evidence. Stripe handles optional identity evidence and payment or payout details directly; KidLoop is not designed to store those documents, bank details or full card numbers. Configured MiniMax and Google services receive only the listing and search inputs described above. Configured Microsoft Azure hosting and Application Insights receive server data; error telemetry is allowlisted to route, method, error message and stack and excludes cookies, request headers, query strings, bodies and form data. We do not sell personal data or run advertising trackers. See our cookie policy for browser storage.

Your rights

Under GDPR, you can:

• See the data we hold about you and your children
• Correct anything that's wrong
• Delete your account, your listings and any child profile
• Receive a copy of your data in a portable format
• Object to processing based on legitimate interest

An honest note on how we handle those requests today

You can already remove a child profile, take an active listing off the public marketplace, and request Stripe Identity redaction from the account area. Removing a listing archives it rather than erasing transaction history. There is not yet a self-service account-erasure or portable-export function. There is also no monitored privacy contact below, so this draft is not launch-ready and the product cannot yet honestly promise an operational manual-request channel.

Children using KidLoop directly

KidLoop accounts are for parents and guardians, not for children. We don't knowingly let a child create or use an account without an adult. If we learn that's happened, we'll suspend the account.

How to reach us

Because KidLoop has no registered company yet, there is no monitored support address to publish honestly. Before this policy leaves draft status, we will add a real contact channel, and a named contact for data-protection questions if the amount of child data we hold warrants one.