Collect less
Only collect information required for an enabled capability. Sensitive histories should not become permanent records simply because storage is available.
PPATCHESPRIVACY PRINCIPLES
PATCHES should protect your privacy — not monetize it.
Our product architecture starts with data minimization, purpose limitation, user control and short retention instead of building another permanent surveillance history.
Location restraint
PATCHES is not designed to make Convex a permanent database of historical driving routes. Location-dependent features should use the least data and retention necessary.
No surveillance business model
PATCHES is designed around paid protection and licensed technology — not selling customer behavior for advertising profiles.
User-controlled protection
Encryption, deletion, consent, recovery and device capabilities should be explicit and understandable, with stronger warnings for irreversible actions.
This page describes PATCHES product and engineering principles. A final customer Privacy Policy, Terms of Service and jurisdiction-specific disclosures will be published before general availability.