Adelante

Adelante privacy notice

Updated 1 October 2026. Adelante is operated by Yousof Selim. Contact: ygshuh@gmail.com. This notice covers Adelante, its native widgets and the Apple Watch companion where available.

Personal choices

Adelante requires no account. Interests, faith preferences, tone, hidden topics, saved-quote and hidden-quote IDs, reading history, appearance, and widget designs are stored on the device. Content-update requests do not include those choices. Native widgets read a local shared snapshot. On supported Apple Watch versions, a bounded selection of eligible quotes, their meanings and sources, and your haptic and motion settings transfers to the paired Watch through Apple WatchConnectivity. The selection can reflect your interests and faith choices. Reading history on Watch stays on Watch. This transfer is between your devices; Adelante does not upload your preferences to provide it. Quotes already copied to an offline Watch are updated when the devices next sync. The app does not include advertising or third-party analytics SDKs.

Settings → Data & privacy can export a JSON backup, restore a backup, or clear personal data. A backup includes preferences, including faith choices, saved-quote IDs, hidden-quote IDs, and designs. The user decides where exported files or copied JSON go. Protect a backup like any other personal file. A restored backup replaces the device's personal choices. Downloaded content and withdrawals are retained when personal data is cleared, so removed content does not reappear.

Restarting the introduction keeps personal data. Resetting recommendation history only clears that history. Android automatic cloud backup and device-transfer backup of Adelante app data are disabled through explicit backup exclusions. Use the manual export to move personal choices. On Apple devices, device/OS backup and restore behavior is controlled by the operating system. Adelante does not provide account-based cloud sync.

Optional content service

A build with a configured endpoint checks for approved library updates. It sends the content version and, when configured, a Firebase App Check token. When a quote is opened, the app also asks the service for that one quote by its ID, so a correction to its words, meaning or source appears without waiting for the next library check. A quote ID can indicate the quote's subject, including religious content. The request carries no preferences, saved IDs or account. At most one such request is made per quote every five minutes. The service and its infrastructure receive ordinary connection information, including the IP address. Firebase App Check uses platform app/device attestation to protect the service. This is separate from advertising tracking. Preferences and saved IDs are not uploaded. The services run on Google Firebase / Google Cloud in the United States. Operational request logs are retained for 30 days. Required administrative and security audit logs are retained for 400 days. These logs are access-controlled. Google also processes information under its own service terms and privacy practices.

A build without an endpoint uses its bundled/cached library without content network requests. Failed network or attestation checks preserve the local library.

Reminders

Reminders are optional local notifications containing a quote and its author. Notification previews follow the device notification settings. Up to four weeks are prepared locally and renewed when the app is opened. Topic and faith preferences are used on the device to select this content. Permission is requested when the user enables them. The schedule and device timezone are used locally; no location permission is requested. Reopening after travel updates the scheduling timezone. Reminder schedules and OS notification permissions are device-specific and are not included in portable backups. Turning reminders off cancels scheduled notifications. Clearing personal data first cancels Adelante reminders.

Sharing and source links

Sharing an image, correction report or backup uses the operating system's share sheet. Story sharing can open Instagram with your design; you decide whether to publish it. Copying a sticker puts its image on the local clipboard for up to ten minutes. Designs you add to iMessage stay in a local App Group collection shared with the Adelante sticker extension, up to 60 designs. They are not included in Adelante's exported backup. Clear saved stickers in Create & share, or clear personal data, to remove that collection. Stickers already sent remain in the recipient's conversation. Nothing is sent to a recipient automatically. External apps and source websites have their own privacy practices.

Content

Original Adelante writing is labeled as such. Sourced quotations and religious passages include available attribution, citation, and translation details. The app provides a correction-report sharing flow. For a correction, contact ygshuh@gmail.com. Meanings are editorial interpretations, not a claim that the author supplied that explanation. Any preparation or review notes attached to a meaning are shown with it.

Optional usage reporting (cloud-enabled builds)

Usage reporting is off by default. Turning on Help improve Adelante in Data & privacy reports when the following happen, and nothing else. The service keeps only counts:

Quote IDs can identify a subject, including religious material. Faith preferences, interests, search text, quote text, the content of a correction report, widget designs, reminder times, names, account identifiers, advertising identifiers and installation, device or session identifiers are not included in the reported events. Each event carries only a random one-time ID, the event name, and where it applies a screen name or a quote ID. As with the content service, each request also carries a Firebase App Check token so the service can confirm it comes from a genuine copy of the app, and the host receives ordinary connection information, including the IP address.

The first-party service aggregates counts by UTC day and quote ID. These measure participating sessions/events, not unique people. Random event IDs prevent retry double-counting; only hashed markers with seven-day expiration are stored for deduplication. Firestore expiry is asynchronous. Aggregate counts have no individual deletion key and are retained for product reporting. Cloud infrastructure request logs have separate project-controlled access and retention; requests inherently expose network metadata to the host.

Turning reporting off clears unsent events and prevents subsequent collection; an already transmitted request cannot be recalled. Unsent events remain only in process memory, are capped, expire after fifteen minutes, and are discarded after bounded failed retries or app termination. The app tries to send unsent events when it moves to the background. Restoring a backup never grants consent on another device. Previously aggregated counts cannot be attributed to or erased for a particular person.

Cloud-enabled versions use these services. Offline versions do not make content-service requests and do not offer usage reporting. The app’s privacy notice reflects the capabilities available in that version. You do not need to enable optional reporting to use reading, widgets, reminders or corrections.

Your choices and contact

You can clear personal choices in the app, disable reminders, turn off usage reporting, or uninstall Adelante. Clearing personal data does not erase a backup you exported elsewhere or aggregate counts already sent. To ask about privacy or exercise applicable privacy rights, contact ygshuh@gmail.com. We may need enough information to understand your request; please do not send sensitive personal details unnecessarily.