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 these routes cover, what they store, 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 yonogamesplus games. These routes verify; they do not transact.
Categories
Strictly necessary cookies are always active. Analytics cookies are off by default. Marketing cookies are off by default. Both optional categories can be enabled with one click and disabled with one click.
How to change your choice
Open the Cookie Settings button in the footer or visit /cookies/. The change is stored locally for 12 months. Withdrawing consent stops subsequent optional scripts immediately.
Consent before script
Optional scripts do not load until consent is granted. Strictly necessary scripts continue regardless.
Evidence
Your stored consent is {'analytics':false,'marketing':false,'necessary':true,'saved_at':''}. Update with the buttons below to refresh the stored object.
Why persistence matters
Persistent consent is what lets optional scripts load without showing the bar on every visit. It is also what lets withdrawal take effect on the next page load. Both directions need a stored value to work.
Contact
Privacy or cookie questions can be sent through /contact/.
Third-party cookies
We do not embed third-party advertising or third-party analytics outside what is listed in the categories above. Where a third-party script is required by the publisher’s onboarding flow, it loads inside their domain, not on this product profile.
Browser controls
Most modern browsers include a cookie control panel. Use the browser’s ‘clear site data’ option to fully reset consent. Then reload this route to set a fresh choice.
Install Yono Games appDirect route. Sponsored affiliation.
Strictly necessary cookies remember drawer state, theme and the mobile sticky CTA visibility. They expire when the session ends.
Analytics
Analytics cookies count visits in aggregate. They do not profile you for advertising. They are off by default and switch on only when you click Allow all.
Marketing
We do not set marketing cookies today. If the publisher’s onboarding flow loads marketing cookies on their own domain, those cookies are governed by the publisher’s policy, not by this product profile.
What changing cookies does not do
Changing cookies does not delete records the publisher holds about your account. Account records live with the publisher.
A short visitor’s reading order
Use the buttons to set or change your consent. Read the categories section for a description of each. Read the ‘how to change your choice’ section for persistence and withdrawal.
How persistence works
When you click a category, we save a single JSON object in your browser’s localStorage. Optional scripts check this object before loading. If you withdraw consent, the object is updated and the next page load stops the optional scripts.
Browser controls
Most modern browsers include a cookie control panel. Use the browser’s ‘clear site data’ option to fully reset our stored consent object. Then reload this route to set a fresh choice. We have no server-side record of your cookie choice.
Why we use localStorage rather than a server
localStorage keeps the consent object on the visitor’s device. It works even after a network failure or a cleared cache. It is more privacy-preserving than a server-side record because we do not need to identify the visitor.
What we will and will not infer
We will not infer the visitor’s identity from the cookie choice. We will not share the choice with a third party. We will not use the choice to retarget advertising.
Submitting a correction
If the description of a category on this route disagrees with what the consent panel actually does, send a short message through /contact/ with the route URL and the disputed description. The desk reviews and publishes a correction.
A working visitor’s checklist
Set or change your consent using the buttons below. Verify the saved object in your browser’s localStorage under the key yg_consent_v1. Clear it through the browser’s ‘clear site data’ option to fully reset consent.
Editorial archive and audit trail
Each category on this route corresponds to a script or storage object the consent panel actually sets. The editorial archive retains the source.
What we mean by ‘Not published’
When a specific cookie or storage key is not yet in use, we say so. We do not list cookies the consent panel does not set.
What we will not do
We will not set advertising cookies. We will not set cross-site tracking identifiers. We will not ship analytics without consent.
What happens when categories change
If a new optional category is added, the route is republished this route with the new category and the new consent panel. Existing consent is preserved across category additions; visitors may re-grant or withdraw on the next visit.
Beyond this article
For privacy, see /privacy/. For terms, see /terms/. For responsible use, see /responsible-use/.
Reading the route on a small screen
The route is single-column on mobile. The consent panel uses the full viewport width. Use a larger viewport for a side-by-side comparison with another publisher’s cookie policy.
What about cross-domain cookies
This product profile does not set cross-domain cookies. Optional analytics are scoped to the verification product. Third-party scripts from the publisher’s onboarding flow load inside the publisher’s domain, not here.
Why we use localStorage
We use localStorage rather than a server because we do not need to identify the visitor. Persistence on the visitor’s device is sufficient for the consent panel and matches the editorial discipline of the rest of yonogamesplus games.
What happens at 12 months
After 12 months without activity, the stored object is considered expired by the consent panel. We do not actively delete it; the visitor’s browser handles the expiry. A returning visitor sees the consent panel as if they had never consented.
What about the consent object structure
The stored object uses three keys: necessary (always true), analytics (false by default), marketing (false by default) and saved_at (ISO timestamp of the last change). The keys are stable so future consent panels can read older objects without migration.
What visitor identity is stored
The consent object does not store visitor identity. It only stores which categories you selected and when you selected them. There is no visitor identifier, no IP address, no device fingerprint in the stored object.
What the route does not do
The route does not render advertising. The route does not embed third-party analytics unless you have granted analytics consent. The route does not sell or share visitor data with advertisers.
What happens at the next visit
On your next visit, the consent panel reads the stored object before any optional script loads. If the object has expired (over 12 months since the last change) or the visitor cleared site data, the consent panel appears again as a first-time visit. If the object is still valid, no panel appears.
Why localStorage not cookies
The consent object lives in localStorage rather than in a cookie so it does not appear in the cookie category list and does not trip cookie policies. It persists across sessions on the same device and clears with the browser’s ‘clear site data’ option.
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.
