Privacy Policy

Breeze moves files between devices without sending them through our servers. This policy lists the data that does leave your device or reaches us through this website, why, who handles it, and how long it is kept.

Last updated: 25 September 2026

The short version

Who is responsible

Simply Fluent OÜ, registry code 16344322, Sepapaja tn 6, 15551 Tallinn, Estonia, makes Breeze and is the controller of the personal data described here. For anything about this policy or your data, email privacy@breezeit.app.

Data that stays on your device

Files you send go directly from one device to the other over your local network. We never receive them.

Device names, trusted and blocked devices, transfer history, and vaults are stored on your devices only. The one exception is under "The license service" below: seat nicknames, encrypted with a key only your devices hold.

Data the app sends off the device

Crash reports (Sentry). When the app crashes or hits an unexpected error, it sends a report to Sentry, in the United States. The report contains where in the code the error happened, the device model, OS version, app version, and a random ID the Sentry library creates for the installation, so we can tell one device crashing often from many devices crashing once. It contains no file names, file contents, or device names, and Sentry does not store your IP address. Crash reports are always on. We rely on our legitimate interest in keeping the app working.

App analytics (TelemetryDeck and Umami), only if you turn them on. Analytics are off by default. If you turn them on in Settings, the app sends usage events, such as the app opening or a device being trusted, to TelemetryDeck in Germany and to our own Umami server. Each event carries the app version, platform, OS version, device model, screen size, language, region, whether Pro is active, a random ID for the session, and a one-way hash of a random ID created for this installation. Events never carry file names or device names. Turning analytics off stops the events and deletes the installation ID. We rely on your consent.

Purchases in the App Store and Google Play. Apple or Google handle the payment, and we never see your payment details, name, or email. RevenueCat, in the United States, checks that the purchase is valid and keeps subscriptions current. It receives the store receipt, a random ID your device creates for purchases, and technical details such as the platform and app version. We never send RevenueCat your name, email, or anything about your files. We rely on the contract with you.

Purchases on breezeit.app and in the Windows app. These go through a checkout run by RevenueCat and Stripe, both in the United States. The checkout asks for your email and payment details. Stripe processes the payment, and RevenueCat records the purchase so our license service can check it. We use these records to handle refunds and support requests, never for marketing. We rely on the contract with you and on our legal duty to keep sales records.

The license service. When Pro is shared with other devices through seats, or a recovery phrase is set up, our license service at breezeit.app stores the license: its plan, status, and expiry date, the store transaction ID, the random purchase ID, and a salted hash of the recovery phrase. For each seat it stores a random device ID, the platform, when the seat was claimed and last used, and the device nickname encrypted with a key only your devices hold. We cannot read the nicknames. The service stores no name, email, IP address, or payment amount. We rely on the contract with you: this is what makes Pro work on the devices you choose.

Feedback you send from the app. If you send feedback, we receive your message, any screenshots you attach, the platform, app and OS version, device model, language, region, and whether Pro is active. Your name and email are included only if you enter them. Feedback is stored with Cloudflare and forwarded to a Telegram chat we use for notifications, so we can read and answer it. We rely on our legitimate interest in answering you and improving Breeze.

Breeze Anywhere (testers only). Anywhere sends files between devices on different networks. When the two devices cannot connect directly, the encrypted connection passes through our relay server at Hetzner in Germany. The relay sees the IP addresses of both devices and how much data passes, and cannot read the files or their names. Anywhere is available only to invited testers.

Update checks (Windows). The Windows app checks updates.breezeit.app for new versions. Cloudflare, which hosts the files, sees your IP address and the app version with each check.

This website

The site uses Umami, on our own server, and TelemetryDeck to count page views, referrers, browser types, and countries. Neither sets cookies. TelemetryDeck keeps a random ID in your browser storage and sends a hash of it, so a returning visitor is counted once. We rely on our legitimate interest in knowing how the site is used.

Downloads. When you download an app from this site, we record the platform, your country, your browser's user agent, and any campaign tags in the link, to count downloads by source.

Signups and email updates. If you sign up, we store your email, the devices you listed, your language, and your country, taken from your IP address, which we do not store. We send email through Listmonk, on our own server at Hetzner in Germany, and Resend, in the United States. Every email has an unsubscribe link. We rely on your consent.

Surveys. Survey answers are stored with your language and country. An email is stored only if you enter one. We rely on your consent.

Contact messages. If you use the contact form, we store the topic, your email, your name if you give one, the message, your language, and when you sent it. We email the message to our own inbox through Listmonk, and your address is added to no mailing list. The notification to our Telegram chat carries only a reference code, the topic, and your language. We need this to answer you. We rely on our legitimate interest in answering messages sent to us.

Signups, survey answers, and feedback also send a notification to a Telegram chat we use. Signup notifications show a shortened email, never the full address.

Services that handle data for us

Cloudflare (hosting, the license service, website forms, feedback), Sentry (crash reports), TelemetryDeck (analytics), RevenueCat and Stripe (purchases), Hetzner (our servers for email and the Anywhere relay), Resend (email delivery), Google Workspace (our email inbox), and Telegram (notifications to us). Apple and Google handle store purchases under their own privacy policies.

Data outside the EU

Cloudflare, Sentry, RevenueCat, Stripe, and Resend are based in the United States. When they receive personal data from the European Economic Area, the transfer relies on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses in their data processing terms.

How long data is kept

Your rights

You can ask to see, correct, delete, or export your personal data, restrict or object to how we use it, and withdraw consent at any time. Breeze has no accounts, so tell us something that lets us find the data, such as the email you used or a purchase receipt.

You can also complain to a data protection authority, such as the Estonian Data Protection Inspectorate or the one where you live.

Permissions the app requests

Children

Breeze is not directed at children under 13. We do not knowingly collect data from children.

Changes to this policy

If we make material changes, we will update the "Last updated" date above and, where appropriate, notify you in the app.

Contact

For any question about this policy or your data, email privacy@breezeit.app.