This policy explains what personal data Listspace collects, why, where it is kept and what you can do about it. Listspace is run by Sjenkie B.V., trading as Yellow House Digital, Buitenhof, 1421 LB Uithoorn, the Netherlands, registered in the Netherlands (Chamber of Commerce NL: 60310030). Sjenkie B.V. is the controller of your personal data. Contact: hello@listspace.app.
1. What we collect
Account: your email address, an encrypted form of your password (we cannot read it), and anything you add to your profile, such as a name and profile picture. We also keep your timezone, the hour you chose and your quiet hours (from 22:00 to 08:00 unless you change them), so the daily summary email arrives at that hour and emails about requests, mentions, assignments and notes on your suggestions wait until your quiet hours end, and, if you turn on a calendar link, so due times show at the right hour in your calendar, and when you accepted these terms and confirmed that you are 16 or older. For one day we keep the time of each notification email and daily summary we send you, so that notification emails come at most once every 30 minutes. Per board, we keep when you last opened it in the app, so Listspace and your assistants can sum up what changed since your last visit. Per item, we keep when you last opened it, so the board can mark what other people changed since. Only you see this. It is deleted with your account, and when your access to the board ends.
Your content: the boards, lists, items, comments, labels, checklists and files you create or upload.
Decisions: when an item on a board is marked as a decision, we keep its state (Proposed, Confirmed, Replaced, Withdrawn or Conflict), the reason given, how it turned out if someone adds that, and its history: who proposed, confirmed, replaced, withdrew or kept it, which assistant proposed it, when, and the item's title at that moment. The history holds account ids, and names are looked up when it is shown.
Email to board: if you turn on a board's email address, mail sent to it is received by our own mail server, on our server in the EU hosted by Netcup. From mail sent from your account address we store the subject, text and attachments as an item, and the attachments are checked for viruses like any other file; other mail is refused and not stored. The mail server keeps no copy of the mail itself; its log records the sender and recipient addresses and is kept for up to 14 days. For each mail that becomes an item we keep its message id, the board or space and the item for 30 days, to stop duplicates and to count the daily limit. Our mail receiver also logs the sending server's IP address and the sender's domain, without the subject or the text, and keeps these lines for 14 days.
Sending an item by email: when you send an item to yourself or to someone else, the email holds the item's content and your name, and goes out through our mail provider, Lettermint. To limit how many emails go out, we keep for 30 days which account sent which item, and a one-way hash of the address it went to.
Calendar link: if you turn one on in Settings, it is a private link that shows the title, board, list and item link of your items with a due date (never the description); anyone with the link can read it, you can renew it or turn it off at any time, and we keep only a scrambled (hashed) form of the link.
AI assistants and apps: for each assistant or app you connect, we keep its name and when it first and last used your account, and we note in an item's history which changes it made, so you can see and disconnect it in Settings.
Slack: if you add Listspace to a Slack workspace, we keep the workspace's id and name and the access token Slack gives us for it (encrypted), and for each Slack user who connects a Listspace account, the user's Slack user id. When you save a message, the item stores its text, the author's name, the channel name, a link back to Slack and the files on the message. We do not read other messages. To let you pick where a message goes, we send Slack the names of your boards and their lists, and after a save, a reply that names the item, its board and list. Only you see these in Slack. Disconnecting in Settings removes the link.
Telegram: if you connect a Telegram chat to Listspace, we keep the chat's id and your Telegram username and first name. When you send something to the Listspace bot, the item stores its text, who a forwarded message came from, and the photos and files you send. We do not read your other chats. The bot's replies name the board and list an item went to, and to pick a board for a photo or file, the bot shows the names of your recent boards. Sending /stop to the bot or Disconnect in Settings removes the link. If you leave notifications to Telegram on, the bot sends the title and a short line of each notification to that chat. Telegram delivers the bot's replies and notifications under its own terms.
GitHub: if you connect GitHub, we keep the id of the installation and the name of the GitHub account or organization. For links to pull requests and issues on your items, we save a copy of their title and state. We use it for up to an hour so the item can show them, and delete it a day after that. Disconnecting in Settings, or removing the app in GitHub, removes the link.
Notifications on your devices: if you turn on notifications in Settings, we keep, for each device (browser) you turn them on for, the address its push service gave it, the two keys that notifications to it are encrypted with, a short label such as "Edge on Windows", and when it was added and last used. An account can have at most 20 devices; when you add another, the one used least recently is removed. A notification has a title, a short line and a link into Listspace. It is encrypted on our server before it leaves, and the push service of your browser's maker (such as Google, Mozilla, Apple or Microsoft) delivers it without being able to read it. We keep each notification we send for 30 days; one that could not be sent within a day is dropped. We also keep which kinds of notification you turned on and which boards you muted. Remove a device or turn notifications off in Settings to stop them.
Passwords and keys: Listspace checks text for what looks like a password, an API key or a token. A change from an AI assistant or the API that holds one is refused. In text that comes in by email, Slack or Telegram, it is removed before the item is saved, with a note that says what kind was removed. In the app, you see a warning before you save one, and you can save anyway. We store neither the secret nor a record of the check.
Refused requests from assistants and apps: when Listspace refuses a request from an AI assistant or app connected to your account, for example because the board's agent access does not allow it or because it sent too many requests, we record which account and which connection made it, the tool or API address it used, why it was refused, the board if the request named one you have access to, and the minute it happened. When the same request is refused again in that minute, we only count it. We do not store what the request asked for, its content or your IP address. We use these records only to keep the service secure and running, which is our legitimate interest. Only Listspace admins can see them, and we delete them after 30 days. A daily summary of them is in the JSON export of all your boards (Settings, then Export).
Admin access to your account: Listspace admins can open a summary of how your account is used (counts, dates and states, never the titles or text of your boards) and its security signals, such as the refused requests above. Each time an admin opens one, we record which admin, which of the two, your account and when, and nothing else. We use this record to keep admin access accountable, which is our legitimate interest, and to answer you if you ask who looked at your account. Only Listspace admins can see it, admins cannot change or delete it, and we delete it after 12 months. When an account's security signals go over a set limit in a day, such as many refused requests or wrong sign-in codes, the admins are told: in their daily admin email, with the account's email address and the counts, and in a short Telegram message to admins who connected Telegram, with the email address shortened (for example j***@example.com) and the counts. Neither ever includes the titles or text of your boards. To send such a Telegram message once a day at most, we keep the account and when it was sent for 2 days.
Accounts an AI assistant sets up for you: we store the email address the assistant gave, its name and a scrambled (hashed) form of the IP address it came from, send that address emails to claim the account and, if it is not claimed within 72 hours, delete the account with everything in it.
Waitlist and invites: if you join the waitlist, we store your email address, your answers to the optional questions (what you would use Listspace for and how you heard about it), when you agreed to be emailed, whether you also asked for product updates, and where you came from (the page, the site that linked to it and campaign tags in the link). If we invite you, we store the invite: its code, your email address, when it was sent and used, and the Pro it includes (a number of months, or Pro with no end date), which is added to your account when you sign up. If you join the Team waitlist on the pricing page, we store your email address, your team size and, if you pick one, the kind of team, only to email you once when Team is available and to see which teams want it first; the entry is deleted after 12 months, or earlier when you use the removal link in our email or ask us.
Following a public board: if you follow a public board without an account, we store your email address, the board you follow, how often you want the email (weekly or daily), when you confirmed and when we last emailed you. We first send a confirmation email; until you confirm, we also keep a scrambled (hashed) form of the confirmation link and of your IP address to stop abuse, and we delete the request if it is not confirmed within 7 days. Once you confirm, we delete the hashed IP address and send the digest you chose, only when something on the board changed. Every email has a link to stop following, which deletes your email address and the follow at once; the follow is also deleted when the board is deleted.
Payments: if you subscribe to Pro, Stripe handles the payment as the merchant of record (see section 4). We give Stripe your email address and your account id and, where they apply, your founder status and the campaign code you used. We keep what Stripe tells us about your subscription: its Stripe ids, the plan, billing period and price, its status and dates, failed payments and refunds, and whether you hold a founder spot. If you ask for Cancel and refund, we keep the fingerprint Stripe gives us for the payment method, which is Stripe's identifier and not the number, for 12 months, also after you delete your account, to tell a second refund from the same card. We never see or store your card or bank details.
Pro trial: to give the 14-day Pro trial once per email address, we keep when your trial started and ends, and a one-way hash of your email address (in lower case, with a +tag removed). For addresses outside the large mail providers we also keep the domain of the address for about a day, to limit how many trials one domain starts in a day. We use these to give the trial, to email you 3 days and 1 day before it ends, and to refuse a second trial for the same address. We check your address against a list of disposable email domains and store nothing about that check. To let a campaign code be used once per email address, we keep a one-way hash of your address with the campaign after you delete your account, with no link to the account, until 30 days after the campaign ends.
Campaign codes: if you use a code from an event or an offer (in a link such as listspace.app/?c=CODE, or under Have a code? in Plan and billing), we store which code you used, when, whether it came from a link or was typed, and what it gave you (free Pro until a date, or a discount on Pro). A code from a link is kept in your browser, and with your new account if you sign up with it, until it is used. If the campaign asks one or two optional questions, we keep your answers with your account; you can skip them. We count tries with codes per account, without storing anything else, to stop guessing. We use this to give you what the code offers, to send the emails before free Pro from a code ends, and to see how a campaign went: totals per campaign, and the answers without your name or email address. Your codes and answers are in the JSON export of all your boards (Settings, then Export).
Founder shares and profile visits: if you are a founder and use "Share that you're Founder #N", we count which channel you chose (X, LinkedIn, Bluesky, the copied link or your phone's share sheet) on which day. We never see or store what you post. For public profile pages (listspace.app/@name) we count how often each is opened per day, with nothing about the visitor.
Limits of the Free plan: when your account reaches a limit of the Free plan (full storage, older history that Free does not show, more guests or another guest role than Free allows, or agent access level 5), we count which limit it was and on which day, with your account. Nothing about what you were doing, and no content. We use the counts, together with whether an account has ever connected an AI assistant, only as totals, to decide what our plans should include.
Guests on a board: when a user invites someone to a board as a guest, we store the email address the board owner entered, the role, the optional end date, when the invite was sent and accepted, and a scrambled (hashed) form of the invite link. We use the address to email the invite and to check that the person who joins is the person invited. If the address has no Listspace account yet, the invite comes with a sign-up invite for that address only.
Technical data: when you use the service, our server and our providers handle your IP address and browser details to deliver pages, keep the service secure and stop abuse. Our server logs each request with the IP address, the time, your browser's name and the page address without anything after a "?", and keeps these logs for 14 days. When a request fails or is refused, the server's error log can hold the full address of that request; it is kept for 14 days too.
Error reports: when something goes wrong in the app or on our server, a report of the error goes to our error-tracking provider Sentry, in its EU region: the error message and where in the code it happened, the page address without anything after a "?", your browser and operating system, and the internal id of your account. It never includes your email address or the content of your boards, and the app does not put your IP address in it. Sentry receives the report straight from your browser, so it sees the address the report arrives from. Tokens, email addresses and anything after a "?" in a link are removed before it is sent.
Problem reports: when you use "Report a problem", we keep what you write, your screenshot if you add one, your account id and email address, and, if you leave "Include technical details" on, the page you were on, the app version, your browser, screen size and timezone, and the last errors the app noticed. We use it only to look into the problem and reply to you. After 12 months we remove your details from a report: your email address, your account, the technical details and the screenshot. What you wrote stays as you wrote it, so anything you said about yourself in the text stays too. Deleting your account does not delete a report: it keeps what you wrote, and your details go at the latest 12 months after you sent it. Ask us if you want your details or your text removed earlier.
Feedback: when you answer our feedback questions, in the app (Help, then Contact us) or when an AI assistant asks you for us, we keep your answers (what you like, what is missing, your rating if you give one) with your account, when you answered, and whether it came from the app or which assistant passed it on. If you decline, we only note that you did, so we do not ask again for 30 days. We quote your answer on our website, with your first name, only if you said yes to that separate question; the answer is no unless you say yes. You can turn the assistant questions off in Settings, under Agents. We use your answers to decide what to build.
Contact us: when you write to us in the app (Help, then Contact us), we keep your message, the topic you picked (a question, feedback, or billing and account), your account, and when you wrote. For a billing and account message we also keep the plan of your account, and never payment details. A question or billing message is also emailed to us, with your account address, so we can reply. We use it to answer you.
Welcome board: when you first open the app, we make you a board called "Welcome to Listspace", from Jordi, with a short hello and a few lessons. It is a normal board of yours. The comments you write by hand on that board, and only on that board, are sent to Listspace staff (Jordi), who may reply on the board. Only the board's owner is forwarded: comments written by an AI assistant or app, and comments by guests of the board, are not. Nothing is forwarded once the board is handed over to someone else or moved into a team space. For each forwarded comment we keep your account, the comment id, the board, the item and the dates (when you wrote it, and when it was answered or marked handled). The text of your comment stays on your board. The person who answers sees your first name, the board and item titles, and your hand-written comments in that thread. A reply comes from a person at Listspace, not from an AI.
Messages: when you use the contact form, your name, email address, message and IP address (the address is used to limit spam).
Wrong passwords: when a sign-in password is wrong, we count it to stop password guessing, for any address typed, whether or not it has an account. We keep the count per account together with a scrambled (hashed) form of the IP address used (for an IPv6 address, of its network block), and per account alone, with no readable email address or IP address. After 3 wrong passwords in a row from one network, password sign-in for that account waits 10 minutes from that network. After 20 wrong passwords within an hour from all networks together (tries made at the same moment count too), it waits 10 minutes from everywhere, and we email the account owner, at most once a day, which needs the account id and the time of that email. When a sign-in succeeds, we also keep a scrambled (hashed) form of the account together with the network it came from, for 30 days after the last right password. That network is not held by the wait from everywhere, so a stranger cannot keep the account owner out from the usual places; its own 10 minutes after 3 wrong passwords still apply. A change of the password ends that for every network, for which we keep a count of how many times the password was changed (never the password), as long as the account exists. People behind one shared network, such as a carrier or an office, count as one network. Our legal basis is our legitimate interest in keeping accounts safe (Article 6(1)(f) GDPR) and the security of processing (Article 32).
Shared boards: when someone enters a wrong password on a shared board link, we store a scrambled (hashed) form of the IP address used, for one day, to stop password guessing.
Views of shared boards: to show the board owner how many people viewed a shared board, we count each visitor once per board per day, without cookies. For that we keep a scrambled (hashed) value made from your IP address, your browser details and a random value that changes every day. The hashed values and the daily random value are deleted the next day, so a visitor can't be recognized across days. After that only the number of views per board per day remains, for 400 days. The IP address itself is never stored.
2. Why we use it
We use your data only to:
- Run the service you signed up for: store and show your boards, sign you in, and send account emails (confirmations, password resets) and, if you keep them on, the daily or weekly summary (what is due, what waits in your Inbox, open items with no change for 7 days or more, and what changed on your boards, at the hour you choose) and a few getting started emails for new accounts (a short welcome from Jordi that links to your welcome board, and what changed when you have been away), each with a link to turn them off. While your welcome board runs, we may also send a short reminder on day 2 and day 4 when a lesson waits and you have not been back, with the same switch to turn it off. We keep which getting started emails we sent, so none comes twice. This is needed to provide the service to you.
- Make your welcome board and answer the comments you write on it, as described in section 1. This is part of the service you signed up for (Article 6(1)(b) of the GDPR). These comments are not shared with any third party beyond the providers that run the service for us (section 4).
- Send the notifications you turn on, to your devices and to Telegram, and the request emails: when an agent's suggestion waits in your Inbox, when an item is due, when someone mentions you or replies in a thread you are in, when someone asks you something or answers your question. A request can be written by another member's AI assistant on that member's behalf, where the board owner allows that, and the message says so. This is needed to provide the service to you, and you can turn them off in Settings.
- Bill your Pro subscription and give you what you paid for. This is needed to provide the service you bought.
- Keep the service secure and stop abuse, such as automated sign-ups and password guessing. This is our legitimate interest in a safe service.
- Run the waitlist: email you when it is your turn, which you agree to when you join, and send occasional product updates only if you ticked that box. Every waitlist email has a link that removes you, and every product update has a link to unsubscribe.
- Read your feedback to improve Listspace, and quote it on our website only with your separate yes.
- Send you news about Listspace (new features, tips, questions for testers) only if you turn it on in Settings. This is based on your consent: we keep when you gave it, and you can withdraw it at any time in Settings or with the unsubscribe link in every such email.
- Answer your messages.
- Count visits without identifying anyone (see section 6), to see which pages are used.
- Count which limits of the Free plan accounts reach, as totals, to decide what our plans should include. This is our legitimate interest in plans that fit how Listspace is used.
- Meet legal obligations.
We do not sell your data, use it for advertising, or train AI models on it. Listspace runs no AI models itself: an AI assistant you connect reads what you allow it under its own provider's terms, which we do not control (see section 4).
3. Where it is kept and how it is protected
Your account and boards are stored in a database on our server in the EU, hosted by Netcup, and sign-in runs on the same server. Your files are stored in Cloudflare R2 in the European Union, and so are the encrypted nightly backups of the database and files. Encrypted backups of the database are also stored with Backblaze in the European Union: a copy is made every 20 minutes and locked against deletion for 7 days, and one a day is locked for 30 days. The website runs on that server too, and emails are sent through our mail provider, Lettermint, in the European Union. Email you send to us, including contact form messages and reports, arrives in our mailbox at MXroute, on a server in the United States, and our replies go out through MXroute. Some providers, such as MXroute and Cloudflare, may process data outside the European Union; they offer standard contractual clauses for such transfers. Backblaze stores the backups in the European Union, but Backblaze, Inc. is a company in the United States, so standard contractual clauses apply to it too. Services you connect yourself, such as Slack, GitHub, Telegram and your browser's push service, may process data outside the European Union under their own terms.
All connections are encrypted (HTTPS), database rules make sure each account can only reach its own boards and the boards it was invited to as a guest, passwords and share-link passwords are stored only as one-way hashes, and attachments can only be opened through short-lived private links. Every file added to an item is checked for viruses with ClamAV, scanned on our server, so the file is not sent to another company for it; until the check is done only the person who added it can open it, and a file with a virus is blocked and deleted after 30 days. Board backgrounds, board pictures and profile pictures are stored at a public address that is hard to guess, so anyone who has that address can see the image. No system is completely secure, but we will tell you without undue delay if a breach affects your data.
5. How long we keep it
We keep your account and content until you delete them or your account. A file you remove stays in the bin for 30 days, so you can put it back, and is then deleted for good; you can also delete it from the bin at once. When you delete your account, we delete your profile, boards, lists, items and uploaded files; copies in backups are removed as those backups expire, within about 6 months. Where other people's boards name you, for example in an item's history because you were assigned to it, picked in a person field, asked or passed a request, or suggested a change, or in a comment that mentions you, your name is replaced by "A former member", and your email address is removed from team invites and board handovers that were sent to you and are no longer open, and from board invites you declined. Feedback you give and messages you send with Contact us are deleted 12 months after you sent them, or earlier with your account. If you let us quote it and we do, we keep it while the quote is on our website. The campaign codes you used are kept with your account and deleted with it, except the one-way address hash that keeps a code to one use per address, which stays until 30 days after the campaign ends; your answers to a campaign's questions are deleted 12 months after you gave them. Records of refused requests from assistants and apps are kept for 30 days, and deleted earlier with your account. The record of when an admin opened your account's summary or security signals is kept for 12 months, also after you delete your account, and then holds only an id that no longer leads to anyone. A few records stay for a fixed time after you delete your account. If your account was ever restricted or suspended, the record of those steps (the reason, our note and the dates, with an id that no longer leads to anyone) is kept for 2 years after the last step. If we gave or moved your founder number by hand, that record is kept for 12 months. If you asked for Cancel and refund, the request (invoice, amount and dates) is kept with our payment records. If you sent an item by email to someone else, the record of that send is kept for up to 30 days. If apps were connected through our sign-in service, the note to disconnect them there is kept until it is done, at most 35 days. A guest's access ends on its end date, if it has one, and is deleted when the board owner removes the guest, when the guest leaves, or with the board or either account. A guest whose access ended on its end date is deleted 30 days after that date. An invite that is never accepted is deleted 90 days after it expired or was declined, or earlier when the owner removes it. When the board owner deletes the account, the boards go with it, and each guest gets a short email that the board is no longer available. Counts of wrong sign-in passwords are kept for about an hour (from the first wrong password of the hour, or 10 minutes after a wait began when that is later), and the record of the email about them for a day after it was sent. The scrambled record of a network that signed in is kept for 30 days after its last right password. Hashed IP addresses from share-link password attempts are kept for one day, and the hashed values that count shared-board views until the next day (the daily view counts for 400 days). The counts of Free plan limits are kept for 12 months, or until you delete your account. After you delete your account we keep the one-way hash of your email address and the dates of the trial until 24 months after the trial ended, and nothing else about the account. A waitlist entry is deleted 12 months after you join if you never create an account, or earlier when you use the removal link in our email or ask us; if you do create an account, it is deleted with your account.
Emails we send you are kept by our mail provider, Lettermint, for up to 28 days, then removed from its backups within 14 days.
If nobody uses a Free account for 12 months, we delete it (see the Terms of Service, "Suspending or ending your account"): we email you 30 days and 7 days before, and the link in those emails or a sign-in keeps the account. Its boards go with it, and each guest gets the same short email as when an owner deletes the account. To tell when an account was last used, we read dates we already keep: sign-ins and session renewals; the last use by your AI assistants and apps, including a calendar app reading your calendar feed; items captured into your Inbox; requests answered and decisions confirmed from a link in an email; the last change, comment or visit on your boards by you or your guests; and clicks on the keep link. For this we store, for each account: the date of the last check, a last-activity date, the reason an account is left out (such as a paid plan), the dates of the two warning emails and the date of the last click on the keep link. They are deleted with the account.
Other data has a fixed period, after which it is deleted:
- Contact form messages: 12 months after you send them. The IP address sent with a message: 30 days.
- Reports of content on a shared board, or of a team by one of its members: who made the report (email address, hashed IP address or account) until 6 months after we handled the report, the rest of the report until 2 years after. A report we have not handled yet stays until we have.
- Team invites: 90 days after they were accepted, canceled or expired. Requests to hand over a board: 90 days after they were answered, canceled or expired.
- Following a public board: when the board can no longer be followed (sharing turned off, a password added, or the board archived), your follow is deleted after 30 days, unless the board can be followed again by then.
- Suggestions in a board's Inbox, from assistants or from people with the Suggest role: 30 days after they were decided (accepted, rejected, sent back or failed), withdrawn or expired.
- The sign-in security log (sign-ins, sign-ups, sign-outs and changes to your password or email address, with your email address and IP address): 90 days. When you delete your account, its entries are deleted within an hour.
- Your away time and note: deleted when your away time ends.
- The record that a welcome board comment was forwarded (your account, the comment id, the board, the item and the dates): 30 days after it was answered or marked handled. A record that still waits for an answer is deleted once the comment is no longer on your welcome board and 30 days have passed since you wrote it. Otherwise a waiting record stays until the comment, the item, the board or your account is deleted.
- An account whose email address is never confirmed: deleted 48 hours after the last confirmation email.
- Rate limit counters, which hold only hashes of IP addresses, email addresses or account ids: 2 days.
- Counts of founder shares and of visits to a public profile: 13 months.
- An API token you revoked: 90 days after you revoked it.
- Payment records (the amounts and dates of payments and refunds): 7 years, as Dutch tax law requires, also after you delete your account.
The history of a decision stays as long as its board, also after the item is deleted, so the board keeps a record of what was decided and why. It is deleted with the board, and so with the board owner's account. When a guest who took part in it deletes the account, the history keeps only an id that no longer leads to anyone, and shows "A deleted account". Each notification we send is kept for 30 days. A device is removed when you remove it, when you turn notifications off on it, or when its push service no longer knows it.
If we close the service, we delete the accounts and their data. The details of a Pro subscription are kept with your account and deleted with it; the amounts and dates of payments and refunds stay, without your account, for our bookkeeping. Stripe keeps its own records of your payments as the law requires of it.
7. Your rights
You can ask us to:
- Give you a copy of your personal data
- Correct it
- Delete it (you can also delete your account yourself in your settings)
- Limit certain uses of it
- Give it to you in a format you can take elsewhere
Where we rely on our legitimate interest (such as security and abuse prevention, the admin records, the visit and limit counts, feedback and problem reports), you can object at any time. We then stop, unless we have compelling reasons that outweigh yours or need the data for legal claims.
Write to hello@listspace.app; we answer within one month. You can also complain to the Dutch data protection authority (Autoriteit Persoonsgegevens) or to the authority in the country where you live.
8. Children
Listspace is not meant for anyone under 16, unless the law of the person's country allows a lower age with the consent of a parent or guardian. We do not knowingly collect data from children; if you believe a child has given us personal data without the required consent, contact us and we will delete it.
9. Changes to this policy
We may update this policy. We will tell you about important changes by email or in the app, and the date at the top always shows the latest version.