Privacy Policy

Last revised:

1. Scope and contact

Eyayoo Studio is the brand used by the individual developer providing these services ("we", "us"). This policy covers our Android and iOS applications and related website and support services that link to or refer to this policy. Store listings show Eyayoo Studio on Google Play and 捷 胡 on the App Store.

Contact us at [email protected] or through our HTTPS contact page. Please include the app name and platform. Features and data processing differ by app, version and platform; the sections below identify when each type applies.

2. On-device data and creative content

Applications save progress, practice results, preferences and, where provided, drawings and recordings in app storage to deliver their features. Full local records are different from the usage events sent to analytics services. The applications covered here do not provide an app-created account or developer-operated cloud synchronization of your progress or works.

In drawing apps with photo or voice features, the camera or microphone is requested when you use the relevant feature. Drawings and recordings are saved on the device. Saving to the photo library or sharing uses the system feature or receiving app you choose; those exported copies have their own storage and privacy controls. The feature does not automatically upload your entire photo library to us.

You can change camera, microphone and photo permissions in system settings. This can prevent the corresponding feature from working. Operating-system backup or device transfer can retain separate copies according to your device and account settings.

3. Usage analytics and choices

Our drawing and training apps use Google Analytics for Firebase to understand feature use and improve the apps. Depending on the app, events include screen and feature visits, level or practice activity, results and duration, and purchase or restore outcomes. The service also processes app-instance identifiers and device, app and network information. These records are not necessarily anonymous.

In updated apps that offer a separate usage-statistics choice, collection is off until you explicitly allow it. You can refuse or withdraw using that app’s privacy settings. Withdrawal stops subsequent collection on that Firebase analytics path and resets its local analytics data; it does not erase previously uploaded records or your local progress and purchased benefits. Older versions and apps without this control do not acquire the new setting merely because this policy has changed; they can have analytics enabled without that in-app switch.

Where linked analytics export is enabled, Google BigQuery holds event-level and user-level analysis copies, including available identifiers and collected usage or purchase events. These copies support analysis and improvement, not restoration of your local progress. They are managed separately from Analytics reports and retention settings.

Reading this policy, accepting the terms, downloading or continuing to use an app, or making a purchase does not authorize optional analytics. Analytics choices, system permissions, advertising choices and purchase-service processing are separate. If your version lacks a choice you need, contact us; this page cannot change the app’s SDK settings.

4. Advertising

In ad-supported app versions, including free training features, Google AdMob processes data such as IP address and approximate location inferred from it, ad and app interactions, diagnostics, and advertising or other identifiers to serve and measure ads and prevent fraud. Rewarded ads apply only where the app offers them. Apps or versions without ads do not use an advertising feature simply because they refer to this policy.

Where applicable, the advertising consent interface and an available advertising-privacy entry let you make or revisit ad choices. On iOS, the system tracking permission is another separate control. Declining tracking does not stop all necessary service processing. An ad-free purchase does not authorize analytics or eliminate transaction processing.

Where AdMob and Analytics are linked, eligible automatic or recommended events, including qualifying purchase events, can support advertising measurement or publisher first-party features subject to the applicable version, service settings and your choices. This does not mean every custom practice event is used for personalized advertising, or override a refusal of advertising consent.

5. Purchases and payment services

Apple App Store or Google Play handles payment through the store you use. The app and Unity IAP process product details, transaction receipts or tokens, purchase status and restoration results to deliver and verify purchased access. We do not ask you to enter payment-card details into our apps.

Unity IAP also has separate transaction-event processing, which can include purchase failures, installation or session identifiers, iOS vendor identifiers, and device, application and regional settings. Depending on the SDK version, technical device attributes can include system startup time and storage capacity. These data support purchasing and related service analysis. A Firebase analytics switch does not control this separate service. Necessary transaction processing does not itself authorize every optional analytical use.

6. Support, website and resource requests

If you email us, we receive your email address, message and any screenshots, recordings, attachments or optional reference you choose to send. We use them to answer your question or address the request, not as a marketing list. Send only what is needed. The website contact form currently prepares a message in your email client; opening a draft does not submit it or upload your device logs.

When you open our website or request online app resources, our hosting, source server and CDN services process requests and related technical information, such as IP address, requested URL, time, response status and client information, to deliver content, monitor performance and protect the service. Cloudflare participates in website delivery and associated access or performance processing. These records are separate from on-device app data. The website stores language and theme preferences locally in your browser.

7. Service providers and their policies

The following services apply to the functions described above, rather than all running in every app. Their policies explain their own processing, safeguards and available controls.

App and advertising services can process technical errors and diagnostic information as part of their operation. Service-related diagnostics are not the same as uploading all of your local app logs to us.

8. Data retention and deletion

How to send a request

To request deletion, use an available in-app contact channel, our website contact page, or email [email protected]. No app account, purchase or enabled analytics is required. The website contact page prepares an email draft; opening it does not send the request. Review and send it through your email service.

Please include the app name, platform (Android or iOS) and data category. Our support team will explain any further information needed to verify your authority or locate records for your specific request. Send only necessary information; do not send passwords, verification codes, payment-card numbers or full receipts.

We assess your authority, the relevant services and records that can be located under our control, then explain the available action and any retention requirement or limitation. For records processed on our behalf, handling may require us to instruct the provider. A single email does not automatically locate or erase every record held by a third party.

Local data on your device

Local progress, preferences, drawings and recordings remain in app storage until removed through an available app function or device data control. An email request cannot remotely erase files held only on your device. Where an app offers deletion of a work or recording, use that function for the selected item. Save or export anything you want to keep before deleting data.

Stopping analytics and requesting historical-data deletion

Where an app provides a usage-statistics setting, turning it off stops subsequent collection on that analytics path. This does not erase uploaded history, advertising data, purchase records or your local progress. Do not enable statistics just to make a privacy request.

Analytics records, linked BigQuery exports, advertising data, Firebase installation records, local progress, purchase rights and support email are distinct. Deletion in one service does not prove deletion in another, and an email address alone may not identify SDK records. Information needed to locate records may be lost after a reset or reinstall, may not be recoverable, and may not cover every historical record.

Retention, providers and necessary limits

Usage analytics follows the relevant service settings. Aggregated reports and BigQuery event-level or user-level exports are managed separately: resetting the app or expiry of Analytics retention does not automatically delete warehouse copies. Advertising, Firebase installation and Unity service records also require their own handling under the applicable purposes, settings and provider rules. There is no single retention period for all these data.

For support messages and attachments, we consider whether the issue is resolved, whether the request still needs handling and any legal recordkeeping obligation. Original messages and attachments are assessed separately from the minimum record needed to document a request and its outcome. Mailbox recovery, archives, synchronization and backups have separate controls and need separate checks.

Website and resource access logs follow the relevant host or CDN’s rotation and retention settings; they may not be identifiable by email address. Store accounts, transactions and fraud-prevention records are managed through Apple or Google and can be retained under store rules and applicable legal obligations. Deleting local app data or support correspondence does not itself cancel a purchase.

Where a provider processes data independently, its privacy-request channel also applies. For Unity’s independent processing, this can include [email protected]. See service providers and their policies for the relevant channels, and the Terms of Service for purchase information.

We explain records that cannot be located or removed and any applicable retention requirement. We cannot promise immediate removal of all copies or one fixed completion deadline across services. Receiving a request or a provider acknowledgment is not proof that deletion is complete. Stopping future collection, deleting local data and handling previously uploaded records remain separate actions.

9. Your requests and rights

Depending on applicable law, you may have rights to access, correct or delete data, restrict or object to processing, request portability, withdraw consent, or complain to the appropriate supervisory authority.

To exercise a right or ask about your data, follow Data retention and deletion above. It explains how to contact us, the minimum information needed, applicable verification and the separate handling of local data and provider-held records.

10. Security, international processing and children

We use HTTPS for website and network service connections where provided, and limit the information requested to the purpose of the interaction. No network or storage method offers absolute security. Service providers may process data outside your country; linked BigQuery analysis data can be held in the United States. Applicable provider terms and legal safeguards govern these transfers.

Our apps have different audiences, including drawing experiences intended for children. Parents and guardians should review the particular app’s store information, supervise purchases and sharing, and manage device permissions. A single age threshold does not describe every app or jurisdiction. If you believe a child’s information was processed inappropriately, contact us with the app and relevant circumstances so we can assess the applicable requirements and available action.

11. Policy updates

Revisions are shown with the date on this page. For material changes, notice or a new choice is provided where applicable law requires it. A policy update does not automatically turn on optional data collection. The Terms of Service describe service use and purchasing; they do not replace privacy choices.