Mntra is a flashcard learning app for Android, published by devls (the “developer”, “we”). This policy explains what data the app touches, why, and who it's shared with.
Your flashcards live on your device. The app does not have a backend, does not log you in, and does not send your decks anywhere. Two narrowly scoped exceptions exist and are documented below: a) crash reports via Sentry (no card content is included), and b) optional AI features that send the text and images you choose directly to an AI provider you sign in to with your own API key.
Flashcard content. The decks, cards, and templates you create are stored in a local database on your phone. Nothing is transmitted off device unless you explicitly use one of the AI features described below.
Audio recording. If you attach an audio recording to a card, Mntra uses the microphone (the RECORD_AUDIO permission) to capture audio from your device and writes the file to the app's private storage directory. Recordings are only created when you tap the record button inside a card editor. Mntra does not open the microphone in the background, does not stream audio anywhere, and does not transcribe it.
Images. Images attached to cards are copied into the app's private storage. They are not uploaded.
Text-to-speech. When you tap the speaker icon on a card, Mntra hands the text to your Android system's text-to-speech engine. Some system TTS engines may fetch voice data or telemetry; that's out of Mntra's control — check your system TTS settings.
Notifications. Mntra can send you a daily local notification when cards are due. The notification is generated on your device from your own data; nothing is sent over the network.
Archive files. When you export a deck, Mntra writes a .mntra archive into your chosen location (e.g. your Downloads folder) or to the share sheet. Importing a .mntra archive reads it back in. Files are only read or written when you explicitly tap Export or Import.
Mntra uses Sentry to capture app crashes and a small number of non-fatal failure events (e.g. an AI provider returning an unparseable response). Crash reports include device model, Android version, app version, and the stack trace of the crashing thread. They do not include the contents of your cards, decks, audio, images, your API key, or any text you typed.
A scrubber strips known PII fields (URLs, query parameters, headers) before any event leaves your device. Sentry data is processed by Sentry, Inc. (or its EU-region instance, depending on configuration) under their privacy terms.
Mntra has optional AI-assisted features that you can unlock by entering your own API key for one of the supported providers (Google Gemini, OpenAI, Anthropic, Mistral). When you enable these features, the app contacts the provider directly from your device.
The following data is sent to the provider only when you actively trigger the feature:
What is sent is exactly what the provider needs to compute a response. Nothing else from your device is sent. Each request is HTTPS-direct between your phone and the provider; we do not run a backend that intercepts or stores it.
The data you send is governed by the provider's privacy and data-use policies, which apply to your account with them, not to the developer of Mntra:
Your API key is stored locally in encrypted shared preferences (AES-256 GCM) on your device and is never sent anywhere except to the provider you configured it for.
Mntra integrates with Sentry (for crash reporting) and with the AI provider you optionally configure. Both are described above. The app uses Google's open-source Android libraries (AndroidX, Jetpack Compose, Room, WorkManager) locally on device; these do not transmit data.
Mntra does not target children under 13 and does not knowingly collect data from any user.
All Mntra data lives in the app's private storage on your device. You can delete everything at any time by uninstalling the app; Android removes the app's private directory on uninstall. There is no cloud copy on our side to delete. Crash reports retained by Sentry expire per Sentry's retention defaults; reach out via the contact below to request deletion.
If this policy changes, the updated version will be published at this URL and the “Last updated” date at the top will change.
Questions about this policy: support@devls.tech
See also: Terms of Service