TingleTown Child Safety Standards

Last Updated: November 17, 2026

These Standards run in the order of prevention, detection, and response: first the means by which minors are kept off the door, then the means by which harm is found before it lands, and last what we do once it is confirmed. TingleTown is a social application for adults, developed and operated by Yunnan Huangqunqi Transportation Co., Ltd., which is also the legal entity.

1. Prevention: keeping minors off the door

TingleTown is open only to users aged 18 or over. The age threshold is not a statement but a set of tightening layers:

  1. Registration gate — the sign-up flow requires a date of birth and an adult declaration, and does not proceed unless both are given; a year alone, a skipped field, or a plainly invented date gets you no further;
  2. Profile notice — the profile states "adults only"; no minor may register, sign in, or use the service in any manner;
  3. Behavioural check — the system stays alert to signals such as school identifiers in a profile, an age visibly at odds with photographs or voice, reports naming an account as a minor within a short span, and self-description as a minor in conversation; any hit moves the case to manual review;
  4. Optional identity verification — where age is disputed, or where a user appeals a restriction, age is confirmed through a third-party verification service; we receive the conclusion only and retain no identity documents.

An adult who helps a minor get around the age limit is answerable on the same footing as the minor.

2. Bottom line: zero tolerance, and four acts that may not be touched

TingleTown applies a zero-tolerance policy towards child sexual exploitation and abuse (CSAE). "Zero" here means there is no tier for minor circumstances and no first offence treated leniently.

The platform strictly prohibits any user from producing, uploading, distributing, or storing any material involving the sexual exploitation or abuse of children. Each act carries its own responsibility: producing is the source, uploading is entry into the system, distributing is spread, and storing is retention — any one of them standing alone is a violation. The following are prohibited alongside:

  1. Any media depicting sexual conduct by a child;
  2. Sexualised language or role-play directed at a child;
  3. Attempts to establish private offline contact with a child;
  4. Distribution of intimate imagery of a minor;
  5. Asking a minor for a home address, school, finishing time, or an opportunity to be alone;
  6. Publishing content that glorifies, excuses, or encourages any of the above.

Any conduct that violates these Standards is handled immediately upon confirmation, with no grace period, and with no exception on account of account tier, payment status, or appeal history.

3. Detection: machine screening and human review

Finding it before the harm spreads rests on two layers, technical and human:

  1. Machine screening — images and short text are classified automatically, flagging suspected sexualised content involving minors, dialogue patterns typical of an adult working on a minor, and the tell-tale moves of luring a minor through an offline event; flagged content enters a review queue rather than being shown publicly;
  2. Human review — the safety team works the queue in priority order, records the outcome in a ticket, and leaves a complete trace of the grounds for action;
  3. Voice clues — voice features in a voice room serve only as an auxiliary prompt for review, never as the sole basis for action;
  4. Continuing checks — suspected accounts recurring on the same device or through the same channel are checked for linkage, to stop verification being bypassed at scale.

4. Detection: two reporting channels, both open

Reporting has no threshold and needs no complete evidence; suspicion is enough to submit:

  1. Inside the app — in the report entries of a private chat, a profile, and a feed card, choose "involves a minor"; the system attaches the reported account identifier, the session time, and a snapshot of the content by itself;
  2. By email — write to service@tingletown-chat.com with "Child Safety" in the subject and the account identifier plus what happened in the body; a guardian reporting for a child should mention the guardianship in passing.

A reporter's identity is confidential by default: the source is not disclosed to the reported party, and your own use is not restricted for having reported. Leads are routed by urgency, and a lead pointing to present danger goes down an immediate channel and is handled at once.

5. Response: what follows once a case is confirmed

Once a violation is confirmed, the following measures apply in proportion to its weight, and may be combined:

  1. Content removed — the original post, forwarded copies, cached thumbnails, and the media in the relevant conversations are cleared together, leaving no opening for a second spread;
  2. Account restricted or banned — muting, disabling of private messaging, suspension, up to a permanent ban with service eligibility terminated, with the linked device and the same payment method dealt with alongside;
  3. Records kept — the time of handling, the grounds, the operator, and the content snapshot are retained for the necessary period, for review and to block a return under a fresh account;
  4. Cooperation with enforcement — evidence of suspected offences is secured and the necessary information provided to law enforcement and the relevant child-protection bodies as the law requires, with cooperation in lawful investigation and evidence gathering.

Information about minors is not within what we actively collect. Where a misstated age, impersonation, or another unanticipated circumstance lets such information into the system, it is deleted immediately upon confirmation and the matching account is restricted. A guardian may write in to ask for access to and deletion of a minor's information in their care, and we act once the guardianship is verified; the general rules on protecting information appear in the TingleTown Privacy Policy.

6. Continuous improvement and how to reach us

Child safety is not settled by a single configuration. We adjust the age threshold, detection rules, and handling workflow as laws change, as Google Play policy is updated, and as industry practice advances; every confirmed child-safety incident is reviewed afterwards to establish whether the entrance failed to hold or detection came too late.

For questions, comments, or complaints about these Standards, our child-protection measures, or the outcome of a specific case, reach us as follows; child-safety mail is handled first: