TinyOffice Google Play Launch Pack and Privacy Policy Draft
Document use
| Use it for | What it contains |
|---|---|
| Website | TinyOffice_privacy_en.html privacy policy page |
| Google Play | App setup, store listing and Data safety prompts |
| Review | Test account, deletion method, testers and 14-day record |
1. Confirm the website link
Upload TinyOffice_privacy_en.html to the website and provide Google Play with a public HTTPS link. Users and reviewers must be able to open it without signing in.
Privacy policy URL: https://[your-domain]/TinyOffice_privacy_en.html
Account deletion URL: https://[your-domain]/TinyOffice_privacy_en.html#account-deletion
Public support email: [support email]
Check the page with mobile data and a private browser window. Do not submit the example domain chesstar.com.
2. Developer and app details
| Field | Value | Status |
|---|---|---|
| Developer | Shanghai Maisi Apu Internet Technology Co., Ltd. | Known |
| Location | Xuhui District, Shanghai | Known |
| App name | TinyOffice | Known |
| Application ID | [AAB / Play Console applicationId] | Fill in |
| Support email | [Email that can answer users and reviewers] | Fill in |
| Website | https://to.ukjfh84.cn | Confirm |
| Privacy policy date | [First public date] | Confirm |
| Privacy contact | [Name or team email] | Fill in |
3. TinyOffice Privacy Policy
This policy explains in plain language what TinyOffice collects, why we use it, and how users can delete their account and data.
1. What we collect
Account information: email, nickname, user ID and login information.
Game content: character settings, level, tasks, chat, morning reports, tarot questions and reports.
Friends and sharing: invite codes, friend relationships and content the user chooses to share.
Purchase records: product, order status and virtual power or token balance changes; Google Play or the payment provider handles card and payment account details.
Technical information: IP address, device, crash or performance data only when the production version actually enables the related SDK or service.
2. How we use information
Create, sign in to and recover an account.
Provide the office, character, chat, task, morning report, tarot, growth and friend features.
Process purchases, refunds, support and account security.
Improve stability, prevent abuse and meet legal requirements.
3. AI and third-party services
Some chat, task or tarot content may be sent to an external AI service. Before publishing, add the real provider, purpose, data location, retention period and cross-border transfer details.
We do not sell personal information. We share only what is needed to provide a feature, complete a payment, process a user-requested share or meet a legal requirement.
4. Storage and deletion
We keep information for as long as needed to provide the service. After an account is deleted, we delete or anonymize related data, except for limited records that the law requires us to keep.
How to delete: users can start deletion in the app and can also email [public support email] to request deletion. Include the registered email and nickname so we can verify the request.
5. Security, age and contact
We use access controls, transfer protection and backup management to protect data. The exact measures must match the production version. Select the real target age in Google Play; do not select children as the target audience unless the product is designed and configured for children.
Privacy contact: [Fill before publishing]
Support email: [Fill before publishing]
Address: Xuhui District, Shanghai [full address]
4. Google Play Console app setup
Fill these in order. Answers must match the production app and backend.
| No. | Play Console item | TinyOffice entry guide | Done |
|---|---|---|---|
| 1 | Privacy policy | Enter the real published privacy policy URL. | [] |
| 2 | App access | If login is required, provide a reviewer test account and steps. | [] |
| 3 | Ads | Confirm whether ads are used; choose No ads only when true. | [] |
| 4 | Content rating | Answer based on AI chat, tarot, social features and user content. | [] |
| 5 | Target audience | Enter the real age range; do not select children unless applicable. | [] |
| 6 | Data safety | Use the mapping below. | [] |
| 7 | Government app | Choose Not applicable if TinyOffice is not a government service. | [] |
| 8 | Financial features | Virtual power and tokens are virtual items, not financial services. | [] |
| 9 | Health | Choose Not applicable if there are no health features. | [] |
| 10 | Category and contact | Choose the closest game category; add support email and website. | [] |
| 11 | Store listing | Prepare icon, screenshots, store text and support entry. | [] |
5. Data safety mapping
Check the production app and backend first. Select only data that is actually collected or shared.
| Data type | Possible Play option | Collection / sharing | Use |
|---|---|---|---|
| Email, nickname, user ID | Personal info or account info | Collected; sharing depends on providers | Sign-in and account management |
| Character, level, tasks and progress | App activity or other app content | Collected when the feature is used | Save game and task progress |
| Chat, tarot questions and reports | Messages or user-generated content | Collected; shared only if sent to an AI provider | Chat, tasks and reports |
| Invite codes and friend relations | Social or app activity | Declare only when the feature is live | Friends and sharing |
| Product, order and virtual item records | Purchase or financial info | Collected; payment details handled by payment provider | Purchases and balance |
| IP, device, crash and performance data | Device or diagnostic info | Declare only when the SDK actually collects it | Stability and diagnostics |
6. Closed testing checklist
Requirement: at least 12 testers for at least 14 continuous days. Keep the tester list, dates and feedback.
| Step | Action | Done standard | Record |
|---|---|---|---|
| 1 | Choose countries | Select the countries where the app will be tested. | [] Date: ____ |
| 2 | Choose testers | At least 12 people actually join; save their emails and join time. | [] Count: ____ |
| 3 | Start test | Confirm each tester can install and open the app. | [] Start: ____ |
| 4 | Keep 14 days | Run the test for at least 14 days; keep feedback and version notes. | [] End: ____ |
| 5 | Create release | Upload the AAB; check login and policy links. | [] Version: ____ |
| 6 | Confirm release | Check countries, testers, version and store details. | [] Date: ____ |
| 7 | Submit review | Submit to Google and save questions and replies. | [] Date: ____ |
7. Reviewer access and launch template
| Field | Value |
|---|---|
| Play developer account | [Account name] |
| Application ID | [com.example.tinyoffice] |
| Reviewer email | [Dedicated test email] |
| Reviewer password | [Do not write in a public document] |
| Login steps | [Open app -> sign in -> enter a core feature] |
| Test countries | [Countries] |
| Tester count | [At least 12] |
| Test dates | [YYYY-MM-DD to YYYY-MM-DD] |
| Issue log | [Link or file location] |
| Support email | [Email] |
| Website | https://to.ukjfh84.cn |
| Privacy policy URL | https://to.ukjfh84.cn/privacy/en.html |
| Account deletion URL | https://to.ukjfh84.cn/privacy/en.html#account-deletion |
8. Final checks
The privacy page opens publicly and all bracketed fields are replaced.
The policy matches the production AAB, SDKs and backend.
Users can start deletion in the app and can also request deletion outside the app.
The reviewer account can sign in and reach core features.
At least 12 testers joined and stayed for 14 days.
Store settings and testing records are saved.
9. Fields still needed
Application ID, support and privacy contact, production AI provider and retention details, the full address, target age, testing records, and any other bracketed fields must be completed before submission.
| Field | Why it matters |
|---|---|
| Website and HTTPS page | Google Play needs a public privacy policy URL. |
| Support email and contact | Users and reviewers need a working contact. |
| Application ID and reviewer account | The ID must match the uploaded package. |
| AI provider and retention period | Must match the real chat and task data flow. |
| Ads, analytics and crash SDKs | Changes Ads and Data safety answers. |
| In-app and external deletion entry | The deletion promise must be workable. |
| Target age and countries | Changes audience, rating and test scope. |