IndSlots Ind Slots · Android companion

DMCA notice

Effective 17 Aug 2026

Takedown procedure

If you believe that material on Ind Slots infringes your copyright, send a written notice to the support desk at /contact/. Include the URL, a description of the work and a statement of good-faith belief.

Counter-notice

If you believe the material was removed in error, send a counter-notice with the same details and a statement under penalty of perjury.

Repeat infringers

Ind Slots reserves the right to remove access for repeat infringers.

What the notice must include

An identification of the copyrighted work claimed to have been infringed. An identification of the material that is claimed to be infringing. Your contact information. A statement that you have a good-faith belief that use of the material in the manner complained of is not authorised. A statement that the information in the notification is accurate.

Where to send the notice

The notice should be sent via the support conversation at /contact/. The desk reads the ticket in the same private thread.

Response time

The desk acknowledges receipt of a takedown notice within five working days. Counter-notices are processed within ten working days. Repeat infringers lose access.

Good faith

Why the desk treats takedowns seriously

Source-referenced artwork

The companion reuses source-referenced artwork under the source-reference policy declared in the YONO index. The desk audits each profile before it lands.

Counter-notice path

If the desk removes a profile in error, the counter-notice path lets the publisher restore the profile. The desk reads the counter-notice in the same private thread.

Repeat infringers

The desk reserves the right to remove access for repeat infringers. The policy is published in the DMCA page and is not arbitrary.

Independent review

The desk does not adjudicate disputes between publishers. If the dispute is between two publishers, the desk removes the disputed material pending resolution.

What happens after notice

The desk's process for takedown and counter-notice

Acknowledgement

The desk acknowledges receipt of a takedown notice within five working days. Acknowledgement goes to the contact email or ticket reference in the notice.

Review

The desk reviews the notice against the snapshot. The desk confirms the URL, the work and the good-faith statement. If the notice is incomplete, the desk asks for the missing information.

Action

If the notice is valid, the desk removes the material or restricts access. The desk logs the action and the source of the notice.

Counter-notice

If the publisher believes the material was removed in error, the publisher can send a counter-notice. The counter-notice must include the same details plus a statement under penalty of perjury.

Restoration

If the counter-notice is valid, the desk restores the material within ten working days. The desk logs the restoration.

Repeat infringers

The desk reserves the right to remove access for repeat infringers. The policy is published in the DMCA page and is not arbitrary.

Avoiding a takedown

Three checks before you publish a profile

Use source-referenced artwork

The companion reuses source-referenced artwork under the source-reference policy. Do not redraw logos; do not re-encode artwork.

Use the source category

The companion uses the publisher's own category. Do not relabel a profile to make it appear under a different category.

Use the source title

The companion uses the publisher's own title. Do not paraphrase the title to make it appear under a different brand.

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.

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.