Open Here Privacy Policy for iPhone & iPad
Effective date: October 13, 2026
This policy covers Open Here for iOS and iPadOS, including its TestFlight beta, provided by Andrei Vasin under the name Broken Man Studios.
No account or advertising
No app account, real name, email address, photo or contact list is required to use Open Here. The app generates an animal nickname and cryptographic identity on your device. It does not contain advertising or analytics SDKs or track you across other apps or websites.
Bluetooth discovery and messages
With Bluetooth enabled, the app exchanges a generated nickname, public identity key and availability/intention information with nearby devices. This allows people nearby to discover you when you are open to chat. Existing conversations can reconnect even when you are not open to new chats. Bluetooth discovery and messaging require the app to remain in the foreground.
Message content is encrypted on the sending device for the receiving device. Chat history, message drafts and the outgoing queue are kept locally. Identity and plan ownership secrets are stored using the device's secure storage. Do not send personal information you do not want your conversation partner to receive; a recipient can retain or share messages outside Open Here.
Names and safety controls
You can give a conversation partner a custom name. This label is stored only on your device and does not change their public nickname or get sent to them or to the relay.
A basic on-device filter can prevent sending and hide some direct threats and explicit harassment. It is not comprehensive moderation, and filtering does not send message content to us. You can block a partner or report concerns from the conversation menu.
Reporting opens an email draft addressed to brokenmanstudios.project@gmail.com with the partner's generated nickname and public app identifier. You choose what description or screenshots to add and whether to send it. No report is sent automatically. If you send a report, we process your email address, the identifiers and the content you choose to share to investigate abuse and respond. Only include material you want our support team to receive.
Deleting a conversation removes its local message contents, draft and custom name. Limited conversation identifiers, relay position and identifiers of deleted messages remain locally so that discovery or a replay does not immediately restore the deleted history. A new incoming message can start a new conversation. This does not remove the other person's copies or encrypted relay records.
Internet delivery
Existing conversations can use our Supabase-hosted relay when Bluetooth is unavailable. The relay receives encrypted message envelopes, message identifiers, conversation capability information and technical request metadata. Stored relay records include encrypted content, a conversation capability hash, sequence identifiers and creation times. The server does not receive your private message decryption keys. Internet delivery does not mean the recipient is currently online.
Relay records are retained to allow later delivery. The app does not automatically erase server records when you remove local app data. We do not sell message or usage data. Infrastructure providers may process network addresses and operational logs to deliver and secure their services.
Plans and location
Plans are public. When you save a plan, the backend receives your generated nickname, the exact map pin coordinates you choose, the planned time and intention. Other app users can view these details. Choose a public meeting place rather than a private address. You can edit, move or delete your own plan in the app; an ownership secret stored on your device authorizes these changes.
Location permission is optional and is used when you ask the map to show your location. Your current location is not automatically published as a plan or used to match chats. The map uses Apple's mapping services, which process map requests under Apple's privacy practices. Declining location permission still allows you to place a pin manually.
Plans stop appearing in the app three hours after their planned time. This display expiration does not by itself guarantee deletion of the corresponding backend record. Deleting your plan removes its active database record; infrastructure backups or logs may retain earlier copies under the provider's retention processes.
Permissions, retention and controls
Open Here requests Bluetooth access and optional location access while using the app. It does not request your contacts, camera or microphone. You can turn off new-chat discovery, block a conversation partner and revoke Bluetooth or location access in device settings. Blocking stops the app from receiving messages from that partner; it does not erase copies they already have.
Local histories and drafts remain until app data is removed. Device backups and app offloading follow your Apple settings; offloading may preserve local data and secure-storage identity items can survive app removal. Removing the app does not delete public plans or encrypted relay records. Delete an unwanted plan before removing the app. Contact us for questions or requests about server-side records; because there is no account, we may need information identifying the relevant record and establishing your authority over it.
Support and TestFlight
If you contact us, we receive the email address, message and attachments you send and use them to respond and investigate issues. During TestFlight testing, Apple may make diagnostics and feedback available to us, including screenshots or comments you submit. Apple's TestFlight and device privacy settings govern this process.
Open Here is a social messaging service and is not intended for children. Avoid sharing sensitive personal information with strangers.
Changes and contact
We will update this policy and the relevant App Store privacy information when the app's practices change. For privacy or support requests, email contact@brokenmanstudios.com.
Read Apple's Privacy Policy, Supabase's Privacy Policy and our Studio Privacy notice.