Loading
LoadingDraft product policy
A plain-language view of where information appears in the current product, with the fuller version underneath. Effective October 6, 2026.
Your problem description and the photos/video you attach to a problem are public. Anyone can see them, so don’t include your exact address, house number, plates, or documents. A neighbourhood-level area is all Flare asks for. Messages inside a private conversation, and anything you share there, are visible only to you and the one professional you’re talking to (plus Flare staff for safety and support).
Account data: your name and email (or phone number, if you sign up that way), and a password hash if you don’t use Google/Facebook sign-in — Flare never sees or stores your Google/Facebook password.
Content you post: problem descriptions, photos/video, public responses, and anything you write in a private conversation or a report.
Location: only the neighbourhood-level area you type in, never a precise address or device GPS coordinate.
Automatic technical data: the same basic, non-identifying page-view data any site collects (page URL, referrer, device/browser type) — see Cookies below for exactly which tools see this and when.
Flare doesn’t collect financial data, government ID numbers, precise device location, demographic data, or data from marketing/advertising partners or data brokers, because none of those exist in the product today.
One required cookie: Supabase’s own session cookie, which is how “you’re signed in” works at all. If you accept the cookie notice, Flare also uses Google Analytics to count visits and page views; declining (or not answering) means that script never loads for you at all, no cookie, nothing sent. Either way, it never gets your name, email, messages, problem descriptions, or anything else you type. It only ever sees the same automatic page-view data any analytics tool collects: page URL, referrer, device/browser basics. Page-view counts are also measured with Vercel Analytics, which doesn’t use cookies or collect anything that identifies you, regardless of your choice. Flare doesn’t currently respond to browser “Do Not Track” signals, since the only optional tracking that exists (Google Analytics) is already off by default and requires your explicit yes.
The professional you choose to continue with sees your private conversation and whatever you share in it — nobody else does. Flare uses a small number of infrastructure providers to run the product at all: Supabase (database, authentication, file storage) and Vercel (hosting), both of which process data only to provide that infrastructure, not for their own purposes. Google Analytics, only if you’ve accepted it, sees anonymous page-view data as described above. Flare does not sell personal data, and doesn’t share it with advertisers, data brokers, or anyone else.
You can download everything Flare has tied to your account, or permanently delete your account, both from your profile page. Deletion removes everything: problems, responses, jobs, messages, addresses, credentials, all of it, and can’t be undone. See Delete your data for the exact steps, including if you signed up with Google or Facebook.
California residents have rights under the CCPA/CPRA (to know what’s collected, to delete it, to correct it, and to opt out of any sale or sharing — Flare doesn’t do either, so there’s nothing to opt out of). Colorado, Connecticut, and Virginia residents have similar rights under their own state laws (CPA, CTDPA, VCDPA). Nevada residents can ask a business not to sell certain data — again, Flare already doesn’t. You can exercise the access/delete rights that apply to you the same way anyone else does, from your profile page, or by using Report something to reach Flare directly.
Flare isn’t directed at children, and you must be at least 18 to create an account (see Terms of use). Flare doesn’t knowingly collect personal information from anyone under 18; if that happens, contact Flare via Report something and it’ll be removed.
No exact-location storage, no payment data, no ad tracking, no verification-vendor data.
If Flare makes a material change to this policy, it’ll be reflected here with an updated effective date, and, once Flare sends account email, you’ll be notified directly for anything significant.