Privacy Policy — Catch-Me
Last updated: 2026-10-15
This Privacy Policy describes how Catch-Me ("we", "the app"), operated by Mauber Informatica LTDA, CNPJ 04.510.476/0001-23, collects, uses, stores and protects your personal data, in compliance with the Brazilian General Data Protection Law (LGPD) and, where applicable, the EU General Data Protection Regulation (GDPR).
1. What Catch-Me is
Catch-Me is an entertainment app where you discover, match and chat with fictional characters operated by artificial intelligence. Characters are not real people; conversations are generated by large language models (AI). This nature of the service drives what data we process and why.
2. Data we collect
| Category | Examples | Source |
|---|---|---|
| Account data | Name, e-mail, date of birth, profile photo | Provided by you or by your social login provider (Google, Apple, Facebook, X) |
| Preferences | Gender of interest, age range, language, usage goals, content level | Provided by you during onboarding and in settings |
| Conversation content | Messages exchanged with AI characters | Generated during use |
| Conversation memories | Summaries and facts extracted from your chats to keep continuity | Derived from conversations |
| Device data | Model, OS, installation identifier, push notification token | Collected automatically |
| Usage and diagnostics | Error/performance events (via Sentry), moderation records | Collected automatically, with sensitive data redacted |
| Analytics data | Pseudonymised usage events (e.g. screens viewed, swipes, matches — never message content) and approximate location (city/region) derived from your IP address | Collected automatically (via PostHog) |
| Purchase data | History of credits (Lips), consumables and redeemed offers | Generated when using the in-app economy |
We do not collect: your precise location (GPS), phone contacts, or content from other applications. For analytics we only process your approximate location (city/region) derived from your IP address — the IP itself is not stored by the analytics provider.
We also process transaction identifiers, product, store, subscription status and credits to validate purchases; the version, language and acceptance time as evidence of explicit acceptance; and, when attribution is enabled, authorised advertising identifiers, Meta's anonymous identifier, Apple AdServices tokens and install, activation, purchase and renewal events. On iOS, IDFA access requires ATT permission. Refusing tracking does not block the service or purchases.
3. Why we process your data (legal bases)
- Operating the service (contract): authentication, profile, conversations with characters, push notifications, credit economy.
- Personalisation (contract/legitimate interest): preferences, language, conversation memories.
- Generating AI responses (contract): your messages are sent to language model providers (see §4) exclusively to generate the character's reply.
- Safety and moderation (legitimate interest/legal obligation): automated content filters, abuse prevention, moderation records.
- Diagnostics and improvement (legitimate interest): error and performance monitoring with sensitive data redacted.
- Product measurement and improvement (legitimate interest): pseudonymised usage events (screens viewed, actions such as swipe/match, usage funnels) and approximate location derived from IP. These events do not include the content of your conversations or the text you type.
- Legal compliance (legal obligation): fiscal retention of purchase records.
We do not sell your personal data. We do not use your conversations for advertising.
4. Sharing with third parties (processors)
We share data only with processors required to deliver the service, by categories of processors (GDPR Art. 13(1)(e) — "categories of recipients"; LGPD Arts. 9/18):
| Processor category | Purpose | Data |
|---|---|---|
| AI model providers | Generate character responses and moderate content | Conversation content, memories and preferences needed for responses and moderation. Avoid including sensitive data in messages |
| Cloud infrastructure, database and network | Hosting, authentication and service protection | Account data, content and technical traffic |
| Platform notification services (Apple/Google) | Push notification delivery | Push token, notification content |
| Error monitoring tools | Technical diagnostics | Technical events with sensitive data redacted |
| Product analytics tools — PostHog Inc. (USA) | Measure product usage to improve it | Pseudonymised usage events (internal identifier, no account name/e-mail), technical device data and approximate location derived from IP — never conversation content |
| Social login providers (Google, Apple, Facebook, X) | Authentication | Per the provider you choose |
We keep an up-to-date internal register of contracted processors; you may request information about specific sharing through the channel in §10.
International transfers may occur (servers in the US); we adopt appropriate contractual safeguards with processors.
Purchases and attribution: app stores and RevenueCat process transactions, internal account identifiers, entitlements and credits. Meta and Apple may receive campaign data and authorised identifiers to measure advertising, with consent where required and other applicable legal bases. We do not send conversation content, names, email addresses or phone numbers for advertising matching. System tracking preferences are separate from acceptance of the Terms.
For Meta attribution, its SDK may process user and device identifiers and in-app interaction events to measure advertising. The SDK privacy manifest also declares possible use for third-party advertising and product personalisation. For purchases and subscriptions, the RevenueCat integration with Meta Conversions API is configured to transmit event type, product, value and available identifiers, including a hash of our internal account ID (`external_id`) for event matching. That hash can still be linked to the account and does not make the data anonymous. Delivery of iOS events without ATT authorisation is disabled.
5. Retention and deletion
- Messages: up to 730 days. Memories: while active, until expiration; deactivated memories are removed after 90 days.
- Moderation and notification logs: 180 days. Account data and acceptance history: while the account exists.
- Mandatory fiscal and operational records may be kept for the necessary legal period, without a direct link to the profile after deletion. External processors also apply their retention policies; requests about those data can be sent to our privacy channel.
To delete your account, use Profile → Edit Profile → Delete account. The request ends access and starts durable removal of the profile, conversations, matches, memories, files, balances, entitlements and linked devices; pending tasks resume after failures. The sign-in identity is removed. Deletion is permanent. You do not need to accept new terms to request deletion.
Deleting an account does not cancel app-store billing or trigger an automatic refund. Cancel the subscription in the store to stop renewal. For privacy requests, data held by processors or inability to access the app, contact [email protected]. We do not store IDFA/Advertising ID in our database or logs.
6. Your rights (LGPD/GDPR)
You may confirm processing, access and correct data, request anonymisation, blocking, deletion or portability, withdraw consent and object to processing based on legitimate interest, as applicable. Use the available in-app options or contact [email protected]. We respond within legal deadlines. You may also contact the ANPD or the competent supervisory authority.
7. Security
We adopt technical and organisational measures: encryption in transit (HTTPS/TLS), row-level access control in the database (RLS), secure authentication (OAuth/PKCE), automated retention policies, redaction of sensitive data in technical logs, and periodic security audits.
8. Minimum age
Catch-Me is intended exclusively for adults (18+). We do not knowingly collect data from minors; accounts identified as belonging to minors will be deleted.
9. Changes to this policy
We may update this policy. Material changes will be communicated in the app or by e-mail. The date at the top indicates the current version.
10. Contact and privacy
Controller: Mauber Informatica LTDA, CNPJ 04.510.476/0001-23. Privacy and data-subject contact: [email protected]. Use this channel for questions, rights requests and information about processors and international transfers.
11. Cookies and technologies on the website
The catch-me.app website uses essential local storage to remember your chosen language and your consent decision (no tracking). Audience measurement is anonymous by default — no cookies and no persistent identifiers (PostHog). Analytics and marketing cookies/identifiers (persistent PostHog, Meta Pixel and, in the future, TikTok Pixel) are only activated after you accept the website banner, and you can change your choice at any time via the "Cookies" link in the footer. Website measurement data is covered by the safeguards in this policy.
12. Email, marketing and engagement tracking
After registration, we may send one welcome email confirming your account and introducing Catch-Me. You can change preferences for non-essential emails through the individual link in each message; leaving one category does not affect essential messages or other categories.
We may use your email address to send:
- operational and transactional communications, such as account and security notices, purchase receipts, material changes to the terms, privacy or service, and notifications about enabled interactions or features (for example, when a character sends a photo or new content is available); and
- Mauber marketing communications, such as news, offers and launches from Catch-Me and other apps, products and services operated by Mauber Informatica LTDA.
Operational communications may be necessary to perform the service, comply with legal obligations or pursue legitimate interests. Marketing communications are processed according to the authorisation granted and applicable law. We do not share your email address so that companies unaffiliated with Mauber can conduct their own marketing.
Preferences and lists may be organised by app. Each marketing email will identify Mauber and the related app, product or service and will include an easy way to leave that list. You may also request cancellation of all Mauber marketing communications at [email protected]. Cancellation does not limit your use of Catch-Me and does not prevent essential messages about your account, security, purchases, rights or the service.
Where permitted by applicable law and enabled for the message, HTML emails may contain a small invisible image (pixel) to record an approximate open, and links may pass through a tracking address before opening the destination to record a click. Data processed may include the email address or recipient reference, message, date and time, delivery or bounce status, approximate open, link clicked, IP address and technical information about the email client or device. An open is only an approximate signal because apps and providers may block or load images automatically. We use this data to confirm delivery, measure engagement and improve communications; we do not use it to infer sensitive data or use conversations for advertising.
We use Amazon Simple Email Service (Amazon SES), from AWS, to send Catch-Me emails. Zoho Mail remains in use to receive messages and replies. Services previously used for sending, such as ZeptoMail and Zoho Campaigns, may retain historical records until the applicable retention periods end, but are not the planned channel for new Catch-Me emails. We may keep internal sending, delivery, bounce, open and click metadata for up to 180 days. Authorisation, cancellation and suppression records may be kept as long as needed to demonstrate and honour your choice and comply with legal limitation periods.