PRIVACY
Mellow Privacy Policy
Effective date: November 9, 2026
Mellow, also called 慢慢, is operated by wangrui li, based in China. This policy explains how the app handles information, the services involved, and the choices you have. It also explains the controls kept for installations that used our previous companion image or backup services.
Privacy contact: wrli1220@126.com. Product support: https://mellow-site.mellow-app.workers.dev/support/.
Privacy at a glance
- Your task library is stored on your device. When iCloud is available, it syncs through your Apple Account's private CloudKit database.
- Apple handles the trial and one-time purchase. We do not receive your payment card details or Apple Account password.
- Sharing usage analytics and crash reports is optional, off by default, and controlled separately. Your choice does not change the price or availability of task features.
- We do not sell personal information or use advertising SDKs, cross-app advertising tracking, or session replay in this version.
- Bundled companions work offline. This version does not offer photo uploads or new image generation. Our active image store is empty; the appendix explains compatibility controls for earlier installations.
- Local data, iCloud copies, shared diagnostics, and previous service accounts have separate deletion controls.
The sections below explain these points in more detail.
1. Your tasks, iCloud, and Apple features
Mellow stores tasks, notes, lists, templates, drafts, attachments, and chosen reminder locations on your device. When iCloud is available, library documents, attachments, your official companion choice and its name sync through your Apple Account's private CloudKit database. Legacy companion history may remain in stored documents or backups, but version 0.2.0 and later do not offer it for selection. When iCloud is unavailable, changes remain on the device until sync can resume. Apple operates its services under its own privacy terms.
You do not need a Mellow service account for ordinary task use. Your task library is not sent to our usage analytics or crash reporting services. Previous installations that explicitly connected to the retired backup service may still have server copies; see the appendix.
The features you choose may also use the following information:
| Feature | Information used and purpose |
|---|---|
| Location reminders | The chosen place, coordinates, radius, and arrival or departure condition are saved with the task and may enter iCloud or your exports. We do not store a history of your movements. Apple handles maps and place searches. |
| Apple Reminders import | The lists you choose are copied into Mellow. Their originals remain in Apple Reminders. |
| Notifications, alarms, and widgets | Task titles and the information needed for reminders or widget displays are processed on the device. Titles may be visible on the Lock Screen or Home Screen according to your choices and system settings. |
| Siri and sharing | Apple handles Siri input. The share extension receives the text and links you choose to share with Mellow. |
| Copy and paste | Content you copy may enter the system clipboard. You control the resulting copies separately. |
| Viewing statistics | Optional viewing statistics stay on the device and can be turned off and cleared. |
You can manage Apple permissions in system Settings. Declining a permission may make the feature that needs it unavailable.
2. Trial and one-time purchase
The user-started 14-day trial and one-time unlock use Apple's App Store and StoreKit. Mellow checks verified transactions on your device to determine the original trial start date, whether the trial has been used, and whether an unlock is active or revoked. The trial does not automatically charge you.
Apple handles purchase authorization and payment. A small access-status file on your device lets the app and share extension apply the same trial limits. It contains the trial start time, trial-used and unlock status, and the latest time observed by the app. This file is excluded from task exports, iCloud task sync, and device backups. StoreKit transactions and this file are not sent to our backend, PostHog, or Crashlytics.
Restoring purchases asks the App Store to refresh your transactions. Clearing task data does not erase Apple's purchase records, which Apple handles under its own privacy terms.
3. Optional usage analytics
Mellow keeps local feature events and performance timings for up to 90 days and 20,000 events. These records are separate from task backups and iCloud. They exclude task and list content, search text, images, locations, content IDs, service accounts, and raw error messages.
Sharing with PostHog is off by default. If you agree separately in Settings, Mellow shares new feature events, outcomes, counts, timings, indicators of whether a field is present, timestamps, app version and platform information, and random analytics, session, and flow identifiers. These records help us understand feature use and performance. Older local records are not uploaded.
We do not use session replay, screenshots, automatic text capture, advertising identifiers, or identification through your service account. A minimal profile under a random analytics identifier allows shared records to be located for deletion. Random identifiers can still distinguish records over time; they do not mean that all information is anonymous. PostHog processes network connections, and we configure it not to attach client IP addresses or GeoIP information to analytics events.
Our project uses PostHog's United States cloud. Its Free plan includes one year of event retention; this is not a guaranteed maximum or a promise to erase every copy on day 365. See PostHog's retention information. Supplier backup, log, and deletion arrangements:
After verifying your request, we use the references you provide to locate and request deletion of the associated analytics profile and events in our PostHog project. We review the result and tell you whether active records have been removed or further provider action is needed. Provider backups and security records can have a different deletion schedule; we do not treat removal from the analytics interface as confirmation that every provider copy has been erased. We do not have a confirmed maximum deletion period for all of these copies. Contact us to follow up on a request.
Turning sharing off clears unsent events from the upload queue. It does not automatically erase records already shared. Clearing local records also stops sharing. Random deletion references remain on the device, excluded from backup, so earlier shared records can still be found.
To request deletion, open Usage & performance records → Request deletion of shared records, export the random references, and email them to wrli1220@126.com. This stops sharing and rotates the remote identifier. Exporting the references does not send the email or complete remote deletion. Do not include task content or account secrets.
4. Optional crash reports
Sharing with Google Firebase Crashlytics is separately optional and off by default. When it is configured and you agree, Crashlytics processes crash stack traces, technical device and operating-system details, and random installation identifiers to help diagnose failures. Mellow does not attach task content, photos, service account identifiers, usage recordings, or custom raw errors. Firebase handles the network connection. This does not enable Google Analytics, advertising, or session replay.
Reports are submitted on a later launch while consent remains valid. Newly granted consent does not upload older reports. Turning sharing off prevents new submissions; reports already handed to the SDK for submission may still be transmitted. Local crash recording may continue until the current process ends.
Firebase states that crash traces and associated identifiers are retained for 90 days before removal from live and backup systems starts. This does not mean every copy disappears on day 90. In Crash reports, you can stop sharing and request deletion for the current recorded Firebase installation. Mellow saves the request before contacting Firebase and keeps an exportable reference on this device, outside task exports, iCloud sync and device backups. Failed requests remain pending and can be retried. A successful SDK response means the request was accepted, not that every live or backup copy has already been erased. Firebase documents a deletion window of up to 180 days for data associated with a deleted installation; see Firebase installation deletion.
Older unrecorded identifiers and other devices need separate review. Export the saved references and contact wrli1220@126.com for a follow-up. Close and reopen Mellow before separately choosing to share again. For help with a request:
If the app cannot submit a request, or you need help with an earlier installation, email the exported crash-request references to our privacy contact. We review the installation reference and request status, explain the available deletion route, and seek Firebase support when needed. We distinguish a request received by us, a request accepted by Firebase, and confirmed completion of deletion. We cannot identify an earlier, unrecorded installation from an analytics reference or an email address alone. You do not need to turn crash sharing on to request help.
5. Retention and deletion of your library
For information under our control without a fixed period below, we keep only what is needed for the stated purpose. We consider the type and sensitivity of the information, whether the service or request is still active, security and recovery needs, and applicable legal obligations. When the purpose ends, we delete or de-identify it unless a specific retention obligation applies. If necessary information must be kept for a legal obligation or unresolved dispute, we limit its use to that purpose and review the need to retain it. Provider-controlled copies follow the separate arrangements described in this policy.
| Information | How it is retained or removed |
|---|---|
| Active library | Stored until you delete it. Device and iCloud copies are separate from independently exported or saved copies. |
| Recently Deleted | Recoverable for 30 days. You can permanently delete a task or empty Recently Deleted earlier. Expiry cleanup runs when Mellow is open. A pending migration from the retired backup service is completed or retired before permanent erasure. |
| Library deletion records | Content-free record IDs and deletion times remain to prevent an offline device or old backup from republishing deleted content. Sync requires a connection. An attachment still referenced by another retained document remains until that reference is removed. |
| Previous custom companions | In version 0.2.0 and later, custom companions can no longer be selected. An active custom image, animation or model, or the retired Mellow preset, switches to Qisi and keeps its name, including after restoring an old backup or syncing an older device. Legacy history may remain in storage, iCloud documents or backups; this selection change does not confirm deletion of those copies. Version 0.1.0 keeps its earlier saved-history controls. |
| Independent copies | Exported files, clipboard contents, separately copied templates or documents, and external backups must be managed separately. Choosing a bundled companion does not delete previously saved artwork. |
Restoring an older system or exported backup may restore old local content until current cloud deletion records have synchronized. Deleting the app does not by itself delete iCloud copies, exported files, shared diagnostics, or a previous service account.
6. Support and privacy requests
Contact wrli1220@126.com to ask a privacy question or request access, correction, or deletion of information handled by our services. If you email us, we receive your email address, the message, and any attachments you choose to send. We use that information to respond and handle your request. Please send only what is needed; do not email task libraries, passwords, recovery secrets, session tokens, or private device keys.
We check this mailbox daily and provide an initial reply within three business days. An initial reply is separate from completing a request. The following explains verification, timing, retention, and your rights.
To protect your information, we verify that a request relates to the records concerned and ask only for the information needed. For shared analytics or crash reports, use the relevant references exported by the app. Do not send passwords, recovery secrets, or your full task library. For local or private iCloud content managed by you and Apple, we explain the available controls.
Our internal target is to complete a request within 30 days after receiving enough information to verify it. Applicable legal rules about when a deadline starts and how long we have take precedence. If we need more information or time, we explain why, what remains, and when you can expect another update. We distinguish live-service deletion from a supplier's remaining backup deletion window.
To ask us to review a decision, email the same address with your original request number. The operator will reconsider the reasons and records and reply with the outcome.
Depending on the law applicable to your request, you may have rights to access information, obtain a copy, correct or delete it, withdraw consent, or appeal a decision. We do not sell personal information, share it for cross-context behavioral advertising, or use it for automated decisions with legal or similarly significant effects. We do not charge a different price or deny task features because you make a privacy request. An authorized representative may contact us; we will verify the authority and the relevant records using the minimum information needed. You may also contact the privacy regulator or attorney general for your state. These options do not limit rights that apply under law.
We use email to handle support requests. Our retention schedule for support working copies under our control is:
- Ordinary support correspondence: no longer than six months after the issue is closed. We delete it sooner when it is no longer needed or a valid deletion request requires earlier action.
- Attachments, diagnostic files, and temporary working copies: no longer than 30 days after their use to handle the issue is complete, and sooner when no longer needed. If an attachment cannot be removed separately from an email, we retain only the necessary summary and delete the original email containing it.
- Minimal privacy-request records: 24 months after the request is closed. These contain a random request number, receipt and response dates, the request category and channel, the outcome, and any necessary reason for refusal. We do not retain the complete email, task content, identity documents, or installation identifiers as part of this record.
For a child's one-time inquiry, we delete contact details and the original message once the reply is complete and they are no longer needed. An ongoing parent or guardian request is limited to information necessary to handle it. A specific legal obligation or unresolved dispute may require retaining necessary information longer; we record the reason and review it. Applicable legal requirements take precedence.
We use NetEase 126 Mail to receive, store, and send support and privacy correspondence. The retention rules above cover support-related messages, sent replies, contact entries, and client or downloaded working copies under our control. Contacts needed for an independent purpose are assessed separately.
Our mailbox has a 30-day recovery window enabled after permanent deletion through webmail. Provider backups and security records may follow separate schedules; this recovery setting is not a maximum for every provider copy. NetEase also handles information needed to deliver and secure email under the terms applicable to its service. We do not have a confirmed maximum retention period for all of its internal copies. When responding to a deletion request, we explain which copies we can remove and any remaining provider retention that is known to us.
You can also manage information directly:
- Edit or delete library content in Mellow, and export it in Backup & recovery.
- Change optional analytics and crash sharing separately in Settings. Use the deletion request process for records already shared.
- Manage system permissions in Apple's Settings and iCloud information through the relevant App and Apple controls.
- Delete a previous service account in Settings → Privacy & data, as explained in the appendix.
7. Providers, processing locations, and protection
Apple provides the system features, iCloud, and App Store services described above. Other providers and their purposes are:
| Provider | Purpose |
|---|---|
| Oracle Cloud Infrastructure | Hosts the Mellow API and Redis cache. |
| Aiven | Hosts the PostgreSQL service database. |
| Cloudflare Workers and R2 | Delivers the information website, routes API requests, and stores private service images, encrypted database exports, and the account-deletion register. |
| Grafana Cloud | Receives the limited operational metrics, logs, and traces described below. |
| PostHog | Provides the separately optional usage analytics described above. |
| Google Firebase Crashlytics | Provides the separately optional crash reporting described above. |
| NetEase 126 Mail | Receives, stores, and sends support and privacy correspondence. |
Our API uses Grafana Cloud, in the US West region, for service metrics, fixed operational status messages, and sampled request traces. These contain random request identifiers, timings, route templates, response codes, and database or cache operation types. These monitoring exports exclude task content, photos, account identifiers, SQL statements or parameters, cache keys, client IP addresses, and raw error text. This service monitoring is separate from optional client analytics and crash reporting.
The current Grafana Cloud Free plan provides 14 days of retention for metrics, logs and traces, as verified in the account's Plan details on October 18, 2026. This describes telemetry retention and does not establish the erasure timing of all supplier backups or security logs. We will recheck this disclosure before changing the plan.
Production administration on Mellow's side is limited to the operator, who normally accesses the administration systems from China. Distribution through the United States App Store does not mean all information is processed in the United States. Processing, storage, backup, and provider access locations:
Our API and Redis cache are hosted in Oracle's Phoenix, Arizona region. The Aiven database uses DigitalOcean infrastructure in California, with database backups in the San Francisco region. The private Cloudflare R2 buckets for images, encrypted database exports, and the separate deletion register use the Eastern North America location setting; this setting is not a guarantee that all related processing or provider access stays there.
PostHog uses its United States cloud, and Grafana Cloud uses its US West region. Cloudflare routes requests through its global network. Firebase Crashlytics operates on Google's global infrastructure, as explained in Firebase's processing-location information. Apple services and NetEase email use their respective service infrastructure. Supplier support, security processing, and administration may occur outside the selected hosting regions. Support correspondence is accessible to the operator in China.
International processing and protection:
Information may therefore be processed outside your state or country, where privacy laws may differ. International processing does not change the purposes and choices described in this policy. We limit the information sent to providers to the service purposes described here and remain your contact for requests concerning information handled for Mellow. Providers may also process limited information for their own service security or legal obligations under their applicable terms.
Our policy is to require providers processing information on our behalf to use it for the agreed service purposes and provide protection consistent with this policy and applicable requirements. If a provider cannot meet those requirements, we will restrict or stop the affected processing. Applicable provider terms and processing roles differ by service; this policy does not assert that a separately negotiated agreement or a particular international transfer certification has been obtained. Where additional safeguards are legally required, we will put them in place before the affected transfer.
We use encrypted connections, private service storage, restricted administrative access, and encrypted database exports to protect information handled by our backend. You can contact us for information about a provider's role, relevant data-protection terms, or safeguards applicable to your request.
Operational backup, replica, and log retention, including how deletion is maintained when restoring a backup:
Encrypted database exports stored in Cloudflare R2 are scheduled to expire under a seven-day lifecycle rule. Aiven also maintains automatic database backups under the lifecycle for our database plan. Deleted records can remain in an existing backup until that backup expires; the R2 rule does not set the retention period for Aiven's backups or other supplier copies. We do not have a confirmed maximum covering every provider backup or replica.
Our host uses a 14-day journal rotation setting, while the Grafana telemetry retention described above is 14 days. Journal rotation is not a promise that each individual log entry is erased exactly 14 days after creation. Provider security and administrative audit records are separate, as described in the appendix.
Before restoring a service backup to use, we apply the separately retained account-deletion register so that deleted accounts are not reactivated. Our recovery process rejects backups older than seven days or created before the register's coverage began. The appendix explains the minimal deletion records retained for this purpose. These restoration controls do not shorten a supplier's separate retention schedule.
8. Children and families
Mellow is intended for people of all ages, including children. Parents and guardians can contact wrli1220@126.com with questions about a child's information. Please avoid sending a child's task content or identity documents in an initial inquiry.
The arrangements for children's use of optional sharing and service features, any necessary parental involvement, and requests concerning children's information are:
Before the first choice to share usage analytics or crash reports, Mellow asks a neutral age-range question on this device, with no option selected. If you do not answer or indicate that you are under 13, both kinds of optional sharing remain off; earlier sharing preferences do not override this restriction. The device saves only whether optional sharing is available, not an age range or date of birth. That decision is not uploaded and is excluded from task exports, iCloud sync and device backups. An eligible answer is not consent: each service still requires its separate sharing choice. A restricted device cannot immediately repeat the question with an older answer.
Parents or guardians can also use Privacy & data → Keep optional sharing off on this device. This stops both kinds of new sharing and keeps their switches unavailable. It does not delete records already sent; use the separate deletion controls or contact us with the relevant exported references. A mistaken choice or earlier child-data request can be reviewed through the privacy contact without sending a task library or identity documents in the first message.
All ordinary task features remain available. We do not request parental consent to enable optional third-party analytics for a child under 13; these contributions stay disabled. Apple controls iCloud, maps, Siri, system permissions and purchases under its own services and family controls. Parents can review those controls separately. New image uploads, generation and image-service signup are not offered in this release. A former account's deletion controls remain available.
If we learn that optional service data was submitted by a child under 13, we stop further nonessential use, identify the relevant records with the minimum information needed from the parent or guardian, and request deletion from the relevant provider. We distinguish provider acceptance from completed erasure. A child's direct support message is used only to address the inquiry and is not added to an analytics profile; information not needed for that response is removed. We do not use children's contact details to send marketing. This local age screen is a self-reported choice, not identity or parental-consent verification.
9. The Mellow website
Our information website is hosted by Cloudflare. Visiting it sends connection information such as your IP address, requested address and browser request headers to Cloudflare so it can deliver and secure the pages. We do not add advertising, analytics scripts, tracking cookies, account registration or file-upload forms to this website. Cloudflare may process infrastructure and security records under its own service terms; the gateway and security-record limits in the appendix also apply to the website. If you contact us by email, section 6 explains how we handle your message.
10. Changes to this policy
We will update this policy when our practices change and revise its effective date. Material changes to the previous image service's recipients or processing purposes require renewed in-app permission before affected uploads. The policy and contact details are available in Settings → Privacy & data and at https://mellow-site.mellow-app.workers.dev/privacy/.
Appendix: Previous image and backup services
What this appendix covers
Official companion artwork is bundled with the app and works offline. For a bundled character, only the selection and name need to sync. Version 0.2.0 and later use only official companions. Previous custom artwork is no longer selectable; legacy records and independent backups may still contain it. Version 0.1.0 retains its previous behavior until updated.
This version does not offer reference photo uploads or new image generation. Earlier test versions offered optional photo-based generation after separate service and photo-processing consent. Selected photos and generated frames were sent through the Mellow service to the disclosed image providers, including OpenAI for generation and quality checks. Removing the feature does not automatically erase previously submitted data.
Information and providers involved
Requests to our Cloudflare API address pass through Cloudflare Workers to our Oracle-hosted service. Cloudflare processes connection addresses, request headers, including authentication information, and the content needed to deliver requests and responses. Worker application logs and response caching are disabled. Cloudflare's global edge network and its own security or infrastructure processing remain relevant.
The previous service processes a random account ID, authentication information, a device signing public key, request IDs, entitlements, and usage records to authenticate requests, enforce limits, and prevent repeated generation. Your device's private signing key remains on the device. Gateway and security log handling:
Cloudflare processes connection information, request metadata, and security signals to route traffic and protect its infrastructure. We have disabled Worker application logs, traces, response caching, and R2 data-access logging. These settings do not disable Cloudflare's own security and infrastructure records, for which we do not have a single confirmed maximum retention period.
Administrative audit records are separate from app request logs: Oracle Cloud audit records are retained for 365 days and Cloudflare account audit records for 18 months under the current arrangements. These records concern management actions; their retention periods do not mean that task content or every app request is stored for those periods. We use the operational information available to us for troubleshooting, security, and investigating service changes. Contact us if a privacy request concerns such records, so we can assess the information involved and any security or legal retention requirement.
As of October 20, 2026, the operator has confirmed there are no historical images, and our active R2 image bucket contains no objects. This release does not call image-generation providers. This inventory does not certify erasure of every earlier supplier backup or security record. If you have a question about an earlier submission, contact us so we can identify the relevant service and request; we do not treat an empty active bucket as a supplier deletion receipt.
Retention and account deletion
| Information | Retention and deletion |
|---|---|
| Reference photos in the active database | Cleared when the generation job ends. Queued jobs expire after 24 hours; interrupted running jobs end after their lease expires. |
| Generated service images | Expire after 30 days or enter object cleanup when the job or account is deleted. Service or storage outages can delay cleanup. |
| Terminal job records | Photo and result fingerprints and obsolete object or lease identifiers are removed after 30 days. Minimal job IDs and terminal states remain while the account exists to prevent a repeated request causing another generation. |
| Service account | In-app deletion removes the active account, sessions, device association, access grants, and jobs, and queues server images for deletion. Redeemed invitations remain used without retaining the deleted account association. |
| Active database deletion receipt | A random account ID and deletion time are retained for 90 days. |
| Independent deletion register | A separate, access-controlled register holds a record version and random account ID to prevent account restoration from an old backup and reuse of the deleted ID. It contains no task content, photos, recovery secrets, or session tokens. The database's 90-day rule does not apply to this register. |
Object cleanup timing, delays, and contact arrangements:
While operating normally, a separate background cleanup service checks for due objects every ten seconds. An item is marked complete only after storage confirms that the specified object is no longer present. Failed items remain queued for a later retry. An in-flight upload lease, a service outage, or unavailable storage may delay cleanup, so this checking interval is not a promise to complete deletion within ten seconds. We monitor the cleanup service and its pending queue. If a deletion request remains pending in the app, contact the support email above. Our initial-response target is separate from completion of deletion. This describes cleanup in the active service; backups and supplier copies follow the separate retention arrangements in this policy.
Independent deletion register retention and recovery controls:
To keep a restored service backup from reactivating a deleted account, we keep a separate deletion record containing only an account UUID and a record version. These records currently have no scheduled expiry and are retained separately from service database backups. They do not contain task content, images, recovery secrets, session tokens, or IP addresses. Account identifiers remain protected personal data. The register uses private access and overwrite and deletion protection; Mellow administration is limited to the operator. During a service restoration, we apply these records before allowing account access. The verified recovery process rejects backups whose creation began before or at the deletion-register coverage boundary, and backups older than seven days. These controls do not erase copies held under a supplier's separate retention rules.
Delete a previous image service account in Settings → Privacy & data. The app saves the request before submission and retries while open and connected. It distinguishes a pending request from deletion in the active service database. Contact us if a request remains pending. Deleting this account does not delete your separate task library, saved companion artwork, or exports.
Previous installations connected to the retired backup service can separately delete that account and its server task and image copies under Privacy & data. Migrating to iCloud does not automatically delete those old server copies.
Existing users can withdraw previously granted photo permission. Withdrawal cancels pending generation and blocks new uploads; it cannot undo processing already performed. Backup and provider copies follow the separate arrangements described in this policy.