1. Scope and controller
This Privacy Policy applies to the Aimsly application and its associated services (“Aimsly”). Aaron Appleman is the operator of Aimsly and the controller of personal information processed through its services. Privacy enquiries and requests may be directed to support@appleman.app.
2. Information processed
Aimsly processes the following categories of information according to the features used and permissions granted:
- User content: goals, plans, progress records, reflections, saved answers and conversations.
- Purchase and service information: transaction records, subscription status, service-account identifiers and age-eligibility status.
- Notification information: device registration details, notification preferences and delivery tokens.
- Usage analytics and diagnostics: usage and purchase-flow events, goal types and configured settings, technical AI-operation metadata, crash reports, performance measurements, recent app actions, app and device information, installation identifiers and network metadata, including approximate location derived from an IP address.
- Support information: messages, contact details and other information voluntarily submitted to support.
Goals and related records may include health-related or other sensitive information entered by the user. Such content is not used for advertising. Configured goal settings are included in usage reporting as described in Section 6.
3. Local storage and iCloud
Goals, progress, reflections, saved answers, conversations and drafts are stored on the user’s device. Local storage or iCloud synchronization alone does not submit content to online coaching. Online processing follows the sharing permissions described in Section 5. If iCloud sync is enabled, the selected information is synchronized through the user’s private iCloud database. Conversation sync is controlled separately. Active timers and unfinished drafts remain local.
A limited record of free goal creations is stored in private iCloud storage even when progress sync is disabled. This record administers the free allowance across devices and reinstallation; it does not contain goal titles, notes or coaching content.
Disabling sync stops further synchronization but does not delete existing copies. iCloud records, offline-device copies, recovery files and exported backups must be managed separately.
4. Purposes of processing
Information is processed to provide the Application and requested services; administer purchase and service entitlements; provide coaching and notifications; respond to enquiries; assess usage and purchase flows; diagnose failures and improve reliability; maintain security; prevent fraud and misuse; and discharge applicable legal obligations.
Optional coaching follows the permissions described in Section 5. Usage analytics and technical diagnostics are governed by Section 6.
5. AI coaching and third-party processing
Online coaching requires express permission to share information with Aimsly’s service, hosted on Google Firebase, and Google’s Gemini API. Shared information may include submitted messages, recent conversation, relevant active goals, progress summaries, coaching preferences, saved answers available for coaching, and notes or learning selected by the user. Private reflection notes and raw activity entries are not uploaded automatically.
Where proactive coaching is enabled under the applicable sharing permission, a limited copy of the authorized context is processed to prepare suggestions between visits. Conversation content is included only as permitted by the applicable sharing choices. Notification permission is separate from permission for AI processing.
AI-sharing permission may be withdrawn in Settings → Data & privacy → Sharing with Aimsly. Withdrawal stops further authorized sharing from that device; it does not recall requests already transmitted. Disabling proactive coaching requests removal of its stored context and messages. An incomplete removal remains pending for retry.
Apple provides iCloud, purchase processing, age-range sharing and platform notification services. Google provides Firebase services and Gemini processing. PostHog provides analytics and technical AI monitoring as described in Section 6. Information is disclosed to these providers as necessary for the purposes stated in this Policy. Processing by service providers is subject to the applicable contractual arrangements and provider terms. This Policy does not expand permissions or rights granted under those arrangements.
Google’s processing and retention of AI inputs and responses are governed by the applicable Gemini API terms. Provider records may be retained for service operation, security, abuse prevention and legal requirements. Deletion of a local record does not establish deletion of provider-held copies.
Aimsly does not sell personal information, use private goal content for targeted advertising, or track users across other companies’ applications and websites. Information may be disclosed where required by law or necessary to address fraud, security threats or the protection of legal rights.
6. Analytics and diagnostics
Usage analytics and crash/performance reporting are enabled by default in versions of the Application implementing automatic reporting. These versions do not provide in-application reporting settings or opt-in/opt-out controls. Previously recorded refusals remain effective. Other versions retain their existing permission requirements; publication of this Policy does not alter collection by an installed version.
Depending on the installed version, Aimsly uses PostHog or Google Analytics for Firebase to understand app usage, goal configuration (including exact configured values), coaching engagement and purchases/subscriptions. Usage reports exclude goal names, logged progress amounts, notes, answers and chat content. PostHog also processes technical AI performance data to improve reliability; these records exclude prompts, responses and app-user identifiers.
Firebase Crashlytics and Performance Monitoring process crash and exception information, fixed error categories, performance measurements, limited app-action history, app/device information, installation/session identifiers and network metadata. The custom diagnostic fields exclude private user content, progress amounts, receipts and account identifiers; native crash reports may include exception messages. The reporting does not capture screenshots, screen recordings or keystrokes. Analytics events may be included in crash reports where both reporting functions are active.
Where the installed version provides withdrawal controls, withdrawal stops new app submissions and clears the relevant local queues or diagnostic history. Service providers may finish processing reports already submitted; information already transmitted cannot be recalled by changing a local permission or clearing a support report. Privacy requests may be submitted under Section 9.
7. Age requirements
Aimsly’s minimum age is 9. Users aged 9–17 may use the core application but may not access Aimsly+, including AI and proactive coaching. Aimsly+ is restricted to users aged 18 or older.
With permission, Aimsly uses an age range supplied by Apple to determine adult eligibility. The eligibility result is retained locally and associated with the online service account where applicable. Aimsly does not receive a date of birth or collect identity documents through this process. Purchase ownership does not establish age eligibility or consent to AI sharing.
A parent or guardian must provide any consent required by applicable law for a minor’s personal-information sharing. Suspected collection without required parental consent should be reported to the contact address in Section 1 so that it can be investigated and appropriate deletion arranged.
8. Retention and deletion
Local content is retained until removed through the applicable app or device controls. Online service records are retained for their operational purpose and subject to the following expiry targets:
- Temporary coaching requests, rate-limit records and pending notification records: one day.
- Reported suggestions and proactive processing records: 30 days.
- Proactive context: 30 days; context older than seven days is not used for new reviews.
- Purchase-linked usage, accounting and purchase-notification records: 62 days.
- Proactive messages and device registrations: 90 days.
Deletion after expiry is asynchronous. Purchase-ownership and service-access bindings have no configured automatic expiry and are retained separately, including after deletion of online coaching data. Support correspondence has no fixed automatic expiry and is retained as necessary to resolve the enquiry and meet associated recordkeeping obligations. Operational logs are configured for 30 days; certain administrative audit logs for 400 days.
The general local usage-event queue and operation/performance history use a 14-day retention window. Recent diagnostic action history is limited to the current app session and the last 15 minutes. Local purchase-flow, subscriber-setup and recovery records remain separately until the relevant app data are removed. PostHog events are currently retained for 12 months; separate local analytics references expire within 365 days without use. For versions using Google Analytics for Firebase, the current settings retain event-level data for two months and user-level data for 14 months; the user-level period may restart following new activity. These settings do not govern most aggregate standard reports. Firebase retains crash reports and associated identifiers for 90 days before deletion begins. Performance Monitoring retains IP-associated events for 30 days and installation-associated or de-identified performance data for 60 days before deletion begins. Other provider-held information follows the applicable provider retention arrangements. See Firebase’s privacy information.
“Delete online coaching data” in the Aimsly+ management controls removes the service account and associated online coaching, notification and request records after ownership verification. Purchase-ownership and service-access bindings remain as described above; other purchase, accounting and security records remain subject to their separate retention purposes. Deletion does not cancel an Apple subscription or remove local content, iCloud records, exports, backups or all provider-held copies. Deletion requests may also be submitted by email.
9. Privacy rights and withdrawal
Depending on applicable law, individuals may request access, correction, portability or deletion of personal information; restrict or object to processing; withdraw consent; appeal a decision; or lodge a complaint with a competent privacy authority.
Requests should be sent to support@appleman.app. Verification proportionate to the request may be required. Requests are subject to applicable law, including any conditions, exceptions and response periods. For information held only on a user’s device or in private iCloud storage, the relevant app, device or Apple controls may be necessary.
iCloud sync, conversation sync, AI sharing, proactive coaching and notifications retain their separate permission controls. Usage and diagnostic reporting follow Section 6. Withdrawal of one permission does not automatically withdraw the others or erase previously processed information.
10. International processing and security
Service providers may process information in the United States and other countries in which they operate. Information about applicable transfer arrangements and safeguards may be requested using the contact details above. Technical and organizational safeguards are used to protect information. No method of storage or transmission affords absolute security.
11. Changes and related policies
Changes to this Policy will be published on this page with an updated date. Publication of an amendment does not constitute consent where consent is required by applicable law. Website support submissions are also governed by the website privacy policy. Use of Aimsly is subject to its Terms of Use.