Privacy Policy for Rose

Last updated: September 7, 2026 · Native app

This Privacy Policy explains how the Rose & Bible native app for Apple and Android processes personal data. Rose provides AI-assisted Bible conversations, Bible reading, audio features, and related user services. Community, group, and event features are disabled in the current release.

1. Data controller

The controller responsible for processing personal data is:

Gracia Lukelo Tshakulongo
Gerresheimer Straße 182
40233 Düsseldorf
Deutschland

Email: lukelo.tshakulongo@rose-bible.com

Operational privacy contact: Gracia Lukelo Tshakulongo
Email: lukelo.tshakulongo@rose-bible.com

2. Summary

Rose processes personal data to provide user accounts, sign-in, chat, AI responses, voice features, Bible content, support, security, and error analysis. Prepared community features are disabled in the current release.

We do not sell personal data. We do not use chat or voice content for advertising. We share personal data only where necessary to operate Rose, provide requested features, maintain security, process payments, comply with legal obligations, or act with the user's consent.

Current native-app path: New chat and call histories are stored locally on the device. Inputs needed for a requested online AI or voice feature are transmitted during use to the Rose backend and the active AI or speech infrastructure. A completed call is not additionally uploaded in full for profile building. Earlier optional profile, memory, training, and review purposes cannot be newly enabled; existing legacy consents can be withdrawn and historical data can be accessed or deleted through the privacy controls.

3. Data we process

3.1 Account and sign-in data

We may process the following data to create and manage an account:

• Email address
• User name or display name
• Secure password credentials when email/password sign-in is used
• Sign-in method, such as email, Google Sign-In, or Sign in with Apple
• User ID
• Profile image, if uploaded
• Language and app settings
• Account creation date and last sign-in

Passwords are not stored in plain text.

3.2 Chat and AI content

When a user chats with Rose, we may process messages, AI responses, stored conversation history, context required to continue a conversation, the selected language, timestamps, request identifiers, and error status.

Users may voluntarily include sensitive information such as religious beliefs, personal crises, health matters, emotional distress, or family circumstances. Rose does not require such information. When a user chooses to provide it, it is processed only as necessary to provide the requested response or feature.

3.3 Voice, audio, and call features

When voice features are used, we may process microphone input, transcribed text, AI responses prepared for speech, connection status, duration, latency and error metadata, and the device's microphone permission state.

The microphone is used only while the user actively uses a voice feature and has granted permission. Raw audio is processed during the active voice feature for transcription and response generation. The current app path stores the completed conversation locally and does not upload it again after the call for server-side profile building. Historical server-side records from earlier versions may remain until deletion.

3.4 Bible and content use

We may process opened Bible passages, searches, favorites, notes, reading history, language and translation choices, and audio playback status where required for the feature.

3.5 Community features

Community, group, direct-message, and event features are not enabled in the current release. The following description applies only after a future activation or to historical records that may still exist.

Community use may involve profile names and images, public or group posts, comments, reactions, friend requests, group membership, direct messages, event participation, reports, blocks, and moderation records.

Content posted in public or group areas may be visible to other users. Users must not publish confidential, highly sensitive, or third-party personal data unless they are authorized to do so.

3.6 Location and events

The current app release does not request operating-system location permission and does not collect device or GPS location. If a map or event feature is enabled later, users may enter a place manually and this Policy will be reviewed before activation.

3.7 Purchase and subscription data

Payments for paid features, subscriptions, and in-app purchases are generally processed by Apple App Store, Google Play Billing, or Stripe where applicable to the platform and product.

We normally do not receive full payment-card details. We may receive purchase status, transaction references, product identifiers, subscription status, and billing information required for entitlement management, fraud prevention, accounting, and support.

3.8 Support communications

When a user contacts support, we may process their name or user name, email address, request content, communication history, and technical details required to investigate the issue.

3.9 Technical data, logs, and security

Operation of the app and backend may involve IP address, device type, operating-system and app version, language and region, timestamps, server and error logs, crash and performance data, security events, API request status, and authentication or session data.

3.10 Notifications

If daily-verse reminders are enabled, the current native app stores the preference and schedules notifications locally through the operating system. It does not register a new APNs or FCM token. Tokens from older builds may remain as historical account data until they are deleted under the applicable retention process.

4. Purposes

• Create and manage user accounts and authentication
• Provide chat, AI, voice, audio, call, and Bible features
• Store settings, favorites, notes, and history
• Provide community, event, and location-based features where enabled
• Process purchases and manage subscriptions
• Provide support and service communications
• Protect security, prevent fraud and abuse, and enforce terms
• Analyze errors, maintain stability, and comply with legal obligations

5. Legal bases

5.1 Performance of a contract – Article 6(1)(b) GDPR

We process data where necessary to provide Rose and the features requested by the user.

5.2 Consent – Article 6(1)(a) GDPR

Where required, we rely on consent, for example for device permissions, optional notifications or analytics. Consent can be withdrawn for the future at any time.

5.3 Special-category data

Users may voluntarily enter content that reveals religious or philosophical beliefs, health information, or other special-category data. The current Rose client does not display a separate online-AI consent dialog and does not send versioned consent evidence with chat or call requests. Historical consent records from earlier builds may remain. The controller must obtain legal review and document an applicable Article 9 GDPR condition before claiming that this processing is lawfully covered.

5.4 Legitimate interests – Article 6(1)(f) GDPR

Our legitimate interests include IT security, prevention of abuse, spam, fraud and attacks, error analysis, stability, performance, community moderation, enforcement of terms, and preservation of evidence for security incidents.

5.5 Legal obligations – Article 6(1)(c) GDPR

We process data where required by tax, commercial, accounting, regulatory, retention, or other legal obligations.

6. AI processing

Rose uses AI systems to answer questions, process text, transcribe speech, and generate speech. User inputs, conversation context, and voice transcripts may be sent to technical service providers where necessary for the requested feature.

Rose is an AI-based product and users are not communicating with a human. The current chat input does not display a persistent AI warning label; the call surface continues to identify the conversation as AI.

We do not use personal chat or voice content to create advertising profiles and do not sell that content. Where possible, AI providers are configured not to use submitted content to train general-purpose models.

AI output may be incomplete or incorrect. Rose is not a substitute for qualified medical, psychological, legal, financial, or pastoral advice. Users should contact appropriate professionals or emergency services in urgent situations.

7. Personalization and automated decisions

The current routine chat does not use previously stored server-side profile or memory records for personalization. Local conversation history can be used on the device when a user continues a conversation or requests call context. Historical profile or memory records may still exist and can be accessed and deleted through the privacy controls.

Rose does not make solely automated decisions that produce legal or similarly significant effects within the meaning of Article 22 GDPR.

8. Service providers

Provider categories may include hosting, databases, authentication, AI and speech processing, text-to-speech, speech-to-text, monitoring, payments, email, notifications, maps, app stores, and sign-in providers.

Depending on enabled production configuration, providers may include Google Cloud / Cloud Run, Supabase, OpenAI, DeepSeek, ElevenLabs, Sentry, Google APIs, Google Maps, Google Sign-In, Sign in with Apple, Apple App Store, Google Play Billing, and Stripe.

Providers process data only as required for their services and are subject to appropriate contractual or legal safeguards where required.

9. International transfers

Some providers may process personal data outside the European Union or European Economic Area. Where required, transfers rely on adequacy decisions, standard contractual clauses, Data Privacy Framework certification, another legally recognized safeguard, or an applicable exception or consent.

10. Retention and deletion

We retain personal data only as long as necessary for the purposes described or as required by law.

• Account and profile data: while the account is active or until deletion
• Chat history and voice transcripts: locally in the current app path until app data or the history is deleted; historical server-side records until user or account deletion or an applicable retention limit
• Raw audio: temporarily for processing unless a feature expressly states otherwise
• Community content: until deletion, moderation, or account deletion, subject to lawful retention needs
• Support requests: while needed to handle and document the request
• Security and server logs: for the necessary operational period or longer where an incident or legal duty requires it
• Purchase and accounting records: for legally required periods
• Backups: according to the provider's technical recovery cycle

Exact provider log and backup retention settings still require operational and legal confirmation and are not represented here as a completed compliance control. Deletion requests are normally processed within 30 days unless legal or technical reasons require more time.

11. Account and data deletion

Users can request deletion in the app through Settings / Account & security / Delete account, through the public page at /account-deletion?lang=en&surface=app, or by emailing lukelo.tshakulongo@rose-bible.com.

Account deletion generally removes the user account, profile, account-linked chat history, saved Bible notes and favorites, account-linked voice transcripts, community data where legally and technically possible, and authentication data in our systems.

Some records may be retained when required for accounting, legal defense, fraud prevention, security, or abuse prevention.

12. Local device storage

Rose may store sign-in state, app and language settings, encrypted application values, local chat history, caches, temporary audio or image data, technical tokens, and enabled offline content on the device. Encryption keys are kept in the platform's secure storage where supported. Users can remove local app data through device settings or by uninstalling Rose.

13. Device permissions

• Microphone: voice input, transcription, and call features
• Camera or photos: profile images and user-selected image attachments
• Bluetooth: audio routing to connected devices where required by the operating system
• Location: not requested as a device permission in the current release
• Notifications: locally scheduled daily-verse reminders when enabled

Permissions can be withdrawn in device settings.

14. Security

Depending on the system component, safeguards include HTTPS/TLS transport, access controls, authentication and authorization, separation of secrets and API keys, security logging, component updates, least-privilege service access, and abuse protection. No app or internet transmission can guarantee absolute security.

Potential vulnerabilities or security incidents can be reported to security@rose-bible.com.

15. Children

Rose is not specifically directed to children under 16. A person under 16 should use Rose only with parental consent where required by applicable law. If we learn that a child's data was processed without required consent, we will take appropriate steps to delete or restrict it.

16. Community rules and third-party data

Users must not publish another person's personal data without authorization. We may review, restrict, or remove content and may restrict accounts where necessary to protect users, enforce terms, prevent abuse, or comply with law.

17. No sale of personal data

We do not sell personal data. If advertising, tracking, or personalized advertising is introduced in the future, this policy will be updated and consent obtained where required.

18. Data protection rights

Subject to the GDPR and applicable conditions, users may have rights of access, rectification, deletion, restriction, portability, objection to legitimate-interest processing, withdrawal of consent, and complaint to a supervisory authority.

Requests can be sent to lukelo.tshakulongo@rose-bible.com.

19. Supervisory authority

Users may lodge a complaint with a data protection supervisory authority, particularly in the country of habitual residence, place of work, or place of the alleged infringement.

20. Changes to this policy

We may update this policy when Rose, its data processing, providers, legal requirements, or security measures change. We will provide appropriate notice of material changes.