IndSlots Ind Slots · Android companion

Ind Slots · brand identity and the verified install route

15 Aug 2026 · Companion desk

The Ind Slots companion publishes a brand identity card on the homepage and uses one first-party access route for every commercial CTA. This post explains what the companion publishes, what it does not, and why the route is single-source.

What the companion publishes

Brand mark, fact strip, screenshot rail, HOT shelf, YONO-style companion rows, mixed app directory preview, promos hub, VIP hub, daily news and a FAQ. Every commercial CTA on the homepage points to /Login/playnow.

What the companion does not publish

No invented bonus figures, rating numbers, user counts, licence claims, testimonial lines or device-specific performance claims. Where a value cannot be verified, the page states that the value is unverified.

Why a single route

Single-route routing keeps the disclosure tight, makes the redirect auditable and lets the support desk answer "where did you go?" with one answer. The redirect is configured at the nginx layer and never depends on JavaScript.

Why an inline disclosure

The disclosure appears on every page in the footer plus the brand identity card on the homepage. Inline disclosure makes the affiliate relationship unavoidable; users cannot miss it even if they skip the legal page.

Why dns-prefetch is allowed

The HTML head sets dns-prefetch and preconnect for the partner origin. That warms the DNS lookup without exposing the destination path in HTML or JavaScript. The full external URL is never placed in public copy.

Why no mirror URLs

The companion never exposes an alternate mirror URL, a side-loaded APK or a partner-side referral link. The same route serves every CTA. Mirror URLs would dilute the disclosure and complicate the support desk's audit trail.

Disclosure policy

Why the disclosure is inline on every page

Placement

The disclosure sits in the footer plus the brand identity card on the homepage. The card is the first product block above the hero illustration, so the disclosure is unmissable.

Wording

The disclosure says Ind Slots is a paid partner of select app brands. Clicking Install App routes through the verified first-party access route. The wording is consistent across pages.

Label

Commercial CTAs use the label Install App. The label is consistent across the homepage, the detail routes and the sticky mobile bar.

Relationship markers

Commercial links carry rel="sponsored nofollow noopener noreferrer". The rel attribute is the relationship marker; the wording is the disclosure.

What a good install route looks like

Five properties the route must satisfy

One route, one redirect

The route serves every CTA on the site. The redirect is configured at the server layer; no JavaScript is involved.

Disclosure is inline

The disclosure appears in the footer plus the brand identity card on the homepage. The wording is consistent across pages.

Rel attribute is set

Every commercial anchor carries rel="sponsored nofollow noopener noreferrer". The attribute is the relationship marker.

DNS pre-warm is set

The HTML head sets dns-prefetch and preconnect for the partner origin. The origin-only hint is allowed; the destination path is never exposed.

No mirror URLs

The companion never exposes an alternate mirror URL, a side-loaded APK or a partner-side referral link. The same route serves every CTA.

Disclosure wording

What the inline disclosure actually says

Identity

Ind Slots is a paid partner of select app brands. The wording names Ind Slots as a paid partner; it does not name the partner brands to avoid implying endorsement.

Route

Clicking Install App routes through the verified first-party access route. The wording names the route category, not the destination URL.

Rel

Some links carry commercial intent and are labelled with rel="sponsored nofollow". The wording surfaces the rel attribute as a relationship marker.

Age

Real-money gaming is restricted to 18+ users in permitted jurisdictions. The wording states the age and the jurisdiction requirement.

Play responsibly

Please play responsibly. The wording closes with a responsible-play reminder.

Placement

The disclosure appears in the footer plus the brand identity card on the homepage. The card is the first product block above the hero illustration.

Supporting reference

Where the additional detail is sourced from

Snapshot file

The full snapshot lives at .control-room/factory-v10-sponsor-data/data/casino_games_full.json. The file holds 973 unique game IDs across 8 providers.

Provider CSV

The provider CSV lives at .control-room/factory-v10-sponsor-data/data/casino_providers.csv. The CSV holds the provider card counts and the captured counts.

Public content JSON

The public content JSON lives at .control-room/factory-v10-sponsor-data/data/public_content.json. The JSON holds navigation, game types, rewards, affiliate, VIP, promotions, daily race and source metadata.

VIP table

The VIP table CSV lives at .control-room/factory-v10-sponsor-data/data/vip_levels.csv. The CSV holds 15 rows from VIP1 to VIP15.

Daily Race leaderboard

The Daily Race leaderboard CSV lives at .control-room/factory-v10-sponsor-data/data/daily_race_leaderboard.csv. The CSV holds the top 50 in the Today and Yesterday tabs.

YONO pool

The YONO pool index lives at assets/img/yono-pool/index.json. The index holds 23 companion profiles with source-referenced artwork files.

Game image pool

The game image pool planner lives at .control-room/factory-v10-sponsor-data/game_image_pool/planner-index.json. The planner holds 973 records keyed by game_id.

Factory selection

The factory selection lives at .control-room/factory-selection.json. The JSON holds the selected module system and the variant matrix.

Capture process

What the desk did on 17 Aug 2026

Capture

The desk captured the public lobby once per refresh cycle. The capture used the public lobby pagination and the public card counts.

Reconcile

The desk reconciled the snapshot with the previously published counts. Any drift in provider counts was logged and surfaced on the homepage fact strip.

Publish

The refreshed getindslots games was published under the same route structure. New IDs got new detail routes. Removed IDs lost their detail routes.

Notify

The /news/ hub carried a snapshot-update post each time getindslots games refreshed. The post listed what changed at the provider level and what to verify before installing.

What this post leaves out

Three things the desk will not add

Bonus numbers

The desk does not publish a bonus number on a news post. Bonus numbers change between captures; the desk refuses to invent a number where the snapshot does not record one.

Ratings

The desk does not rate any app, any provider or any partner. Rating is editorial opinion; the desk publishes verifiable facts only.

Predictions

The desk does not publish predictions about future events. Predictions are not verifiable; the desk publishes what happened, what the snapshot records and what to verify.

How to verify

Three checks before you take this post at face value

Compare to the snapshot

Open the snapshot at .control-room/factory-v10-sponsor-data/data/casino_games_full.json. The post's numbers should match the snapshot.

Open the source

Open the public lobby URL referenced in the post. The page should render. The numbers should match.

Ask the support desk

Open the support desk at /contact/. The desk reads the question in the same private thread and follows up if the post is wrong.

Editorial note

What the desk says about this post

Source

The post cites its source by file name and row ID where relevant. The desk confirms the source exists and the row is present in the snapshot.

Date

The post carries a date. The date is the publication date, not the event date. Historical events are labelled as such.

Verification

The post is verifiable. Each fact can be traced to a snapshot row or a public source.

Length

The post aims for 750 to 1,300 words. The desk rejected any padding and rejected any post that exceeded 1,600 words.

Further reading

Where to read more

Snapshot

The full snapshot lives at .control-room/factory-v10-sponsor-data/data/casino_games_full.json. The file holds 973 unique game IDs across 8 providers and is the source of every getindslots games fact on the companion.

Affiliate disclosure

Ind Slots is a paid partner of select app brands. Commercial CTA links carry rel="sponsored nofollow noopener noreferrer". The disclosure appears inline on every page in the footer plus the brand identity card on the homepage.

Support desk

Open the support conversation at /contact/. The desk reads the ticket in the same private thread and follows up within minutes during staffed hours.

Sitemap

The full route list lives at /sitemap.xml. The sitemap includes every detail route keyed by game_id and every companion profile keyed by slug.

Feed

An Atom feed lives at /feed.xml. Add it to your feed reader to receive an entry each time the desk publishes a post.

Cookie choices

Strictly necessary cookies keep the site working. Optional categories help us understand traffic and tailor offers. You can change your selection any time.