Privacy Policy
This policy explains how Indus Gaming handles information through indusgaming.xyz and the Indus Studio workspace: accounts, Minecraft tools, games, rewards displays and project updates.
1. Operator and scope
Indus Gaming and Indus Studio are the website and workspace names used in this policy.
Indus Gaming is personally operated by Bjorn Aidan Collins, currently based in Thailand. Indus Gaming is the website/brand name, not a registered business.
Public support and privacy contact: bjorncollins2004@gmail.com.
If you email this address, the operator receives your sender details, message and any attachments in a Gmail mailbox to respond to your enquiry. Bjorn personally handles privacy and deletion enquiries at this address.
This policy covers the website's handling of information, including its exchanges with Indus Command. It does not describe all processing by Discord, Google, YouTube, Patreon or other sites you visit. The Terms of Service describe use of the website.
2. Accounts and Discord
You can register with an email address and password or sign in through Discord. For an email account, the website stores your normalised email address and a password hash. It also stores an internal account ID, account role and creation time.
If you choose Discord sign-in or link Discord to an existing account, Discord supplies your user ID, username and avatar reference. The website stores these to recognise your account, show your profile and connect eligible rewards activity. This connection requests Discord's basic identification permission; it does not request your Discord email, private messages or list of connected third-party accounts.
The website exchanges a temporary Discord authorisation code for an access token to retrieve your profile. The account record stores profile identifiers, not that access token. Short-lived records bind the sign-in or linking attempt to the browser and, when linking, the signed-in account. Sign-in, registration and linking events are recorded with the account ID, method and time.
Signing out clears the website session cookie. It does not delete your account, activity records or Discord link.
3. Tools, AI requests and saved plans
City Planner sends the city name, modpack, dimensions, style, transport choices, terrain and notes you submit to the website server. The server sends that information to the OpenAI API to generate a plan, then sends the generated plan for a build checklist.
Structure Generator runs in your browser and uses no AI service. The building, its settings and any schematic file you choose under "Check a paste" stay on your device: they are not sent to the website server or to OpenAI. Opening the tool and downloading a schematic are recorded as navigation events (section 6), without the building or its settings. The tool handlers accept text and settings; they do not provide a member file-upload service.
The generation requests do not deliberately add your website account ID, email or Discord profile to the AI prompt. Any personal information you put in your text will, however, be included. Avoid submitting secrets or information you do not have permission to use.
Saved city-plan names, output, tasks and checklist progress are kept in this browser's local storage. They are not an account-synchronised project library. The Clear saved plans control removes saved plans; separately stored checklist preferences may remain until you clear the site's browser storage. Downloads remain on your device until you remove them.
The website records generation usage separately from project content. Generation handlers do not save a server project history, but diagnostic errors can include generated design text. This is not a promise that prompts or output are never retained in logs or by the AI provider.
OpenAI's API data controls differ from consumer ChatGPT settings. OpenAI documents a default of no model training on API data unless the API customer opts in, and abuse-monitoring retention with exceptions. See OpenAI's API data controls.
4. Games and rewards
The Games hub's practice games run in your browser. Sound preferences and the last selected Minecart yard can be stored locally. Practice play does not earn Points.
Rewards mode in Minecart Dispatch, Tower Control and Last Line sends the linked Discord identity, selected game and difficulty, session identifiers and ordered controls to Indus Command through the website server. Indus Command stores the authoritative session, accepted actions, result, entry fee and settlement receipt. Practice sessions remain local and cannot become reward claims.
Daily Spin stores account and Discord identifiers, display name, claim identifiers, outcomes, acknowledgement and retry information. For eligible claims, the website sends Indus Command the Discord identifier and claim ID. The bot supplies the authoritative fee and reward result.
The website also requests linked reward profiles, rankings, community statistics and Epoch information from Indus Command. Public leaderboards and win feeds can display names, results and Points. Minesweeper and the logo reward are retired; historical game records, receipts and reconciliation evidence are retained.
Reward eligibility follows the relevant programme's existing rules. This policy does not change current enrolments, earned entitlements or agreed Epoch rules.
5. Cookies and browser storage
The website uses the following first-party cookies when the relevant feature is used. Cookie expiry is separate from deletion of related server records.
| Cookie | Purpose | Configured lifetime |
|---|---|---|
indus_session | Signed-in website session | 7 days; cleared on sign-out |
discord_oauth_state | Protect a Discord sign-in or linking attempt | 5 minutes; cleared during a valid callback |
indus_anon | Recognise anonymous tool usage and enforce its limit | 365 days |
Earlier versions of the homepage also set an indus_youtube_consent cookie to remember agreement before showing YouTube content. The website no longer needs or reads it, and removes it the next time you open the homepage.
Local storage also holds saved city plans and checklists, sidebar choices (scoped to a guest or website account), game sound settings and the last Minecart yard. No automatic expiry is set for these preferences. Clearing site data removes them and may remove work you wanted to keep; signing out alone does not clear them.
Session storage holds a temporary portal-transition marker and Rewards game session/action references for retry recovery. It is normally limited to the browser tab's session, subject to browser restore behaviour. The transition marker is removed when the workspace reads it. Historical Minesweeper storage may remain until browser expiry or removal; the retired feature no longer reads or creates it.
You can manage cookies and storage in your browser. Blocking necessary storage may prevent sign-in, remembered settings or game recovery. The legal pages themselves set no cookies and run no tracking scripts.
6. Usage and technical information
The website records tool-use counts and selected navigation events, such as entering the workspace, opening supported tools, downloading a Structure Generator schematic and choosing Discord connection actions. Records contain a tool or event name, time and, where available, the account ID or anonymous usage token. Administrators can view usage totals and recent account/activity information to operate the service.
These are the website's own usage statistics. The website does not load Google Analytics. A Google or YouTube API connection is not Google Analytics.
Hosting systems receive technical request information such as an IP address, requested URL and browser headers when serving the site. Application errors are logged for troubleshooting. Hosting logs and diagnostics can have different retention from website records. No single retention period for all hosting logs or backups is stated here.
7. Project news and media
The released homepage shows editorial project information and locally hosted artwork. Owner tools can also upload Epoch panel artwork. Epoch artwork uses public asset URLs, including staged or historical artwork that remains stored; it should not contain confidential information.
The homepage Status section shows public channel, series and modpack information gathered by the website's server. You don't need to agree to anything to view it, and viewing it doesn't make your browser contact YouTube, Modrinth or Discord.
The Status editor lets the operator save drafts of the section and upload project images. It is an owner feature, not a general member-upload service. It stores content, saved revisions, publication records, the operator's account ID and media metadata on the website's storage. TikTok follower and view figures in the section are entered by the operator; the website does not connect to TikTok.
In the Status service, unpublished drafts and images are restricted to the owner. Publication makes the selected visible content and its media available to visitors. An asset needs to be referenced by the current publication to be served through its public Status URL. Removing it from that publication removes that route's public access, but does not erase the retained file, historical revisions or copies already downloaded.
8. YouTube
The Status section shows the channel's latest public uploads, Shorts and Indus Metropolis episodes. The website's server reads them from YouTube's public video feeds, which list each video's ID, title, publication date, view count and thumbnail. The server copies the thumbnails and serves them from the website, so displaying the section does not make a visitor's browser contact YouTube.
For the subscriber count and the channel's total views, the server uses YouTube API Services (the YouTube Data API) with an API key. This reads public channel statistics only. It does not involve a Google sign-in, YouTube Analytics or any visitor's YouTube account.
The server checks these sources at intervals of at least 15 minutes, with backoff after failures. YouTube statistics that could not be refreshed for 29 days stop being shown and are deleted. Copied thumbnails and video details are deleted within 30 days of a video leaving the feeds. Video links open YouTube's own website; the Status section does not embed a YouTube player. Status backups leave out these source caches.
Earlier versions of the Status section also used a read-only connection to the operator's own channel, under the OAuth app name Indus Website Status, to read YouTube Analytics content types. That connection has been retired: the website no longer reads YouTube Analytics, and the cached classifications it produced have been deleted. Access granted to the app can be removed in Google Account connections.
Google handles information under the Google Privacy Policy. Use of YouTube features is also subject to the YouTube Terms of Service.
9. Providers and external content
- Railway hosts the website and its persistent server storage. Website administrators can access operational records needed to manage the service.
- OpenAI receives the tool inputs and generated intermediate text described above to provide AI generation.
- Discord supplies account identification and remotely loaded profile avatars. Indus Command supplies reward data and handles eligible claims. The Status integration separately reads public Discord invite counts; that is not a member-account connection.
- Google/YouTube supplies public channel and video information and channel statistics to the website's server, as described in section 8. Visitors' browsers do not load YouTube images or players on the homepage.
- Modrinth supplies public details of the Indus Gaming modpack to the website's server: versions, download count, icon and gallery images. The website serves copies of those images itself.
- unpkg and jsDelivr serve third-party 3D-viewer scripts referenced by the workspace. Loading those files sends a request to their hosts. The site's fonts are hosted locally.
Status video links open YouTube's own website; no YouTube player is embedded. Operator-uploaded Status images are served from website storage. Links to Patreon, Discord, YouTube, TikTok, Modrinth and external projects take you to separately operated services when followed. A link alone differs from a thumbnail or script loaded while viewing this website.
External services handle the requests they receive under their own terms and privacy policies, including Discord's privacy policy. The website's disclosures do not set those providers' retention periods.
10. Retention, deletion and choices
Some lifetimes are implemented: Discord linking records expire after five minutes and are consumed on a valid attempt; expired records are cleaned up on startup or another attempt. Retired Minesweeper records are no longer automatically pruned by gameplay. Browser storage follows the behaviour described above; the YouTube cache has the separate limits described above.
Accounts, general usage/login/navigation records, reward receipts and Epoch artwork do not have a general automatic deletion schedule. Status revision/media history also has no general automatic deletion schedule. Resetting a usage limit, hiding content or signing out is not deletion. Operational logs and backups can have different retention from the active database.
The owner's intended retention approach is:
- Accounts: keep information needed to provide the account. On a valid deletion request, remove or anonymise information no longer needed, subject to specific, justified legal exceptions.
- Activity and security records currently have no fixed deletion schedule; privacy and deletion requests are reviewed individually by Bjorn Aidan Collins.
- Rewards: keep the minimum information needed to settle existing entitlements, prevent duplicate claims and resolve disputes. A record's historical value alone does not justify keeping all personal information indefinitely.
- Media: keep material while needed for its published purpose or a retained draft; review unused uploads for cleanup.
- Backups: confirm actual expiry arrangements and ensure completed deletions are reapplied after a restore before affected data returns to normal use. Immediate erasure from every backup is not promised.
YouTube API data is subject to YouTube's separate requirements, including the refresh and deletion limits described in section 8. General retention criteria do not extend those limits.
These retention intentions do not mean that automatic deletion or a complete backup-restoration procedure is currently in place.
There is no self-service delete-account feature. Send privacy or deletion requests to the email in section 1; Bjorn Aidan Collins will personally review them. Account ownership should be verified proportionately using information needed for the request. Do not send a passport, identity document, password or access token as a routine part of an enquiry. Technical deletion and backup-restoration procedures are not yet complete. Requests are reviewed individually; no automated outcome or fixed response time is promised. Deleting website-held YouTube data would not delete data held by YouTube.
11. Security, rights and audience
The website uses password hashing, signed session cookies and restricted administrator/owner routes. These measures reduce risks but cannot guarantee perfect security. Keep account credentials private and use only information you are comfortable submitting to the tools.
Hosting and providers may process information outside your country.
Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing, obtain a portable copy, withdraw consent where processing relies on it, or complain to a relevant regulator. Those rights may have conditions and exceptions.
Indus Gaming is intended for teenagers aged 13 and over and adults, not children under 13. For accounts and interactive features, the minimum is 13 or any higher age required by applicable law and the relevant service. Parent or guardian involvement is required where the law requires it. Discord sign-in does not verify a visitor's age or establish that all consent requirements are met.
These policies do not change existing Epoch eligibility, enrolments or earned entitlements, or introduce an 18+ rewards rule.
12. Changes and contact
This page shows its effective date and will identify later updates. Material changes should be brought to users' attention before taking effect, with renewed consent where required for a new use of connected-service data.