Information used
Identity and contact details, registered vehicles, mileage, bookings, service history, Vehicle Health assessments, fuel records, memberships, orders, notification choices, and support activity.
DRAFT V1 · PRIVACY SUMMARY
How CarPlug uses your vehicle and account data.
This Version 1 product summary explains the data paths implemented in the platform. CarPlug Ghana must approve the formal policy owner, address, retention periods, and effective date before launch.
Why it is used
To authenticate your account, operate the workshop and store, calculate explainable Vehicle Health, provide reports and fuel insights, verify membership, deliver requested notifications, prevent fraud, and keep auditable business records.
Zeus privacy
You can use Zeus without an account. Guest guidance sends your question and relevant public CarPlug catalogue options to the configured AI provider. When you are signed in with a selected vehicle, guidance may also send limited vehicle context—including year, make, model, bounded Vehicle Health, latest-service, fuel-trend, and catalogue information. CarPlug excludes your name, phone, plate, VIN, and complete records. For eligible general guest questions, CarPlug may privately retain a SHA-256 question digest, a validated redacted answer, and its public source links for up to 30 days so Zeus can answer the same question without another AI-provider request. The question text is not retained in this cache; personal, account, booking, product-compatibility, symptom, warning-light, and safety questions are excluded. Signed-in demand analytics store a coarse topic and SHA-256 prompt digest rather than the raw question; guest questions are not written to customer conversation records. An optional, off-by-default control lets you share a redacted question-and-answer sample in CarPlug’s private R2 improvement dataset. Rating a Zeus answer also submits a redacted copy of that question, answer, and your helpful or not-helpful rating. These samples contain no customer or vehicle ID, are marked for human review, and are never treated as automatically correct training material.
Firebase authentication and notifications
When Firebase phone sign-in is enabled, Google Firebase processes the phone number and verification activity to authenticate the account and prevent abuse. Firebase Cloud Messaging processes a device token and notification delivery metadata. CarPlug does not ask for or store your one-time code after Firebase verifies it.
Deletion and retention
Account deletion revokes sessions, deactivates active ownership, and pseudonymises direct profile identifiers. Workshop, membership, payment, order, safety, fraud-prevention, dispute, and accounting records may be retained when legally or operationally required.
Your controls
You can edit fuel records, manage notification preferences, distinguish user-added from CarPlug-verified history, archive vehicles, and delete your account in the mobile app. The public account-deletion page explains the in-app and support-assisted request paths.