bluebell App Privacy Policy

1. Privacy overview and scope

bluebell does not collect your personal information through the app.ty settings, Agent events, workspace contents, or usage behavior to developer-owned servers, or include advertising, cross-app or cross-site tracking, or third-party analytics SDKs.

This policy covers the bluebell apps for iPhone, iPad, and Apple Watch, bluebell Mac, and its bundled bluebellctl command-line tool. It also explains data processing that may occur through Apple system services, website visits, and support emails you choose to send.

For privacy or product questions, contact bluebellkit@163.com.

Features that need cross-device sync or remote notifications use the Apple Account signed in on your device and Apple’s iCloud, CloudKit, and system notification services. We do not ask for your Apple Account password or verification codes, or read your private CloudKit database through the app’s business interfaces.

2. Activity settings and local device data

bluebell stores your training durations, repetitions, countdowns, custom haptic Flows, reminders, and appearance preferences on your device to display settings, run activities, and restore state. Local preferences such as appearance may not sync between devices.

The current version does not request HealthKit permission or read or write Apple Health records. bluebell provides haptic rhythm guidance, not medical diagnosis or treatment.

iPhone sends activity settings through its paired connection to Apple Watch. When you initiate sync on iPad, the app writes the full activity configuration to your private iCloud database for a Watch using the same Apple Account to read, without an iPhone relay. This may include Flow names you enter, Loop definitions, durations, repetitions, reminder times, notification preferences, and information used for sync versions and acknowledgments.

Cloud configuration keeps the latest published snapshot and acknowledgment state. Local editing drafts on iPhone and iPad do not merge automatically. After syncing, Watch runs activities from its local cache.

3. Agent completion events and cross-device notifications

bluebell Mac receives Agent completion events you explicitly submit through bluebellctl. It stores the source name, project display name, summary, time, and information needed for integration, deduplication, delivery, and retries locally. Workspace paths, session IDs, or turn IDs supplied in commands are used locally and are not uploaded as their corresponding remote-event fields.

Remote delivery on Mac is enabled by default. When an event permits remote delivery, the switch is on, and iCloud is available, the app writes the event ID, source name, completion type, project display name, summary or notification body, time, randomly generated source-device ID, and data-format version to your private iCloud database. These records support cross-device retrieval and system notifications. The random device ID identifies the event’s origin; it is not an advertising identifier and does not make the other record contents necessarily anonymous.

You can turn remote delivery off on Mac, or use --local for an individual bluebellctl event to keep processing local. Mac local notifications have a separate control.

bluebell does not automatically upload full workspace paths, raw Agent requests, session or turn IDs, deduplication keys, complete conversations, prompts, or source code. However, source names, project names, summaries, or test notification text you enter may contain that material or other personal information. The app does not guarantee that it will detect or remove sensitive content automatically. Submit only what the reminder needs.

Notifications may display your submitted text in Notification Center or on a device’s Lock Screen. Use each device’s system notification settings to control permission and previews. Connectivity, device state, permissions, Focus, and Apple’s routing may affect presentation. Acceptance of an event or a successful iCloud write does not mean a notification has been delivered.

4. Developer access and third-party services

The activity settings and Agent events described above are not uploaded to developer-owned application servers. Private CloudKit records are used between devices through your Apple Account. The developer does not read or manage your private records through the app’s business interfaces.

Apple’s privacy policies and terms govern its iCloud, CloudKit, and system notification services. You can read the Apple Privacy Policy. bluebell does not promise that Apple services process data only in a particular region, and does not describe your private CloudKit database as a developer-operated server.

The current apps have no advertising, cross-app or cross-site tracking, or third-party analytics SDKs. We do not use advertising identifiers. These statements do not mean that no data passes between devices, and do not replace Apple’s explanation of its system services.

5. Retention, deletion, and your choices

Mac keeps up to 200 recent events in local history. Choosing to show 20, 50, 100, or all changes only the display count, not that storage limit. The limit also does not define the retention period of every local queue or cloud event.

Clearing recent notifications on Mac deletes only the local history list. It does not delete pending candidates, the delivery queue, deduplication information, or existing cloud records, and does not withdraw notifications already delivered to other devices.

Turning off Mac remote delivery clears the local outgoing queue. Events received while it is off remain local and are not replayed when it is turned on again. Requests already submitted to CloudKit may still finish, so the switch cannot withdraw submitted requests or delivered notifications. Disabling system notification permission alone does not disable cloud transmission.

The current version has no automatic expiry cleanup or in-app, per-record deletion for Agent cloud events. Uninstalling the app, deleting device files, or clearing local history does not delete existing iCloud records.

You can review the iCloud storage-management options in Apple’s system settings; available options vary by device, OS version, and Apple service. For data-management questions, contact the support address above or Apple Support. The developer cannot sign in to your Apple Account for you or directly delete your private cloud records.

6. Support email

When you choose to email a support or privacy question, we receive your sender address, message, and any attachments you provide, to respond and troubleshoot. This is separate from automatic app uploads.

Do not send passwords, verification codes, banking details, complete Agent conversations, or unrelated sensitive information. Obscure private content in screenshots and error messages first.

We retain emails only as needed to handle your request and necessary follow-up, then delete them unless retention is required by law. Contact bluebellkit@163.com to request access to, correction of, or deletion of your personal information in support emails. Such requests do not authorize or enable the developer to manage your private iCloud records on your behalf.

The support address uses NetEase Mail. Email transmission and storage are also subject to that service’s terms and privacy rules. The app-related statements in this policy do not promise that website hosting produces no access logs.

7. Website visits

bluebellkit.com and bluebellkit.cn use Tencent Cloud EdgeOne Makers (formerly Pages) for hosting and delivery. When you visit, hosting and security services may process your IP address, visit time, requested path, browser or device User-Agent, and network and security events to deliver pages, maintain security and stability, compile aggregate traffic statistics, and troubleshoot. The website operator can view aggregate metrics and access logs as supported by EdgeOne. Actual processing and retention follow Tencent Cloud’s service rules and privacy policy. We do not promise a fixed retention period, processing only in a particular region, or complete anonymity.

This website has no advertising, cross-site tracking, or third-party analytics scripts, and does not load third-party remote fonts, images, or videos. Styles, font fallbacks, and images are provided with the site itself. External reference links contact the relevant third party only when you choose to follow them. Website access logs are separate from app-local data and your private iCloud records.

8. Policy updates

We will publish policy updates here and revise the date. If the apps’ data processing changes materially, we will explain the change in release notes or in the app and update the App Store privacy information accordingly.