MCar Lead Privacy Policy
Updated 1 November 2026
This policy explains how MCar Lead at mechanichead.com handles account and dealership data. MCar Lead is a browser-based CRM for car dealerships: lead assignment, customer follow-up, test-drive scheduling and lead-statement reconciliation. Contact the MCar Lead team at hijabcantic@gmail.com about this policy.
Data we collect
When you register or sign in by email, we collect your email address and optional display name. When you choose Google sign-in, Google provides a unique account identifier, your verified email and basic profile, including your name and potentially a profile-picture URL. We store the identifier, email and display name to link your account; we do not download or store your Google profile photo. We do not request access to Gmail messages, contacts, Drive files or calendars.
Why we use Google and account data
We use your verified email, name and Google identifier only to authenticate you, link subsequent sign-ins to the same account, identify your account in the app and match the email your dealership manager invited. Registration alone does not grant store access. Google account data is not used by MCar Lead for advertising, sale, unrelated profiling or training AI models.
Customer inquiry forms and imports
Campaign links let customers submit a name, contact details, vehicle interest, request and contact permission without a CRM account. Authorized staff can paste conversations or import CSV records for review. We store original text, campaign attribution, consent evidence and duplicate indicators in the store database. Unassigned public inquiries are available to managers; sales can review their own drafts and records assigned to them. Public submissions cannot read store records. A daily hashed IP identifier and submission times limit form abuse. LINE OA messages are received only after a manager configures the Official Account connection. Personal LINE chats, historical chats and Meta accounts are not read automatically.
LINE Official Account messages
When a manager connects a LINE Official Account, we verify inbound webhook signatures and store the OA-scoped LINE user identifier, incoming message text or message-type metadata, message identifiers and timestamps. We use these to group conversations and link subsequent messages to the same inquiry or assigned lead. Channel credentials are encrypted and available only to the server. We do not fetch attachment binaries or send automatic replies in this version. Received unsend events remove the stored message text; explicit staff notes remain subject to the store record policy. Unassigned conversations are manager-only, while assigned conversations are visible to the assigned salesperson.
Dealership records
Managers and invited sales staff may enter customer names, telephone numbers, email addresses or LINE IDs, vehicle interests, lead sources, consent evidence, assignment and follow-up history, test-drive appointments and reconciliation records. We use these records to provide the dealership workflow and audit trail. Managers can access their store data; sales staff can access leads assigned to them. The dealership must have permission to enter and contact its customers.
Security and technical information
We store data in the hosted application database provided through Sites and Cloudflare. We use HTTPS in transit, server-side role checks and HttpOnly session cookies. Sign-in codes, link tokens and session tokens are stored as hashes. Email codes and links expire after ten minutes and are single-use; an app sign-in session expires after fourteen days unless revoked earlier. Hashed IP identifiers, request times, failed attempts and operational logs may be processed to prevent abuse and troubleshoot the service.
Service providers and sharing
Google handles the sign-in authorization you choose to initiate. Resend receives recipient email addresses and message content to deliver verification and invitation emails. Sites and Cloudflare provide application hosting, database and operational infrastructure. These providers process information needed for their respective services, potentially outside your country. We share dealership records only through authorized store access, manager-requested exports/backups, necessary service operations or a valid legal requirement. MCar Lead does not sell Google user data or customer records.
Retention and backups
Account identifiers and dealership records remain while needed for an active account and store operation, or until an approved removal request is carried out. Expired verification challenges, Google sign-in state and sessions are cleaned up during service activity; cleanup is not an immediate scheduled deletion guarantee. Up to twenty business snapshots are retained in the app. Managers may download copies; downloaded copies remain under their control. Business audit or locked-statement records may need separate retention review before removal.
Access, correction, deletion and withdrawal
For a copy, correction or deletion of your account data, contact hijabcantic@gmail.com from your registered email. For customer or dealership records, contact the responsible dealership manager; the MCar Lead team can coordinate the request. We verify identity and authority before acting and explain any records that need retention. Signing out revokes the current app session. A manager can disable store access. You can also remove MCar Lead access in your Google Account connections; this does not itself delete existing dealership records. Requests are handled manually; there is no automatic account-deletion button in this version.
Cookies and choices
A necessary session cookie keeps you signed in; browser local storage remembers your chosen interface language and retains unconfirmed CRM operations, including their entered fields, on this device until confirmation or explicit discard. Clearing site data removes these local drafts; they do not transfer to another device. Temporary sign-in state protects the Google flow. The app does not implement advertising cookies. You can use email sign-in instead of Google, but store access still requires a manager invitation.
Drafts on this device
Customer forms, quick capture and follow-up inputs are retained in tab session storage. Unsent drafts are removed when reopened after 24 hours. Unconfirmed inquiry submissions keep the same receipt until confirmation to avoid duplicates. Closing the tab or clearing site data can remove these drafts.
Changes and contact
We publish policy updates on this page with an updated date. Before using Google account information for a materially different purpose, we will update the disclosures and obtain any authorization required. Questions and data requests: hijabcantic@gmail.com.