Privacy Policy

1. Who this covers

FlyerDuty is a service of Helical, LLC ("FlyerDuty," "we," "us"). This Privacy Policy explains what we collect through the FlyerDuty website and web app, why, who we share it with, and the choices you have. It covers clients, Runners, affiliates, people who ask for access, and people who come across a FlyerDuty campaign without an account: someone who scans a printed QR code, visits a public profile, or receives a flyer at their door.

2. What we collect

Account and sign-in information

Your email address, full name, password (stored only as a one-way hash), account type (client, Runner, affiliate, or admin), and, for clients and affiliates, an optional business name. If you sign in with Google, Microsoft, or Okta, we store which provider and the account identifier and email address it gives us. We keep a record that you confirmed your email with a code (codes are stored only as one-way hashes and expire), and, if you turn on two-factor sign-in, the secret your authenticator app uses and one-way hashes of your recovery codes. We also record when you last signed in. For a Runner listed in the Marketplace, signed-in clients see roughly when that was, rounded down to 5 minutes (for example, "Signed in 2 hours ago"). Clients can also see the latest sign-in among Runners near a place, without being told which Runner it was.

Profile information

A profile photo and banner if you add them, whether your profile is public, and, for Runners: home address (used to find gigs near you), whether you have a printer and which sizes you can print, whether you're taking gigs and which kinds, your rates, and how far you'll travel for a gig.

Mobile phone number and text messages

If a Runner adds a mobile number, we store it once it's confirmed with a code we text to it, along with the line type our SMS provider reports (we only accept mobile numbers), which kinds of text you turned on, the hours you want texts and your time zone, and whether your number has replied STOP. We keep a log of the texts we send (the number, the message, and whether it was delivered to the carrier).

Other contact details you give us

• A client may add a contact name, email, and phone number to a campaign so the Runner or affiliate doing the work can reach them.
• A campaign's printed material may include a phone number or website chosen by the client; that appears on the material itself.
• Affiliates give a venue's business phone number, and when submitting a new venue, the name and phone number of its property manager, so we can confirm they're authorized to list it. Our staff may note how that was confirmed.
• People asking for access while sign-ups are closed give their name, email, city, state, and optionally a phone number, business name, and message.

Identity and business verification

Before certain actions (claiming gigs as a Runner, listing a venue as an affiliate), we may require identity or business verification through a provider such as Stripe Identity (individuals) or Middesk (businesses). We store the check's status and which provider ran it. The provider collects and keeps your ID documents and any selfie under its own privacy terms; we don't receive or store copies of them. When Stripe Identity verifies a Runner, we also receive the address on their ID. We keep only its town, state, postal code, and a point rounded to about 1 km, to check that the work areas they choose and the locations their device reports are near where they live. We don't keep the street address.

Precise location

We collect precise latitude and longitude tied to the work being done:

• a Runner's home address, to match nearby gigs;
• where a Runner is when they start and end a work session, and where each placement or drop-off was logged;
• a spot proposed for a hand-out or a drop-off address list, when a client and Runner agree on locations;
• the work areas a Runner chooses for hand-outs and drop-offs (clients see them only as a rough area);
• a Runner's current location, only while they've turned on location sharing, and the location sent when they claim a gig from where they are;
• an affiliate venue's address; and
• a campaign's target area (a map pin and radius).

We don't track your location in the background unless you turn on location sharing. Without it, your device shares your location only when you take one of these actions. With it on, the app sends your location while it's open, and you can turn it off at any time in your settings or by removing the app's location permission on your device. We check each location reading for signs it was faked, such as a mock-location app or an impossible jump between readings, and keep readings for 30 days. Locations are rounded before being shown to anyone who isn't part of that gig.

Work and activity records

Gigs claimed, work-session start, pause, and end times, placements, skipped addresses, expenses, print pickups, ratings and comments a client leaves for a Runner, reputation scores, disputes and problem reports with their descriptions, and the outcome of each. A Runner's recent ratings and comments can appear on their public profile, without the client's name.

Messages

Messages and photos sent through FlyerDuty's chat between a client and the Runner or affiliate on a gig, or between a client and a venue. FlyerDuty staff can read a conversation to provide support or resolve a dispute.

Photos, videos, and documents

Photos and videos uploaded as proof of a placement, drop-off, delivery, or venue check-in; receipts for expenses and printing; print-shop invoices; venue photos; and the artwork and logos of a campaign. Proof is visible to the campaign's client and to our staff, and kept as a record of the work.

Payment and payout information

Our payment processor, Stripe, collects card details through its own form; your card number never reaches our servers. We store Stripe's identifiers for your customer record and saved card, the card's brand and last four digits, and records of the holds, charges, refunds, tips, chargebacks, payouts, and earnings tied to your gigs.

Taxpayer information (Runners and affiliates)

Stripe Connect collects the identity, tax, and bank details it needs to pay you and handles tax forms such as the 1099. We store only your Stripe account identifier and whether payouts are enabled; we don't collect or store taxpayer identification numbers or bank account numbers.

Residential drop-off addresses (third-party data)

For a drop-off campaign, the client gives us street addresses where material should be left. These usually belong to people who don't use FlyerDuty. We use them only to route the gig and track which addresses were visited. See "Your choices" for how a resident can stop their address being used.

Reports and opt-outs from the public

If you report a problem with a campaign or opt out from a printed QR code, we store the report, any message you write, the address you give for an opt-out, and a one-way hash of your IP address to limit abuse.

Device and visit data

When someone scans a campaign's QR code, follows the website link on a campaign's page, or views a Runner's or venue's public profile, we record the visit for the campaign's or profile owner's statistics (for a profile, including which share link was used). To count repeat visits only once, we store a one-way device fingerprint computed in your browser by the open-source FingerprintJS library (no data goes to FingerprintJS) and one-way hashes of your IP address and browser user agent. We skip the fingerprint when your browser sends a Do Not Track or Global Privacy Control signal.

Cookies, local storage, and server logs

We use one essential cookie to keep you signed in. If you aren't signed in and arrive on one of our public city pages for clients, Runners, or venues, we set a first-party cookie that lasts 30 days. It holds a random visit ID, the first page you landed on, the domain of the site that linked you there (not the full address), and any campaign tags in the link, such as utm_source. We use it to count visits to those pages and clicks on their sign-up buttons. If you then create an account, we keep it with your account to measure which pages and links bring people to FlyerDuty. We store a one-way hash of the visit ID, never the ID itself. Your browser also stores a few preferences on your device, such as light or dark mode and prompts you've dismissed. We don't use advertising or third-party analytics cookies. Our servers briefly process your IP address and request details to run the Service, keep it secure, and limit abuse.

3. How we use this information

• to run the marketplace: matching campaigns with Runners and affiliates, and tracking each gig from posting to payment;
• to verify identities and businesses where required, and to prevent fraud such as faked placements, duplicate scans, or fake accounts;
• to take payments and make payouts through Stripe;
• to show statistics to campaign and profile owners;
• to communicate with you by email and, if you opt in, by text, as described below; and
• to meet legal obligations and keep required business records.

How we use your email address

• confirming your email when you sign up, password resets, and security notices such as two-factor sign-in being turned on or off;
• updates on your gigs, campaigns, payments, payouts, refunds, disputes, and chargebacks, and when a card needs updating;
• for Runners, when a client offers you a job directly and when new gigs are posted near you, sent only during the hours you choose (you can turn either off in your settings);
• telling you when FlyerDuty opens in an area you joined the waitlist for, and decisions on an access request; and
• occasionally, telling you about a new feature you can use with your account.

We don't sell your email address or send third-party advertising.

How we use phone numbers

• A Runner's mobile number is used only to text the verification code you request, the confirmation when you turn alerts on, and the alerts you turned on (new gigs near you, jobs offered to you), within the hours you chose. It isn't shown to clients, other Runners, or the public.
• A campaign's contact phone is shown only to the client and the Runner or affiliate working that campaign, so they can coordinate.
• A venue's phone and its property manager's phone are used to confirm the affiliate is authorized to list the venue.
• A phone number in an access request is used only by our staff to contact you about the request.

We don't use any of these numbers for marketing calls or texts.

4. Who we share it with

• The other people on a gig. A client sees the Runner or affiliate on their campaign in a limited way (never a home address, phone number, or payment details); a Runner or affiliate sees the client contact details needed to do the work.
• Service providers that run parts of the Service for us, only for that purpose: Stripe (payments, payouts, identity verification, tax forms), Middesk (business verification), Twilio (text messages and phone line-type checks), Resend (email delivery), Google Maps Platform and OpenStreetMap (turning addresses into map locations and finding print shops), Google, Microsoft, and Okta (if you sign in with them), Amazon Web Services (hosting and databases), and Cloudflare (network delivery and security). Map images in the app load from OpenStreetMap, and blog images from Sanity, so those services see your IP address.
• Legal requirements. When required by law or legal process, or to protect the rights, property, or safety of FlyerDuty, our users, or others.
• A business transfer. If FlyerDuty is sold or merged, your information may move with it under this policy.

We don't sell personal information. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third parties.

5. Your choices

Access, correction, and deletion

You can see and update most of your information in the app. To get a copy of your data, or to have your account and its data deleted (except what we must keep, such as financial records), email [email protected].

Text messages

Reply STOP to any FlyerDuty text to stop all texts, or turn alerts off or remove your number in your settings. You can also change the hours texts and alert emails may arrive.

Email

Runners can turn off job-offer and new-gig emails in their settings, and choose the hours they arrive. Other account and transactional emails are part of having an account; if you don't want any of them, you can close your account.

Public profile

Runners and clients can make their profile private in their settings, which hides its details, photo, and banner from everyone but you and our staff.

Residential address opt-out

Recorded and automatically enforced for hand-delivered drop-offs. The QR code on printed material links to a page with an "opt out" option. If you give your address when opting out, we exclude it from future door-to-door drop-offs across all FlyerDuty campaigns, not just the one you saw. Matching is best-effort: small differences in how an address is written are usually caught, but not every rewording. Hand-to-hand distribution and placements at partner venues aren't covered, because they aren't tied to an address. If you opted out without an address, or still receive drop-offs, email [email protected] and we'll handle it by hand.

Do Not Track and Global Privacy Control

We honor these signals for the device fingerprint described in section 2. When your browser sends either one, we also don't set the visit cookie or record your visits to our public city pages.

6. How long we keep it

We keep account and campaign information while your account is open, then for as long as needed for legal, tax, and dispute purposes. Notifications in your inbox are deleted 30 days after you read them and after 90 days otherwise. Verification codes expire within minutes. Records of visits to our public city pages are deleted after 13 months; where an account came from is deleted with the account. Logs of texts we sent are kept as a record of consent and delivery. Verification status is kept as a record after an account closes, without the documents, which the provider holds.

7. Children's privacy

FlyerDuty is not for children, and we don't knowingly collect information from anyone under 18.

8. Changes to this policy

We may update this policy. A material change is published as a new version. Using the Service after a change means you accept the updated policy.

9. Contact

Email [email protected], call 470-486-5144, or write to Helical, LLC, 113 S. Perry Street, Suite 206 #14902, Lawrenceville, GA 30046, United States.