Draft privacy information.
These development data practices describe the implemented application. A final privacy policy, responsible entity, contact and retention schedule still require review before real services.
Open your account data controlsDevelopment accounts and DEMO
Configured sign-in uses Supabase email authentication and stores consented account records. Explicit DEMO screens are read-only and do not authenticate or load real private accounts. Theme preferences and optional unsent request drafts may be stored locally; sign-out clears account drafts.
Collect only what is needed
The application uses verified email, consented name, optional +92 phone, basic vehicle information, service symptoms, general zones and quotation or booking records. Photos are optional. Identity documents and precise GPS are not default intake requirements.
Limit who can see it
Account and database checks isolate garages and requests. Eligible verified workshops see anonymized briefs before assignment. Booking contact and exact site disclosure need the accepted assignment and current consent. Uploads remain private and each image read rechecks access.
AI and third parties
Optional server-side symptom analysis requires separate consent, enabled configuration and a call allowance. Known identity/contact details and precise locations are redacted; photos are not sent. The manual quotation path remains available. Database reports contain aggregate outcomes, not personal fault text; processor agreements and data residency still require review.
Choice and retention
Account tools support profile correction, owner-set reminder consent, paginated record downloads and deletion requests with independent review. A request does not immediately erase records, cancel services or waive financial obligations. Automated erasure is disabled pending an approved retention policy and execution process. No marketing delivery is activated.
Security and contact
Usage is recorded to run and improve the service: pages visited, buttons and fields used (never what you type), device type and time, linked to your account when signed in. Only MFA-verified administrators can view it, and raw activity is deleted after 90 days. Privileged workflows require verified roles and operator MFA. Account holders can invalidate all existing application sessions. Private notes and finance evidence stay in their scoped workflows. External monitoring and the responsible privacy contact must be configured and tested before launch; no contact address is invented here.