Bleedy Privacy Policy

Bleedy stores the following information in local app storage on your device:

• Subscription names, amounts, currencies, billing intervals, and billing dates.
• Trial, active, cancelled, paused, or archived status where applicable.
• Reminder configuration and device-local notification identifiers.
• Cancellation, restore, edit, and related action history.
• Projected and realized avoided-spend records.
• Base-currency preference and rebuildable exchange-rate cache.
• Onboarding completion state.

Ideal Lab does not operate an account-based Bleedy cloud database that receives these subscription records.

The current Bleedy release does not require a user account. It does not include an advertising SDK, a product analytics SDK, or cross-app / cross-site tracking code.

When currency metadata or exchange rates are refreshed, Bleedy sends HTTPS requests to api.frankfurter.dev. A rate request may include your selected base-currency code so the service can return the requested public exchange-rate data.

Bleedy does not send subscription names, subscription amounts, cancellation history, savings-ledger entries, or backup contents to Frankfurter.

Frankfurter states that its API does not collect personal data, while its public service is delivered behind Cloudflare, which may process ordinary technical request information. See the provider's current information at frankfurter.dev.

Bleedy uses your device operating system to schedule local subscription reminders. Notification permission status and scheduled notification identifiers are handled on the device. Bleedy does not require an account-based remote push-notification service for these reminders.

A Bleedy backup is created only when you choose Export Backup. The current backup is a JSON file created locally on your device and is not encrypted.

Bleedy then opens the operating system share sheet. If you choose a cloud drive, messaging service, email provider, computer, or another destination, that destination handles the file under its own terms and privacy policy. Ideal Lab does not receive a server copy of the backup through Bleedy.

When you import a backup, Bleedy reads the selected file locally, validates its schema and checksum, shows a preview, and writes restored data only after you confirm the restore.

Core Bleedy records remain in local app storage until you change or delete them, restore another backup over them, or remove the app. Operating-system backup or migration behavior may vary by platform and device settings.

Backup files exported outside Bleedy are separate copies. Removing Bleedy does not delete those external files; delete them from the location where you saved them when you no longer need them.

The current Bleedy release does not sell your subscription records and does not use them for third-party advertising or cross-app / cross-site tracking.

If Bleedy's data behavior changes, this policy and the relevant app-store privacy disclosures will be updated before or with the release that introduces the change. The effective date at the top of this page will also be updated.