Effective: 2026-08-28. Use /contact/ for private, no-email support.
This product profile is built from a published snapshot of the publisher’s public content. The snapshot is the only source we cite on these routes; we do not pull in additional claims from social posts, third-party listings, advertisements or outside reviews. Where the snapshot does not publish a value, the row is labelled Not published and we invite you to verify the answer at the publisher’s own page or through the support inbox.
These routes are written for shortlisting visitors and audit-minded readers, not for legal professionals. They explain what the verification profile does, what it stores, what it routes and how to make choices about cookies and consent. They are kept in plain language by design. Where professional legal advice matters for your decision, treat this as background and consult a qualified lawyer.
How we treat unverifiable claims
Shortlisting visitors ask us about licence numbers, regulator filings, payment processors, retention windows and security audits. We do not publish any of those because the snapshot does not publish them. The honest answer is “not in source” rather than a confident guess. Where you need that information for an operating decision, contact the publisher directly.
What these routes will never do
These routes will never ask you for credentials, never display a checkout, never publish a direct APK, never invent a regulator approval, never copy a third-party publisher’s branding and never mislead you into believing the company behind these pages operates any app shown in the directory. The verification profile does not transact.
What we collect
Strictly necessary cookies for site functioning. Optional analytics and marketing cookies only after you click Allow all. Personal data on /contact/ (name, contact method, message) is sent to the support inbox pipeline.
Why we collect it
Necessary cookies keep the verification profile working. Optional cookies improve the library. Contact data routes your message to the support team.
Where it is processed
On the operator’s own infrastructure. We do not sell or rent personal data.
Retention
Contact conversations are kept for as long as needed to resolve the issue and a reasonable audit window afterwards. Strictly necessary cookies expire when the session ends. Optional cookie choice is stored for 12 months in your browser.
Your choices
Adjust cookie categories in /cookies/. Withdraw consent as easily as you gave it. Use the browser’s ‘clear site data’ control for full reset.
Children
This product profile is intended for visitors 18+. We do not knowingly collect data from minors.
International transfers
Some infrastructure may be hosted in regions outside India. Where a transfer happens, the recipient is bound by data-protection terms at least as protective as those described here.
Your rights
Where applicable law grants rights (access, deletion, portability, objection, restriction), exercise them by writing to the team through /contact/ with a clear subject line. We respond within the statutory period.
Related routes
For cookies, see /cookies/. For terms, see /terms/. For responsible-use settings that apply to the publisher, see /responsible-use/.
Install Yono Games appDirect route. Sponsored affiliation.
We do not run third-party advertising on this product profile. The cookie categories above list what is set; what is not listed is not set.
No analytics outside your choice
Analytics cookies only activate after you click Allow all. Withdraw that choice and analytics stops loading on the next page load.
Honouring withdrawal
When you withdraw, we delete the stored object and stop subsequent optional scripts in the same session. A future session will treat you as a fresh visitor until you choose again.
Support inbox retention
Support conversations are kept for as long as needed to resolve the issue. If you ask us to delete a thread, we do so within the statutory period.
Children
We do not knowingly collect data from visitors under 18. If you believe a child has interacted with this product profile, write to the team through /contact/ and we will delete the relevant records.
A short visitor’s reading order
Read the ‘what we collect’ section first, then the ‘why we collect it’ section, then the ‘your choices’ section. The remaining sections are short and self-contained.
Why a privacy route
Verification profiles collect a small amount of data: cookie consent and contact-route submissions. We publish this route so the data is transparent, recoverable and deletable at the visitor’s request.
What is and is not shared
Personal data on /contact/ is sent to the support inbox pipeline. We do not sell or rent personal data. We do not share visitor identifiers with advertising or analytics outside what the visitor has consented to.
Cookie discipline
Strictly necessary cookies are always active. Optional analytics and marketing cookies load only after the visitor clicks Allow all. The choice is stored locally for 12 months and can be withdrawn at /cookies/ as easily as it was granted.
Children and minimum age
This product profile is intended for visitors 18+. We do not knowingly collect data from minors. If you believe a minor has interacted with this product profile, write to the team through /contact/ and we will delete the relevant records.
Submitting a correction
If a clause on this route disagrees with the publisher’s own privacy posture, send a short message through /contact/ with the route URL and the disputed clause. The desk reviews and publishes a correction.
A working visitor’s checklist
Use the Cookie Settings link in the footer to set or change consent. Use the browser’s ‘clear site data’ option to fully reset consent. Use the /contact/ route to ask for a deletion or export.
Editorial archive and audit trail
Each section on this route corresponds to a published behaviour of the verification profile. The editorial archive retains the underlying snapshot so an audit-minded reader can verify each section.
What we mean by ‘Not published’
When the snapshot or the publisher’s policy is silent on a particular data field, we say so. We do not invent fields we do not collect.
What we will not do
We will not sell or rent personal data. We will not share visitor identifiers with advertising or analytics outside what the visitor has consented to. We will not run third-party advertising on this product profile.
What happens when the source changes
If the publisher amends its privacy posture or we collect a new optional data field, the desk republishes this route. The audit trail keeps the prior version for reference.
Beyond this article
For cookies, see /cookies/. For terms, see /terms/. For responsible use, see /responsible-use/.
Reading the route on a small screen
The route is single-column on mobile. Each section remains readable. Use a larger viewport for a side-by-side comparison with another publisher’s policy.
What about jurisdiction-specific clauses
Where the publisher operates across multiple jurisdictions, additional jurisdiction-specific clauses apply. The route summarises the general posture; jurisdiction-specific clauses live on the publisher’s site.
Why we publish a retention window
We publish the retention window rather than an open-ended statement because audit-minded readers benefit from a fixed horizon. The window matches the operational need of the support inbox and the editorial archive.
What about the editorial archive
The editorial archive retains the snapshots that drive prior revisions. The archive is internal. Personal data is not stored in the editorial archive; the archive contains only the snapshot payloads and the source URLs.
What about visitor behaviour analytics
If you have granted analytics consent, anonymous page-view counts are collected. We do not collect visitor identifiers, device IDs, IP addresses beyond what the server logs automatically, or any field that could identify you. The collected aggregate is purged on a fixed schedule.
What the cookie consent does
Cookie consent governs only analytics and marketing scripts. It does not control the publisher’s own onboarding flow on the publisher’s domain. To withdraw consent, use the Cookie Settings button in the footer.
What the consent object includes
The stored object uses three categories: necessary, analytics and marketing. Each is on or off. The saved_at field is the timestamp of the last change. The object is held in your browser’s localStorage under the key yg_consent_v1.
Cookie preferences
Strictly necessary cookies keep core site features working. Optional analytics and marketing cookies are off by default. You can withdraw consent as easily as you give it.
