Keptkeptlife.app
Kept · Privacy

Privacy Policy

How Kept handles account, community and personal reflection information.

Reviewed and confirmed by the developer on 3 October 2026. This policy describes the supplied build information and identifies any remaining limitations.

Who operates Kept

Kept is developed by Ayobami Dosumu, an individual developer, not a company. Contact support@keptlife.app for support or privacy questions. Do not email private prayers, journal entries or habit-plan details.

Updated 3 October 2026. This notice describes the build information supplied by the developer. Live service configuration has not been independently verified.

Apple sign-in and account information

Kept requests name and email through Sign in with Apple. Apple may supply your email or a private relay address; name and email may not be returned after your first authorization.

The app sends Apple's signed identity token and the returned name to Kept's backend. The backend verifies the token with Apple and stores your app-specific Apple identifier, email if present and display name if present to recognise your account later.

Kept sends its Kept user ID to RevenueCat to associate your customer record and refresh subscription access. The Apple identity token goes to Kept's backend, not RevenueCat.

Local reflections and sensitive information

Plan, Journal, Prayer, SOS and habit information appear to remain in on-device storage in this build. No cloud backup or cross-device sync implementation was identified in the supplied build description. Creating an account preserves local information; it does not create a server backup. Device or operating-system backups have not been confirmed.

Community prayers and participation are different: they are sent to the backend. These may reveal religious beliefs and can involve special-category personal data.

Information not yet specifiedThe developer must document the applicable Article 6 lawful basis and separate Article 9 condition for sensitive faith-related processing. These legal decisions remain unresolved; this notice does not select consent or another condition.

Communities, Buddy invitations and service providers

Community profiles, memberships, invitation records, prayer requests, replies, announcements, prayer times, reports, blocks and Buddy relationships are sent to Kept's backend and stored in MongoDB. Community content is intended to be member-restricted. This website displays no community posts or public directory.

For Buddy invitations by email or phone, the app sends the contact to Kept's backend. The backend stores a hash of the contact alongside the invitation, rather than the raw contact. A hash does not necessarily make the record anonymous. The backend returns a share link for you to share; no automatic SMS or email delivery was found for these invitations. The recipient must use or create an account and accept; the backend checks the same-sex rule.

Purchases use Apple StoreKit/App Store and RevenueCat. RevenueCat receives customer and purchase information to manage entitlements and acts as Kept's subscription authority. Community creation also has a backend RevenueCat entitlement check.

Passwordless email sign-in is separate: if enabled, an email address and one-time code are sent through Resend. Its live availability is unconfirmed.

Information not yet specifiedConfirm the live backend and database hosts/regions, provider roles and transfer safeguards, enabled Resend configuration, and actual staff/admin access. Member access restrictions are described as intended behaviour, not an independent permissions audit.

Analytics implementation

The analytics module is designed to send events to a configured Kept backend for storage in MongoDB. Events can contain an anonymous ID, selected habit category, trigger/action codes, outcome and broad length buckets. The schema excludes free-text journal and plan content.

The supplied source review found no calls to this module elsewhere in this build. Whether events are currently emitted is unconfirmed. An anonymous identifier alone does not establish that the information is anonymous, and faith-related categories may be sensitive.

Retention and account deletion

Retention periods and deletion behaviour have not yet been confirmed. No promise of immediate or complete erasure is made. This includes backend records, shared content, reports, payment information and backups.

Information not yet specifiedConfirm what is deleted or anonymised, what remains visible to others, retained-record reasons and durations, backup expiry and processing time. Verify the in-app account deletion flow.

See account deletion help.

Privacy questions and choices

Contact support@keptlife.app to request access, correction, deletion or other applicable data-protection rights. Availability depends on applicable law and the processing concerned. The detailed request-handling process remains to be confirmed. Do not send passwords, sign-in codes or private reflection content.

UK privacy concerns can be raised with the Information Commissioner's Office.

Website and support correspondence

This website has no private prayer/journal form, public community feed, payment form or added analytics script. Its hosting platform can process technical request information; actual logging and retention remain unconfirmed. If you email support, your email address and message are information you provide for responding to your enquiry.

Further changes will be dated on this page. Any changes to the practices described here will be reflected in this policy.