Privacy Policy

Contents

1. Scope and Account Information
2. Information We Process
3. Alarms, Routines, and Statistics
4. Camera and Motion Tasks
5. Personal Videos and Media
6. Screen Time and App Blocking
7. How We Use Information
8. Analytics, Attribution, and Tracking
9. Purchases and Subscriptions
10. Service Providers and Data Sharing
11. Data Retention
12. Data Security
13. Your Choices and Data Deletion
14. Your Privacy Rights
15. Children's Privacy
16. International Processing
17. Changes to This Privacy Policy

1. Scope and Account Information

RouseWell does not require you to create a personal profile or sign in to a RouseWell account to use its routine features. It nevertheless creates a random service identifier, and uses installation and transaction identifiers to operate connected features.

These identifiers can link activity and purchase records over time. They are pseudonymous identifiers, not a guarantee of anonymity. The identifiers is generated randomly rather than derived from your identity or device characteristics. A separate purchase token associates an Apple transaction with the relevant service record.

This Policy covers the application and its related services. Independently operated Apple and other third-party services also have their own privacy notices.

2. Information We Process

Information you provide or create

• Alarm and reminder settings, routine times, repeat days, labels, and task preferences.
• Custom typing text, theme selections, and videos you choose to import.
• Blocking schedules, selected restrictions, break choices, and related settings.
• Messages and attachments you voluntarily submit for assistance.

Routine content and media are handled locally as explained below. If you voluntarily send a support message, we receive its content, sender information, and any included diagnostics. A prepared support draft can include the identifiers, device identifiers, tracking-permission status, device model, operating system, and application version. The advertising identifier is included only when authorized. You can review or remove these details before sending; preparing a draft does not send it automatically.

Technical and service information

Connected services and integrated SDKs process information such as:

• Device model, operating system, application version, language, region, and time zone.
• IP address and technical request information generated when connecting to a service; an IP address may indicate a general region.
• installation identifiers, Apple's identifier for vendor (IDFV), and provider-specific identifiers from AppsFlyer, Firebase, and Meta.
• Apple's advertising identifier (IDFA), only when tracking is authorized and a valid identifier is available.
• Application openings, onboarding completion, purchase-screen views, checkout activity, event times, and relevant error or status information.
• Advertising source, campaign, click, or referral parameters received through attribution services or supported links.
• Purchase and entitlement information described in Section 9.

RouseWell does not request GPS location, access to your address book, microphone recording, or HealthKit records for its current features. Technical identifiers and approximate regions inferred by network services are distinct from precise device-location access.

3. Alarms, Routines, and Statistics

Alarm definitions, reminder labels, custom task text, routine schedules, and execution history are stored on your device. The application shares the settings needed to schedule alarms and restrictions with the relevant Apple system services and its own on-device extensions.

Statistics are calculated from recorded application events, including task completion, confirmed snoozes, blocking-session endings, and breaks. They do not establish how long you slept, whether you were awake, or whether you took medication.

We do not upload your full routine schedule, medication-related notes, custom task text, or detailed routine history to advertising or analytics providers. General application and purchase events are handled separately, as described in Section 8. RouseWell does not provide its own cloud synchronization of your local routine history.

4. Camera and Motion Tasks

Camera

Camera access is requested when you begin a task that needs it. Live images are analyzed on your device using Apple's vision technologies to detect the selected object, person, face, or body-part target.

Task frames are processed in memory. RouseWell does not save them as a photo or video recording, upload them to a remote recognition service, or send them to advertising providers. Detecting a face or body part is used only to evaluate the selected task; RouseWell does not create a face-identity profile or use these tasks for biometric identification.

Motion

Walking, shaking, and squat-related tasks use supported motion and step-counting information while the task is active. Processing takes place on your device. Raw sensor streams are not uploaded to our services or advertising and analytics providers, and are not stored as a historical sensor recording.

Task progress and completion records may be retained locally without keeping the underlying camera frames or raw motion stream. You can change camera or motion access in your device settings; the affected tasks may then be unavailable.

5. Personal Videos and Media

When you choose a personal video through Apple's media picker, RouseWell receives the selected item rather than general access to your entire photo library. An item stored in iCloud may need to be downloaded through Apple's services before import.

RouseWell prepares an on-device copy for playback and may create a converted video, an audio resource, and a cover image. These copies are stored locally for your selected theme. They are not uploaded to our servers or supplied to advertising or analytics providers.

Removing an original item from Photos does not necessarily remove an already imported copy. Device backups may also contain local application data, depending on your Apple and device settings. Such backups are separate from a RouseWell cloud-sync service.

6. Screen Time and App Blocking

With Screen Time authorization, RouseWell uses Apple's Family Controls, Managed Settings, and Device Activity technologies to apply your restrictions and scheduled breaks.

Selections made through the system picker are represented by privacy-preserving tokens for applications, categories, and websites. Relevant tokens, schedules, and session state are stored in an on-device shared container accessible to RouseWell and its Screen Time extensions. They are used to apply and restore restrictions, including where overlapping plans remain active.

RouseWell does not upload these selection tokens to its servers or advertising and analytics providers, enumerate your full installed-app list for advertising, or collect the content you view inside another application. A blocking selection is not a browsing-history report.

Revoking Screen Time authorization can prevent restrictions and associated protections from functioning. Previously recorded local events are not automatically erased when a permission is withdrawn.

7. How We Use Information

We use the relevant information to:

• Save and operate your alarms, reminders, tasks, themes, blocks, and breaks.
• Show summaries of recorded activity on your device.
• Load available purchase options, prepare orders, verify transactions, restore access, and reconcile entitlements.
• Maintain service continuity and retry incomplete service requests.
• Understand application use and measure the effectiveness of advertising and referral campaigns.
• Diagnose service errors, prevent misuse and purchase fraud, and maintain security.
• Respond to messages you choose to submit.
• Meet applicable legal obligations and resolve disputes.

Where applicable law requires a legal basis, processing may be necessary to provide requested services, meet a legal obligation, pursue legitimate interests permitted by that law, or act on your consent. Consent is obtained separately where required and can be withdrawn without affecting the lawfulness of earlier processing.

8. Analytics, Attribution, and Tracking

RouseWell integrates AppsFlyer for installation, session, and campaign attribution; Firebase Analytics and Firebase Installations for application analytics and installation identifiers; and Meta App Events for application and purchase-event measurement. Our own service also receives installation, attribution, and selected application and checkout events.

Information sent through these systems can include the identifiers and technical information listed in Section 2, application openings, onboarding completion, purchase-screen views, product identifiers, checkout prices and currencies, and campaign information. Meta's SDK can automatically collect supported application and in-app-purchase events. Checkout information records a purchase attempt or offer and does not by itself establish a completed payment.

Your tracking choice

Apple's App Tracking Transparency permission controls tracking that requires that permission. RouseWell reads IDFA only when authorized, and its advertising-ID collection and Firebase advertising-consent settings reflect the system choice.

Declining tracking does not disable all network requests, SDK initialization, analytics, or attribution processing. Service and SDK identifiers, IDFV, basic application events, and attribution updates may continue to be processed. The application currently has no separate in-app switch to turn off all analytics or attribution.

Those identifiers must not be used to bypass a tracking refusal. Linking information across other companies' applications or websites for tracking remains subject to Apple's requirements and any additional consent required by law. Allowing tracking is not a condition of using free routines or purchased features.

You can change the system choice in Settings → Privacy & Security → Tracking. Withdrawing permission stops future authorized IDFA collection and removes IDFA from pending application reports. It does not automatically delete previously transmitted data or all other identifiers and events.

Camera frames, raw motion data, personal videos, medication-related notes, custom task text, complete routine schedules, and Screen Time selection tokens are not included in our advertising or analytics event payloads.

9. Purchases and Subscriptions

Apple processes in-app payments. RouseWell does not receive your full payment-card number or your Apple Account password.

RouseWell and its purchase services process product identifiers, order references, transaction and original-transaction identifiers, a purchase-association token, signed Apple transaction information, purchase and expiration dates, verification results, and entitlement, renewal, refund, or revocation status as available.

Signed transaction information is sent to our purchase-verification service to validate and reconcile access. It is not sent as a raw purchase-verification payload to AppsFlyer, Firebase, or Meta. Separate purchase-related measurement, including supported automatic SDK events, is described in Section 8.

Purchase records and requests awaiting confirmation may be retained locally and retried when a connection becomes available. Deleting local routine data does not cancel a subscription, erase Apple's records, or necessarily remove records needed to restore or reconcile a purchase.

10. Service Providers and Data Sharing

Relevant information is disclosed to the services needed for the purposes described above, including:

• Apple: system capabilities, media selection, App Store purchases, and transaction services.
• AppsFlyer: installation, session, referral, and campaign attribution.
• Google Firebase: application analytics and installation services.
• Meta: application-event and supported purchase-event measurement.
• Infrastructure and operational providers: hosting, service delivery, security, and handling messages you submit.

The information involved depends on each provider's function, configuration, and applicable permissions. Providers' own notices include the Apple Privacy Policy, AppsFlyer Services Privacy Policy, Firebase privacy information, and Meta Privacy Policy.

We may also disclose information when legally required, to protect against fraud or security threats, in connection with a lawful business transfer subject to applicable protections, or at your direction.

Depending on the jurisdiction and actual use by a recipient, advertising-related disclosure can be considered a “sale,” “sharing,” or processing for targeted advertising even without a monetary payment. The absence of a direct data sale does not mean that these rules cannot apply. Relevant rights are described in Section 14; the system tracking choice is not a universal substitute for all statutory privacy choices.

11. Data Retention

Retention depends on the information and its purpose:

• Live task input: camera frames and raw motion samples are used transiently for the active task rather than retained as recordings.
• Local routines and media: definitions, recorded events, imported copies, and settings remain in the relevant on-device storage until removed. Deleting a plan does not necessarily delete its historical events or previously imported media.
• Service identity and purchases: identifiers, entitlement records, transaction history, and pending requests can persist to support restoration, transaction reconciliation, and reliable retries. A Keychain identifier may survive app removal; persistence is not guaranteed.
• Attribution and analytics: local attribution information is not automatically cleared merely because tracking is declined. Data already sent to providers is subject to the applicable service configuration and retention practices.
• Operational and legal records: necessary records may be retained for security, accounting, legal obligations, and dispute resolution.

There is no single automatic deletion period covering every category. Records should be retained only while needed for the stated purpose or a lawful retention requirement. Removing the application is not a request to delete every server-side or third-party record, and backup copies may remain under the applicable backup settings and retention rules.

12. Data Security

RouseWell uses platform security features, including application sandboxing, restricted on-device shared storage, Keychain storage for its service identifier, and HTTPS for its service requests. These measures help protect information during local storage and transmission.

No device, storage system, or network transmission is completely secure. Protect access to your device and Apple Account, and review information before including it in a support message or attachment.

13. Your Choices and Data Deletion

You can edit or remove individual alarms and blocking plans using the controls provided in the application. Review any active session separately, because changing a future schedule may not end a session already in progress. Historical records and imported media can remain after a plan is deleted.

System settings let you change alarm, Screen Time, camera, motion, and tracking permissions. A permission change affects the corresponding future access or processing; it does not automatically erase data previously stored or transmitted.

Deleting the application generally removes its local application container. Offloading it can preserve documents and data. Keychain entries, shared storage, backups, Apple transaction records, and records held by service providers may persist separately. Removing the app is therefore not a complete service-data deletion mechanism.

The current application does not provide a self-service account-deletion or complete server-data-erasure control. Local deletion actions do not represent such a request and do not cancel an Apple subscription. Statutory data rights, where applicable, remain available regardless of this product limitation.

14. Your Privacy Rights

Depending on your location and the law that applies, you may have rights to access or obtain a copy of personal information, correct inaccuracies, request deletion, restrict or object to certain processing, or withdraw consent. Some jurisdictions also provide rights to opt out of a sale or sharing of personal information or targeted advertising, appeal a rights decision, and complain to a privacy regulator.

These rights can be subject to verification and lawful exceptions, including records needed for a legal obligation or to establish or defend a claim. You will not be unlawfully discriminated against for exercising applicable rights. Withdrawing a permission may nevertheless make a feature that needs that permission unavailable.

An operating-system tracking setting and the local deletion controls described above have limited purposes. They do not, by themselves, exercise every right concerning information already held by our services or another provider.

15. Children's Privacy

RouseWell is intended for adults aged 18 and older and is not directed to children. We do not knowingly collect children's personal information in violation of applicable law. If such collection is identified, appropriate steps will be taken to remove the information unless lawful retention is required.

16. International Processing

Connected services and service providers may process information in countries other than the one where you live, and those countries may have different privacy laws. Local-only task processing does not itself send your camera frames, raw movement samples, or personal videos abroad.

Any cross-border transfer must comply with applicable requirements, including legally required safeguards or another valid transfer mechanism. A provider's participation in a transfer framework does not mean that every RouseWell data flow is covered by that framework.

17. Changes to This Privacy Policy

We may revise this Policy when application features, providers, data practices, or legal requirements change. The revised version will show an updated date, and material changes will be communicated where required by law.

If a new use of information requires consent, that consent will be requested before the relevant processing. Continued use of the application alone does not replace consent or a system permission that must be obtained separately.