What this software and this website do with information about you.
Private beta notice — 28 October 2026
The current native apps are being tested in a private beta. The operator’s database username service is live following the verified migration of earlier ownership records. Descriptions of the updated privacy safeguards below refer to native beta build 2026102801; older builds can behave differently. This notice does not announce a public launch.
Your shared content travels between devices. Files, messages, group chats, posts and shops move over their owners' internet connections. BridgeDrop operates a separate username directory and moderation service. Reports you choose to submit are sent to that service.
Your identity is signed by your device. The operator keeps a directory of username bindings and public cryptographic identities. A binding identifies a device key, not a verified person. Account recovery and moving that identity to another device are not yet a supported account service. Wallet features are paused in the current native beta and existing encrypted vault data is preserved. Operator request payloads do not include an advertising identifier or your personal browsing location.
Normal direct connections expose network addresses: the devices yours connects to can see its internet address. A private profile changes who can see posts; it does not by itself hide your network address. Details are under Finding people across the internet.
Interface typefaces and icons are bundled with the application. Operating-system services, external links and website hosting are described below.
When a direct connection is impossible, a transfer can be relayed through a machine that you or the other person chose. Transport relays carry encrypted bytes and cannot read the encrypted file contents. They can observe connection addresses, timing and traffic volume. This differs from community hosts that deliberately keep readable shared content.
Optional location and local discovery. When you tap “Use my location,” the native app asks for foreground location permission. The platform geocoder uses that one-time position to find a city and postcode. Exact device coordinates are not kept in Rust storage; a point rounded to hundredths of a degree can be saved for approximate distance filtering. The app does not track location in the background. Your personal browsing point stays on your device; explicitly saving a shop location publishes that shop’s approximate point. You can also geocode an entered city without device-location permission. Treat city labels and postal information you enter as shared information: older beta builds can publish the full saved postcode. Updated builds reduce public postal information to a five-digit US ZIP, UK outward code, three-character Canadian prefix or broad prefix elsewhere, and omit personal and community points. Public profiles, shops and opted-in communities can be discovered in that area. Shops keep a separate saved area. A public community listing can include an invitation; a listed private city chat requires founder approval. Removing an area stops new announcements, but existing network records can take time to expire.
Search. Devices advertise a bounded set of words from their public profile, public video captions, shop names and available listings so people can find them. Private video captions are excluded. Results depend on network reachability; there is no complete central index.
Photos you add to listings are resized and stripped of their metadata, including location, before they leave your device. A place you type on a post or listing is shared exactly as you wrote it.
The live database service uses a short-lived challenge and device signature to establish control of a public identity. The operator verified and imported earlier ownership records before enabling new database allocation. An updated client does not mark a legacy cached claim registered until the service confirms that the name belongs to that device. A device signature is not proof of a person’s real-world identity.
Earlier beta clients registered names on public Solana devnet. Historical blockchain records may have been copied and cannot be removed by an app update. Wallet balances, transfers, creation and recovery interfaces are paused in the current native beta. Existing encrypted vaults are retained; deleting app data without a usable backup can permanently lose access to those keys. Older builds can behave differently.
In its normal direct connection mode, BridgeDrop uses the public distributed hash table also used by IPFS to help devices on different networks find each other. BridgeDrop devices can participate in that network too:
The public discovery network is separate from BridgeDrop’s operator service. Direct service requests, including reports, are described above.
A private account restricts posts to approved followers in cooperating apps. Approved followers receive signed access passes. Removing a follower changes the access policy; the privacy update also revokes passes when blocking approved followers and repairs older blocked grants. Cooperating devices reject old passes after receiving the new policy. Offline or modified devices may retain older policy or content, and recipients can save material they already received. This is access control, not a promise to erase every copy.
Turning your profile off marks your profile and posts unavailable to cooperating apps, including followers. Other devices need to receive that updated state before they stop sharing their copies. Independently saved copies are not erased. Messages can still work.
Either way, what is already on someone else's device stays theirs: we cannot reach into it, and neither can you.
Your device keeps transfer history, messages and community conversations, known devices and their last-known addresses, vouches, settings, retained media and diagnostic logs where enabled. A device identity key is stored in the operating system’s credential store where supported, or in a restricted local file. Wallet vaults and other local app files are separate from the operator’s records.
Deleting local app files does not delete the operator’s directory or report records, external backups, credentials retained by the operating system, or another person’s copies. Deleting a post or listing stops your device sharing it. Cooperating devices hide blocked content after receiving updated policy, but we cannot erase independently saved copies. Sharing and storage controls vary by build. The beta does not yet provide a complete in-app account deletion or recovery service.
The operator database holds verified usernames, public device identities, first/last registration timestamps, submitted reports, review decisions, active bans and administrative audit notes. It does not hold wallet recovery secrets, private messages, your browsing location or a central copy of your media library. If you include personal information in a report or email, that information is available to the moderation team. Report records and audit history currently remain until an operator removes them; there is no automatic expiry. Private reports are not exposed through a public API or sold to advertisers.
This website is hosted on Vercel. The hosting service handles your internet address and request information and can record server logs. The static page code does not set cookies or include an analytics or advertising-tracking script.
Page assets, including typefaces, are served from this site rather than a font CDN. External links you choose to open, including advertiser links, are handled by those destinations under their own policies.
You can contact privacy@bridgedrop.app about information held in the username directory or moderation records, including requests to access, correct or delete information. Applicable privacy rights and retention obligations depend on the circumstances and law. Deleting local app data does not submit such a request to the operator.
The intended first public launch is for adults aged 18 or older in the United States. The current private beta does not have an implemented in-app age or region eligibility gate, and this page does not claim that users’ ages have been verified. Public-launch eligibility, terms acceptance, deletion controls and legal review remain separate launch requirements. Concerns about a child using the service can be sent to support@bridgedrop.app.
If this policy changes in a way that affects what is collected, the date above changes and the previous version stays available on request. We will not begin collecting something new without saying so here first.