Skip to content
Quick To Connect

Legal

Privacy Policy

What Quick To Connect collects, including location traces, job photos, provider ID check results, and insurance documents, how it is used, how long it is kept, and who it is shared with.

Effective date: November 9, 2026. This policy describes how Quick To Connect, LLC (“Quick To Connect,” “we,” “us,” or “our”) collects, uses, shares, and retains personal information when you use our websites, web app, and mobile apps (together, the “Service”).

The Service is an on-demand snow removal marketplace for Wasilla and the Mat-Su Valley, Alaska. It is not a generic website, and this policy is written for what the product actually does, including precise location, job photographs, and provider documents.

Questions: support@quicktoconnect.com.

1. Who this policy covers

This policy applies to everyone who uses the Service: customers, solo providers, fleet companies, fleet drivers and dispatchers, and visitors to https://quicktoconnect.com.

It does not apply to Stripe, Apple, Google, or other companies you deal with directly (for example, when you complete Stripe Connect onboarding or pay with Apple Pay). Their policies govern the information you give them.

2. Information we collect

2.1 Account and identity

  • Name, email address, and phone number
  • Password, stored only as a one-way hash — we cannot read it
  • Profile photo, if you upload one
  • Two-factor authentication secrets, stored encrypted
  • Social sign-in identifiers if you use Apple or Google sign-in
  • Account display name and marketplace role (customer, provider, or fleet)

2.2 Device, session, and security

  • IP address, browser or app version, device type, and a device fingerprint used to detect fraud
  • Sign-in history (time, IP, and a device/browser string)
  • Expo push-notification token for your device, registered when you sign in and removed when you sign out
  • Phone-verification records (destination number and a hashed one-time code)
  • Crash and error reports (see Sentry, below)

2.3 Customers

  • Service addresses: street, city, state, ZIP, notes, photos you upload, and the driveway or lot outline you draw
  • Precise GPS coordinates of each property, used to price, dispatch, and verify arrival
  • Job records: service type, snow depth, prices, discounts, ratings, timestamps, and status history
  • Before-and-after photographs taken by the assigned provider
  • In-app chat messages with the assigned provider
  • Disputes you file, including category, description, and any photos you attach
  • A Stripe customer identifier and payment-method identifier. We do not store card numbers, CVVs, or bank account numbers
  • Credits, referrals, and automatic-plowing settings if you use those features

2.4 Providers, fleets, and drivers

  • Driver’s license expiry date (solo drivers)
  • Auto insurance declarations page (or, for fleets, a commercial liability certificate), carrier, policy number, coverage amount, and expiry date
  • Vehicle and equipment details and photos you upload
  • Home or depot address and service-area radius
  • Availability you declare, and whether you are online
  • Precise device location while you are online or on an active job (see Section 3)
  • Every driver verifies their identity with Stripe Identity before taking jobs, whether they drive solo, for a fleet, or own or run the fleet they drive for: a photo of your driver’s license and a live selfie, which Stripe compares to the license photo. Stripe keeps the images, the face comparison, and the details it reads from the license, under its own policy. We keep the result (verified or not, the date, and any error reason), the name read from the license, and, for solo drivers, the license expiry date
  • A Stripe Connect account identifier and payout-enabled status. Tax identity (SSN/EIN) and bank details are collected by Stripe, not by us
  • Earnings, payouts, ratings, job performance, and any warnings or suspensions

2.5 Information we do not collect

We do not store payment-card numbers. We do not run a criminal background check. We do not receive or store the selfie images or face data from identity verification; those stay with Stripe. We do not sell your personal information.

3. Location

Location is the most sensitive data the Service uses. Please read this section even if you skip the rest.

3.1 Customers

We store the coordinates of properties you add so we can dispatch a provider and confirm they arrived. We do not continuously track a customer’s phone.

3.2 Providers and fleet drivers

While you are online or on an active job, the Provider app collects precise location from your device, even when the app is closed or not in use, so that:

  • The assigned customer can watch you approach on the live map
  • We can verify you are within about 200 meters of the property before you mark arrived
  • Our operators can see online providers on a live operations map for dispatch, safety, and fraud prevention
  • We can investigate no-shows, GPS spoofing, and disputes

We do not collect provider location while you are offline with no job. Going offline stops the live stream unless you hold a job, which keeps sending your position until it ends; signing out stops it. A position your phone sends while you are offline with no job is held for up to 2 minutes and used only if you go online in that time. On a job, we save your position about every 30 seconds from the moment you accept it until you complete it, and for up to about 5 minutes after while your phone is still sending it, with your phone’s own time for each point and whether your phone reported it as a mock (simulated) location. We also save where you were when you started work and when you finished, and the truck you arrived in. That record stays with the job. Location from time off any job is deleted after 90 days (Section 6).

Before the operating-system prompt, the Provider app shows an in-app explanation of background location. It then requests “Always” permission so we can share your position with customers while you are online or on a job. You can decline Always; tracking then works only while the app is in the foreground, and some job features may fail.

3.3 Who can see live location

  • The customer on that job, from acceptance until the job ends
  • The assigned provider (their own device)
  • Fleet dispatchers on the same fleet account, for their drivers
  • Quick To Connect operators with admin access, for all providers who are currently online

4. How we use information

  • Create and secure your account, including phone or email verification and optional 2FA
  • Price, book, dispatch, track, complete, and pay for jobs
  • Send job updates by push notification, email, and SMS fallback
  • Verify provider arrival, photos, insurance, and license expiry
  • Process authorizations, captures, refunds, credits, and payouts through Stripe
  • Handle disputes, no-shows, cancellations, and fraud
  • Show snow conditions and forecasts, and operate automatic plowing, using the National Weather Service. It receives an approximate location of your property (about 1 km), not your identity
  • Improve reliability (crash reports, rate limiting, abuse detection)
  • Comply with law, tax, and payment-network rules, including information Stripe needs for 1099-K when enabled
  • Communicate about the Service. You can opt out of marketing email. We may still send transactional messages needed to perform a job or secure your account

5. Who we share information with

We share personal information with service providers who process it on our behalf, and with the other party to a job when that is required to perform the Service (for example, a customer sees the assigned provider’s name and live location; a provider sees the property address and notes).

Processors we actually use:

  • Stripe, Inc. (USA) — payments, payouts, and provider identity verification via Stripe Identity
  • Amazon Web Services (USA) — storage of photos, avatars, and insurance documents
  • Mailgun (USA) — transactional email
  • Twilio (USA) — SMS one-time codes and SMS fallback when push cannot be delivered
  • Expo / Apple Push Notification service / Firebase Cloud Messaging — push delivery
  • Google (USA) — Maps, Places autocomplete, and geocoding of addresses you enter
  • Sentry (USA) — crash and error reporting. We attempt to avoid sending card data, full JWTs, or precise location traces in error payloads
  • Hetzner (hosting) — the application database and files that make the Service run. These servers may be located outside the United States

We also share information if required by law, to protect rights and safety, in connection with a merger or sale of the business, or with your direction.

The National Weather Service receives an approximate location (about 1 km) of the property you book or view, not your identity.

None of this sharing includes your mobile number or your consent to receive texts for anyone else’s marketing. Text messaging opt-in data and consent are never shared with third parties, as described in section 11.

6. Retention

GPS: A provider’s location from time off any job is deleted automatically 90 days after it is recorded. Location recorded during a job (the trail from accept to about 5 minutes after complete, and the coordinates at each status change) is part of the job record and is kept with it, whether or not anyone files a dispute, so we can answer a damage or injury claim.

Insurance documents: When a provider uploads a new insurance document, the one it replaces is kept, hidden from the provider, for 2 years after it was replaced, then deleted, so we can answer a claim about a job done while it was in force. If the provider closes their account after doing a job, it stays with their sealed claims record and is deleted with it; otherwise it is deleted at close.

Everything else: Job records, photographs, chat messages, reviews, sign-in IP history (deleted when you close the account, except what a provider’s sealed claims record keeps), and event logs are kept until we no longer need them for the Service, accounting, tax, chargebacks, disputes, safety, or legal obligations. There is no shorter automated deletion schedule for those categories.

Account closure: You may close your account in the Service. If you have a password, we ask for it before closing. If you don’t, and your phone is verified, we text you a code to enter. We remove your name, email, phone, and photo, sign you out everywhere, and delete the Stripe customer and Connect records we hold. We also delete saved addresses you never booked, and your sign-in history and insurance documents, except what a provider’s sealed claims record keeps. An address a job used keeps its street with that job; its notes, driveway drawing, and hazards are deleted. We cannot close the account while a job is still going, or while your report on a job is still open. Closing a company signs everyone there out. A driver who only belongs to that company is closed too. A driver who also has their own account keeps that account. When a provider, fleet, or fleet driver who did a job closes or leaves, we first seal a claims record: legal name, contact details at closing, the ID check session reference and the name read from the license of anyone who drove, every sign-in (time, IP, and device/browser string), every insurance document still on file with its carrier, policy number, and expiry, truck plates, and the fleet a driver worked for. Only our team can see it. It is kept for 2 years after that provider’s last job, then deleted, so we can answer a damage or injury claim. A report or incident on one of that provider’s jobs keeps it longer: while the report is open, for 2 years after the report or incident, or until the end of a legal hold our team sets. Closure does not delete historical jobs, payments, job photos, chat messages, reviews, or event records tied to that account. Those remain as business records. Email support@quicktoconnect.com if you need a broader deletion request; we will honor it except where we must retain information for an unresolved dispute, a legal requirement, or fraud and safety.

7. Your choices and rights

  • You can access and update name, email, password, notification preferences, properties, and payment methods in the app or web app
  • Providers can go offline to stop live location
  • You can disable push notifications in device settings; we will still email or SMS when a job requires it
  • You can close your account as described in Section 6

Residents of the United States may request access to, correction of, or deletion of personal information we hold, or an explanation of our sharing practices, by emailing support@quicktoconnect.com. We will verify the request and respond within the time required by applicable law. We will not discriminate against you for exercising these rights.

If you are in the European Economic Area or United Kingdom, we still process the categories above in order to perform a contract with you and for our legitimate interests in operating a safe marketplace. The Service is built for Alaska and is not directed at the EU. Contact us at support@quicktoconnect.com to exercise GDPR rights if they apply to you.

8. Children

The Service is for people 18 years or older. We do not knowingly collect personal information from children under 13. If you believe we have, contact support@quicktoconnect.com and we will delete it.

9. Security

We use TLS in transit, hashed passwords, encrypted 2FA secrets, tenant isolation in our application, and Stripe for card data. No method of transmission or storage is completely secure. Do not send payment-card numbers to us by email or chat.

10. Cookies and similar technology

The marketing site and web app use cookies and similar storage to keep you signed in, remember preferences, and keep the Service secure. We do not operate a third-party advertising network on the marketing site. Your browser can block cookies; some features will then fail.

11. SMS

If you give us a phone number, we use it to send verification codes and, if you enable SMS or if push cannot be delivered, job and account messages. Message frequency varies. Message and data rates may apply. Reply STOP to opt out of non-essential SMS, or HELP for help. We may still send messages required to complete an active job or secure your account.

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. Twilio sends our texts as our service provider and uses your number only to deliver them.

12. Changes

We will post changes on this page and update the effective date. If a change materially expands how we use location or other sensitive information, we will provide additional notice (for example in the app or by email) where required.

13. Contact

Quick To Connect, LLC
Wasilla and the Mat-Su Valley, Alaska
support@quicktoconnect.com
https://quicktoconnect.com/contact

For account deletion requests you may also use in-app account close, or email support@quicktoconnect.com with the subject line “Delete my account.” Dedicated pages: account deletion and data deletion.