BaynaAvailability

Last updated: 2026-07-02

Privacy Policy

Bayna is designed for private expense tracking from bank alerts without requiring bank account login. This policy explains the data Bayna uses, why it is used, and which launch decisions still need final release verification.

Developer and Privacy Contact

Developer: Tiny Foundry.

Privacy contact: privacy@usebayna.com.

Support contact: support@usebayna.com.

What Bayna Is

Bayna helps organize transaction information for personal review. Bayna is not a bank, wallet, lender, payment service, credit product, investment advisor, tax advisor, or accounting service.

Data Bayna Uses

Bayna may use the following data to provide app functionality:

  • Bank SMS and bank notification content, when you grant the relevant Android permissions, to detect transaction-like alerts.
  • Transaction records created from alerts or manual entry, such as amount, currency, date, merchant or counterparty label, category, budget context, notes, source type, and review metadata.
  • Source metadata, such as sender/app labels, hashed source identifiers, timestamps, and source type, to help avoid duplicate imports and explain where a transaction came from.
  • Category and budget settings that you create in the app.
  • Google account identity and Google Drive app-data files when you choose to connect Google Drive backup.
  • Local notification permission status and app-owned notification identifiers when Bayna shows transaction action notifications.
  • Support and privacy emails that you send to Tiny Foundry.

Bayna should not use raw SMS or notification text as public-facing transaction content. The release build must be checked before publication to confirm exactly which source metadata, hashes, logs, diagnostics, and backup fields are stored.

How Bayna Uses Data

Bayna uses data to:

  • Detect transaction-like alerts from sources you choose.
  • Create and display a spending timeline.
  • Let you review, edit, categorize, budget, and delete transactions.
  • Prevent the same imported source from being added again after deletion.
  • Back up and restore your Bayna data when you choose Google Drive backup.
  • Respond to support, privacy, deletion, and accessibility requests.
  • Maintain app reliability and comply with app store or legal obligations.

Bayna does not use SMS, notification, or financial data for advertising.

Permissions

Bayna asks for permissions only when they support a feature you choose:

  • SMS permissions let Bayna read bank SMS alerts for expense tracking.
  • Notification access lets Bayna read selected bank or wallet app notifications for expense tracking.
  • Notification permission lets Bayna show app-owned transaction alerts and actions.
  • Google Sign-In and Google Drive app-data access let Bayna create, list, restore, and delete Bayna backups in your Google Drive app data.

You can skip automation and track manually. You can also change permission choices later from Android settings and Bayna settings where supported.

Google Drive Backup

If you connect Google Drive backup, Bayna uses the Google Drive appDataFolder scope. Backup files are stored in private app data for the Google account you choose. They are hidden from My Drive and are not stored on Bayna servers.

You can disconnect Google access in Bayna, revoke access from your Google Account, and delete Bayna Drive backups from the app where the delete action is available.

Bayna's use of Google user data is limited to providing backup and restore functionality. The OAuth consent screen, Drive scope wording, and any Google API Services User Data Policy requirements must be reviewed before public launch.

Third-Party Services

The current inspected app dependencies include Google Sign-In, Google APIs, Google API authentication, local notifications, Drift local database support, and related Flutter packages.

Firebase Analytics, Firebase Crashlytics, and Google Play Billing are planned launch decisions, but they were not present in the inspected pubspec.yaml at the time this policy was prepared. If those services are added to the release build, this policy, Google Play Data Safety, and App Store privacy details must be updated before publication.

Data Sharing and Sale

Bayna does not sell personal data. Bayna does not share SMS, notification, or transaction data with advertising networks.

Data may be shared with service providers only when needed for features you choose, such as Google account and Drive services for backup. Support emails are handled through the email systems used by Tiny Foundry.

Website Privacy

This website is intended to be a static marketing and support site. No website analytics, advertising pixels, cookies, or attribution scripts were identified in the inspected source. Deployment-provider analytics or externally added scripts must be checked before publication.

Retention and Deletion

Data stored on your device remains until you edit, delete, reset, uninstall, or otherwise remove it through app or operating-system controls. Drive backups remain in Google Drive app data until you delete them or revoke/remove access through Google controls.

Support and privacy emails may be retained as needed to respond to your request, maintain records, comply with obligations, and protect the service.

See the Data Deletion page for deletion steps.

Your Choices

You can:

  • Use Bayna manually without SMS or notification automation.
  • Change Android permissions from system settings.
  • Delete transactions and categories in the app where supported.
  • Delete local app data by using app reset or operating-system app data controls.
  • Delete Bayna Google Drive backups where supported.
  • Contact privacy@usebayna.com for privacy questions or requests.

Changes

This policy will be updated when Bayna's data practices, SDKs, permissions, or support contacts change.