KeyZup Notice at Collection — Just-in-Time Notices
| Field | Value |
|---|---|
| Version | 1.0.0 |
| Effective date | August 8, 2026 |
| Audience | Customers and service providers (independent technicians and locksmith companies) at the point of data collection in the mobile/web UI |
| Acceptance method | Displayed just-in-time at the relevant UI moment; some notices paired with an affirmative action (e.g., OS permission, checkbox) |
| Change notice | Updated in-product when flows change; effective date updated on posting |
| Governing law | the laws of the state in which KeyZup is organized, without regard to its conflict-of-laws principles |
How to use these
Each block below is written to sit next to the relevant control in the real app or website (permission prompt, upload screen, billing screen, etc.). Keep each block short and place a link to the full Privacy Policy. Where a notice pairs with consent or a required disclosure, it is presented together with the affirmative action (for example, an OS permission prompt or a checkbox).
1. Location permission
What we collect: Your device location (precise and/or approximate) while you use location features. Why: To match you with nearby jobs or providers, route to the service site, and coordinate on-site service. Who may receive it: The matched provider or customer for the job, and our infrastructure vendor (Firebase/Google). Required or optional: Optional — you can decline or later revoke it in your device settings, though some matching features may not work. Learn more: See our Privacy Policy. privacy@keyzup.com
2. Identity / document upload
What we collect: Identity documents, licences, insurance, and business documents you upload. Why: To verify provider or company identity and eligibility for trust and safety, on a point-in-time basis. Who may receive it: Stored in Firebase Storage with owner/admin access only; KeyZup administrators access them through short-lived signed links. Not public. Required or optional: Required to become a verified provider/company; you choose whether to proceed with onboarding. Learn more: See our Privacy Policy. privacy@keyzup.com
3. Background screening
What we collect: Your consent and the information needed to initiate a background check with a screening provider. Why: To assess eligibility for the platform. KeyZup stores only the check status/reference — we do not store the background report itself. Who may receive it: The background-screening provider that performs the check, which acts as a service provider; KeyZup receives status/reference back. Required or optional: Required where screening applies; you must provide separate authorization first. Screening is point-in-time. Learn more: See the Background Screening Consent Framework and Privacy Policy. privacy@keyzup.com
4. Billing card setup (providers/companies)
What we collect: Your payment card details, entered directly into our payment processor. Why: To bill provider platform fees and company subscriptions through your provider wallet. Who may receive it: Stripe processes and tokenizes the card. KeyZup does not store your full card number — only a card summary and a Stripe token reference. Required or optional: Required to pay platform fees / subscribe. Note: customers pay providers directly and do not enter card details here for service payments. Learn more: See our Privacy Policy. privacy@keyzup.com
5. Message / photo upload
What we collect: The messages and images you send in in-app chat. Why: To let you communicate and share job-relevant photos with the other party. Who may receive it: The other participant in the conversation; images are stored in Firebase Storage. Required or optional: Optional — only what you choose to send. Learn more: See our Privacy Policy. privacy@keyzup.com
6. Portfolio publication (providers)
What we collect: The portfolio images and details you choose to publish. Why: To showcase your work on your public provider profile. Who may receive it: These are intentionally public on your profile once published and may be seen by anyone. Required or optional: Optional — publish only what you want shown publicly; you can remove items. Learn more: See our Privacy Policy. privacy@keyzup.com
7. Push notifications
What we collect: A push token and related device data. Why: To send you job updates, messages, and account notifications. Who may receive it: Firebase/Google (FCM) and Apple/Google push infrastructure. Required or optional: Optional — you can decline or turn off notifications in your device settings. Learn more: See our Privacy Policy. privacy@keyzup.com
8. Company technician data access
What we collect / what is shared: When you join or are added to a locksmith company, certain of your profile, job, and verification-status data may be visible to that company's authorized administrators. Why: To let the company manage its technicians, assign work, and meet its own trust-and-safety obligations. Who may receive it: The company's authorized administrator users within KeyZup. Required or optional: Required to operate as a technician under a company; the scope of company access is limited to what the company needs to manage its technicians and meet its trust-and-safety obligations. Learn more: See our Privacy Policy. privacy@keyzup.com