Ind Slots publishes installers for Android 7.0 and above. Check Settings < About phone < Android version.
Support
Ind Slots runs a private support desk at /contact/. Tickets persist in local storage and the same agent replies in the same thread.
Common checks
Try these first
Most installers fit under 200 MB. Free up storage if the install stalls at the verify step.
Always install via /Login/playnow. Side-loaded APKs are not endorsed.
If your region is excluded from real-money play, the install flow will block itself when you reach the operator. Use a permitted jurisdiction.
When the install hangs
Three steps before opening a ticket
Clear the partner app data
Settings < Apps < [partner] < Storage < Clear data. Re-open the install route. The verify step usually resumes within 30 seconds.
Restart Android
Hold the power button, tap Restart, then re-open the install route. Restarting clears any cached connection error that survived the partner app data clear.
Check the network
Real-money installers require a stable network. Try a different Wi-Fi or switch to mobile data. If the partner is down, the install will time out and the page will tell you so.
Confirm the route
Always start the install from /Login/playnow. If you reached the install via a side-loaded APK, the package hash will not match and the partner will refuse it.
When the package looks unfamiliar
Two checks before you commit
Compare package name
The package name on the partner's own download page should match the package name shown after the install verify step. A mismatch is the single most common sign of a copy.
Compare game ID
Each game on this product profile carries a stable ID. Compare the ID shown on the detail route to the ID shown on the partner's own page. Mismatched IDs mean getindslots games record has been moved.
Compare artwork
The artwork on the partner's own lobby should match the artwork on the detail route. The companion reuses the source artwork; if the partner shows something different, the partner has updated its own getindslots games.
When in doubt, stop
Stop the install, open /contact/, send a screenshot of the unfamiliar package and wait for the support desk to confirm the route.
FAQ
Reader questions
What if the install hangs at verify?
Clear the partner app data, restart Android, and re-open the install route. If the hang persists, open a support ticket.
How long does a support reply take?
The desk replies in the same private thread. Initial replies usually arrive within minutes during staffed hours.
Can I delete my ticket?
Yes. Open the support desk and click the reset button. The previous conversation is cleared from local storage.
Where is the support desk hosted?
The desk is a Control Room managed delivery file under /contact/. The support inbox lives outside this project root and is managed by the orchestrator.
Package checks
Three signals that the package is the one you intended
Package name
The package name on the partner's own download page should match the package name shown after the install verify step. A mismatch is the single most common sign of a copy.
Signature hash
The partner signs every installer with a release key. The signature hash is published alongside the download URL. If the install verify step reports a different signature, the package was re-signed and is not the published version.
Size and version
Size and version are published. If the installed package is markedly different in size or version, the partner has shipped a new build that the companion has not yet captured.
First-run experience
The first run should match the screenshots published on the partner's own site. A different first run is a sign that the package was repackaged.
Contact pattern
What to include in a support ticket
The route
The exact URL you reached, including any query string. The desk uses the route to confirm which snapshot the issue relates to.
The action
The action that triggered it: shortlisting, inspecting, installing, uninstalling, funding, withdrawing or playing. The desk uses the action to classify the issue.
The package
Package name and version, if you have already installed. The desk uses the package to confirm whether the package matches the snapshot.
A screenshot
If the issue is visual, attach a screenshot. The desk reads screenshots in the same private thread.
Account issues
What to check when the account acts up
Cannot log in
Reset the password at the partner's own login page. The companion does not host the login form; the partner owns it. If the reset email never arrives, open a support ticket.
Cannot deposit
Check the partner's published payment methods. The companion surfaces the route; the partner publishes the methods. If a method is missing, the partner has not enabled it for your region.
Cannot withdraw
Confirm the KYC status. Most partners require KYC before the first withdrawal. The KYC flow is owned by the partner; the companion does not see it.
Bonus did not credit
Confirm the offer terms. Some offers require a minimum deposit, a specific game or a specific time window. The companion surfaces the offer name; the partner publishes the terms.
VIP level did not update
The VIP level tracks the rolling 30-day bet total. A bet placed today updates the total within 24 hours. If the level is still wrong after 48 hours, open a support ticket.
Free withdrawal quota is exhausted
The quota resets per cycle. The cycle is published by the partner. If the quota is exhausted mid-cycle, the partner charges the published fee.
What the desk can and cannot do
Scope of the support desk
Can
Confirm the route. Confirm the package. Confirm getindslots games record. Confirm the snapshot. Confirm the disclosure. Confirm the install button. Open a feedback loop with the partner.
Cannot
Refund a deposit. Reverse a withdrawal. Change a partner's terms. Edit a published getindslots games record. Speed up a payment processor. Bypass a regional block. Replace a forgotten password.
After you open a ticket
What the desk does with the message
Acknowledgement
The desk acknowledges receipt of the ticket. The acknowledgement includes a ticket reference that you can quote in follow-up messages.
Classification
The desk classifies the issue as install, deposit, withdrawal, VIP, promo or content. Classification drives which team handles the ticket.
Investigation
The desk investigates the issue against the snapshot. If the issue is route- or disclosure-related, the desk fixes it in the next refresh. If the issue is partner-side, the desk opens a feedback loop.
Resolution
The desk replies in the same private thread. The reply explains what changed and what to verify on your side. The reply persists in the local storage until you reset the conversation.
When to escalate
Three signals that you should stop and ask
Wrong package signature
If the install verify step reports a different signature hash than the partner's published hash, stop the install and open a support ticket. The package may be a copy.
Unreachable partner
If the partner's site is unreachable from your network but other sites are reachable, the partner may be blocking your region. Open a support ticket to confirm the regional block.
Mismatched bonus
If the bonus you received does not match the offer terms published by the partner, stop and open a support ticket. The desk reads the ticket and follows up with the partner.
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.