Security
No logo wall. Everything below is how the product actually behaves, and every claim here is implemented, or explicitly marked as forthcoming.
Payments
Payments run on Stripe. Card details never touch Strobe’s servers, and strong customer authentication applies as required in the EU.
The venue is the seller of record for what it sells, and its own fiscal register still closes the bill. Strobe takes the deposit; it does not become the merchant for a room’s drinks. At launch, deposits settle to Strobe and are transferred to the venue after the night, while Connect verification completes; that is a four-to-eight-week process and it is deliberately not on the critical path for a first night.
Each person’s share is a separate payment, so each can be refunded independently, which is exactly what happens, automatically, if a group’s pool doesn’t complete.
Data location
Personal data is hosted in the EU. Where a provider processes data outside the EEA, standard contractual clauses and a transfer impact assessment apply. The detail is in the privacy policy.
Access control
Row-level security on every table in the product database, default deny. A venue only ever sees its own guests’ records.
A venue sees a guest’s name, their booking, who is on their table and whether they arrived. Nothing else.
No facial recognition, no biometrics, no stored document images. An age check records that it happened and who did it, never a scan.
Reputation as a band, rather than raw history, is designed and not yet built. It is marked as planned in the privacy policy and it is marked as planned here, because a page that promises every claim is implemented has to keep the promise on the claims it has not implemented too.
Location
No location tracking, no geofencing, no background location, no continuous tracking. The app makes one narrow location call (to determine a phone’s country code) and nothing else.
Presence features, when they ship, will be derived from door check-in: opt-in, off by default, mutual-accept only, venue-level only, and auto-expiring.
Your control
Export your data or delete your account from your settings, or by writing to us. Records that must be retained for fiscal or safety reasons are anonymised rather than kept, and we say so at the moment you ask.
Found a vulnerability?
Write to strobesocial@gmail.com. Good-faith research is welcome and we will not pursue researchers who report responsibly, stay within their own accounts and do not degrade the service. There is no bug bounty. Our machine-readable contact is published at /.well-known/security.txt.
No security claim on this page that isn’t implemented. No certification logo Strobe doesn’t hold.