Privacy policy
Effective and last updated: 17 November 2026
Google sign-in is optional. Guest progress is saved in your browser. With your permission, Google progress is saved in your own Drive app-data folder. We do not receive your Google password or use Google API information for advertising.
1. Who operates the app
Atelier Roulette is a browser-based, single-zero roulette simulation operated by zhonecloud-sketch at https://zhonecloud-sketch.github.io/prototypes/rou/home.html. This policy covers the app and its public homepage, privacy, and terms pages. Contact: zhonecloud@gmail.com.
The app uses virtual play credits. It does not offer deposits, cash withdrawals, purchases of credits, or monetary prizes.
2. Data collection and Google user data accessed
The app accesses Google user data only after you select “Connect Google” in Table settings and grant the requested permissions. It obtains basic identity information from Google’s user-information service and reads or writes its own Google Drive app-data save. The data categories and storage locations are described below.
| Information | Access, purpose, and storage |
|---|---|
| Guest progress and preferences | Your play-credit balance, pending round and wager details, up to 222 recent completed spin results, and settings are stored in this browser’s local storage. Guest play does not request your Google profile. |
| Google identity | When you authorize Google sign-in, Google supplies a stable account identifier, name, and email address. The app uses them to identify your save and display your session. Google may return other basic profile details, such as a profile-picture URL; this version does not use or persist those additional details. |
| Google Drive save | The app finds, creates, reads, and updates atelier-roulette-bankroll-v1.json in its private Drive app-data folder. Its contents are your account identifier, play-credit balance, pending wagers and round details (including the selected outcome, result source, and replay or random-seed information), up to 222 completed results, save revision, session identifier, and save timestamp. The app also accesses the save’s file identifier, name, modification time, and version information to locate and update it safely. Your Google name and email are not included in this save file. |
| Temporary authorization | A short-lived Google access token is held in page memory while the app is open. It is not saved in browser local storage. The token lets the app make the profile and Drive requests you authorized. |
| Support messages | If you email us, we receive your email address, message, and any information or attachments you choose to send. We use them to respond to your request. |
The operator does not run a central player-account or bankroll database for this static app. Guest saves stay in your browser and Google saves stay in your Google Drive. The operator does not ordinarily have access to either save.
3. How and why Google user data is used
Your Google account identifier associates the save with the correct player. Your name and email identify the current session on screen. The short-lived access token authorizes these requests and the Drive requests you approved.
The app restores the saved balance and recent results at sign-in. It saves changes to wagers and completed rounds while you play, resumes outstanding rounds, calculates your personal statistics, and checks save revisions to detect another session changing the same balance. This allows the last saved bankroll to be restored on a later visit or another device using the same Google account.
Guest saves and preferences support the same gameplay features locally. Support messages are used to answer questions, resolve problems, and handle privacy requests. These data uses provide the app’s visible features; spin statistics are calculated for your own session and do not create an advertising profile.
4. Google permissions
Google displays an account and permission screen before access is granted. The app requests these scopes:
| Scope | Purpose |
|---|---|
openid | Identify the Google account associated with your save. |
email | Display your account email during the session. |
profile | Display your account name as part of the session. |
https://www.googleapis.com/auth/drive.appdata | Read and write this app’s own private save data in Google Drive. |
The Drive permission does not allow the app to browse your ordinary Drive documents, photos, or other apps’ private data. Its save is hidden from the normal Drive file list. Choosing Guest lets you play without granting these permissions.
5. Google API data and Limited Use
Atelier Roulette’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. We limit this information to the visible sign-in, save, restore, and related support features described in this policy.
We do not sell or rent Google user data, share it with advertising networks, data brokers, or information resellers, use it for targeted or personalized advertising, determine creditworthiness, or use it for lending. Google Workspace API data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models. The current app contains no advertising trackers or analytics SDKs.
Human reading of Google API data is not part of ordinary operation. Any such access must be limited to the specific data you affirmatively allow us to access for support, a necessary security investigation, or a legal requirement, in accordance with Google’s Limited Use rules.
7. Storage and retention
- Browser data: guest saves and preferences remain until they are replaced during use or you remove this site’s stored data. Local storage is managed by your browser.
- Google identity: the session name, email, and account identifier are held in page memory for the session. The account identifier is retained in the Drive save for as long as that save exists.
- Drive data: the private save remains in your Drive until you remove the app’s hidden data or remove it through Google’s app-management controls. It has no automatic inactivity deletion period. The app updates the current save as play continues. Closing the app or selecting “Leave table” does not delete that save.
- Access tokens: tokens are kept only in the current page’s memory and are cleared when the app resets the Google session or the page closes or reloads. Google authorization expires after a short lifetime, and the app may ask you to reconnect to continue saving.
- Recent results: the saved statistics window retains up to the latest 222 completed spins; older results are replaced as new ones arrive.
- Support messages: messages are retained for as long as reasonably needed to handle the request, resolve related issues, or meet legal obligations. Contact us to request deletion of support correspondence.
The operator does not keep a separate backup or archive of your private Drive save. Third-party hosting and service providers manage their own logs and retention under their policies.
8. Your choices, deletion, and disconnection
Clear guest data and preferences
Finish or leave your session, then clear this site’s stored data in your browser’s privacy or site settings. This removes local guest saves and preferences.
Delete the Google Drive save
Close the app first so it cannot write the save again. On a computer, open Google Drive settings, choose Manage apps, find Atelier Roulette (or the name shown on its Google consent screen), then choose Options → Delete hidden app data where available. Deletion removes your saved play credits and round history. A later Google session may create a fresh save if you grant access again.
Remove Google access
Open your Google Account’s third-party connections, select the app, and remove its access. The app will no longer be able to access Google data without renewed authorization. Removing access should not be assumed to delete all previously stored data; delete the hidden Drive save separately when you want it removed.
The operator cannot remotely erase data held only in your browser or private Drive. We can help you locate the relevant controls. You may contact us about access, correction, deletion, or other privacy rights that apply where you live. If you send a request, provide only the information needed to identify the issue; do not send passwords or access tokens.
9. Service providers and network information
The public site is hosted on GitHub Pages. Google provides account authorization, profile access, and Drive storage. The app may download the Three.js rendering library from jsDelivr or unpkg when a local copy is unavailable, and may request a recorded-results file from its configured feed address. If you select a local result file, its contents are read in your browser and are not uploaded by the app.
These requests may disclose technical details such as your IP address, browser information, requested URL, and request time to the relevant provider. The app does not intentionally send your Google profile or saved bankroll to GitHub, the rendering-library CDNs, or the recorded-results host. The public information pages use embedded styling and logo images and include no tracking scripts.
Providers process their own service information under their respective policies, which may involve countries outside your own. See Google’s Privacy Policy and the GitHub General Privacy Statement. Opening external links is subject to the destination’s privacy practices.
10. Security and data protection
Google identity and Drive requests use HTTPS, which encrypts those requests in transit. Google handles account selection and passwords in its own interface; this app never receives or stores your Google password. Access tokens stay in page memory instead of persistent browser storage. Drive access is limited to this app’s private app-data folder, and the app checks save revisions and uses browser session locks where available to reduce conflicting writes.
Your browser protects its own local storage, and Google manages account and Drive security under its policies. We do not claim an additional app-specific encryption layer for stored saves. Use a device and Google account you control, secure them with appropriate access protections, and check the saved status before closing the app. No browser or network security measure can guarantee absolute protection.
11. Adults and children
Atelier Roulette is intended for adults aged 18 or older and is not directed at children. We do not knowingly request Google information from children. Contact us if you believe a child has used the app or sent personal information so we can help address the issue.
12. Changes to this policy
We will update this page and its date when the app’s privacy practices change. Material changes will be brought to users’ attention on the site. New uses of Google information will be disclosed and any required consent obtained before those uses begin.
13. Game analytics
When you open the game or operator analytics, the account server uses the country Cloudflare estimates from your IP address. The analytics database stores country codes. It uses the game account for signed-in visits and a hashed browser session identifier for signed-out visits. Signed-out visits are counted for 30 days and expired entries are removed on subsequent game visits.
The operator reviews country totals, wagered round counts, and net returns in the access-controlled developer console. Multiplayer reports use settled server wagers. If you are signed in to an Atelier account when a solo wager settles, the game sends the round identifier, winning number, and wager amounts and selections to calculate the round’s stake and net return. Solo analytics retain the round identifier and calculated totals with the Atelier account. Deleting that account removes its location and play records.
14. Contact
Operator: zhonecloud-sketchApplication: Atelier Roulette
Support and privacy: zhonecloud@gmail.com