Privacy Policy
The short version
- We collect what a job needs and very little else.
- We do not sell your information, and we do not share it for advertising. There is no ad business here to feed.
- A customer's exact address and phone number are hidden from a business until it takes the job; before that it sees the area, not the street.
- A crew member's live position is seen by their own business, for dispatch, and by one customer: the one they are driving to, while the job is marked on the way, so she knows when to expect them. It is never on a public map and never seen by other businesses.
- On the public map, every business is an approximate area of about a mile, never an exact point. The one exception is a food truck's parked spot, a public place it chooses to share.
- We store a hash of an IP address rather than the address itself wherever we only need to tell repeat visitors apart.
- The location data inside photos is removed before a photo is stored.
- If an open flare finds nobody free, we keep it for twelve hours and tell you once if someone who can help frees up (by text, only if you said yes to texts). Then we stop.
- You can ask us for your data or ask us to delete it, and we will do it.
1. What we collect
If you are a customer
- What you type when you send a flare or an order: your name, phone number, what you need, when you want it, an address if the job needs one, and — if you give them — an email address, a price you expect to pay, and the name and number of somebody you booked it for.
- How you paid, if you tell a business "I've paid" on your job page (for example "with Zelle"). We never see the payment itself.
- Your email on the launch list, if you asked to be told when Flare opens.
- Your approximate location, only if you allow your browser to share it, and only to centre the map and work out who covers you. If you say no, the map defaults to downtown Detroit and everything still works.
- What you did on the site: which businesses you looked at, which flares you sent, whether a QR code brought you here.
- Your review, if you leave one.
- Who you follow, if you tap Follow on a business. The follow belongs to your phone, not to a name: we keep which businesses that phone follows so it can get their news. The business sees how many people follow it, never who.
- A rough area for nearby food alerts, only if you save one: a point rounded to about a kilometre, never where you go. When a food truck you follow parks within 3 miles of it, you get one notification (at most one a day, never at night). Clear it or switch the alerts off any time.
- Text messages about your job, only if you ticked the box to get them (it is optional). We keep a record that you agreed, and when.
You do not need an account to use Flare as a customer. We do not ask you to make one.
If you are a business
- Account details: your name, your business name, email, phone, the city you work from, and the areas you cover. If you sign in with Google, Google tells us your name and email address and that Google has verified it. We never see your Google password.
- Verification documents: EIN or business registration, certificate of insurance, trade licence where one applies. These are the most sensitive things we hold and they are treated accordingly — see section 4.
- Your crew: the names you enter for seats, how they're paid (an hourly rate or a yearly salary, and whether they're exempt from overtime) if you choose to record it, their time card punches (clock in, clock out, breaks, and every change to a punch with who made it and why), and background-check status. We do not keep background-check reports. If a business uploads one as proof, we keep the file only until we have reviewed it (at most 30 days) and then delete it. After that we store only whether the result was clear, the report date, the screening company, the report's reference number and when it expires, plus a record of each step (uploaded, ordered, cleared, not cleared, sent back, expired), when, and who at Flare decided. We never record why a check was not clear. Michigan seals records, and cached results go stale in a way that becomes a liability.
- Your work: jobs, prices, times, photos, mileage, and the money figures the console computes from them.
- Photos. Phones write the GPS position a photo was taken at into the file. A job photo is taken at somebody's home, so we strip that location and the camera details out on upload, before the photo is stored. Job photos are deleted after 90 days.
- How you pay Flare. Your card or bank account is collected by Stripe on Stripe's own page. We keep the type (card or bank), the last four digits, and whether payments succeed.
- QuickBooks, only if you connect it. We keep the access tokens Intuit gives us and use them only to send your Flare jobs and invoices to your own QuickBooks. Disconnecting deletes them.
- Your app's notification token, if you allow notifications, so Apple or Google can deliver them to your phone.
- Live position of a crew member's device, while their app is open and they are working, for their own business's dispatch board. While a job is marked on the way, the customer of that job also sees it on her job page, with a rough arrival time, until the crew member marks that they have arrived. We keep only the latest position, not a trail.
- Today's spot, for a food truck, when the owner goes on the map: the place it is parked, shown publicly until it goes off the map (or for 14 hours at most).
- Free roam, if a business turns it on: the position of the phone that turned it on decides which nearby flares it is offered. The public map shows only the roughly one-mile area it is in, updated at most every ten minutes. It ends after four hours, or when the business goes off the map.
If you apply for a job through Flare
If a business on Flare posts a job and you apply on its Flare job page, we collect what you type: your name, phone and email, when you can work, your experience, a resume link if you add one, the answer to any license question, and which site the link came from. It goes to that business and nobody else. The business decides who to contact and who to hire; Flare doesn't screen, score or rank you. We send you one email confirming your application. Applications that don't lead to a hire are deleted after 12 months; you can ask us to delete yours sooner.
Automatically, from anybody
- Standard request information: browser type, pages requested, timestamps.
- A salted hash of your IP address. Not the address. It is enough to tell one person scanning a QR code ten times from ten people scanning once, and enough to rate-limit abuse. It is not enough to identify or locate you.
What we deliberately do not collect
- No full card or bank numbers, ever. A customer pays the business directly, by whatever method that business uses. A business pays Flare through Stripe, and the card or bank details go to Stripe, not to us.
- No social security numbers, no dates of birth, except where a background-check provider requires them, in which case they go to that provider and are not retained by us.
- No third-party advertising or analytics trackers. There is no Google Analytics, no Meta pixel, and no advertising cookie on this site.
2. Why we have it
| What | Why |
|---|---|
| Your flare details | So a business can turn up and do the job |
| Your address and phone | Given to the business only once they take the job |
| Location | To show who covers where you are |
| Verification documents | To check a business is real and insured before letting it near a customer |
| Job and money records | So a business can run its books, and so a dispute two years from now can be settled |
| Live crew position | So a business can see where its own crew is, and so a customer can see her crew on the way |
| Hashed IP | Rate limiting and abuse prevention |
| Email address | Job notifications, invoices, and telling you when these terms change |
| Phone number | Texts and calls about a job you booked, if you agreed to them |
We do not use any of it to build an advertising profile.
3. Who else sees it
The business you contacted sees your name, what you need and your area, and — after they take the job — your address and phone number.
Nobody else on Flare sees your details. Businesses cannot browse customers.
Our service providers, each doing one job and contractually barred from using the data for anything else:
- Netlify — hosting, the database, and the sign-up forms on the site.
- Resend — sending email.
- Stripe — billing businesses by card or bank account (ACH). Stripe receives the payment details directly; we receive a confirmation.
- Twilio — sending job text messages and, where a Flare line is assigned to a job, connecting calls and texts through it so a customer and a business can reach each other without swapping numbers.
- A background-check company (such as Checkr or Certn) — only when a business orders a check through Flare, and only the person's name and email, so the company can ask them directly for consent and details.
- Google — "Sign in with Google", turning a typed address into a map position, and delivering notifications to Android phones.
- Apple — delivering notifications to iPhones.
- Intuit (QuickBooks) — only for businesses that connect their own QuickBooks, and only that business's own jobs and invoices.
Law enforcement, only where we are legally required, and we will tell you unless we are legally prohibited from telling you.
A buyer of the business, if Flare is ever sold — in which case this policy travels with the data and you would be told before anything changed.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those phrases are defined under California law. We have never done so and there is no plan to.
4. How it is protected
- Verification documents are held in private storage and are reachable only through short-lived signed links. They are not publicly addressable, and a link that leaks stops working.
- Passwords are hashed inside the database. The plaintext never lands in a log, and the hash never travels over the network.
- Session cookies are signed, HTTP-only, and checked against a live session record on every single request — so signing out, or a seat being claimed on another phone, kills a session immediately.
- One seat, one device. Signing in on a second device signs the first one out.
- The money screens are owner-only, enforced on the server, not just hidden in the interface.
- Everything is encrypted in transit and at rest, with automated backups.
No system is perfect. If we ever have a breach that affects you, we will tell you promptly and tell you what actually happened.
5. How long we keep it
| What | How long |
|---|---|
| Job records, invoices, Flare fees | Seven years. These are business records; a tax authority or a dispute can reach back |
| Your account, while it is open | Until you close it |
| A closed account | Public listing removed at once; records kept as above |
| Verification documents | While the account is open, plus two years |
| Background-check reports a business uploads | Until we review them, thirty days at most |
| Background-check records (the verdict, dates and who decided) | Five years from each step, then deleted automatically |
| Live position pings | Thirty days |
| Follows and a saved area | Until you unfollow or clear it, or the phone stops accepting notifications |
| Job photos | Ninety days, then deleted automatically |
| Hashed IPs in the rate limiter | One day, then swept automatically |
| Reviews | Kept, because removing them on request would make the ratings dishonest |
| Marketing emails | Until you unsubscribe |
6. What you can ask for
Whoever you are and wherever you live, you can ask us to:
- Tell you what we hold about you, and give you a copy.
- Correct anything wrong.
- Delete what we hold, except records we must keep for tax, accounting or dispute purposes — and we will tell you exactly what we kept and why.
- Stop emailing you anything that isn't about a job you are actually part of. Every such email has an unsubscribe line and our postal address.
- Stop texting you. Reply STOP to any Flare text.
Email hello@flaredetroit.com. We answer within thirty days, usually much sooner. We will not charge you and we will not make you jump through hoops.
California residents: these are the rights the CCPA gives you, offered here regardless of whether Flare currently meets the thresholds that would require it. We do not discriminate against anyone for exercising them.
7. Cookies
Flare sets one cookie, flare_session, and only after you sign in. It holds a signed token that identifies your session. It is HTTP-only, secure and same-site. Deleting it signs you out. If you sign in with Google, a second cookie lives for the few seconds of that sign-in to prove the answer from Google is the one you asked for, and is then deleted.
We use browser local storage on your own device to remember small things like whether you dismissed a tip. That never leaves your device.
There are no advertising cookies and no third-party trackers, so there is no consent banner. That is the point of not having them.
8. Children
Flare is not for anyone under 18 and we do not knowingly collect information from children. If you believe a child has given us information, email us and we will delete it.
9. Where the data lives
Flare is operated from the United States and the data is stored in the United States. We do not currently offer the service in the European Union or the United Kingdom and do not market to people there.
10. Changes
If we change this policy in a way that materially affects you, we will email you at least thirty days beforehand and ask you to accept the new version. Every version is kept, numbered and dated.
Flare Metro Detroit, Michigan hello@flaredetroit.com
If you think something here doesn't match what the product actually does, tell us. That would be a bug, and we would want to fix it.