中文Back

Utopia · Company & support

Privacy policy

Pre-release draft · Not effectiveReview date: 2026-10-10. Draft legal text is not registration consent.

Data handling for Owl Focus and its optional Utopia account, checked against the current client and server implementation. Unconfirmed deployment arrangements are identified.

Version2026-10-10 · Local review draft
Effective dateNot effective; not registration consent.
Proposed responsible companyChangzhou Wuwei Technology Co., Ltd.
Privacy contactprivacy@utopiaduo.com
On this page

1. Scope and responsible company

This draft covers local Owl Focus features and the Utopia account and Focus cloud features a user chooses to enable. The proposed responsible company is Changzhou Wuwei Technology Co., Ltd. (常州武维科技有限公司). Address: Room 507-2, Building C, Tian An Cyber Park, No. 588 Changwu South Road, Wujin District, Changzhou, Jiangsu 213164. Privacy contact: privacy@utopiaduo.com.

It does not cover Owl Letter, Owl Sleep, future hardware, unopened launch notifications or third-party sign-in. A shared Utopia account does not automatically combine App profiles, owls, work records, letters, relationships or sleep records.

2. Local use and storage

You can meet and name your owl, start, pause and end focus sessions, and use local records, the in-app album, notes and settings without an account. Local data includes timer parameters and durations, record cards, scene and memory content, preferences and note/task text. The in-app album is not the system photo library. Notes are encrypted locally; the entire database is not encrypted.

The current sync flow does not upload this Focus content before an explicit cloud binding. Operating-system backups, development tools and TestFlight diagnostics are separate paths; this is not a promise that all data always stays on the device.

3. Accounts, verification and age

Requesting a verification code sends a phone number or email, an app-generated device ID, device name, platform and Focus audience marker. These support contact verification, account creation/sign-in, sessions and abuse prevention. The service stores credential digests and encrypted values, verification states, code challenges and attempt records. Code expiry is not a retention limit for all records.

New cloud accounts process birth year and month to calculate eligibility. This is not exact birthday verification. The current rule rejects requests classified below its age-14 threshold, including the month of the fourteenth birthday. Local timers remain available. Eligibility, rule version and confirmation time are stored; the absence of separate birth-year/month columns does not prove their absence from request logs or backups.

Production code-delivery providers, age handling and request-log practices remain to be confirmed. Public account services are not open; this draft is not registration consent.

4. Cloud sync after an explicit choice

Successful code verification alone does not upload local Focus content. A user must compare local and cloud data, choose and explicitly bind a Focus profile. Sync can then include profile/owl IDs and names, timer/pause/end facts, records, scene and memory cards, preferences, versions, operation IDs, deletion markers and receipts for continuity and conflict handling.

Note/task text is not in the current client sync queue, and memory snapshots exclude private task text. Legacy encrypted-note server interfaces remain, so this is not a promise that no server can store notes. Switching accounts does not silently attach another account’s local data.

The current launch client restricts moving an owl between devices and blocks sync if the cloud owl belongs to another device. Cloud-sync support does not establish unrestricted continuity across devices.

5. Permissions, media and exports

Timer reminders request notification permission and schedule local notifications; refusing permission does not block local timing. Audio/video play scene media. The other-music-app option yields background playback without reading another music app’s account, library or listening history.

The reviewed business calls did not include location, contacts, camera, system photos or ad tracking. Expo configuration disables microphone and Face ID purpose declarations, and this local repair removes the older declarations from the iOS project. Verify the final signed package; source and configuration review do not replace dependency, runtime-permission and package review.

A user-initiated export creates a local file for the system share interface and may contain plaintext notes. The chosen recipient processes its copy under its own rules. Deleting Focus data does not delete exported files.

Sharing a record or album generates an image locally and opens the system share interface. Task titles are excluded from share cards by default and can be included at your choice. Copying a caption writes it to the system clipboard. Review the preview before sharing; recipient-app, clipboard and system copies are not jointly controlled by Focus sync or account deletion.

6. Diagnostics and TestFlight

The client records technical page, command, loading and performance events. Classified ordinary local diagnostics use a 14-day rule with cleanup on subsequent active writes; cleanup while the app is inactive is not guaranteed. Unknown legacy formats, unclassified security events and production logs require separate review.

TestFlight collects beta usage/crash information and provides diagnostics to the developer. Voluntary feedback can include screenshots, comments and technical details. This is separate from Focus sync and is not disabled by local-only use. Company-side access and retention of exported feedback remain unconfirmed.

This draft does not promise zero third-party SDKs, zero diagnostics, local-only processing of all data or end-to-end encryption of all data. Package privacy manifests and App Store disclosures must match actual handling.

7. Retention, deletion and backups

Signing out clears local login credentials and attempts server-session revocation, with retryable failures. It does not delete local Focus content or the Utopia account.

Current Focus-data and Utopia-account deletion flows have a seven-day waiting period. A pending request can be cancelled before its deadline. Final cleanup depends on maintenance, service receipts and device connectivity; all copies are not guaranteed to disappear on day seven. See the deletion page.

Current Focus cleanup covers sessions, sync history, settings, album content and associated copies, while retaining minimal deletion cases/markers. Other devices, system backups, shared files and legally retained data are distinct. Production retention categories, legal bases, backup windows and restoration safeguards are not finalized. A 24-hour internal target or proposed 30-day backup window is not a verified service promise.

8. Recipients, regions and open items

Actual verification-delivery, hosting, database, media, gateway and backup providers, received fields, storage/access regions and cross-border arrangements remain unconfirmed. The final policy must identify them rather than rely on a generic possible-third-parties statement.

Age/minor arrangements, log retention, rights-request handling and backup cleanup need review against deployment. The age gate alone is not a compliance assurance for every region.

9. Choices and privacy requests

Settings allow preference changes, reminders to be disabled and local exports. Once account services open, deletion and cancellation of pending requests use the in-app flow. Contact privacy@utopiaduo.com for access, correction, copies, deletion, withdrawal, complaints or problems accessing the app.

Support and privacy mailboxes are active and handled by the responsible team; no response time is promised. Describe the product and issue without sending verification codes, passwords, access tokens or unnecessary private notes. Identity checks should be proportionate.

10. Version and updates

Local review version: 2026-10-10. No effective date. Actual processing details, mailbox handling, legal review and the final package must be verified before publication, aligned with app consent versions and App Store disclosures. This draft does not signify Apple approval.