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.
Acceptance
Using this product profile means accepting these terms. If you do not accept, do not use the verification profile.
Permitted use
Use the library for personal shortlisting. Do not scrape, mirror, republish or commercialise the listings without written permission.
Account behaviour
Accounts on third-party publisher platforms are governed by those publishers’ terms, not these. We do not have access to your account, deposit details or play history.
No guarantees
Library entries are based on a snapshot. Studios can add, rename, retire or suspend products at any time. We do not guarantee availability, payout speed, RTP or app version.
Sanctions
We may restrict access for misuse, scraping or violation of these terms without prior notice.
Cookies and consent
See /cookies/ for how this product profile handles cookies and consent categories.
Changes
We may update these terms. The effective date at the top of this route is the date the current version came into force. We do not email individual visitors about term changes; visitors are responsible for checking back.
Severability
If any provision of these terms is held unenforceable, the remaining provisions continue in force. The unenforceable provision will be replaced by an enforceable provision that most closely matches the original intent.
Related routes
For privacy, see /privacy/. For cookies, see /cookies/. For responsible use, see /responsible-use/.
Install Yono Games appDirect route. Sponsored affiliation.
The editorial desk does not alter the staged snapshot to fit a preferred narrative. Articles are revised only when the snapshot itself changes, never in response to commercial pressure.
No commercial guarantee
We do not guarantee a specific install count, signup rate, retention curve or lifetime value. We verify the snapshot. The publisher is responsible for the figures they publish about their own product.
Use of generated content
The library entries and detail pages are assembled from snapshot rows plus published artwork. We do not generate imagery for games. We do not generate illustrations for the legal or the cookie routes.
Misuse of the verification profile
Impersonating this product profile, harvesting the library, or presenting its rows as a publisher’s own marketing material is prohibited and may be a trade-mark violation.
A short visitor’s reading order
Read the acceptance section first, then the permitted use section, then the no-guarantees section. The remaining sections are short and self-contained.
Why terms of use
Verification profiles need a published terms-of-use route so that an audit-minded reader knows what they can and cannot do with the data on the verification profile. We keep the route short and in plain language by design.
What an audit-minded reader will look for here
Look at the no-guarantees section. Read it. If you then decide to install through the publisher’s onboarding, that’s your call; this product profile does not promise availability, payout speed, RTP or version numbers.
What this route will not do
This route will not pretend to publish a product rating. It will not cite third-party reviews of the publisher. It will not publish a count of downloads or sign-ups.
What happens when terms change
We update the route in place. The effective date at the top of this route is the date the current version came into force. We do not email individual visitors about term changes.
Submitting a correction
If you spot a clause that disagrees with the publisher’s own terms, 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
If you are using this route to make a business decision, treat it as background. The route is the verification product’s published terms; it does not replace a qualified lawyer’s review of your specific situation.
Editorial archive and audit trail
Each clause 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 clause.
What we mean by ‘Not published’
When the snapshot or the publisher’s terms are silent on a particular clause, we say so. We do not invent clauses that the verification profile does not actually enforce.
What we will not do
We will not cite third-party reviews of the publisher. We will not invent a count of downloads or sign-ups. We will not publish a clause that the verification profile does not actually apply.
What happens when terms change
We update the route in place. The effective date at the top is the date the current version came into force. We do not email individual visitors about term changes.
Beyond this article
For privacy, see /privacy/. For cookies, see /cookies/. For responsible use, see /responsible-use/.
Reading the route on a small screen
The route is single-column on mobile. Each clause remains readable. Use a larger viewport for side-by-side comparison with another publisher’s terms.
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 keep the clause set small
We keep the clause set small because the verification product only does a few things. A long clause set would not match what the verification profile actually does. Each clause on this route corresponds to a behaviour the verification profile actually applies.
What about the publisher’s terms
The publisher’s terms govern product use, account behaviour, deposit, withdrawal and dispute resolution. This verification product’s terms govern use of the verification product itself. The two are separate. Where a conflict matters for your decision, consult the publisher’s terms directly.
What about the editorial archive
The editorial archive retains the snapshots and source rows that drove prior revisions of each article. The archive is internal. Where the archive contains a value that disagrees with what is currently published on a route, the most recent route publication is the source of record for the current behaviour.
Reading the route as a contract
Use the route as a baseline for what the verification product does and does not promise. Where a clause on the route is unenforceable in your jurisdiction, the remaining clauses continue in force. Where a clause requires professional interpretation, consult a lawyer.
What happens to historical clauses
Historical clauses are not republished on the route. The audit trail in the editorial archive keeps prior versions so an audit-minded reader can match a clause to the version that was in force on a given day.
A note on editor changes
When the verification product’s editorial discipline changes, we update the routes that explain it (this one and the privacy and legal routes). The audit trail records the date of each change. Visitors do not need to opt into each change; the effective date at the top of the route is the date the current version came into force.
A note on governing language
Where the verification product’s routes exist in more than one language, the English version of this route is the source of record. Translations exist for visitor convenience; they do not displace the English version.
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.
