App privacy policy

1. Controller and scope

The planned controller for Ruby Messenger is Tim Tiefenbach – TeaFan Media, Storchenallee 31a, 65201 Wiesbaden, Germany. Privacy questions can be sent to [email protected].

This page is intended to cover data processing in the Ruby Messenger iOS app and its backend. The separate website privacy policy covers rubymessenger.app and the invite-link fallback page.

2. Planned data categories

Depending on the features used, Ruby Messenger is expected to process account and profile information, age category and guardian status, invite and contact relationships, messages and media, vocabulary and learning progress, device and push-notification data, security and diagnostic information, and subscription entitlement information.

The final policy will list the exact data fields and distinguish required service data from optional analytics.

3. Purposes and legal bases

Data is planned to be used to provide accounts, invitation-only messaging, furigana and explanations, vocabulary learning, notifications, subscriptions, Family access, support, security and abuse prevention. The final policy will assign and explain the applicable legal basis for each purpose and launch territory.

4. Service providers and recipients

The final policy will identify all processors and recipients used at launch. The current technical plan includes Apple services, Supabase, the Ruby Messenger server and hosting providers, RevenueCat for purchase status, push-notification infrastructure, authentication providers selected by the user, and the named language-model provider used for furigana or explanations.

Message text may need to be processed by the Ruby Messenger server and the named language-model provider to provide language features. The exact provider, processing region and safeguards will be stated before public release.

5. Purchases and RevenueCat

Apple processes payment and store transaction data under its own terms. Ruby Messenger plans to send a pseudonymous Ruby Messenger user UUID and purchase-status information to RevenueCat. Email addresses and names are not planned as RevenueCat App User IDs or customer attributes.

6. Children and Family accounts

People under 18 will not be offered their own sign-up, trial, paywall or StoreKit purchase. The planned Family flow requires an eligible adult payer and guardian, a Family seat and a separate guardian notice and consent step. No optional product analytics is planned before the required age and consent checks.

7. Retention, deletion and privacy choices

The final policy will define retention periods for each data category and explain in-app account deletion, export, correction, consent withdrawal and support requests. It will also describe what must be retained for legal, security or transaction-record obligations.

8. International transfers and security

The final policy will document processing locations, international transfer safeguards and the contracts used with providers. Ruby Messenger plans transport encryption, access controls and server-side authorization; the final description will match the implemented production system.

9. Your rights and updates

The final policy will explain applicable rights of access, rectification, erasure, restriction, portability, objection, consent withdrawal and complaint to a supervisory authority. The effective date and change history will be added before public release.