Privacy Policy

BelongFlow is operated by BenOfficialCO. The operating team also acts as support.

• Identity and contact — your name, and the email address or mobile number you sign in with. Optionally a photo, city and social handles if you choose to add them.
• Community and event participation — the communities you belong to, events you say you are interested in or reserve a spot for, and per-community answers such as why you joined or who referred you.
• Attendance and check-in — when you check in to an event, which event, and whether it was your first time with that community. Where an organizer uses arrival or proximity rules, the check-in records that the check happened and its result.
• Messages — private messages between you and a community's organizers, and community updates sent to you.
• Volunteering — if you offer to help at an event, the role you asked for, any note you wrote, and whether an organizer approved it.
• Friends (BFFs) — mutual connections you explicitly accept, and whether you chose to let friends see that you are going to an event.
• Location — where an organizer uses proximity rules, your device location is used at that moment to work out whether you are near the event. It is used transiently for proximity, discovery and check-in, and is not kept as a record of where you have been.
• Invitations — when someone brings you as a guest, the invitation credential is stored only as an irreversible fingerprint, never as a readable invitation code.
• Technical and session data — the sign-in session stored on your device, and server logs needed to keep the service working and to diagnose failures. BelongFlow does not keep its own table of your past sign-in sessions; authentication sessions are handled by our authentication provider.

To sign you in; to show you the communities and events you belong to; to let organizers run their events, check people in, and understand attendance and retention; to deliver messages you and your communities send each other; and to keep the service secure and debuggable.

Cloud and service infrastructure processes the requests needed to operate BelongFlow. We use Supabase for authentication, database and storage services. We use MapTiler for map services; it receives the network and map requests needed to serve maps. We load typefaces from Google Fonts; your device's request for those font files reaches Google, which receives standard network information such as your IP address. BelongFlow does not provide these services with user data for targeted advertising.

Each community is separated at the database level. Organizers of a community see the members, attendance and messages of that community only — never another community's. Your private conversation with one community is not visible to any other community. Organizers cannot see whether you have read their message. Friends only see that you are attending an event if you turn that on.

We do not sell your data. We do not use facial recognition or any biometric identification. We do not run advertising against your data. BelongFlow does not move real money and does not send marketing email on an organizer's behalf.

We keep your account and participation data while your account exists, because attendance history is what makes a community's records meaningful. You can edit most details yourself in your profile. You can request access to or correction of your information, or ask us to close your account. Access and correction requests are reviewed by a person, and there is no automated data export yet. A closure request is reviewed too: we confirm it came from you, explain what can be removed and what may need to be retained, and if it is approved it returns to your signed-in account where you re-enter your current password and confirm. Closure begins only after that final confirmation, and you can cancel any time before it begins. Some de-identified records and organization-owned operational history may remain where retention is legitimate. If you choose to share optional feedback when requesting closure, it is stored without your name, email, phone or sign-in user ID, and may be kept in de-identified or aggregated form to improve BelongFlow.

Some records may need to be retained to preserve legitimate event or community history, security and audit integrity, resolve disputes, comply with applicable law, or because the record belongs to an organizer's operational history. BelongFlow does not use a fixed automated retention schedule.

BelongFlow is new: expect changes and occasional errors as it grows. If something goes wrong, tell us — that is how we improve it.