Kenji Koikeda (trade name: 10dots) ("we", "us") explains below how we handle information about users of the online game "Last Paycheck" (Japanese title: AIに仕事とられた) (the "Service").
| Category | Information | Purpose |
|---|---|---|
| Account | A user ID we issue, the authentication provider's identifier (uid), guest/member status, created and last-used times | Sign-in, account management, fraud prevention |
| Nickname | The nickname you set (or one assigned automatically) | Display in rankings |
| Game records | Rooms joined, assigned roles, application type, in-game results (e.g., final assets), connection and activity status | Running the game, role lottery, completion rewards, fraud prevention |
| Rankings | For members only: nickname, role, final result, end time. Guests are not included in rankings (play history is separate; see below). | Ranking and hall-of-fame display |
| Play history | Results recorded when a game ends: the whole game's result (how the world developed, rankings per role, chart data — no other participants' user IDs or nicknames) and your own record (role, rank, final assets, whether humanity survived, participation status). Guests' records are also saved, under an anonymous per-device identifier | Showing your past records; sharing results (section 4) |
| Points | Records of points granted, spent, expired and returned; purchase records (payment identifiers, product, amount, currency, date) | Managing points, handling purchases and refunds, accounting |
| Inquiries | The content of your inquiry and your contact details (e.g., email) | Replying and keeping a record |
| Ad measurement | Records of ad impressions and clicks, using a hashed random device identifier to avoid counting the same ad repeatedly in a short time; ad reports | Ad statistics, click-fraud prevention, ad review |
| Access logs | IP address, access time, URL, browser type, etc. (recorded by the hosting service) | Troubleshooting, preventing abuse, operations |
| Surveys | Answers you choose to give (please do not write personal information in free text) | Improving the Service |
1.Registration and sign-in use Google LLC's authentication service (Firebase Authentication). Guests use a random per-device identifier.
2.When you sign in with a Google account, Google provides your name, email address and profile picture to the authentication service (Firebase), which manages them. We do not store your name, email address or profile picture in the game's database, and we do not show them in the game. We store only what is listed in section 1, such as the user ID we issue.
3.The authentication provider handles information under its own privacy policy.
1.Points are purchased through Stripe, Inc. ("Stripe"). Card numbers and similar details are entered on Stripe's checkout page and are not stored on our servers.
2.To confirm payments, we receive from Stripe, and record, the payment identifier, the product purchased, the amount, the currency and the result.
3.If you enter an email address or other details at checkout, Stripe handles them under its own privacy policy. For purchases in USD, taxes may be added at checkout.
1.Play history. When a game ends, we save (a) the result of the whole game (world), including how the world developed, rankings per role and chart data — it does not include other participants' user IDs or nicknames — and (b) your own record (your role, rank, final assets, whether humanity survived, and your participation status). Guests' records are also saved, under an anonymous per-device identifier. You can see the records of games you took part in on the in-game history screen (members only; guests are only told that records exist).
2.Sharing results. If you use "Copy URL" or "Share to social media" on the result screen, a public URL showing the whole game's result is created. Anyone who knows the URL can view it without signing in. The public page shows the whole-game result described in item 1(a); it does not include user IDs, nicknames, points, email addresses or other personally identifying information. To highlight the sharer's position, only the role and the rank within the role put in the URL are used (a nickname is added to a shared image only if you choose to). We ask search engines not to index the page, but we cannot prevent people who know the URL from sharing it further.
3.Carrying over a guest's records to a member account. When a guest becomes a member, the guest records on that device (play history, role history and free points) are carried over to the member account only once. Free points are carried over up to the member's holding limit. To confirm the transfer, both the guest's and the member's credentials are used at that time. A guest identifier that has been carried over cannot be used for another transfer.
We use the following providers to operate the Service. We do not provide personal data to third parties without your consent, except as required by law.
| Provider | Use | Information involved |
|---|---|---|
| Google LLC (Firebase Authentication) | Sign-in | Information needed to sign in (name, email and picture for Google sign-in) |
| Stripe, Inc. | Payments | The product and amount, and the user ID we issued; your payment details |
| Cloudflare, Inc. | Hosting servers and databases, delivery | All Service data held on the servers; access logs |
| OpenAI (ad review) | Assisting review of ad content | Ad text, excerpts of the landing page, images, advertiser company name. Advertisers' contact details are not sent |
| Slack (operator notifications) | Notifying the operator | Ad review results and operational alerts such as payment mismatches (users' emails are not included) |
These providers' servers may be located outside Japan. [TBD: disclosure for transfers to other countries — confirm with a professional.]
| Information | Retention |
|---|---|
| Account, nickname, role history | Until you delete your account; then deleted (only the deleted identifier and time are kept to prevent sign-in with credentials issued before deletion) |
| Play history | Members: the latest 100 records (older ones are deleted first), until you delete your account. Guests: 30 days while unregistered (and the latest 100). Becoming a member switches to the member rule. Deleting your account deletes your own records |
| Shared results (public URL) | 1 year from the day you share. Results that were not shared are deleted once no user's record refers to them. Shared results are not deleted when you delete your account, because they contain no personally identifying information; to ask for deletion, use the contact in section 12 |
| Ranking records | Raw records are deleted after 1 month. The hall of fame keeps only top entries. Everything is deleted when you delete your account |
| Points records | After you delete your account, the user ID is anonymized and the records are kept as accounting records. Retention period: [TBD (e.g., 7 years)] |
| Purchase records | Same as above. [TBD] |
| Game logs (for verification) | [TBD] |
| Ad measurement and reports | [TBD] |
| Inquiries | [TBD] after the matter is closed |
| Access logs | Depends on the hosting provider's settings. [TBD: check Cloudflare's log retention] |
The Service stores your sign-in state, a random identifier, display settings (such as language) and play counts in your browser's storage (e.g., localStorage). You can delete them in your browser settings, but guest data may become unrecoverable. [TBD: add if advertising or analytics cookies are used.]
1.You may ask us to disclose, correct, stop using, or delete your personal information. Members can delete their account, nickname and rankings with the in-game account-deletion feature.
2.For other requests, contact us below with information that identifies your account (such as your user ID). We may need to verify your identity.
Users under 18 need a legal guardian's consent to buy points (Terms of Service, Article 3). [TBD: handling of users under 13.]
We take measures such as encrypted communication (HTTPS), access control and verification of credentials to prevent leakage, loss or damage. Payment secrets (Stripe keys) are kept in the server's secure storage and are not written to logs or records.
We may revise this policy. We will announce important changes in the Service.
Kenji Koikeda (trade name: 10dots) / 4F Kabutocho Dairoku Hayama Bldg., 17-2 Nihonbashi-Kabutocho, Chuo-ku, Tokyo 103-0026, Japan / contact@studio10dots.com
Effective date: [TBD]