Direct child collection includes support requests with limited retention
Although services are mostly intended for adults or teens and child-related information can come from parents, KWS sometimes collects directly from children. The stated example is support information such as a child’s name and communications; support chats may be monitored and recorded. KWS retains it for 10 days after ticket closure, unless needed for legal obligations, disputes, enforcing agreements or protecting rights.
Details not recorded for this card
Supporting quotations
This statement explains how we process information collected directly from children. In most cases, our services are intended to be used either by adults or teens.
However, in certain circumstances we collect information directly from a child, including:
Customer support information: Information a child gives us when they contact us for help, such as their name, the content of their chats and other communications for us. When a child contacts us for customer support, chat sessions with our representatives may be monitored and recorded. This information is retained for 10 days after the customer support ticket has been closed, unless it needs to be retained to comply with legal obligations, resolve disputes, enforce our agreements or protect our rights.
Qualifications & exceptions
Ten days runs from closure of the support ticket.
Legal obligations, dispute resolution, agreement enforcement or rights protection may require longer retention.
Retention & Deletion · Company practice
Retention depends on purpose, data type and legal needs
You can request deletion of some information at any time by emailing privacy@kidswebservices.com. Otherwise KWS keeps information as long as necessary for collection purposes or other legitimate purposes, including legal obligations, disputes, agreement enforcement and rights protection. Periods vary by data and interaction context. KWS considers amount, nature and sensitivity, harm risk, purposes and alternative means, and legal, regulatory, tax or accounting requirements; this is not a fixed deadline for all information.
Details not recorded for this card
Supporting quotations
You can delete some personal information whenever you like by contacting us at privacy@kidswebservices.com.
Otherwise, we retain personal information for as long as necessary to fulfil the purposes we collected it for, or for other legitimate purposes such as complying with our legal obligations, resolving disputes, and enforcing our agreements or protecting our rights.
Retention periods vary significantly depending on the different data types, the purposes for which they were collected and the context of our interactions with you.
the amount, nature and sensitivity of the data;
the potential risk of harm from unauthorised use or disclosure of the data;
the purposes for which we process the data and whether we can achieve those purposes through other means;
applicable legal, regulatory, tax or accounting requirements.
Qualifications & exceptions
The at-any-time deletion statement covers some information, not every record.
Legal and other legitimate needs can extend retention.
Support information is normally kept for ten days after ticket closure
KWS’s specific support example is ten days after the ticket is closed. It may retain that information longer when needed for legal obligations, resolving disputes, enforcing agreements or protecting rights.
Details not recorded for this card
Supporting quotations
For example, customer support information is retained for 10 days after the customer support ticket has been closed, unless it needs to be retained to comply with legal obligations, resolve disputes, enforce our agreements or protect our rights.
Qualifications & exceptions
The clock starts at ticket closure.
Legal obligations, disputes, enforcement or rights protection can justify longer retention.
Cross-references
qualifies (model-proposed): Retention depends on purpose, data type and legal needs — Support information has a stated ten-day period after ticket closure, subject to the listed legal, dispute, enforcement and rights-protection extensions.
Retention & Deletion · Company commitment
Providers must delete unneeded data; Partner-controller retention is separate
KWS requires third-party providers to delete information once no longer necessary for their services or legal, regulatory, tax, accounting or reporting requirements. For Partner-controlled Age Gate and Kid Account Management processing, users must consult the Partner’s privacy policy or contact it to learn retention periods; KWS’s periods do not establish those Partners’ periods.
Details not recorded for this card
Supporting quotations
We require any third-party service providers we use to delete personal information once it is no longer necessary for them to provide the services or to satisfy any legal, regulatory, tax, accounting or reporting requirements.
Where our Partners act as controllers when processing you or your child’s personal information (i.e. Age Gate services and Kid Account Management services), please refer to their privacy policies or contact the Partner directly for information on how long they retain your personal information.
Qualifications & exceptions
Provider legal, regulatory, tax, accounting and reporting needs are retained exceptions.
Partner-controller retention must be checked with the Partner.
Not stated here
Partners’ privacy policies are not supplied; their retention periods are unknown here.
California deletion has operational and legal retention exceptions
California residents have a deletion right, but KWS may retain information when needed for operational or legal reasons. Examples include providing KWS, transactions or contract performance; security, integrity or debugging; exercising legal rights for itself or others; internal uses aligned with user expectations; and legal obligations. Responses may also be limited for legal claims, compliance or law-enforcement cooperation.
Details not recorded for this card
Supporting quotations
deletion of your personal information.
We will delete your personal information, unless retention is necessary for operational or legal reasons, including to:
provide KWS, complete transactions, or perform our contract with you;
ensure the security or integrity of KWS, or debug KWS;
exercise legal rights on behalf of ourselves or others;
enable internal uses aligned with user expectations; or
comply with a legal obligation.
We may also limit how we respond to your requests, including when necessary to handle legal claims, comply with applicable laws or legal obligations, or cooperate with law enforcement.
Qualifications & exceptions
California residents only; deletion does not require removing records needed for the listed operational or legal reasons.
AgeGraph keeps verification metadata, but not the verification details themselves
After successful verification, verified status includes your age threshold, verification method, first and subsequent verification dates and times, associated Partner and App, initial device country, and KWS and verification-provider transaction IDs. KWS says it never stores the underlying verification details, such as card details, in this description of AgeGraph. The status is stored against your hashed email address, scrambled so it is no longer directly identifiable as an email address.
Details not recorded for this card
Supporting quotations
Once you have been successfully verified, we remember this by storing:
your verified age threshold (e.g. 16+ , 18+);
the method of verification used, e.g. ‘individual verified by payment card using Stripe’, but we never store the verification details (e.g. your card details) themselves;
the date and time you verified your age for the first time and subsequent times using AgeGraph, as well as the Partner and Partner App for which those verifications were made;
the country in which your device is located at the time of initially interacting with us; and
a KWS generated transaction ID for each verification and any transaction IDs provided to us by our verification partners such as Stripe.
We call this the verified status.
We then store this verified status against your hashed email address in AgeGraph. In non-technical terms, this means we scramble your email address using an algorithm so that it’s no longer directly identifiable as an email address.
Qualifications & exceptions
The described record is created after successful verification.