Breadly – Privacy Policy

On-device data may include accounts, categories, budgets, activities, and transactions.

Data is stored locally on your device using SQLite and is not transmitted to our servers unless cloud sync is enabled.

We do not collect advertising identifiers. Crash reports are collected in every mode, including local-only mode, as are pseudonymous performance metrics that record app launches and the screens you open but not what you enter — see Diagnostics & Error Monitoring and Performance Metrics below.

Local-only data can be permanently lost due to sign-out, uninstall, device loss/theft, factory reset, clearing app data, storage corruption, app/OS failures, or user error.

We cannot recover local-only data under any circumstances. You are solely responsible for backups and verification of local records.

Authentication is provided via Clerk. You can sign in with Apple or with Google, on both iOS and Android.

When you sign in with Google, we receive your name, email address, and authentication identifiers from Google. We do not receive your Google password.

When you sign in with Apple, we receive an authentication identifier and the email address Apple shares with us — your own, or a private relay address if you choose to hide yours — and your name if you choose to share it. We do not receive your Apple Account password.

Minimal account metadata is stored to operate login and manage your session, including your device's time zone setting, which Clerk records when your account is created and each time you sign in.

Expense data remains local unless sync is enabled.

Subscription purchases are processed by Apple App Store or Google Play and validated via RevenueCat.

We do not store full payment card details.

Purchase metadata (product ID, entitlement status, transaction ID) may be processed to validate access.

If enabled, synced data (for example accounts, categories, budgets, activities, and transactions) is transmitted to cloud infrastructure via PowerSync (sync engine) and stored in a PostgreSQL database hosted by PlanetScale (United States).

Synced data may be accessed and managed from Ukraine for operational purposes such as support and debugging.

Synced data is used solely to provide synchronization and backup across your devices.

The app stores your default currency preference and per-account currency selections.

Exchange rate data is fetched from third-party currency data providers and stored server-side to support multi-currency conversions and display.

Exchange rates are provided for informational and convenience purposes only. Rates may be delayed, incomplete, or inaccurate and should not be relied upon for financial decisions.

Currency preference data follows the same storage model as other app data: local-only unless cloud sync is enabled.

We use Sentry for crash reporting and diagnostics.

When you are signed in, Sentry error reports are linked to your account identifier, email address, and name.

If your session expires, Sentry error reports stay linked to your account identifier until you sign in again or erase the data on this device, including while you keep using the app on this device. Until the app next restarts, they may also stay linked to your email address and name.

Sentry reports, and the short app-session records Sentry uses to measure how often the app crashes, also carry random identifiers for your app installation and app session. These are not linked to your account, name, or email unless you are signed in or your session has expired as described above.

Sentry may record your IP address, and the approximate location it derives from it, with error reports and app-session records in every mode, whether or not you are signed in.

Unhandled application errors, and errors that make the app show its error screen, are also recorded by Expo's EAS Observe service: the error type, message, and stack trace.

If the app crashes in its native code, a crash report is also sent to EAS Observe on a later launch: the exception or signal type, the error message or the operating system's termination reason, and, where available, up to 50 frames of the native stack trace, normally the crashing thread's. On iOS the report comes from Apple's MetricKit and also carries the technical details needed to read that stack trace: the names and build identifiers of the app and system code it passes through, the number of threads, and, for a crash caused by an invalid memory access, a description of the memory region involved. On Android it comes from the app's own crash handler and the system's record of why the app exited.

These EAS Observe reports are associated with the same random installation and app-session identifiers as the performance metrics below, not with your account, name, or email. Because they share the session identifier, an error can be placed in the sequence of screens opened in the session where it occurred.

Sentry reports include device and app information (such as device model, OS version, memory, storage and battery state, network connection type, language and time zone settings, app version, and installed update) and a short trail of technical events from before the error: app lifecycle and system events (for example the app moving to the background, the keyboard opening, low memory, or a change in network connectivity); on iOS, the title of each screen shown and the kind of control tapped (with the fixed caption of a native button, such as "Save"); the web address without query parameters, method and status code of the app's network requests; diagnostic log messages written by the app and the libraries it uses; and app update checks.

Used only for troubleshooting and improving stability.

Crash reports do not include what you type or your financial data: no transactions, account or category names, amounts, or balances.

We use Expo's EAS Observe service to collect pseudonymous app performance metrics, such as app launch time, time to first render, time to interactive, and screen navigation timings.

Alongside these timings, technical metadata is collected: device model, OS version, app version, update and runtime version, network connection type and whether it is metered or limited by Low Data Mode (iOS) or Data Saver (Android), device thermal state, battery level and charging state, low-power mode, slow and frozen frame counts and total frame-freeze time, how long each stage of app startup took and whether the launch screen reached its time limit, a summary of the network requests the app makes while it starts up (how many there were and how many failed, bytes sent and received, total time and overall download speed, plus the hostname, response status code, duration, time until the first byte of the response arrived and bytes received of the slowest one), and your device's language/region setting.

Screens are identified by their route pattern (for example "/transactions/[id]") — never by the specific record you opened.

Navigation metrics also carry the non-identifying options a screen was opened with — for example whether the categories view was showing income or expenses, or which kind of account was being created. Parameters that name a specific record are removed before the metric leaves your device, and the resolved screen address is dropped along with them.

Because each navigation metric names the screen and the app session it belongs to, these metrics also record how the app is used: which screens were opened, in what order, and when. This is the product interaction data listed in our App Store and Google Play privacy disclosures.

Metrics are associated with a random identifier the app creates for its installation and a random identifier for each app session; neither is linked to your account, name, or email. The installation identifier is the device identifier listed in our App Store and Google Play privacy disclosures. It is not an advertising identifier and is not used to track you across other companies' apps or websites.

No personal or financial data, and no screen contents, are included in performance metrics.

Used to measure and improve app startup, navigation performance, and stability, and to understand in aggregate how the app's screens are used (for example, how often a screen is opened). Not used for advertising or to build a profile of you.

If you use CSV import, selected CSV files are processed to create categories or transactions.

Imported data follows the same storage model as manually entered data: local-only unless cloud sync is enabled.

You are responsible for reviewing imported data accuracy before relying on it.

The app may receive over-the-air (OTA) updates that do not require a separate app store download.

Update checks and downloads transmit technical metadata such as platform, runtime version, release channel, and the identifiers of installed updates, together with the same random installation identifier used for performance metrics, to Expo's EAS Update service.

To tell you when a new store version is available, the app asks the App Store (iOS) or Google Play (Android) for the latest version of Breadly. On iOS this sends only the app's App Store identifier to Apple's public lookup service, which, like any server, receives your device's IP address.

Updates may modify app functionality, fix bugs, or change features. Continued use of the app after an update constitutes acceptance of any changes.

Certain features may be labeled "Early Access" or "Beta" and made available to a limited group of users.

Data generated or processed by early access features follows the same storage model as other app data (local-only unless cloud sync is enabled).

Early access features may change, be removed, or behave unpredictably. Data created during early access may be affected if a feature is modified or removed.

Transaction attachments (receipt images and voice memos) are a planned feature. The current app does not record audio, take photos, or attach files to transactions, and it requests no camera or microphone permission.

If and when attachments are launched, they will be stored locally by default and follow the same sync behavior as other data when cloud sync is enabled, and they will not be transcribed or processed by AI unless you explicitly use a planned AI feature (see Planned AI Features below).

You will be able to use Breadly without recording or attaching anything. This Privacy Policy will be updated before attachments are launched.

Planned features include AI-powered receipt scanning via photo, voice-to-text input for transaction entry, AI-assisted categorization, budgeting suggestions, and spending insight tools.

These features are currently inactive and no AI provider processing occurs unless and until such features are launched and enabled by you.

If and when enabled, relevant content (such as receipt images or audio recordings) may be processed by third-party AI providers, potentially in the United States or other jurisdictions.

AI processing may occur on-device, in the cloud, or a combination of both, depending on the feature and implementation.

AI features will be optional. You will be able to use Breadly without enabling them.

AI outputs may be inaccurate and must be reviewed by you before use.

Before activation, we will update this Privacy Policy and required store privacy disclosures to reflect the live data flows.

Advertising is currently not active.

If advertising is enabled in a future release (for example for non-subscribers), third-party advertising providers may collect device identifiers, advertising ID, IP address, and limited usage data.

Where required (such as EU/EEA), consent will be requested before enabling personalized ads.

On iOS, any tracking activities will require ATT permission before tracking occurs.

Before activation, we will update this Privacy Policy and required store privacy disclosures to reflect the live advertising data flows.