Last updated: 30 October 2026
Privacy Policy
Aura SMS is a privacy-first Android SMS organizer. This Privacy Policy explains how Aura SMS handles information when you use the Aura SMS mobile application and website.
Summary
Aura SMS is designed to process personal SMS content on your device. We do not sell message content or use SMS content for advertising. Core SMS organization runs locally. The app also sends usage and diagnostic information to Google through Firebase Analytics and Crashlytics, as described below. Online AI summaries, when available and requested, are a separate feature.
Information the App Accesses
- SMS and MMS data: message body, sender, timestamp, read state, thread information, delivery state, and message type when Aura SMS is used as the default SMS app.
- Notification data: local notification content needed for message alerts, OTP banners, and reminder cards.
- Financial message details: transaction amount, merchant, bank name, balance, due date, or card due details parsed locally from SMS messages.
- App settings: themes, rules, blocked keywords, cleanup preferences, templates, and local user preferences.
- Backup data: if backup is enabled, encrypted app data may be prepared for user-controlled backup and restore.
How Information Is Used
Information is used to provide core messaging features, categorize the inbox, extract OTPs, build reminders, show finance summaries, apply rules, send messages, restore data, prevent spam, and improve app reliability.
Local Processing
Classification, OTP extraction, finance parsing, reminder detection, and rule automation are designed to run locally on the device. These core processing functions do not require uploading personal SMS content. If you request an online AI summary and the feature is configured with a valid API key, the selected message body and sender, or recent conversation messages and sender, are sent to Google's Gemini service to generate the summary. When online summarization is unavailable, the app uses a local fallback. This message-content transfer is separate from Firebase analytics.
Google Analytics for Firebase
We use Google Analytics for Firebase to understand app usage, improve features, and measure the performance of SMS categorization and OTP detection. Usage and diagnostic data are transmitted to and processed by Google; they are not stored only on your device.
- Automatically collected data: app-instance identifiers, app version, device and operating-system information, language, session and engagement information, and approximate location derived from network information. These identifiers can distinguish installations and are not the same as fully anonymous data.
- App events and preferences: screens viewed, tabs selected, and settings such as the selected theme, default-SMS status, and OTP auto-delete preference. Depending on the feature used, events may also describe categories, counts, success/failure states, and whether an AI summary was generated online or locally.
- SMS and OTP processing metadata: message category, parsing time, whether a message contains an OTP or transaction, SIM slot index, OTP length and format, generic detection keywords or methods, message-length ranges, and OTP-copy actions and timing. Sender addresses are converted into generic sender-type categories before being included in these events.
The app's custom analytics events do not include raw message bodies, actual OTP digits, contact names, full sender or recipient phone numbers, transaction amounts, or the text you type into search. The app manifest removes advertising-ID permissions. Analytics still uses app-instance identifiers to measure usage.
Firebase Crashlytics
We use Firebase Crashlytics to diagnose crashes and non-fatal errors and improve reliability. Reports may include installation/session identifiers, device model and operating-system details, app version, crash times, stack traces, exception messages, and diagnostic logs or breadcrumbs such as the current screen, active tab, app settings, and generic OTP-processing results. The app does not intentionally add message bodies or OTP digits to these diagnostic logs.
Google Services and International Processing
Google receives analytics and crash-reporting data as a service provider. Data may be processed on Google's infrastructure outside your country. For details, see Google's Privacy Policy, Firebase Privacy and Security, and Google Analytics data collection. Online summaries are also subject to the Gemini API terms.
Sharing
We do not sell personal information. We do not share SMS content with advertisers. We share usage and diagnostic data with Google for analytics and crash reporting as described above. Message content may be sent to Google when you request an available online AI summary. Other disclosures may occur to provide a user-requested feature, comply with law, protect users, or complete a backup/restore action selected by the user.
Retention and Deletion
Messages and parsed records remain on the device until deleted by the user, removed by an automation rule, cleared through app settings, or removed by Android/system storage behavior. OTP cleanup can delete older OTP messages based on user preferences.
Analytics data is retained according to the retention settings of our Google Analytics property and Google's applicable service policies; aggregated reports may be retained separately. Firebase states that Crashlytics keeps crash traces and associated identifiers for 90 days before starting removal from live and backup systems. Deleting local app data or uninstalling does not automatically delete analytics or crash reports already transmitted to Google. Contact us with privacy or deletion requests; our ability to locate a report may be limited because we do not attach your phone number or an account identity to these events.
Security
Aura SMS uses Android platform permission controls, local Room database storage, default-SMS role checks, and minimized data handling. Backups, when enabled, should use encryption before transfer or restore.
Children
Aura SMS is not intended for children under 13. Users should comply with local age and consent requirements.
Your Choices
- You can decline permissions, but SMS organizer features may not work.
- You can remove Aura SMS as the default SMS app in Android settings.
- You can delete messages, rules, reminders, and local app data from the app or Android settings.
- The current app version does not provide an in-app switch to disable Firebase Analytics or Crashlytics. Removing SMS permissions or changing the default SMS app does not by itself turn off telemetry. Uninstalling stops future collection by the app but does not remove data already sent.
- You can choose not to request online AI summaries.
- You can contact us for privacy questions at privacy@aurasms.pro.
Contact
Privacy contact: privacy@aurasms.pro
Website: https://aurasms.pro