Insurance Requirements Framework
| Field | Value |
|---|---|
| Version | 1.0.0 |
| Effective date | August 8, 2026 |
| Audience | Provider-side users (independent technicians and locksmith companies); internal trust/operations |
| Acceptance method | Not a click-through policy; internal framework stating the insurance coverage KeyZup requires of providers |
| Change notice | Material changes communicated to affected parties; provider-facing requirements are issued to providers |
| Governing law | the laws of the state in which KeyZup is organized, without regard to its conflict-of-laws principles |
0. Purpose and scope
This document states the insurance coverage types KeyZup requires for the KeyZup marketplace. Coverage limits are those required by KeyZup and applicable law.
KeyZup is a technology marketplace / intermediary. It does not perform locksmith services; independent technicians and locksmith companies do. Customers pay providers directly. Nothing in this framework makes KeyZup the insurer, guarantor, or underwriter of any provider, nor does listing a coverage type imply any claim is covered.
Coverage limits are those required by KeyZup and applicable law and apply as provided by the laws applicable to your jurisdiction.
1. Independent technician — required coverage types
For independent technicians operating on the platform, KeyZup requires the following coverage types, as applicable to the technician's activities and jurisdiction.
| Coverage type | Why it may apply | Required limit |
|---|---|---|
| Commercial General Liability (CGL) | Third-party bodily injury / property damage arising from work | limits as required by KeyZup and applicable law |
| Errors & Omissions / Professional Liability (where appropriate) | Alleged negligent service, faulty workmanship, or advice | limits as required by KeyZup and applicable law |
| Commercial Auto (where driving for work) | Liability arising from vehicle use in the course of work | limits as required by KeyZup and applicable law |
| Tools & Equipment coverage | Loss/damage to the technician's own tools and equipment | limits as required by KeyZup and applicable law |
| Cyber / Privacy (where applicable) | Exposure from handling customer data / smart-lock or connected systems | limits as required by KeyZup and applicable law |
Which types are mandatory depends on jurisdiction and activity profile, as provided by the laws applicable to your jurisdiction.
2. Company — required coverage types
For locksmith companies operating on the platform (and their affiliated technicians), KeyZup requires the following coverage types, as applicable to the company and its affiliated technicians.
| Coverage type | Why it may apply | Required limit |
|---|---|---|
| Commercial General Liability (CGL) | Third-party bodily injury / property damage | limits as required by KeyZup and applicable law |
| Commercial Auto | Fleet / work vehicle liability | limits as required by KeyZup and applicable law |
| Workers' Compensation / Employer coverage (where legally required) | Statutory coverage for employees | limits as required by KeyZup and applicable law |
| Employee / contractor coverage | Coverage extending to workers performing services | limits as required by KeyZup and applicable law |
| Errors & Omissions / Professional Liability | Alleged negligent service or faulty workmanship | limits as required by KeyZup and applicable law |
| Umbrella / Excess liability | Additional limits above primary policies | limits as required by KeyZup and applicable law |
Workers' compensation and employer requirements are jurisdiction-specific and statutory and apply as provided by the laws applicable to your jurisdiction. Company coverage does not automatically satisfy individual technician requirements (see Verification, Licence & Insurance Policy, company vs. personal coverage).
3. KeyZup — platform / intermediary coverage
KeyZup maintains insurance appropriate to its role as a marketplace intermediary. As an operating business and platform, KeyZup's coverage addresses:
- Platform / commercial general liability — general third-party exposure for KeyZup as an operating business.
- Technology E&O — errors/omissions arising from the software platform, verification workflows, and badge logic.
- Cyber liability — data breach, security incident, and privacy exposure from customer/provider data.
- Media liability — exposure from platform content, provider listings, and badge/verification representations.
- Crime / fraud — internal and third-party fraud, social engineering, funds/data theft.
- Contingent liability — exposure that could flow to KeyZup from provider acts/omissions despite the intermediary model.
- Hired / non-owned auto exposure — any auto exposure attributable to platform operations.
- Marketplace / platform endorsements — endorsements specific to two-sided marketplaces and intermediary status.
Coverage types, limits, and endorsements are those required by KeyZup and applicable law, consistent with KeyZup's intermediary / non-service-provider posture.
4. Provider insurance record fields
For each provider insurance document on file, capture at least the following (aligns with the insurance verification category):
| Field | Notes |
|---|---|
| Carrier / insurer name | Issuing insurance company |
| Policy number reference | Store reference; treat as sensitive |
| Coverage type | Map to Section 1 / Section 2 types |
| Limit | Recorded value; compare against the limits required by KeyZup and applicable law |
| Effective date | Coverage start |
| Expiry date | Drives renewal-evidence workflow (Section 5) |
| Certificate on file | Whether a certificate of insurance (COI) / evidence is stored |
| Additional insured (where applicable) | Whether KeyZup or a company is named as an additional insured where required |
5. Renewal-evidence workflow
- Capture effective and expiry dates for every insurance record.
- Ahead of expiry, prompt the provider to submit a renewal certificate / updated evidence.
- On successful review, update the record (new effective/expiry dates, certificate on file); on failure or lapse, the provider may lose "Insurance Confirmed" status and be subject to suspension/restriction once enforcement is enabled (see Verification, Licence & Insurance Policy).
- Maintain history of prior certificates for audit.
- Renewal review is a records check and is point-in-time; a certificate on file does not guarantee coverage remains in force or that any claim is covered.