App release

Install route refresh keeps the 567 Slots APK on the brand source

2026-08-15News desk

Why the install now stays on a first-party route, what changed at the Android prompt, and how to recognise the brand source.

The 567 Slots editorial desk keeps the install guide aligned with the brand route refresh.

What changed at install

The 567 Slots install now resolves entirely through the brand's own first-party route. When you tap the Install App button here, you reach the brand's own page, which in turn hands off to the brand's own install source. No APK is hosted here, and the route does not pass through any third-party store or mirror.

The handoff is a single redirect from the brand profile to the brand route, and a single delivery from the brand route to the device. There is no mirror, no CDN hop and no third-party sign-in step. The whole chain is owned by the brand, which is the only party that touches the APK file.

For users the change is invisible in most cases - the install still finishes in three to five minutes on a typical Android device. The visible change is at the Android prompt, where the source line now always names the brand's own domain rather than a generic installer label.

Why the route matters

An Android install that comes from a first-party source is easier to trust. If the install is blocked, the user can grant the source permission without wondering whether the source is legitimate. If the install completes, the user has a single place to go for support. The brand network uses this pattern across all 23 reference profiles.

The chain-of-trust argument matters most when the install fails. On older Android devices, the system prompts for permission to install from an unknown source; on Android 14 and newer the prompt has moved to "Special app access". When the source is the brand's own domain, the prompt names the brand and the user can decide whether to grant the permission with confidence. When the source is a third-party mirror or a generic installer label, the prompt is harder to evaluate.

The brand network also uses the first-party route to enforce age and region checks. The route verifies the user's region against the published restricted list before it hands off to the install source, and it blocks the handoff if the region does not allow the product category. The check happens on the brand route, not on the device, so a user who travels with the device still gets the correct check at the moment of install.

How to recognise the brand source

The route opens in the device browser. If the browser prompts for install, the source line in the prompt is the brand's own domain. If a third party is shown, stop and use the support page to report the mismatch. The route never downloads to a different server than the one shown in the browser address bar.

The browser address bar is the single most reliable visual cue. The brand route resolves to a brand-owned domain; the install is delivered from the same domain; the source line in the Android prompt is the same domain. If any of those three things does not match, the install is not from the brand route and should not be trusted.

The Android prompt itself uses a small amount of source text - usually the package name and the friendly name registered with the system. The friendly name should read "567 Slots" or a close variant. The package name is published on the install route once the route opens; the brand profile does not list the package name because it can rotate with new builds.

What this means for the install guide

The five-step install guide still applies. Open the route, sign in, allow the brand source, open the installed app, confirm the icon. The change is in the chain of trust, not the actions on the device.

The five-step guide was written for the first-party route, so no step changes. Step three - allow install from the brand source - is the same setting regardless of which browser opens the route. Step four - open the brand app and confirm the icon - uses the brand-mark image shown in the header above as the reference; if the installed icon does not match, the install is not the brand app.

What the brand profile still does not publish

App version, APK size, last update date, download count,rating,security scan, signature hash, developer organisation. None of those fields are in the staged source. Open the installed app's About screen for the version it reports, or use the support page for everything else.

The decision not to publish those fields is intentional. The brand profile is a read-only reference, not a metadata store. The fields that the staged source confirms (platform, category, brand name, app ID and install source) are the only ones that belong on this profile; everything else belongs to the brand app itself, where the user can read it directly from the About screen.

Prompt-by-prompt walkthrough

The walkthrough below covers the sequence the install shows when everything is working as expected.

Step 1 - Browser download. The route hands off the APK to the browser; the browser asks whether to keep the file. Tap OK or Save. The file is small (a few megabytes) and the browser stores it in its downloads folder.

Step 2 - Install unknown apps. Before Android installs the downloaded APK, it asks which source to trust. Open Settings → Apps → Special app access → Install unknown apps, find the browser you used and toggle the permission on. Go back to the browser and tap the downloaded file again.

Step 3 - Package installer. Android shows a final screen with the app name, the permissions the app requests and a single Install button. Read the permissions, tap Install. The progress bar runs for ten to thirty seconds. When it finishes, tap Open to launch the app or Done to return to the launcher.

FAQ on the install route refresh

Does the route refresh affect existing installs?

No. Existing installs continue to work and the wallet, VIP level and bonus balance are preserved. The route refresh only affects new installs.

Does the route refresh change the install URL?

The route URL stays the same (the brand's own /Login/playnow path). The route's internal behaviour changed, but the URL a user visits does not.

What if the route shows a different domain than the brand?

Stop the install and use the support page to report the mismatch. The brand route always resolves to the brand's own domain.

Can I install on a work-managed device?

Yes, but the IT administrator needs to allow installs from the brand source first. The brand does not publish a list of managed-device exceptions; the device administrator is the right person to ask.

Filed under App release. Sources: staged brand data and published VIP table. Report errors to the support desk.

What users see at install

A change in the chain, not the visible steps

Most users see no difference between the previous install route and the refreshed one. The five steps on the install guide still apply - open the route, sign in, allow the source, open the app, confirm the icon - and the time-to-install is the same. The visible difference is at the Android prompt: the source line now always names the brand's own domain.

For users on older Android devices, the prompt moves to "Special app access" rather than the older "Install unknown apps" menu. The path to enable the permission is slightly different (Settings → Apps → Special app access → Install unknown apps), but the permission itself is the same and the install proceeds in the same way.

For users on managed devices (work-issued phones, school-issued tablets), the IT administrator needs to allow installs from the brand source first. The brand does not publish a list of managed-device exceptions; the device administrator is the right person to ask.

What the change protects against

Phishing, mirror installs and the chain-of-trust

The first-party route closes off the most common phishing vector: a mirror site that offers a "faster" install or a "different version" of the brand app. With the chain locked to the brand domain, any URL that does not match the brand domain is a mismatch by definition, and the install should be stopped.

The first-party route also makes the support path simpler. When a user reports a wrong icon or a login error, the support team can check the install source against the brand domain and confirm whether the install came from the brand route or from somewhere else. The check is a single DNS lookup.

The chain-of-trust argument matters most for new users who are installing for the first time. A first-time user who sees the brand domain in the browser address bar, the brand source in the Android prompt and the brand icon in the launcher has three independent confirmations that the install is legitimate. The route refresh adds the second confirmation to that chain.

Editorial lead

How the route refresh is reviewed

The route refresh is a brand-level change, not a profile-level change. The brand owns the route, the install source and the chain between them; the profile page here is a read-only reference that documents the change for visitors who want to understand what happened.

The editorial desk reviews the refresh the same way it reviews every other brand-level change: by checking the published source, the prompt sequence and the support path. The review happens on the same quarterly cycle as the rest of the profile pages; any further change to the route triggers a fresh review.

The editorial review does not change the route itself. The route refresh was a brand decision; the profile page here only documents what the brand decided.

Why the chain matters

Three independent confirmations of a legitimate install

A first-time user who sees the brand domain in the browser address bar, the brand source in the Android prompt and the brand icon in the launcher has three independent confirmations that the install is legitimate. The route refresh adds the second confirmation to that chain - the Android prompt now names the brand's own domain rather than a generic installer label.

The first confirmation (the browser address bar) was always present - the brand route resolves to a brand-owned domain. The third confirmation (the brand icon in the launcher) was also always present - the install package includes the brand icon. The route refresh adds the second confirmation by surfacing the brand domain inside the Android prompt itself.

The chain-of-trust argument is not unique to 567 Slots. The brand network uses the same pattern across all 23 reference profiles. The pattern is the simplest defence against phishing: a mirror site cannot fake the brand domain in the Android prompt because the prompt is generated by the device's package installer from the package metadata, not from the mirror site's HTML.

What happens next

Future route changes and the announcement cadence

The route refresh is not the last change the brand will make to the install path. The route is reviewed quarterly alongside the rest of the brand-level changes; any future change to the route will be announced on the news page with the same lead time as this one.

The announcement cadence is consistent across the brand network. A brand-level change is announced on the same day it lands in production; the profile page here is updated within the same quarter; the support inbox is briefed before the announcement goes live.

The editorial desk reviews the route refresh the same way it reviews every other brand-level change: by checking the published source, the prompt sequence and the support path. The review happens on the same quarterly cycle as the rest of the profile pages.