This Privacy Policy explains how Oar ("Oar", "the app", "we", "us") handles information when you use the Oar Android application. Oar is developed and maintained by an independent developer, Ridill.
Oar is built around a simple principle: your financial data stays on your device by default. The sections below describe exactly what data exists, where it lives, and what — if anything — ever leaves your phone.
Oar does not require an account, does not show ads, has no in-app purchases, and does not sell or share your personal data. All of your transactions, budgets, and other financial records are stored only in a local database on your device unless you explicitly turn on Google Drive backup.
Data Oar Stores Locally, On Your Device
Oar stores the information you enter to use the app in a local database on your device. This includes:
- Transactions (amount, currency, note, date/time, type, tags, folders)
- Budget cycles and spending limits
- Scheduled/recurring payments and reminders
- Tags, folders, and currency preferences
This data never leaves your device unless you turn on the optional Google Drive backup feature described in Section 3. Android's own automatic device backup is also disabled for Oar, so this data is not silently copied anywhere by the operating system either. Uninstalling the app permanently deletes this data from your device.
Optional: Sign in with Google
Signing in is never required to use Oar — you can skip it entirely during setup and use every core feature of the app without an account. Signing in exists solely to authorize the Google Drive backup feature described below.
If you choose to sign in with your Google account, Oar receives:
- Your email address
- Your display name
- Your profile photo URL
This information is used only to identify your backup file in Google Drive and is not sent to any server other than Google's own (via Firebase Authentication). You can sign out, or delete your linked account, at any time from Oar's Settings screen.
Optional: Google Drive Backup
Oar includes an optional backup feature. If you turn it on and choose a backup password:
- Oar creates an encrypted copy of your local database, protected with the password you choose.
- Only a cryptographic salt used to verify your password is stored alongside the backup — your password itself is never stored or transmitted anywhere.
- The encrypted file is uploaded to a private, hidden storage area of your own Google Drive account called the "app data folder." This space is invisible in your normal Drive file list and cannot be accessed by any app other than Oar, including by the Oar developer.
- Restoring a backup downloads that same file from your Drive and decrypts it locally, on your device, using the password you provide.
Nobody other than you — not even the Oar developer — can read the contents of your backup without your backup password. See Google's Privacy Policy for how Google Drive and Google Sign-In handle data on their end.
Optional: Automatic Transaction Detection from SMS
Oar can optionally read incoming SMS messages to automatically detect and pre-fill bank transaction alerts. This feature is:
- Off by default. It is only activated if you explicitly grant SMS permission and enable it during onboarding or in Settings.
- Processed entirely on your device. When enabled, Oar inspects incoming messages from recognized bank/payment senders, extracts the transaction amount, type, and note using on-device pattern matching, and discards the raw message text immediately afterward.
- Never transmitted or stored as raw text. Only the extracted transaction fields (amount, note, date, type) are saved to your local database, in the same way as a transaction you enter manually. The original SMS content is not saved to Oar's database, not uploaded to Drive, and not sent to us or any third party.
You can disable this feature at any time from Settings, which also revokes the app's use of the SMS permission going forward.
Diagnostic Data (Crash Reporting)
Oar uses Firebase Crashlytics to help us find and fix bugs. If the app crashes or encounters an unexpected error, technical diagnostic information is sent to Firebase, including:
- The error/exception type and stack trace
- Device model, OS version, and app version
- An anonymous, randomly generated installation identifier (not linked to your name, email, or Google account)
This diagnostic data does not include your transactions, budgets, backup password, or other financial information you've entered into the app.
Oar also uses Firebase Remote Config to remotely toggle features (for example, temporarily disabling the SMS auto-detection feature) and to update the text-matching patterns used for SMS parsing described in Section 4. This only sends configuration to your device — it does not transmit any of your personal or financial data.
Data We Do Not Collect
To be explicit about what Oar does not do:
- No advertising or ad-tracking SDKs of any kind
- No in-app purchases or payment processing
- No access to your contacts, call log, location, camera, or microphone
- No behavioral analytics, no event tracking, no third-party marketing pixels
- No sale or sharing of personal information to third parties for advertising purposes
Third-Party Services
Oar relies on the following third-party infrastructure providers, all operated by Google:
| Service | Purpose | Data involved |
|---|---|---|
| Firebase Authentication | Optional Google Sign-In | Email, name, profile photo (only if you sign in) |
| Google Drive API | Optional encrypted backup/restore | Your encrypted backup file (only if you enable backup) |
| Firebase Crashlytics | Crash & error diagnostics | Stack traces, device/app info, anonymous install ID |
| Firebase Remote Config | Feature flags & SMS parsing patterns | None (config is delivered to the device, not collected from it) |
These providers act as data processors on our behalf and are bound by Google's own privacy and security commitments. See Google's Privacy Policy and Firebase's data processing terms for details.
International Data Transfers
Because Firebase and Google Drive are operated by Google, diagnostic data and any backup you choose to create may be processed on servers located in the United States or other countries where Google operates infrastructure. Google maintains its own safeguards for cross-border transfers (including standard contractual clauses), described in Google's Privacy Policy.
Data Retention
- Local app data is retained on your device until you delete it in-app or uninstall Oar.
- Google Drive backups are retained in your Drive account until you delete them (see Delete My Data) or revoke Oar's Drive access.
- Crash diagnostic data is retained by Firebase Crashlytics per Google's standard retention window (currently up to 90 days), after which it is automatically deleted.
Your Privacy Rights
If you are in the European Economic Area or United Kingdom (GDPR)
You have the right to:
- Access the personal data we (via our service providers) hold about you
- Correct inaccurate data
- Request erasure of your data
- Restrict or object to certain processing
- Receive a copy of your data in a portable format
- Withdraw consent at any time, without affecting processing carried out before withdrawal
- Lodge a complaint with your local data protection supervisory authority
Where Oar processes data based on your consent (Google Sign-In, Drive backup, SMS auto-detection), that consent is optional and can be withdrawn at any time from within the app. Diagnostic crash data is processed under our legitimate interest in keeping the app reliable and secure.
If you are a California resident (CCPA/CPRA)
You have the right to:
- Know what personal information is collected, used, and disclosed
- Request deletion of your personal information
- Correct inaccurate personal information
- Opt out of the sale or sharing of personal information — Oar does not sell or share personal information, so there is nothing to opt out of
- Not be discriminated against for exercising any of these rights
To exercise any of the rights above, see Delete My Data or contact us using the details in Section 13.
Children's Privacy
Oar is a general-purpose personal finance tool and is not specifically directed at children. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information (for example, by signing in with a Google account), please contact us and we will delete it.
Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes to the app or applicable law. The "Effective date" at the top of this page will always reflect the latest revision. Material changes will be noted in the app's release notes where practical.
Contact Us
If you have questions about this Privacy Policy, or want to exercise any of the rights described above, contact the developer using the details below.
Contact the developer
Ridill — Oar developer
Email: ridillperson+oarsupport@gmail.com
Source code: github.com/remi-naz/Oar