On this page

Bridge Loop Privacy Policy

Last updated: 21/10/2026. Data controller: Eduardo Figueiredo dos Santos. Privacy contact (data protection officer): suporte@bridgeloop.app.

1. In one sentence

Bridge Loop does not collect, transmit to us, or store on our servers any of your data (we have no servers for that). It only links your Android phone to your Mac over your own network, Bluetooth, or cable, with end-to-end encryption between the two devices. There are no accounts, ads, or usage analytics. Nothing goes to the internet or the cloud, and nothing is sold.

2. What the phone app (Android) accesses, and why

Everything below travels only between your paired phone and Mac, never through a server of ours:

Data	Why	Android permission
Screen image and app sound	to mirror the screen on your Mac	screen capture (you approve each start, or for up to 30 min) and microphone (only to capture app sound; Bridge Loop does not record your voice). Nothing is recorded: the video just passes to the Mac window
Taps and text coming from the Mac	to control your phone with your Mac’s mouse and keyboard	Accessibility service: injects the taps, scrolling, typing, and Back, Home, and Recents buttons that you perform in the Mac window. To apply text edits, it reads the text of the field where the cursor is. Bridge Loop does not read other apps’ content for any other purpose, never acts on its own, and does not work without a connected paired Mac
Notifications (app name and icon, title, text, action buttons)	to show them on your Mac, and to reply to and dismiss them	Notification access. You choose which apps. Bridge Loop does not store the content
List of apps with a launcher icon (app name and identifier, no icon)	to build the “apps that notify your Mac” list	no extra permission
Clipboard text	copy on one device, paste on the other	the Mac sends what you copy on it (if the option is on); on the phone, the app notices when you tap “Copy” through the Accessibility service and, since Android only lets an app read the clipboard while it is in the foreground, the service uses an invisible 1-pixel window (created by the Accessibility service) to be able to read the copied text even when the app is in the background; or you use “Send what I copied”. Text flagged as sensitive (password managers) is never sent
Files you choose to send	to transfer between the devices	your choice, at that moment (drag on the Mac; “Send files to Mac” or Share on the phone)
Device name, battery level, app version, screen state (on/off)	to show status on the Mac, flag updates, and save battery	none
Bluetooth, Wi-Fi, and local network	to find the Mac and connect	Nearby devices, Local network
App notice (ongoing notification) and start with the phone	to keep the connection ready	the app’s own notification permission; you turn “Start with the phone” on or off in Settings

3. What the Mac app accesses

Local network and Bluetooth, to find and connect to your phone. The phone announces itself on your local network (Bonjour) and the Mac looks for it there.
The phone’s image and sound, to show in the mirroring window (not recorded), and the clicks and keyboard you use in that window, to send to the phone.
Phone notifications, to show them as Mac notifications (macOS notification permission). Bridge Loop does not keep their content, but macOS stores notifications in the Notification Center on the Mac, under the system’s own rules and retention; to erase them, clear the Notification Center.
The Mac’s clipboard text, to send to the phone, except what password managers mark as confidential. You can turn the option off in Settings.
Files you drag to send; received files go to Downloads/Bridge Loop.
Installing the app on the phone by cable: the Mac runs Android’s adb tool locally; none of it goes through the internet.

4. What is stored, and where

Only on your own devices: each device’s identity key (in the macOS Keychain and the Android Keystore), the list of paired devices, your settings, received files, and the connection log (section 6). Also the license key (in the macOS Keychain; a copy in the Android app’s private storage, outside backups), the free trial start date and the latest date the Mac has seen (only in the macOS Keychain), and the most recent list of revoked licenses the device knows. The Android app turns off Android backup (allowBackup off), so the identity and pairings do not go into cloud backups.

5. Security

Connection uses ECDH P-256, HKDF, and AES-256-GCM; the two devices authenticate each other with their own keys, and pairing requires the same 6-digit code on both. The Mac’s identity key lives in the Keychain and the phone’s in the Android Keystore. The protocol is new and has not yet had an independent external audit (there was an internal security review in October 2026).

6. Logs

Each device keeps a local log of connection events (time, connection type, reason for a drop) for diagnostics. It includes the Mac’s and the phone’s name and the local-network IP addresses used in the connection. It contains no message, notification, or clipboard content and no pairing codes. It leaves the device only if you copy the diagnostics and send them to someone.

7. Purchases, free trial and license

Free trial: the start date (and the latest date the Mac has seen, to notice a clock set back) is stored only on your Mac (Keychain). We do not send those dates to anyone.
Payment: processed by Google Play (or Apple, if the app is ever there). We do not see or store card details. The store tells us only what is needed for the sale and refund: order code, amount, date and country, and in some cases the purchase e-mail.
License: the license is a key signed by us. It carries only an order code and, at most, the beginning of your e-mail (for example, ed*@gmail.com), never the full e-mail. The app checks it without internet, and the paired Mac and phone exchange it over the encrypted channel to unlock the pair, without identifying you beyond that**. For website purchases, we send the license key to the purchase e-mail.
Revocation: after a refund, the license code is added to a signed list of revoked licenses, which ships inside the app and is passed between the paired devices. The app does not check the internet for this today.
Refunds: see the Terms of Use (15 days).

8. Website, updates and third parties

The app does not use ad SDKs, usage analytics, cloud crash reporting or tracking.
Website and license e-mails: This website is hosted on Cloudflare, which may record technical access data (such as IP address and browser type) for a limited time to operate and protect the service. The site uses no tracking cookies, usage analytics or ads, and its pages are static, with no forms.
Mac app updates: Today the Mac app does not query any server of ours to learn about new versions; it updates the phone app over a cable, without the internet. If that changes, this policy will be updated first, saying what data goes in the query.

We do not sell or share your data for advertising. Only the providers that make the purchase work (item 7) handle purchase data, and they may be in other countries; they follow their own policy. The app's content (screen, notifications, files, clipboard) never goes through us or third parties: it goes straight between your two devices.

10. How long we keep data

In the app: until you delete it (uninstall the app, remove the pair under "Paired phones", or clear the data).
Purchase data (e-mail, amount, date, code): for as long as needed to meet legal, tax and refund obligations, and then we delete it.

We handle purchase data to perform the contract with you and to meet legal obligations. The app's sensitive permissions (Accessibility, notifications, screen capture) work with your consent, given on the explanation screen before each one and which you can withdraw at any time in Android settings.

12. Your rights (LGPD art. 18)

You can ask for: confirmation of processing; access; correction; anonymization, blocking or deletion; portability; information on who we share with; and to withdraw consent. Because the app does not collect personal data, requests normally concern purchase data; write to suporte@bridgeloop.app and we reply within 15 days. You may also complain to Brazil's National Data Protection Authority (ANPD). If you are in the European Union, the United Kingdom or California, the same contact serves to exercise the rights your law gives you (access, correction, deletion, objection; we do not sell personal data).

13. Security and incidents

We use end-to-end encryption between the devices and keep as little as possible. If an incident could bring relevant risk or harm to purchase data, we will tell you and the ANPD within the legal deadline.

14. Children

The app is not directed to children or to anyone under 13, and we do not knowingly collect children's data.

15. Changes to this policy

If we change what the app accesses or what we do with data, we will tell you in the app and on this page before the change takes effect. The date at the top shows the last update.

16. Contact

suporte@bridgeloop.app · https://bridgeloop.app. Security flaws: see SECURITY.md.