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.
Auto AI privacy
When you use CPG Auto AI, web-assisted guidance may send your question and limited selected-vehicle context—including year, make, model, bounded Vehicle Health, latest-service, fuel-trend, and catalogue information—to the configured AI provider. CarPlug excludes your name, phone, plate, VIN, and complete records. Demand analytics store a coarse topic and SHA-256 prompt digest rather than the raw question.
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.