Privacy policy

01

Who we are and what this covers

Rikhath LLC provides Hereafter, a reflection, reading and personal-practice app. This policy describes the native app, its optional Android attention tools, the disposable browser preview, and this privacy-policy website. Features can vary by platform and build; standard Android builds do not include the device-control service.

For privacy questions, contact imran.hassan@rikhath.com. This policy applies from 7 November 2026 and describes the features currently implemented.

02

Personal records stay on your device

Information you choose to save can include journal entries, check-in answers, prayer and practice records, intentions, responsibilities, feelings, gratitude, selected background or faith, goals, reading preferences, bookmarks, learning progress, topic consent, recommendation feedback, reminder settings, and an active focus timer. Dates, time zones, timestamps and internal identifiers support these features.

The native app stores these records in an encrypted local database. Its random encryption key is held by the operating system's secure storage. Hereafter has no app account, personal-record backend, advertising SDK or app analytics service. It does not automatically upload these records to us, and we do not sell them or use them for advertising.

New journal writing stays in the editor until you explicitly save it. Guidance starts off for each new entry. When you enable guidance, only topics you explicitly select inform local recommendations; Hereafter does not scan journal text or send it to an AI service. A pause choice is temporary and does not create a habit history or journal entry.

03

Prayer times and location choices

You can select a city from the bundled city list or enter coordinates and a time zone for offline prayer-time calculations. These choices and calculation preferences are saved locally. Hereafter does not request GPS access or contact a location service. Timers and reminders do not mark prayer, worship or responsibilities completed.

04

Optional Android app and website shields

Device-control builds offer optional app shields, opening pauses and supported-browser domain shields. You choose the rules, accept a separate in-app disclosure, and enable Android Accessibility access yourself. You can decline it and keep using the rest of Hereafter.

The service processes active app and window package identifiers locally to match the apps you selected. The app-selection screen lists launchable apps so you can choose them. If you separately enable website shields, the service checks known browser address-bar fields only when they are unfocused and are not password fields. It extracts the domain, discards paths and queries, and matches local rules or a bundled domain list. These checks can run while Hereafter is in the background.

The service does not inspect page contents, messages, passwords, keystrokes or journal entries. It does not transmit inspected app or domain identifiers to us, record an opening or browsing history, or provide network-wide filtering. Unsupported or hidden address bars may not be detected, and a shield can appear after a request starts.

Selected app and domain rules and their consent settings are stored in the encrypted personal database. The Android service uses a minimal configuration mirror encrypted with a device-held key. It contains no journal or faith records. Turn protection off in Hereafter or revoke Accessibility access in Android Settings; essential device functions remain accessible.

05

Optional screen-time estimates

Screen-time estimates require a separate opt-in and Android Usage Access. Only when you request the overview, Hereafter reads operating-system app-usage summaries for the selected one-day or seven-day period and displays estimates locally. It does not continuously monitor or upload these summaries, and does not retain them as a completed-session or usage history. Displayed estimates are cleared when you leave the screen or background the app. You can disable this feature or revoke Usage Access in Android Settings. Shields do not require Usage Access.

06

Reminders, app lock and public widgets

Reminders start off. Notification permission is requested only after an explicit reminder action. Schedules and identifiers are kept locally, and notification wording is generic rather than including private writing. The operating system processes notification delivery and can delay or suppress alerts.

Optional app lock uses your device's authentication system. Hereafter receives an authentication result, not your fingerprint, face template or device passcode. Native screen protection limits app-switcher exposure; Android also restricts screenshots. Device encryption and lock do not make an unlocked or compromised device inaccessible to others.

Public widgets receive bundled public prompts and dates only. Journal text, faith choices, prayer answers, commitments and other personal records are not supplied to the widget.

07

Read-aloud, source links and services you choose

Read-aloud sends only the displayed public passage to your selected device text-to-speech engine, never your private notes. That engine or voice may use its provider's online services; offline playback depends on installed voices and device settings. Its provider's privacy terms apply.

Public reading texts and other core assets are bundled for offline use. Source and licence links open an external website only after you choose them, using public references rather than your journal text or selected background. The destination website and your browser handle that visit under their own privacy practices.

If you choose a file provider, sharing app, email service or backup destination, that service handles the material you explicitly give it under its own terms. Hereafter does not automatically send private backups to a cloud service.

08

Backups, retention and deleting local data

Saved personal records remain locally until you edit or delete them, erase the app's data, or uninstall it. Hereafter excludes its private database, secrets and service configuration from automatic device backup and transfer using platform controls. Device loss, key loss or uninstall can permanently lose records unless you created a usable backup.

You can explicitly export a password-protected encrypted backup and choose where to keep it. It can include saved records and preferences, including selected app and domain rules, but omits active timers, native encryption keys and screen-time totals. Restore disables reminders, device protections and restored topic guidance until you choose them again. We cannot recover a lost backup password or decrypt a backup for you.

Settings → Erase all local personal data removes the app's saved personal records, derived guidance, reminder schedules, private encryption keys, internal backup caches and device-control settings, and starts a fresh local store. Individual entries can also be deleted. Hereafter cannot delete exported files or copies you gave another service; remove those from their destinations separately. Internal encrypted backup caches expire on a later launch after 24 hours or are removed by erase-all.

There is no Hereafter account to close and no server copy of your local journal for us to retrieve or delete. Use the app or your device's app-data controls to remove local records. If you contact support, we process the email address, message and attachments you send to respond and resolve the request. Keep private entries and backup passwords out of support messages. Request deletion of support correspondence by email; necessary legal or security records may need to be retained.

09

Browser preview and this website

The browser app preview holds disposable demonstration records in memory and resets on reload. It does not provide the native app's encrypted persistence, device lock or Android shields. Use fictional information in that preview.

This public policy website contains no sign-in, forms, advertising, analytics scripts or app records. Our website host, Vercel, processes ordinary request information such as IP address, request time, requested page and browser headers to deliver and secure the website. Its privacy policy is at https://vercel.com/legal/privacy-policy. We do not add tracking cookies or link these website requests to your private app records. Email providers and app stores separately handle email, downloads, purchases if any, and platform diagnostics under their own policies.

10

Your choices and privacy requests

You control what you enter and save, which optional permissions you enable, and what you export. You can edit or delete personal records, revoke topic consent, reset personalization, turn off reminders or protections, and erase local personal data. Revoking a permission stops the associated feature; it does not automatically delete unrelated saved records.

Depending on where you live, applicable privacy laws may provide additional rights over information held by us, such as support correspondence. Contact imran.hassan@rikhath.com to make a request. We may need enough information to verify and address it, and we cannot access data that exists only on your device. Do not send us someone else's private information unnecessarily.

11

Changes and contact

We will update this policy and its effective date when our practices change. New optional access still requires the relevant in-app disclosure and your explicit action. You can read this policy without enabling device-control permissions.

Privacy contact: Rikhath LLC, Hereafter — imran.hassan@rikhath.com.