TingleTown Privacy Policy

Last Updated: November 17, 2026

This Policy is written around you. It does not open with what we gather, but with what you hold — the rights you have over your personal information, and how far we, as the party that handles it, must meet those rights. When you finish reading, you should be able to say at once what data exists, what it is used for, whom it goes to, and how far you can call us off at any given step. TingleTown is developed and operated by Yunnan Huangqunqi Transportation Co., Ltd., which is also the legal entity; the registered address is in the contact block at the end.

1. You hold the initiative throughout

In TingleTown you are not the passive source of information. The five rights below — to view, to correct, to erase, to withdraw consent, and to obtain a copy — carry no threshold and no fee, and may be exercised at any time. Our duty is to carry each one through: to build the entry point into the app, to receive the request, and to send you the outcome.

This Policy takes effect upon your first launch of the application, your submission of any form on the web pages, or the first email you send to support. If any clause is unacceptable to you, stop using the service; that step needs no permission from us.

2. Four categories of information we hold for you

Gathering is confined to the smallest scope the service requires, and falls into four categories: account information, device information, usage behaviour, and payment information.

2.1 Account information (provided by you)

  1. Sign-up and sign-in credentials — email address, salted password digest, and the unique account identifier returned by third-party sign-in;
  2. Profile contents — nickname, avatar, gender, date of birth, home city and self-introduction, together with the interest tags you select;
  3. Content you publish — feed posts, direct messages and voice clips, and the body of any ticket you file with support.

2.2 Device information (recorded by the system)

  1. Device model and operating-system version;
  2. IP address and network type (Wi-Fi or cellular);
  3. Carrier details and system time-zone setting.

2.3 Usage behaviour (produced as you act)

  1. Sign-in and sign-out timestamps;
  2. Feature click paths and time spent on each page;
  3. Search keywords, session length, and interaction frequency.

2.4 Payment information (down to the order layer only)

Membership and value-added benefits are settled exclusively through Google Play Billing. Only two things land on our servers: order results (product identifier, subscription start and end, transaction state, settlement country or region) and an entitlement receipt (a signature string used to check whether a subscription is still active).

Card numbers, expiry dates, CVVs, payment passwords, and one-time codes are all entered inside Google's payment pages. They cannot reach our servers or our logs; we neither store them nor have any route to retrieve them.

3. This information serves five purposes, and no sixth

The uses are fixed to the five below. To open a new one, this Policy must first be amended and your consent obtained afresh:

  1. Making features run — authenticate you against credentials, deliver private messages and voice to the other device, and unlock entitlements against order results;
  2. Improving the service — read click paths and dwell time to find where it stutters and where people leave, then decide what the next release touches;
  3. Holding security — use device traces and behaviour patterns to spot bulk registration, device farms, account takeover, and fraud, writing outcomes back to report tickets;
  4. Answering you — handle tickets, emails, and reports, and return the result to you;
  5. Meeting legal duty — keep, disclose, or erase what applicable law and regulators require, and answer lawful requests from competent authorities.

We do not sell user profiles, do not apply your information to targeted marketing unrelated to those five uses, and do not let automated processing alone produce decisions with legal effect about you.

4. Which third parties the information reaches

Delivering the features requires third-party SDKs and services. Each takes only the narrow slice its duty needs and answers to its own privacy policy:

  1. Firebase Analytics (analytics) — de-identified event names and device models, used for statistics and retention;
  2. AdMob (advertising) — ad-slot impressions and clicks, and advertising identifiers, used for settlement and frequency capping;
  3. OneSignal (push notifications) — push tokens and delivery receipts, used to route notices to your device;
  4. Cloudinary (media hosting) — the avatar, feed images, and voice files you upload;
  5. Mixpanel (behavioural analytics) — de-identified feature events, with message bodies and contact details excluded.

Advertising and analytics do carry device identifiers beyond the app. If you prefer not to take part, reset or delete the advertising identifier in system settings and switch off personalised recommendations in the app — core features keep working regardless. Any change to this list is published with the next update of this Policy.

5. Five rights, each matched to what you can do

None of the five needs a reason, and none carries a fee. They may be completed in the app, or by writing in:

  1. View — see the profile summary under "Me — Privacy & Account — My Data," or ask by letter for a description of our processing;
  2. Correct — any profile field may be amended directly, and the change holds once saved;
  3. Erase — remove posts, messages, and images one by one, or close the whole account at https://www.tingletown-chat.com/;
  4. Withdraw consent — take back system permissions such as location, camera, microphone, and notifications, or switch off non-essential improvement uses in the app; withdrawal does not reach processing already completed;
  5. Obtain a copy — apply by letter, and we deliver a structured file (JSON or CSV), normally within 15 business days.

Objections to our handling are welcome too. We verify identity first and reply within a reasonable period; if the answer falls short, you may complain to the data protection authority where you live.

6. Anyone below 18 is not collected from

TingleTown is open only to adults aged 18 or over, does not provide services to minors, and does not actively gather personal information from them. No one below 18 may register, sign in, use the service in any manner, or enter behind another person's account.

Should a misstated age, impersonation, or another unforeseen circumstance let a minor's information into the system, it is deleted upon confirmation, the matching account is restricted, and we check the same device and channel for signs of the verification being bypassed at scale. A guardian may also write in to ask for access to, and deletion of, information about the minor in their care. The full account of the age threshold and of reporting and enforcement sits in the TingleTown Child Safety Standards.

7. How information is stored and guarded

Retention is capped at what the purpose requires, and disposal follows once the cap is reached: profile data lasts as long as the account, and passes to the deletion process afterwards; device traces roll over the last several release cycles for fault tracing, then are aggregated or discarded; behaviour records are archived per statistical period, leaving only aggregates; orders and entitlement receipts are kept for the statutory tax, financial, and audit terms.

Security is built in layers: TLS throughout in transit; AES-256 at rest with keys kept apart from the data; least-privilege access by role with every operations action logged; a code review before each release and penetration testing each quarter; confidentiality undertakings at onboarding and annual privacy training. Should personal information be disclosed, tampered with, or lost, we tell you and the regulator within the period the law sets once confirmed, stating the scope of impact and the remedies already applied.

8. How this Policy changes, and whom to talk to

When features change, the service model is adjusted, or law and regulators move, this Policy moves with them. New versions are posted in the in-app notice area, and the date at the top is refreshed alongside. Should a change materially touch the reach of your rights, we tell you separately by pop-up or in-app notice before it takes effect and, where needed, ask for consent again; without that consent, the new use does not start.

For questions, comments, or complaints about this Policy, our handling practices, or the exercise of your rights, reach us as follows; we reply within a reasonable period: