privacy policy

who we are

Matraca provides bilingual keyboards and practice features for Android and iOS, plus a macOS voice and practice app. This policy explains how we handle your personal data when you use the apps, the keyboard, and our website.

The entity behind Matraca is based in São Paulo (Brazil) and Lisbon (Portugal) and acts as the controller of the data described here. For anything privacy-related, reach us at contato@matraca.ai.

keyboards on Android and iOS

On iOS, to translate while you type, the Matraca keyboard needs the "Full Access" permission that iOS requests when you install a third-party keyboard. We know that permission is scary, and it deserves an honest explanation. The macOS app does not use this permission.

On Android, you enable and select the keyboard in system settings. When you tap to convert, the selected text or current line is sent to Matraca’s backend for translation, corrections, and storage in your account history. Ordinary typing outside a requested conversion is not sent to our service. You can switch keyboards or disable Matraca in Android settings.

On iOS, the keyboard sends text to our backend when you request conversion or use voice features that depend on the service. Ordinary typing outside these actions is not sent. Full Access enables the necessary communication between the keyboard, app, and service; it does not mean that we log every keystroke.

What we do NOT do, and never will:

• We do not log or store what you type in password fields, credit card fields, or any field iOS marks as secure — the keyboard is disabled in those contexts.
• We are not a keylogger: we do not silently capture everything you type in other apps outside of Matraca's translation flow.
• We do not sell, rent, or trade what you type. Your keystrokes are not a product.
• We do not use the content of your messages for targeted advertising.

Text sent for translation always travels encrypted and is used only to produce the response and run app features (like your practice history and streak). You can revoke Full Access at any time in iOS Settings — without it, the keyboard's translation features stop working.

what we collect

We collect the minimum needed to make the app work and improve it:

• Account data: account identifier, display name, email, and authentication data from your sign-in provider. If you provide or import them, we also process your profile photo, biography, and date of birth.
• Text processed for translation: the sentences you write in the translation flow, and their translations, tied to your account to power history and practice.
• Audio and transcription: when you voluntarily start a voice feature, we capture your recording and generate a text version to provide the requested feature.
• Contacts and invitations on Android: with your permission, we read names and email addresses from your contacts on the recipient-selection screen. Only the email addresses you select or enter are sent to the backend when you confirm invitations; we do not upload your entire address book.
• Notifications: installation identifier, APNs token on iOS, language, time zone, chosen days and time, and notification preference. These data allow delivery of the reminders you enable.
• Reports and blocks on Android: the reason and details you submit, identifiers for the report, your account, and the reported group, member, or exercise. We also store the users you block to apply your preference.
• Streak and social data: consecutive days, completed chapters, friend connections, and the friendly pressure that keeps the conversation going.
• Optional usage analytics: navigation and product-action events, only after you opt in. We do not send practice text, audio, names, or emails to Amplitude. Events may include a technical device identifier and, after sign-in, the account identifier; these identifiers are not anonymous data.
• Device data: platform, app version, language, time zone, and technical identifiers needed by the service. App configuration comes from our backend; we do not request GPS location for this purpose.
• Free-access control and security: word and audio usage, request limits, and access status linked to the account. Financial records and technical identifiers of deleted billing customers help reconcile payments and prevent old events from restoring deleted links.

audio, microphone, and transcription

Matraca captures audio only when you voluntarily start a voice feature and while recording is active. Android, iOS, or macOS microphone permission is requested before the first capture.

In the macOS app, recording and transcription are processed locally on your Mac with the Parakeet model. Raw audio is not sent to our backend or to the providers below. Recordings may remain in local history according to the retention setting you choose and can be deleted in the app. Resulting text is sent only when needed for features you request, such as translation, exercises, account history, or feedback.

For features that use remote transcription, the app sends audio to our backend. On iOS, this depends on your permission for remote transcription. The server validates the account, format, duration, and usage limits before sending the audio to OpenAI to produce text. We do not save captured raw audio in the database or put it in application logs.

• OpenAI — receives audio for remote transcription requests. It also receives text submitted for translation, corrections, tutoring, exercise generation, and exercise speech generation. The history preference does not prevent processing needed for the feature you request.
• For text requests we use store=false. OpenAI documents no API training by default and no content retention for transcriptions, while text and speech generation may have abuse logs for up to 30 days. Our preferences do not change provider retention.

You can revoke microphone access at any time in Android app permissions or in iOS or macOS Privacy & Security settings. This prevents new recordings and disables features that rely on voice without affecting features that do not use the microphone. On macOS, you can also delete local history in the app. To request deletion of a transcript or other data tied to your account, email contato@matraca.ai.

how we use your data

We use your data to:

• Operate the keyboard and deliver the translations you request.
• Transcribe audio you choose to record and provide the requested voice features.
• Maintain your account, streak, chapters, and connections.
• Process subscriptions and payments.
• Improve the product, fix bugs, and understand what works.
• Send important service notices and, with your consent, product news.
• Comply with legal obligations and protect against fraud and abuse.

legal bases

We process your data on the basis of contract performance (delivering the app and feature you requested), your consent (where applicable, including microphone access), our legitimate interests (security, product improvement, fraud prevention), and compliance with legal obligations. Under LGPD and GDPR, you can withdraw consent at any time.

third parties and processors

We don't work alone. To run Matraca, we share strictly necessary data with providers acting as processors, under contract and confidentiality obligations:

• Stripe — payment and subscription processing.
• Resend — delivery of account messages, email verification, password recovery, invitations, and enabled service notices. It receives the recipient and message content needed for delivery.
• RevenueCat — purchase validation and subscription-status management on Android and iOS; RevenueCat receives technical account identifiers and purchase events, but not full card details.
• Intercom — customer support and messaging when you open that feature in the app; the technical account identifier, device data, and conversation content may be shared.
• Render — hosting of the website, API, and background processing. PostgreSQL stores account, authentication, practice, file, and operational data. Authentication is managed by our backend using Better Auth; this version does not use Firebase for authentication or storage.
• OpenAI — remote audio transcription and text processing for translation, corrections, tutoring, exercises, and speech generation. The flows and controls are described in the audio section of this policy.
• Amplitude — optional product and teacher-program events after you opt in. Turning it off discards pending local events; this action does not remove events already received by the provider. Payment and commission analysis uses operational records separate from this consent.
• Google Play — Android app distribution, purchase processing, and management of subscriptions purchased through the store.
• Apple — App Store distribution and billing on iOS, APNs notifications you enable, and Developer ID signing and notarization on macOS.

Background tasks run in our backend. The PostgreSQL queue stores references to the records needed for processing, without copying practice texts to an external queue service. Before running a task, we check the account, preferences, and content availability. Infrastructure backups have separate retention; removal from the active database does not mean immediate physical removal from every backup.

We do not sell your personal data to anyone.

reports and blocks

You can report groups, members, and exercises within the Android app. We use the submitted reason, details, and references to review inappropriate content and prevent abuse. To preserve the report's context, we may store the member's display name or the group's name and rule. Exercise reports store references to the set and item, without duplicating exercise text or audio in the report. The team responsible for the service may access this information to handle the case.

Blocks are personal and tied to your account. We store the blocked person's identifier and display name to hide them and the groups they own, prevent invitations between you, and let you manage your blocks. You can unblock people in the Blocked users list. Reports and blocks follow the retention and deletion rules described in this policy.

payments and subscriptions

Payments for subscriptions purchased on the website are processed by Stripe. Your card details are collected and handled directly by Stripe under PCI-DSS standards — Matraca does not store your full card number. We receive from Stripe only what we need to manage your subscription, such as payment status and the last digits of your card. Subscriptions made through the App Store are managed by Apple. On Android, in-app purchases are processed by Google Play. Matraca and RevenueCat receive purchase identifiers and status needed to enable access, without receiving full card details used in the store.

data retention

On macOS, captured audio remains in local history according to the retention configured in the app. For remote transcription, the backend processes audio in memory without saving it in the database. Transcripts are treated as text. Generated exercise audio may be stored with exercise content and follows its expiration. Provider retention is independent and described in the audio section.

Practice texts and transcripts follow your history preference and a configured period of 1–365 days, with 30 days as the default. Turning off history removes saved texts and derived learning content; turning off personalization removes derived content while preserving permitted history. A shorter period also shortens existing deadlines. Increasing it or turning history back on does not restore deleted content. Usage and scoring statistics remain separate from texts.

Deletion removes the sign-in identity and linked personal data after external-service cleanup completes. Billing, commission, and payout facts are retained with the sign-in link removed. Pseudonymous billing-customer identifiers may also remain to prevent old events from restoring deleted links. These records are not used for advertising, are not necessarily anonymous, and have their own purposes and retention.

delete your Matraca account

On iOS, request deletion under profile > settings > delete account. The flow requires recent authentication and confirmation and shows the operation status. Accepting the request revokes sessions and blocks new account actions; cleanup may continue in the background. Deletion is shown as complete only after backend confirmation, subject to the retention exceptions above.

You can also request deletion without accessing the app: email contato@matraca.ai with the subject Delete Matraca account and include the email address of the account you want to delete. You can use the same channel to request deletion of specific data without deleting the entire account.

Account deletion does not replace subscription management. Review and cancel App Store purchases in Apple subscriptions and Google Play purchases in that store. Web subscriptions can be managed on the subscription page and through the Stripe portal provided by the service.

security

We use encryption in transit and at rest, access controls, and security practices proportionate to the risk to protect your data. No system is perfect, but we treat your data the way we'd want ours treated. If a significant incident occurs, we will notify you and the relevant authorities as required by law.

international transfers

Matraca operates between Brazil and the European Union, and our providers may process data in other countries. When we transfer data internationally, we apply the safeguards required by LGPD and GDPR, such as standard contractual clauses and adequacy checks.

your rights

Under LGPD and GDPR, you have the right to access, correct, update, port, and delete your data, as well as to object to or restrict certain processing and withdraw consent. To exercise any of these, write to contato@matraca.ai — we respond within the legal timeframes. You may also lodge a complaint with the competent data protection authority (ANPD in Brazil, or your EU supervisory authority).

children

Matraca is not made specifically for children, and we do not knowingly collect children's data without the consent required by law. If we learn we've collected data from someone below the permitted age without the necessary authorization, we'll delete or correct that data.

changes to this policy

This policy may change as the product evolves or the law changes. When a change is significant, we'll let you know in the app or by email and update the date at the top. Continuing to use Matraca after that means you agree to the current version.

talk to us

Question, request, or complaint about privacy? Send a message to contato@matraca.ai. We're in São Paulo and Lisbon.