Exa Privacy Policy

The short version

The updated free beta is Exa beta.10 (version code 100009). It needs no subscription, has no Internet permission, and does not include Google Play Billing, Play Integrity, or Exa's access-verification service. It works offline. The productivity records you create stay in Exa's app-private storage on your device unless you deliberately export or share a copy.

Earlier free versions include beta.9 (100008) and beta.3 (100002), which also work offline without a subscription or Internet permission. The free-version storage, export, deletion, and support-sharing information on this page applies to all three free betas; available features and bundled guidance may differ.

Exa has no separate account or login, no ads, no analytics, and no third-party advertising trackers. Opening a website, emailing support, or choosing a document provider happens through other apps and can send information outside your device.

This policy also explains versions with paid access, including beta.8 (version code 100007), in the separate section below. Those subscription disclosures do not describe the free beta's app data flow.

Who provides Exa

Exa is provided by Advancing Quality Lives LLC. The permanent public Android application ID is org.advancingqualitylives.exa.

Exa is a general productivity and external-memory tool. It is not a medical device and does not diagnose, treat, cure, or prevent any medical condition. It is not a medical or emergency service; consult a qualified healthcare professional for health decisions.

You choose what to enter. Your notes may include health information or other sensitive personal information. The local storage, export, deletion, and voluntary support-sharing boundaries in this policy apply to that content too.

Information Exa handles on your device

Depending on the features you use, local Exa records can include:

atoms and nested steps, lists and checklists, modes, organization choices, and completion history;
manually entered Civi people and relationship-support notes;
manual Anchors, Cycle queues and timers, alarms and reminders;
Bridges between Exa records and Inbox captures;
Freedom Zone and My Clearing activities; and
Quiet state, preferences, onboarding choices, schedule and occurrence identifiers, one bounded recovery record, and version metadata needed to operate the app.

These records are stored in app-private storage on the device. Android backup is disabled in the versions covered here. Exa does not automatically upload these records or operate a server-side copy of them. If you voluntarily send a record or export to support, it becomes part of that correspondence, as described under Contact.

The public app does not automatically read another Exa installation or pull records from other apps, accounts, contacts, calendars, calls, messages, notifications, or computers. Import occurs only when you select an Exa backup file.

The free beta: collection, sharing, and tracking

App data: free beta.10 does not automatically send your records, usage analytics, or subscription-verification information to Advancing Quality Lives LLC. It has no network service or remote diagnostics.
Ads and analytics: there are no ads, advertising SDKs, analytics SDKs, or third-party trackers in the app.
Accounts: there is no separate Exa account, password, or login. Google Play and Android operate under their own policies when you download or update an app.
Your choices: an export goes to the destination you select. A website visit or email uses your browser or email app. These separate flows are explained below.

Only for versions with Google Play subscription access

This section applies if you use a version with Exa's subscription controls, such as beta.8 (100007). It does not mean a subscription is required for free beta.10 (100009).

Access verification: paid versions send limited purchase and app-verification data to the access-verification service. This can include the Google Play purchase token and product identifier, subscription status and timing, an installation public key or identifier, signed request and anti-replay information, app version and package identity, and Play Integrity verification material. Exa does not send the productivity records you create through that access-verification flow.
Service providers: Google Play processes the subscription purchase and Play Integrity check. Advancing Quality Lives LLC's contracted hosting provider processes the access-verification request. These transfers provide, secure, restore, and support subscription access, not advertising. Google Play associates the purchase with the Google Play account used for the transaction.
Network access: paid versions include Internet access for Google Play Billing, Play Integrity, and subscription-access verification. This is separate from the free beta's offline behavior.
Payment: any available offer, eligibility, price, and renewal terms are shown by Google Play before you confirm a purchase. Use Google Play to manage or cancel a subscription; deleting app data or uninstalling does not cancel it.

Visiting this website

These pages are static and do not set cookies, run scripts, submit forms, or load tracking resources. Your browser connects to the hosting provider to retrieve them. The provider processes connection and request information, such as your IP address and the requested page, to deliver and protect the site. This website traffic is separate from Exa's offline app records.

Your export, import, and deletion controls

Export: Export happens only when you choose it. Exa asks Android's document interface to save a portable copy to a location or document provider you select. The exported file contains your Exa records and becomes a user-managed copy. A provider you choose may store or sync that copy under its own terms; Exa does not send it to Advancing Quality Lives LLC or a developer-selected service.
Import: Import happens only when you select an Exa file through Android's document interface. Exa validates and previews the file. If you confirm, the import replaces the current Exa record set; it is not a background sync or an automatic merge.
Recovery copy: If Exa finds unreadable local state, it preserves that state instead of silently replacing it and can let you save a troubleshooting copy. That copy is user-managed like an ordinary export and can contain the Exa information stored on your device.
Delete All: The in-app Delete All flow cancels Exa alarms and timers, erases Exa's app-private productivity records, and returns the app to first-run setup. In a paid version it also removes the locally cached access lease. It does not delete voluntary support correspondence or cancel a subscription. Any transaction or access-verification records held by Google Play or the paid access service are separate from the app's local records.
Uninstall: Uninstalling Exa removes its app-private records under Android's normal app-removal behavior.
Exported copies: Delete All and uninstall do not delete files you previously exported. Those copies remain wherever you chose to save them until you delete them through that location or document provider.

Android permissions and why they are used

Free beta.10 (100009), beta.9 (100008), and beta.3 (100002) declare the following seven alarm and reminder permissions. These support alarms and reminders that you choose to create; they are not used for marketing or advertising tracking.

android.permission.POST_NOTIFICATIONS: Shows user-created alarm and reminder notifications on supported Android versions.
android.permission.RECEIVE_BOOT_COMPLETED: Restores user-created alarm scheduling after a reboot and responds to relevant package, date, clock, and time-zone changes.
android.permission.SCHEDULE_EXACT_ALARM: Allows a user to schedule a precisely timed alarm. Android treats this as revocable special access.
android.permission.FOREGROUND_SERVICE: Runs the visible alarm-ringing service when a scheduled alarm fires.
android.permission.FOREGROUND_SERVICE_SYSTEM_EXEMPTED: Supports the exact-alarm-triggered foreground alarm experience on applicable Android versions.
android.permission.VIBRATE: Provides haptic output for a user-requested alarm.
android.permission.WAKE_LOCK: Keeps alarm execution awake long enough to present and control an active alarm.

Paid versions only: beta.8 (100007) additionally declares android.permission.INTERNET for Google Play Billing, Play Integrity, and Exa's subscription-access verification service. Google Play libraries also contribute billing and network-support manifest entries. Free beta.10 includes none of those libraries or network permissions.

Notification access and exact-alarm access are requested only when a user chooses to set up an alarm. A user can deny or later revoke these permissions in Android settings, although the related alarm behavior may then be unavailable.

The versions covered here request no location, camera, microphone, Bluetooth, advertising-ID, package-inventory, or broad-storage permission.

Keeping local information safe

Your device's lock, Android's app isolation, and your handling of exported files are important protections. Exported files can contain the Exa information you entered, so store and share them with the same care you would use for other personal notes.

How long information remains

Exa keeps its local productivity records on your device until you change or delete them, use Delete All, clear Exa's app storage through Android, or uninstall the app. Advancing Quality Lives LLC does not retain an automatic server copy of those records. Information you voluntarily send to support is handled as correspondence, separately from the app.

For paid versions, limited subscription and access-verification records may be retained to provide or restore access, prevent abuse, handle support or disputes, keep necessary transaction evidence, and meet legal obligations. Google Play separately retains purchase information under Google's policies. This does not apply to subscription data collection by free beta.10, which has no such flow.

Files you export are separate user-managed copies. They remain at the location you selected until you delete them there.

Audience

Exa is intended for people aged 9 and over. Children aged 9–12 should use it with a parent or caregiver, who can help them learn the controls, set up reminders, choose where backups are saved, and contact support. Exa does not provide a social feed, public user-to-user exchange, or supplied mature content.

Changes to this policy

This is a living policy. Advancing Quality Lives LLC will review it when Exa's behavior, permissions, included services, support practices, or data flows change. Material changes will be reflected in the policy text and its effective date, and the Google Play Data safety declaration will be updated when required.

Effective date: September 9, 2026.

Contact

For privacy questions about Exa, email privacy@advancingqualitylives.org. Replies may come from Exa App Support.

Emailing Advancing Quality Lives LLC is optional and happens outside Exa's on-device app data flow. The company and its email provider receive the sender address, message, and any attachments you voluntarily send so the company can review and respond to the request.

For children aged 9–12, we recommend that a parent or caregiver contact us and help choose what information to share.

Do not attach an Exa export, screenshot, record title, or record content unless you deliberately choose to share it and it is reasonably necessary for the question. Exa exports can contain the productivity information you entered.

Advancing Quality Lives LLC may retain support or privacy correspondence for as long as reasonably needed to respond, document the resolution, protect the service or legal rights, and meet applicable obligations.