Verification, Licence & Insurance Policy
| Field | Value |
|---|---|
| Version | 1.0.0 |
| Effective date | August 8, 2026 |
| Audience | KeyZup provider-side users (independent technicians and locksmith companies); internal review/trust operations |
| Acceptance method | Provider onboarding acceptance (click-through) at account creation and on material update; re-acceptance on version change |
| Change notice | Material changes communicated in-app and/or by email; continued use after the effective date constitutes acceptance |
| Governing law | the laws of the state in which KeyZup is organized, without regard to its conflict-of-laws principles |
1. Purpose and operating model
KeyZup operates as a technology marketplace / intermediary. KeyZup does not perform locksmith services. Services are provided by independent technicians and locksmith companies who are not KeyZup employees. Customers pay providers directly; KeyZup does not process customer payouts to providers. KeyZup charges providers platform fees and companies subscriptions.
This policy defines the documents KeyZup may collect to support provider verification, how those documents are reviewed, and — separately — what any future public verification badge does and does not communicate. Verification and any background checks are point-in-time checks, not guarantees (see Section 11).
Current status of features described here: Enforcement is currently OFF. No background-check vendor is connected. No public verification badges are launched yet. Company approval does not auto-approve individual technicians. Sections describing badges and background checks are forward-looking and are not live.
2. Required document categories
The platform implements the following canonical verification document categories. Which categories are required depends on role (technician vs. company) and jurisdiction (Section 3).
| Category (canonical) | Applies to | Purpose |
|---|---|---|
identity | Technician; company principal | Confirm the person's claimed identity against a government-issued document |
licence (locksmith licence) | Technician (jurisdiction-dependent) | Evidence of an individual locksmith licence where the jurisdiction requires one |
insurance | Technician; company | Evidence of applicable insurance coverage (see Insurance Requirements Framework) |
police_clearance / background | Technician (where enabled) | Police clearance or background-check documentation, where applicable and lawful |
business_registration | Company | Evidence the business entity is registered |
business_license (company licence) | Company (jurisdiction-dependent) | Company-level locksmith/operating licence where required |
proof_of_address | Technician; company | Confirm a claimed address |
Expiry dates are captured for time-limited documents (e.g., licences, insurance, clearances). See Section 5.
3. Jurisdiction dependency
Licensing requirements vary by jurisdiction. KeyZup launches initially in the United States (multi-state) and the app also supports Canada (Ontario and Quebec).
- United States — per state. Some states require a locksmith licence, some do not, and some require manual review to determine applicability, as provided by the laws applicable to your jurisdiction, including the per-state matrix and any local/municipal requirements.
- Canada — ON / QC. Requirements are assessed per province, as provided by the laws applicable to your jurisdiction (provincial equivalent).
Where a jurisdiction does not require a locksmith licence, absence of a licence document is not a deficiency, and no "Licence Verified" badge (Section 10) may be asserted on the basis of licensure that does not exist there.
4. Review standards
Document review aims to confirm that a submitted document (a) is of the correct category, (b) is legible and appears authentic on its face, (c) matches the provider's claimed identity/entity where relevant, and (d) is unexpired at time of review.
- Review is a records check, not an investigation, audit, or field inspection.
- Review confirms information available at the time; it does not validate ongoing conduct or work quality.
- Some determinations (e.g., US states requiring manual review) are routed to a human reviewer.
- KeyZup may rely on issuing-authority records or third-party sources where available and lawful; where a background-check vendor is later connected, its findings are governed by that vendor's scope and this policy's point-in-time disclaimer.
5. Expiry and re-verification
- Expiry dates are captured where documents are time-limited.
- Ahead of and upon expiry, KeyZup may request re-verification / resubmission of a current document.
- Failure to provide current documentation by the required date may result in loss of any associated verified status and/or suspension or restriction (Section 8) of the ability to receive jobs, subject to enforcement being enabled.
- Re-verification restores verified status only after successful review of the newly submitted document.
6. Rejection and resubmission
- A submitted document may be rejected where it is illegible, wrong category, expired, mismatched, incomplete, or reasonably suspected to be inauthentic.
- The provider is notified of rejection and may resubmit. KeyZup may limit resubmission attempts or require additional documentation.
- Rejection of a document is an operational determination about that document; it is not a legal finding about the provider.
7. Company coverage vs. personal requirements
- Company approval does not auto-approve technicians. A company's verification (e.g.,
business_registration,business_license, companyinsurance) covers the company. Individual technicians affiliated with a company remain subject to their own applicable requirements (e.g.,identity, individuallicencewhere required, and any technician-level checks). - Where a company policy is intended to extend coverage to affiliated technicians, that extension must be documented at the individual/coverage level; company-level records alone do not establish technician-level coverage.
8. Suspension and restriction
- KeyZup may suspend or restrict a provider account (including limiting eligibility to receive jobs) where documentation is missing, expired, rejected, or suspected fraudulent, or pending review of an incident (see Incident, Complaint & Appeal Policy).
- A suspension or restriction is an operational, precautionary measure. It is not a legal finding of wrongdoing.
- These mechanisms exist in the system; enforcement is currently OFF and will be enabled per launch decisions.
9. Fraud and suspected alteration
- Documents reasonably suspected to be forged, altered, or fraudulently obtained may be rejected, and the associated account may be suspended or restricted pending review.
- Suspected fraud may be referred to the relevant issuing authority, insurer, or law enforcement where appropriate.
- Submitting falsified verification documents is grounds for removal from the platform.
10. Public badge meanings (forward-looking; none live yet)
No verification badges are live yet. The following defines the only approved badge labels and their precise meanings for when badges are enabled. Badges are server-derived from the underlying document/check records — they are not self-declared by providers and are not editable client-side.
Only these five badge labels are approved. No other verification wording is permitted.
| Badge (exact label) | What it means | What it does NOT mean |
|---|---|---|
| Identity Verified | At the time of the check, an identity document was reviewed and appeared to match the provider's claimed identity. | Does not mean the provider is safe, trustworthy, or of good character; does not guarantee current identity status or ongoing conduct. |
| Licence Verified | At the time of the check, a locksmith licence (individual) applicable to the provider's jurisdiction was reviewed and appeared valid/unexpired. | Does not mean a licence is required or exists in jurisdictions that do not license locksmiths; does not guarantee the licence remains current, unrevoked, or that work will meet any standard. |
| Insurance Confirmed | At the time of the check, an insurance document evidencing applicable coverage was on file and appeared valid/unexpired. | Does not mean any particular claim is or will be covered, that limits are adequate, or that coverage remains in force; coverage terms are set by the insurer, not KeyZup. |
| Background Check Completed | At the time of the check, a police_clearance / background document or connected-vendor check was completed within its defined scope. | Does not mean the provider has no criminal history beyond the check's scope/jurisdiction, is safe, or will behave lawfully; scope and recency are limited. |
| Company Verified | At the time of the check, company records (e.g., business_registration and, where required, business_license) were reviewed and appeared valid. | Does not verify or vouch for any individual technician affiliated with the company; does not guarantee the company's ongoing standing or the quality/safety of its work. |
10.1 Prohibited claims
KeyZup and its surfaces must not describe providers or badges using broad or absolute terms, including but not limited to: "Safe," "Trusted," "Fully vetted," "Guaranteed," or "KeyZup certified." These terms overstate the point-in-time, records-based nature of verification and are prohibited in product copy, marketing, and provider-facing labels.
11. Point-in-time-check disclaimer (prominent)
POINT-IN-TIME CHECK — NOT AN ONGOING GUARANTEE. Any verification or background check reflects only the information available at the time the check was performed. A completed check is not an ongoing guarantee of a provider's identity, licence status, insurance coverage, background, character, conduct, or the quality or safety of any work performed. Status can change at any time after a check. KeyZup is a marketplace intermediary and does not perform the services, supervise providers, or warrant outcomes.