Approximate before acceptance
The server stores exact meeting coordinates separately and creates one stable, randomly offset public area inside the host’s chosen radius.
Safety by design
Flare combines privacy-minimised location sharing, host approval and server-enforced access rules. These controls support judgment; they do not replace it.
A fixed privacy area
The approximate map position is generated once and stays stable. It is not recalculated on every refresh, which helps prevent repeated public samples being averaged to infer the private point.
The server stores exact meeting coordinates separately and creates one stable, randomly offset public area inside the host’s chosen radius.
Only the host and accepted participants can read exact meeting details or participate in the event chat.
Members can exit a flare; hosts can remove participants; blocking creates bilateral separation and revokes relevant access.
Flares disappear from discovery at expiry. Exact details and chat become inaccessible to members according to the event lifecycle.
Restricted meeting and chat records may be retained for up to 30 days for incident response, then automatically deleted unless a preservation hold applies.
Reports, warnings, restrictions and suspensions are enforced behind the interface and recorded in an immutable moderation audit trail.
Meet thoughtfully
In Australia, call Triple Zero (000) for urgent police, fire or ambulance assistance.
Built for the moment