Privacy policy

1. Privacy contact

For questions about how the amen app uses personal information, contact support at amenapphilfe@gmail.com. You can use this address for access, correction, deletion, restriction, portability, withdrawal of consent and other privacy requests.

This policy describes processing associated with the amen app. Apple and Google also process information for their own services under their respective privacy policies. Their responsibilities do not replace the responsibilities associated with amen or reduce your rights.

2. Support and email correspondence

If you contact support, your email address, message, attachments and details needed to resolve the request are processed through the support email service. Please do not send passwords, complete payment details or sensitive information that is not needed to answer your question.

Article 6(1)(b) applies to requests about your contract or pre-contractual questions; Article 6(1)(f) applies to other correspondence and handling complaints. Relevant correspondence may be retained to resolve the issue, meet legal duties or establish and defend claims. Sensitive information requires an additional lawful condition.

3. Accounts, authentication and profile

During onboarding, amen can create a guest account without requiring an email address or Sign in with Apple. The account has a unique identifier and session information. Your chosen name and supported saved activity are associated with that account identifier. Guest access does not require verification of your real-world identity; account-linked information can still be personal data. Account identifiers, session credentials and preferences are stored with account services and on the device to maintain access and supported synchronization. Access after signing out, reinstalling or changing devices depends on the available authentication and recovery information. Account information also includes creation and update times.

You can link supported guest-account information through Sign in with Apple. Apple may provide an identifier, name and an email or private relay address; amen does not receive your Apple-account password. Linking can associate or transfer supported conversations, profile and progress records, depending on existing account information and successful completion. It does not make every device-only item available elsewhere. Returning users with an existing email/password account can use the available login and password-reset controls. Account services process the required credentials and recovery information. The usual bases are Article 6(1)(b), proportionate security under Article 6(1)(f), and legal duties under Article 6(1)(c).

4. Onboarding answers and faith personalization

Onboarding uses answers about faith goals, a faith vision, reading habits, obstacles and personal struggles to select relevant content. These answers are saved locally in the current flow. Denomination is also saved with account chat settings and can be included in personalized Google AI requests. Some onboarding reflections are selected from prepared, localized text rather than generated by AI. The current denomination step requires a selection to continue.

These answers can reveal religious beliefs or personal circumstances and are covered by the sensitive-data section. Each purpose and recipient requires an appropriate lawful basis and, where applicable, an additional condition for sensitive data. Continuing onboarding, reading this policy or allowing a device permission does not by itself provide explicit consent for sensitive-data processing. Contact support at amenapphilfe@gmail.com about your answers, preferences or privacy requests.

5. Reading activity, notes and personalization

Amen uses language, Bible-version choices, reading activity, streaks, achievements and settings to provide the selected features. Bible notes and verse highlights are saved in local app storage in the current version. Account-based saved verses, saved chat messages, conversations, profile information and supported progress records use cloud storage where available. Signing in does not by itself synchronize every locally saved item across devices. Device and backup settings can also affect local information.

The purpose is to provide reading, progress and personalization functions, usually under Article 6(1)(b), with additional protection where information reveals beliefs or other sensitive circumstances. Use the relevant note, highlight or conversation controls to manage saved content. Keep a separate copy of information important to you; this does not reduce your rights to a conforming service. Public profile and ranking visibility is explained separately below.

6. Public profile and leaderboards

Leaderboards display ranking information to other users, including your display name, profile picture where available, country flag, reading streak, badges, score and rank. Supported progress records are synchronized with the ranking service to calculate and show these results. Profile and ranking information is therefore different from a private note or conversation.

The country code for the flag comes from the device's region setting rather than GPS coordinates. Choose a name and photo suitable for this visibility and avoid confidential information in profile fields. Shared image links may also allow others to view the image. Ranking processing generally supports the feature under Article 6(1)(b), with additional protection for sensitive information. Contact amenapphilfe@gmail.com about displayed information or privacy requests.

7. Nema AI chat

Nema uses an enhanced Google AI model to provide AI chat. Your message and relevant conversation history are sent to Google to generate a response. Context may include your name, selected language and faith preferences when used for personalization. Relevant messages can also be sent to Google to create a short conversation title. The conversation is generated by AI rather than a human adviser.

Google AI services may also support Bible explanations and personalized reading recommendations. Relevant answers, passage references or text are used for the feature you request. Prepared onboarding reflections are handled as described in the onboarding section. Avoid sharing passwords, payment details or confidential information about another person. Requested features generally rely on Article 6(1)(b), with an additional lawful condition for sensitive personal data.

8. Google AI services

Google processes the information sent to its AI services to generate the requested answer. Its handling of inputs and responses depends on the applicable service terms and settings, including provisions concerning model improvement, safety and retention. Google's AI service terms are available at Google AI service terms.

Security, abuse prevention and legal obligations can involve temporary retention or review of AI requests. This policy does not promise that every provider record is deleted immediately. For Google's own privacy information, see Google privacy policy. You may contact support with questions about the handling of your chat information.

9. Conversation history and deletion

Conversations, messages, responses and titles may be saved locally and with your account so you can return to them. Closing a conversation or the app does not delete saved history. Saved messages and related account records can be separate from the conversation currently shown on screen.

Use available conversation controls or contact support at amenapphilfe@gmail.com to request deletion or a copy. Removal from active history, associated records, provider processing and backup expiry are separate parts of handling a request. Deletion does not automatically recall exported or shared copies. Records needed for legal obligations or claims may remain with restricted use.

10. Read-aloud audio

When you request generated speech, the app sends the text to be read, voice settings and generation instructions to Google. This can include Bible text, a devotional or a prayer. Generated audio and voice information may be cached on your device for playback.

Read-aloud generates speech from text and does not itself record your microphone. Relevant text is processed to provide the requested audio; provider security and legal records may also apply. Playback generally relies on Article 6(1)(b), with additional protection if the text contains sensitive personal information.

11. Bible Lock and Screen Time

Bible Lock uses Apple's Screen Time functions when you authorize them. Apple-provided selection identifiers for chosen apps, app categories and supported web domains, together with schedules, unlock settings and reading progress, are stored locally for the app and its extensions to provide the feature. Authorization does not give amen general access to messages or browsing history. You can manage or revoke Screen Time access in system settings.

For an AI reading recommendation, your selected need, requested reading length, preferred language and recent chapter references can be sent to Google. Recent references help avoid repeated recommendations and are also stored locally for this feature. Processing generally provides the requested feature under Article 6(1)(b), with additional protection for sensitive information. Apple controls its own framework processing; device permissions do not supply consent for unrelated analytics or sensitive-data purposes.

12. Profile photos and device permissions

When you save a profile photo, the selected image is stored with the relevant account service. It can appear with your profile or ranking information. Shared image links may give others access to that image. Amen uses the image you select; adding a profile photo should not be understood as making every image in your photo library available to the app.

You can manage relevant photo and Screen Time permissions in iOS settings. Saving wallpapers or Live Photos uses the permission needed to add the selected content to Photos, as explained below. Denying a permission can limit its feature. A device-capability authorization is separate from consent to advertising or sensitive-data processing. Apple's privacy information is available at Apple privacy policy.

13. Notifications and reminder schedules

For remote verse and prayer reminders, amen sends the device push token, app language, time zone, enabled reminder types and selected delivery times to the notification service. Registration can be associated with your account. Supported streak or trial reminders can instead be scheduled locally on the device. This information is used to provide the reminder and delivery features you choose.

You can change reminder preferences in the app and notification permission in iOS settings. Delivery depends on permissions, device settings and available services. Revoking a permission does not itself establish that every previously registered token or service record has been deleted; contact amenapphilfe@gmail.com for deletion requests. A trial reminder does not cancel a subscription or replace Apple's renewal information. The trial reminder mentioned during onboarding refers to an email from Apple about the upcoming end of your trial, not an email sent by amen. Apple handles these emails using your Apple Account information under Apple privacy policy. Amen does not control Apple's email delivery or timing.

14. Days with Jesus and widgets

If you use Days with Jesus, amen saves the date you choose locally to calculate the day count. You can change or reset the date in the feature. The date, Bible content, preferences and access information needed by supported widgets are shared with the app's extensions on the device. Bible Lock also uses shared device data for its authorized functions.

Widgets and notification previews can show faith-related content on your Home Screen or Lock Screen. People who can see the screen may also see that content. Choose widgets and previews with this visibility in mind. Requested widget functions generally rely on Article 6(1)(b), with additional protection where information reveals religious beliefs or other sensitive data.

15. Comics, wallpapers, scenes and music

When you open comics, wallpapers, 360° scenes or audio, amen requests relevant content from delivery services and can keep local copies or caches for display and playback. Delivery involves the requested file and ordinary network connection information, including the IP address used for the connection. Supported background-music preferences are saved locally and can also be stored with your profile to provide the selected listening experience.

The current 360° viewer displays downloaded panoramas controlled by touch; it does not use the device camera to capture the surrounding room. Saving a wallpaper or Live Photo adds selected content to Photos with the requested permission. Copies saved to Photos or shared outside amen are separate from account records and are not automatically recalled by account deletion. Media processing generally provides your requested feature under Article 6(1)(b).

16. Purchases and Apple

Apple handles App Store payments and billing. Amen does not receive your full payment-card number from an Apple in-app purchase. Purchase validation services use account identifiers, transaction details, products, trial status and subscription access information to recognize your purchases. Apple's purchase and usage rules are available at Apple App Store terms and usage rules.

Purchase status and technical identifiers may be associated with your amen account and used for subscription attribution. Access administration generally relies on Article 6(1)(b), legally required records on Article 6(1)(c), and optional marketing processing on consent where required. Apple's handling of purchase information is described in Apple privacy policy.

17. TikTok measurement and app attribution

App versions introducing direct TikTok measurement use the TikTok App Events SDK to report installations and qualifying free-trial starts for advertising measurement and optimization. A purchase-validation service confirms trial status before the app reports a trial start. SDK transmissions can include event names, timestamps and event identifiers, app and session information, device identifiers such as Apple’s vendor identifier (IDFV), device model and system version, language, IP/network information and technical diagnostics. Access to Apple’s advertising identifier (IDFA) depends on Apple’s tracking authorization. TikTok’s processing is described in TikTok privacy policy.

The direct TikTok integration does not add prayer text, chat content or onboarding answers to its configured marketing events. Even without those contents, use of a faith-related app can suggest religious interests. TikTok may use event data for reporting, advertising optimization and, where permitted, matching and audience creation. Older installed app versions can still use previous measurement integrations that report onboarding steps, paywall interactions and purchase-related activity. The data flow therefore depends on the installed version; updating the app does not erase information previously received by providers. Crash data may also be used for analytics and investigating technical faults.

18. Apple tracking choice and anonymous attribution

In versions using the direct TikTok integration, the SDK starts when the app opens, before the Apple App Tracking Transparency (ATT) request in the opening onboarding carousel. The SDK includes the ATT status in requests. Declining or not answering the prompt does not disable the SDK or stop every event, configuration or diagnostic request. The choice must be respected for tracking across other companies’ apps and websites; it does not restrict access to amen features. You can manage Apple’s permission in Settings → Privacy & Security → Tracking or contact amenapphilfe@gmail.com about privacy choices.

Apple’s SKAdNetwork (SKAN) provides a separate form of privacy-preserving advertising measurement that can operate without ATT authorization. Apple controls the aggregated postbacks, their timing and whether detailed conversion information is available; an ordinary SDK event is separate from a SKAN postback. See Apple SKAdNetwork information. This policy is information, not consent: where applicable law requires prior consent for SDK collection or transmission, that requirement still applies. Apple’s ATT choice does not replace every consent or other legal condition.

19. Religious beliefs and other sensitive data

Denomination, prayer, faith goals and conversations may reveal religious beliefs, health or other special categories of data under Article 9 GDPR. Such processing needs both an Article 6 basis and an applicable Article 9 condition, ordinarily explicit consent for optional faith personalization. Reading a policy, using the app or allowing Apple tracking is not that explicit consent.

You may request withdrawal, restriction or deletion at amenapphilfe@gmail.com and change available preferences. Withdrawal does not invalidate earlier lawful processing. Avoid entering sensitive data about other people without authority. Disclosure of sensitive choices to analytics providers needs its own justification; this document cannot create consent or make an otherwise unlawful disclosure lawful.

20. Children and parental authorization

Use of amen must comply with applicable child-data rules, legally effective parental authorization where required, and the conditions of external services. An App Store content rating does not replace these requirements. Google's AI service conditions are linked in this policy and remain relevant to features that use those services.

Where consent is needed, the requirements for children depend on local law. Contact support if you believe a child's information was processed without the necessary authorization. We will investigate the request and arrange the restriction or deletion required in the circumstances.

21. Purposes and legal bases

The relevant bases depend on the purpose: Article 6(1)(b) for requested account, reading, AI and purchase-access services; Article 6(1)(c) for legal duties; Article 6(1)(f) for proportionate security, service operation and handling non-contractual correspondence; Article 6(1)(a) for processing requiring consent.

Device-storage rules may also require consent unless access is strictly necessary. Special-category data additionally needs an Article 9 condition. We cannot replace consent-required advertising with a blanket legitimate-interest claim. Required account information is needed for the relevant service; optional information and permissions can be declined, with possible limits to their features.

22. Service providers and other recipients

Recipient categories include providers of account authentication, cloud hosting and storage, purchase validation, app measurement, advertising attribution and support email. Google provides AI services. Apple provides App Store purchases, sign-in, notifications and relevant device functions. Information shared depends on the feature and purpose. TikTok receives the advertising measurement data described above in app versions with its direct SDK integration; see TikTok privacy policy.

Necessary information may also be shared with authorized support personnel, professional advisers or authorities where legally required. Processing and any international transfers remain subject to applicable safeguards. Contact amenapphilfe@gmail.com for more information about recipients and arrangements relevant to your information.

23. International transfers

Providers can operate or give authorized support access outside your country, including outside the European Economic Area. Server region, support access and further subprocessors must all be considered; choosing an EU database region does not by itself rule out every international transfer.

Where GDPR transfer rules apply, a transfer needs an applicable safeguard, such as an adequacy decision covering the recipient or appropriate contractual safeguards, including standard contractual clauses and any necessary additional measures. Contact us for information about the safeguards relevant to your data. We do not promise universal EU-only storage.

24. Retention criteria and backups

Account and synchronized content are retained to provide your account and chosen features until removed or no longer needed. Local caches depend on device and app controls. Support records depend on the request and legal obligations. Transaction records, fraud evidence and disputed matters may need longer retention under applicable law.

Cloud, AI and measurement services retain information according to the relevant purpose, agreements and legal duties. Deleted records may remain in protected backups until they expire, and legally required records may be retained with restricted access. Contact support for the retention criteria applicable to your information.

25. Deleting your account

You can request account deletion through the app. If you cannot access the account or the request does not complete, contact support at amenapphilfe@gmail.com. Proportionate identity verification may be needed to prevent unauthorized access or deletion; you will not be asked to send a password. Deleting an account and removing device-only content are separate operations. Local notes, highlights or preferences can remain independently of the account; use their available controls and the Days with Jesus reset control, or contact support for help.

Uninstalling the app alone does not delete cloud account records. Removing access through Sign in with Apple is also separate from requesting deletion of information held by amen. Neither app removal nor amen account deletion automatically cancels an Apple subscription: cancel it separately through Apple subscription cancellation. Device copies, exported content, backup expiry and records subject to lawful retention are distinct from removal of the active account.

26. Your rights and complaints

Where the GDPR applies, you can request access, correction, erasure, restriction and, where the conditions are met, portability. You may withdraw consent and object to processing based on legitimate interests for reasons relating to your situation. You may object to direct marketing at any time.

Send requests to amenapphilfe@gmail.com. We normally respond within one month; legally permitted extensions require notice and reasons. Requests are normally free, subject to statutory exceptions. You may complain to the supervisory authority where you live, work or believe an infringement occurred. Contacting amen first is not a condition for complaining.

27. Security and automated processing

Data transfers use encrypted connections where supported, with access controls and other technical and organizational safeguards appropriate to the processing. No online service can guarantee absolute security. Protect your device and account, and report suspected unauthorized access.

AI generates responses and personalization, and automated checks can manage access or purchase entitlement. These functions are not presented as decisions about legal rights, credit, employment or medical treatment. If you believe an automated result significantly affects you, contact us for review and the protections applicable to that decision.

28. Changes and related documents

The date and version at the top identify this notice. We will update it when services, recipients or legal requirements change and provide additional notice where required. Publishing a revised notice does not authorize a new purpose that requires consent.

The Terms of use explain use of the app and purchases. Updates to this policy do not reduce mandatory privacy rights. Contact support at amenapphilfe@gmail.com if you have questions about this notice or how your information is used.

Apple information

• Apple App Store terms and usage rules · See more here
• Apple standard license agreement · See more here
• Apple privacy policy · See more here
• Apple subscription cancellation · See more here
• Apple refund requests · See more here

Further information

• Google AI service terms · See more here
• Google privacy policy · See more here
• TikTok privacy policy · See more here
• Apple SKAdNetwork information · See more here