Privacy Policy

Last updated: November 19, 2026

1. Who we are

Autoentic LLC is a Texas-registered limited liability company. We build and operate the Autoentic vehicle paint thickness verification system, used by paint protection film (PPF) shops, dealerships, auction houses, and vehicle owners to produce tamper-evident inspection records.

For any privacy question, email legal@autoentic.com. We have not designated a formal Data Protection Officer; privacy requests are handled directly by the Autoentic team at the same address.

2. Scope

This policy covers three surfaces, which we collectively call the "Service":

  • The marketing and partner site at autoentic.com
  • The Autoentic mobile app for Android and iOS, used by inspectors and PPF shop technicians
  • The backend API at api.autoentic.com

3. Information we collect

We collect only what we need to operate the Service. The categories below cover everything we collect across the website, the app, and the backend.

  • Organization and manager information. Business name, business address, business phone number, manager email, manager role (partner or admin), and billing details for organization-level billing handled by Stripe. Once we confirm a business, its name is shown publicly beside each record it makes from then on, on that car's Paint Passport. It stays there for as long as the record exists.
  • Vehicle owner information. When a vehicle owner books a service through autoentic.com, we collect contact details and billing information for the booking, processed through Stripe.
  • Shop buyer information. When a business orders a probe or kit from the shop on autoentic.com, we collect the buyer's name, email address, phone number and billing address, the name and address the order ships to, the business's name and type, the record that the buyer accepted the Terms of Sale and, if the buyer answers, how they heard about us. The buyer enters these on a checkout page run by Stripe, which also takes the card details; we do not receive the card number. We use these details to fill the order and, if the business has no Autoentic account yet, to open one; the buyer's phone number and billing city, state, ZIP and country then also become the business's contact details. We give DeFelsko Corporation, which makes the probe and ships it directly, the name and address the order ships to, the buyer's phone number, what was ordered and the shipping speed. We ask DeFelsko to send us back the tracking number and the probe's serial numbers.
  • Referral buyer information. When a car buyer asks for a quote through a dealer's referral link, we collect what they type: their first and last name, mobile number and email address, their vehicle (year, make and model, and the VIN if given) and what they want quoted. We check that the number is a mobile number and text it a 6-digit code, and we keep a record of that text (its message ID, when it was sent, and the number's line type). We keep a record of the buyer's consent: the exact wording they ticked and its version, the shop and dealer it named, when they ticked it, the IP address and browser of their phone, the privacy policy version they saw, whether the link came by QR code or text and, for a texted link, when the salesperson confirmed the buyer asked for it. We also keep a keyed code made from the number, which cannot be turned back into the number without our secret key, so we can tell whether a number has already asked or asked us not to text it again. If a salesperson added the vehicle's VIN to the link, we hold it with the link and delete it if no request is sent.
  • Dealer salesperson information. The name a dealer's manager types for each salesperson, and counts of the quote links each salesperson's page makes.
  • Shop acceptance records. When a partner shop accepts a referral, we keep who clicked Accept, when, the words on the button, the payment method charged (its brand and last four digits, or Link), and the IP address and browser used, as the record of the shop's permission for that charge.
  • Technician information. Self-declared first and last name and a personal mobile phone number. The phone number is used to text the technician a one-time passcode when they sign in. It is also sent with an inspection, but only while our servers do not yet have an ID for that technician; after that, inspections carry the ID instead. The organization dashboard of the PPF shop that employs the technician shows the last four digits of the phone number, not the full number. When a technician is invited by a partner organization, the organization may take account-affecting actions, including revoking the technician's access, viewing all of the technician's session submissions, and removing the technician from the organization.
  • Authentication data. Email addresses for partner and admin login, login timestamps, and one-time passcode delivery logs. For anyone who adds a passkey: its public key and its ID, the name its owner gives it, the kind of device or password manager that holds it, when it was added, and which passkey each sign-in was made with. The passkey itself never leaves the owner's device or password manager.
  • Probe and device data. The serial number and model of the DeFelsko PosiTector probe paired over Bluetooth; the device model, operating system and its version; and the app version and build. On every version of the app from Apple's App Store, and on Android from the first version after 1.3.0, each inspection also records the platform, app version, build and update it was measured with. When the app checks for updates, Expo, the service that delivers them, receives a random identifier for that installation and the operating system.
  • Vehicle data. The Vehicle Identification Number (VIN), typed in or read from a photo of the VIN plate, and decoded vehicle metadata (year, make, model, trim, body style, factory paint code).
  • Measurement data. Paint thickness readings in microns per body panel, panel sequencing, raw gauge readings, and the calculated Factory Originality Confidence Score (FOCS).
  • Optional VIN photos. A technician may photograph the VIN plate instead of typing the VIN. On every version of the app from Apple's App Store, and on Android from the first version after 1.3.0, the app asks first: it sends a photo only after a one-time OK that names Google Gemini, the AI service that reads it, and it deletes the photo file from the device before sending it. Android versions up to 1.3.0 send the photo when the camera is used, without asking first, and leave the photo file on the device. A photo whose VIN is read is not kept. When reading fails, the photo is kept on our servers for up to 7 days so we can find out why, and then deleted. Google reads the photo through the paid Gemini API, does not use it to train its models, and may keep it for a limited time under its API terms to detect misuse. The VIN can always be typed instead, and the OK can be taken back by reinstalling the app or clearing its data.
  • Location. One location fix when an inspection is submitted: precise, or approximate when the device allows only approximate location. It is stored with the inspection record and sealed with it, as audit context. A technician may decline, and the inspection is then sent without a location; a reference measurement needs one. The app asks for the permission before using it.
  • Bluetooth and camera permissions. Bluetooth permission to find and connect to the DeFelsko probe, and camera permission to photograph the VIN plate. We do not request access to the device photo library.
  • Diagnostic data (Sentry). Crash reports and stack traces; performance traces for a sample of app activity, and app sessions (whether each ended in a crash); breadcrumbs covering Bluetooth events, API calls, screens, and taps, with email addresses, VINs, phone numbers, and passcodes removed as each breadcrumb is recorded; the device model, operating system, app version, and build; and the technician's internal ID, the shop's ID, and the probe's serial number. We do not send measurement values or VIN photos to Sentry.
  • Server logs. Request timestamps, request paths, response codes, and user-agent strings from autoentic.com and api.autoentic.com. Our application database keeps raw IP addresses only in the records listed here: the terms acceptance on an access request and on a business account, a website sign-in session, a referral buyer's consent and a shop's referral acceptance. Other IP addresses are hashed before they are stored. Outside that database, raw IP addresses appear in two places only: the access logs of the reverse proxy on our own servers, where they are kept until the logs are rotated, and the record of a VIN lookup that failed, which keeps the request's IP address and browser details for up to 7 days so we can find out why.
  • Cookies on autoentic.com. Our complete cookie inventory: (1) a first-party, HTTP-only sign-in cookie, bound to the session, set when partners and admins log in; (2) a first-party, HTTP-only passkey cookie, set only while a passkey sign-in or a passkey being added is in progress, for up to 5 minutes; (3) __cf_bm, cf_clearance, and _cfuvid — Cloudflare Turnstile bot-protection cookies set only on the Request Access form and on the referral quote page, persistent for up to 30 minutes, used solely for fraud prevention. For traffic statistics we use a cookie-free tool that we run ourselves; it does not set cookies and does not store personal data. We use no other cookies. We do not deploy advertising or behavioral-tracking cookies in the Autoentic app, in api.autoentic.com, or in the partner and admin dashboard surfaces of autoentic.com. We do not respond to browser Do Not Track signals because we do not engage in cross-site behavioral tracking.

4. How we use information

  • Operate the Service. Pair probes to organizations, collect measurements, generate FOCS scores, and produce certification artifacts.
  • Maintain the audit trail. Location, timestamp, probe serial number, technician identity, and panel sequence form the legally significant record produced by an inspection. Inspection records are sealed with a hash chain so that any modification after submission is detectable.
  • Verify identity. SMS one-time passcodes to technicians when they sign in; email one-time passcodes to partner managers and admins at login.
  • Detect fraud and protect data integrity. We analyze panel sequencing and inspection timing to detect anomalies indicative of fraudulent or non-compliant inspections. This processing is workplace-quality monitoring conducted on behalf of the partner organization that employs the technician, under the organization-level consent established in our Terms of Service. Anomaly flags trigger human review by Autoentic personnel; they do not, by themselves, suspend, terminate, or otherwise take legally significant action against any technician.
  • Provide customer support. Respond to inquiries sent to support@autoentic.com.
  • Bill for the Service. Invoice partners for platform usage and vehicle owners for bookings, and take payment for shop orders, processed through Stripe.
  • Fill shop orders. Pass an order to DeFelsko to ship, and tell the buyer how the order is going.
  • Handle referrals. Send a buyer's request to the shop they named and a referral copy to the dealer; text the buyer the code they ask for; email the buyer about their request; record and honour withdrawals; prevent made-up or repeated referrals; and, before refunding a shop for a number it says does not work, call that number once to check.
  • Maintain reliability. Use Sentry for crash and error monitoring and review server logs for debugging and incident response.
  • Comply with the law. Respond to lawful subpoenas, court orders, and regulatory requests, including, where lawfully compelled, by producing inspection records, audit-trail data, and certification-artifact metadata in response to a subpoena, court order, or other valid legal process.
  • Improve the Service through aggregated insights. We may use aggregated and de-identified data — that cannot reasonably be linked to any individual, vehicle, vehicle owner, or organization — for service improvement, scoring-model development, and product analytics. Aggregated and de-identified data is not subject to the rights described in Section 10. We do not train AI or machine-learning models on identifiable user data, VIN images, or organization-specific records; model development uses only aggregated and de-identified data as described above.

5. Legal bases for processing

Autoentic is a B2B service primarily serving United States customers, but the backend runs on EU-hosted infrastructure. Where European data protection law applies, we rely on:

  • Performance of contract — operating the Service for partners and vehicle owners, filling shop orders, and handling a referral quote request a buyer makes.
  • Legitimate interests — maintaining the audit trail, preventing fraud, and keeping the Service reliable.
  • Legal obligation — retaining records and responding to lawful requests.
  • Consent — for any optional feature where you actively opt in, and sending a referral buyer's details to the shop and dealer they named.

We will formalize EU-specific representation, Standard Contractual Clauses across all subprocessors, and a complete GDPR rights workflow before our formal launch in the European Union.

6. Third-party processors

A subprocessor is a third-party vendor that helps us run the Service. Each vendor below receives only the data needed for its specific role.

  • Hetzner. Servers in the United States that host the backend, the database, the website, and the tools we run ourselves, and storage in Finland that holds our encrypted database backups.
  • Cloudflare. CDN, DNS, and TLS termination for autoentic.com static assets, plus Turnstile bot protection on the public Request Access form and the referral quote page. Sees request metadata (IP, user agent, request path) for traffic that passes through the edge.
  • Twilio. Sends transactional SMS one-time passcodes to technicians for identity verification and the 6-digit code a referral buyer asks for, and checks whether a referral buyer's number is a mobile number.
  • Resend. Sends transactional email, including login one-time passcodes, partner approval notifications, account messages, shop order emails (among them the order details we pass to DeFelsko), a referral buyer's status emails, and referral copies sent to a dealer's customer-records email address.
  • Sentry. Collects mobile and web crash reports, error events, and breadcrumbs for debugging.
  • Expo. Delivers app updates. Receives a random identifier for each installation of the app, and its operating system, when the app checks for an update.
  • Marketcheck. VIN-to-vehicle metadata lookup. We send only the VIN string and receive vehicle attributes back.
  • NHTSA vPIC. The public vehicle database of the U.S. National Highway Traffic Safety Administration. When our own VIN lookup fails, the app asks it directly for the vehicle's details, sending only the VIN.
  • Google Gemini. Reads the VIN from VIN photos (see Section 3). We use the paid Gemini API, under which Google does not use submitted content to train its models.
  • Stripe. Payment processing for organization-level partner billing, for vehicle owner bookings, and for shop orders, including the checkout page where a shop buyer enters the details in Section 3.
  • File servers for the 3D pages. When a visitor opens a page with a 3D car (the Paint Verification and How It Works pages), the browser fetches files from Google (www.gstatic.com), from raw.githack.com (a file proxy), and from GitHub (raw.githubusercontent.com, where that proxy's file is kept). Each of them sees the visitor's IP address and browser details, as any web server does.

Each company listed above is bound by contract to protect the data it receives at least as this policy does, and to use it only to provide its service to us. The exceptions are the parties we have no contract with, which receive no more than this: NHTSA and Marketcheck receive only the VIN, and the file servers for the 3D pages (Google's gstatic, GitHub, and raw.githack.com) receive only a visitor's IP address and browser details when a page fetches a file.

DeFelsko Corporation also receives a shop buyer's details (see Section 3), to ship the order. It is not among the companies listed above: it is a separate company, and we do not control how it handles those details.

A referral buyer's partner shop and dealer, and the company that runs the dealer's customer records, also receive the buyer's details (Section 12A). They are not among the companies listed above: they are separate companies, and we do not control how they handle those details.

When we add or change a subprocessor, we update this page. A Data Processing Addendum is available to partner organizations on request to legal@autoentic.com.

7. International transfers

Our backend, database, and primary application infrastructure are hosted on Hetzner servers in the United States. Our encrypted database backups are stored with Hetzner in Finland. autoentic.com static assets and CDN routing pass through Cloudflare's global edge network. Personal data is processed in the following jurisdictions:

  • United States — primary application infrastructure (Hetzner), Twilio, Resend, Sentry, Expo, Stripe, Marketcheck, NHTSA, Google (Gemini, and gstatic for the 3D pages), GitHub, Cloudflare, DeFelsko, and a referral buyer's partner shop and dealer.
  • Finland — encrypted database backups (Hetzner).
  • Ireland and other EU regions — some Resend infrastructure regions.
  • Not stated — raw.githack.com, whose operator does not say where it runs; it is served through Cloudflare's network.

For transfers from the European Economic Area, the United Kingdom, or Switzerland to the United States, we rely on (a) the EU-US Data Privacy Framework, the UK Extension to the EU-US DPF, and the Swiss-US DPF certifications maintained by our subprocessors that participate in those programs (including Twilio, Resend, Sentry, Expo, Stripe, Cloudflare, and Google), and (b) Standard Contractual Clauses with supplementary measures where DPF coverage does not apply. Neither applies to the parties named at the end of Section 6 that we have no contract with: NHTSA and Marketcheck receive only the VIN, and the file servers for the 3D pages receive only a visitor's IP address and browser details. Nor does either apply to DeFelsko, which receives a shop order's details in the United States to ship the order there. Autoentic LLC itself is not currently DPF-certified; we will evaluate certification before our formal EU launch.

8. Retention

Inspection records, FOCS scores, and certification-artifact metadata are designed to remain independently verifiable years after the original inspection. Buyers, sellers, lenders, insurers, auction houses, and regulators may rely on a Certification Artifact long after the partner organization that produced it has closed its account. The retention windows below reflect what is needed to keep these artifacts validatable, not a default of holding data forever.

We keep different categories of data for different periods, based on what each category is used for and what we are legally obligated to retain.

  • Inspection sessions and measurement data. Retained for as long as the partner organization's account is active, and up to 7 years after account closure to support the evidentiary purpose of the FOCS certification artifact.
  • Technician names and phone numbers. Retained while the technician is associated with an active partner organization. When the organization removes a technician, the technician's access ends and their name and phone number are erased at once, in that organization. When a technician deletes their own account, their name and phone number are erased in every organization that lists that number: at once in the app, and within 30 days of a verified request through our Account Deletion page, which also says what stays. When we close an organization's account, the names and phone numbers of its technicians are erased at once, as a removal erases them.
  • Sentry crash data. Expires and is deleted by Sentry within 30 days.
  • Server access logs. Retained at the reverse proxy on our own servers until the logs are rotated. We do not maintain a long-term archive of raw access logs.
  • Email and SMS one-time passcode challenges. Stored on Autoentic systems for the lifetime of the challenge (typically a few minutes). Deleted on use, or within about a day of expiring. Delivery metadata held by Resend (email) and Twilio (SMS) is retained according to those vendors' own retention policies, except that Twilio's messages are deleted once no shop's records hold a technician's number or, for a referral buyer, once we delete the buyer's number and no other record we hold has it, as our Account Deletion page explains. To limit how often a sign-in code can be asked for, we keep a keyed code made from the email address of each website account. It cannot be turned back into the address without our secret key. It has no end date today, and it stays after an account is closed.
  • VIN photos. Not kept when the VIN is read. When reading fails, kept on our servers for up to 7 days for troubleshooting, then deleted. Google's own handling is described in Section 3.
  • Shop orders. Order records, including the buyer's contact details and the address the order shipped to, are kept for 5 years after the order, for tax, warranty and dispute records, and then deleted. A business's contact details stay with its account while the account is active. Stripe and Resend keep their own copies under their own retention policies.
  • Referral requests. The record of the buyer's consent is kept for 5 years after the referral closes, as proof of what the buyer agreed to and of any withdrawal, and then deleted; it keeps the keyed code made from the number, not the number. Twilio's copies of a buyer's code texts are deleted when we delete the buyer's number, unless another record we hold still has that number. Codes sent to a number that never became a request stay under Twilio's own retention until the person asks us to delete them. We cannot erase the referral copy in the dealer's customer records or Resend's copy of it, the buyer's emails held by Resend, the shop's own records, or, for up to 30 days after a deletion, Twilio's backups.
  • A closed business account. A partner organization closes its account by asking us, and our staff close it. Its inspection records stay as they are, sealed and checkable, as the first item in this list says. At the close we erase its technicians' names and phone numbers, delete every website sign-in of the organization, with its sign-in history, and erase its street address, phone number, booking email, map position, website and opening hours, and the contact details and message on its sign-up request. We keep its name, the short name in its web address, its city, state, ZIP code, country, time zone, business type and tier, so its past records still read correctly; the record of its acceptance of our Terms, as proof of our contract; and its plan and payment references and its customer record at Stripe, for tax and billing records. We do not yet remove its saved card from Stripe. A closed organization gets no notice of changes to this policy or our Terms. If it reopens, we send it the current versions. Our Account Deletion page lists everything a close erases and keeps.
  • Post-termination data export. Following the closure of a partner organization's account, the organization may request a portable copy of its measurement and inspection data within 30 days of closure, in a structured, commonly used, machine-readable format. Send the request to legal@autoentic.com. A close deletes the organization's sign-ins, so we email a confirmation to the billing email Stripe holds for the organization and need a reply from it, and we ask for the serial number of a probe it registered with us. If Stripe holds no billing email for it, we ask for other proof, and we send nothing until we are satisfied the request comes from the organization.

9. Security

  • Encryption in transit. TLS 1.2 or higher between the app, autoentic.com, and api.autoentic.com.
  • Encryption at rest. The live production database is stored on an encrypted volume (LUKS2, AES-256) whose key is held only by Autoentic. Database backups are encrypted separately: each backup file is encrypted with a key derived from a master key held only by Autoentic, so the backup file is unreadable without that key.
  • Tamper-evident inspection records. Every inspection session and panel result is sealed with a hash chain so that any modification after submission is cryptographically detectable.
  • Authentication. Email and SMS one-time passcodes for human users, and passkeys for signing in to the website; static API keys with per-request authentication for the backend API.
  • Breach notification. If we confirm a breach affecting personal data, we will notify affected users within 72 hours of confirmation.

10. Your rights

You may request to access, correct, delete, or receive a portable copy of the personal data we hold about you, and to object to or restrict certain processing. To request deletion of your account and associated personal data, visit our Account Deletion page. For all other privacy requests, email legal@autoentic.com. Inspection records are not deleted on request: they stay, sealed, for the period in Section 8. A request removes what in them names a person, such as a technician's name and phone number. Where and when a car was measured stays with the record. Shop order records are kept for the period in Section 8 even if you ask us to delete them, and we cannot recall details already passed to DeFelsko. A referral buyer's consent record is not deleted on request during its 5 years (Section 8): it is the proof of what was agreed and of any withdrawal. A request deletes the buyer's name, number and email. You may designate an authorized agent to submit privacy requests on your behalf. We accept the agent's authority on the basis of any one of: (a) direct confirmation of authority from you to Autoentic, (b) a written power of attorney granting the agent authority under the law of your jurisdiction, or (c) any other proof prescribed by applicable privacy law. If we deny a request, we will explain the basis for the denial; where applicable state law provides an appeal right, we will also describe how to appeal that decision.

We respond to verifiable consumer requests within 45 days of receipt. If we need additional time we will inform you in writing; the response window may be extended once by up to 45 additional days. Access and data-portability requests are limited to twice within any 12-month period.

Where Autoentic processes personal data of a technician or other authorized user on behalf of a partner organization — for example, a technician's name, phone number, or session activity — Autoentic acts as a service provider under the CCPA and as a processor under GDPR-style frameworks. The partner organization is the controller of that data. If a technician submits a privacy request to Autoentic for organization-controlled data, we will direct the technician to contact their employing organization, and we will support the organization in fulfilling the request as required by applicable law. A technician can also delete their own account, in the app or through our Account Deletion page, without going through their organization. That erases their name and phone number; the organization still controls the rest.

California (CCPA / CPRA). California residents have the rights described above plus the right to know what categories of personal information we collect. Some of the information we collect — precise geolocation captured when an inspection is submitted, and payment information processed through Stripe — is Sensitive Personal Information under the CPRA. Autoentic uses Sensitive Personal Information only for the purposes described in Section 4 and does not use it to infer characteristics about you. You may request that we limit the use and disclosure of Sensitive Personal Information by emailing legal@autoentic.com. Autoentic does not sell personal information and does not share it for cross-context behavioral advertising. Where you have enabled a legally recognized browser-based opt-out preference signal — such as Global Privacy Control (GPC) — we recognize and apply your preference in accordance with applicable law. GPC operates as an opt-out of the sale and sharing of personal information; because we do not sell or share, applying the signal has no operational effect, but we record the preference to confirm our practice.

Virginia (VCDPA). Virginia residents have the rights described above plus the right to opt out of profiling that produces legally significant decisions. Autoentic does not engage in such profiling.

Texas. The Texas Data Privacy and Security Act (Tex. Bus. & Com. Code Ch. 541) applies to non-small-businesses. Autoentic operates as a small business under the United States Small Business Administration size standards and is therefore presently outside the general consumer-rights regime of TDPSA Subchapter B, except that Autoentic does not engage in the sale of sensitive personal data (Tex. Bus. & Com. Code § 541.107). We honor the access, correction, deletion, and portability rights described above for Texas residents on the same terms regardless of TDPSA's threshold applicability.

Nevada. Under Nevada Revised Statutes Chapter 603A, Nevada residents have the right to opt out of the sale of personal information. Autoentic does not sell personal information; if this changes, Nevada residents may exercise the opt-out by emailing legal@autoentic.com.

European Union. Until our formal EU launch, EU users may exercise the rights above via legal@autoentic.com, including the right not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects. Where we use automated analysis — such as the anomaly detection described in Section 4 — affected individuals may request human review. Full GDPR rights infrastructure will be in place at launch.

11. Children

The Service is a B2B inspection tool for licensed professionals and is not directed to anyone under 13. We do not knowingly collect personal information from children under 13. If we learn we have collected such information, we will delete it promptly.

12. SMS and mobile communications

When you give your mobile phone number to sign in, or to receive a code that confirms a request you make (such as a referral quote request, Section 12A), we use it under this section solely to deliver transactional SMS messages: one-time passcodes (OTP) for identity verification and request confirmation. We do not use your number to send promotional or marketing messages. Your consent to receive these messages, and the record of that consent, are never sold, transferred, or shared with any third party, and we never share your number with third parties for marketing purposes on the strength of that consent. A referral quote request is a separate choice you may also make; Section 12A says what it sends, and to whom. This section is about the mobile number used for those messages. A phone number given at the shop's checkout (see Section 3) is a contact number for the order and, if we open an account, for the business. Giving it at checkout does not sign it up for text messages, and we pass it to DeFelsko so the order can be delivered.

You may opt out of SMS messages at any time by replying STOP to any message. Opting out may limit your ability to complete verification steps within the platform. To request help, reply HELP to any message or contact support@autoentic.com. Standard message and data rates may apply based on your carrier plan.

12A. Referral quote requests

A car dealer that takes part in Autoentic's referral programme may offer you a free quote from one partner paint protection or detailing shop, by showing you a QR code or, if you ask, texting you a link. That text comes from the salesperson's own phone, not from Autoentic.

To ask for the quote, you give your name, mobile number and email address, choose your vehicle, tick a box that names the shop and the dealer, and confirm your mobile number with a 6-digit code we text you. Asking for the quote is a separate choice from agreeing to receive our code (Section 12). When you make it, at your direction:

  • The shop receives your name, mobile number, email address, your vehicle, what you want quoted and the wording you agreed to, but only after it accepts your request and pays Autoentic a referral fee. The shop may then call or text you about that quote, as the wording you ticked says.
  • The dealer receives a copy of your request with your name and mobile number, your vehicle, what you want quoted and the shop's name, in its customer records, to keep track of the referral. The dealer earns a credit on its Autoentic bill when the shop accepts.
  • We email you about your request, and keep a record of your consent (Section 3).

We pass your details to the shop and the dealer only because you asked us to; we do not sell personal information. The shop and the dealer are separate companies. Our agreements with them limit how they use your details, but we do not control their systems.

You can withdraw at any time: reply STOP to our code text or to the shop's texts, tell the shop or the dealer, or email support@autoentic.com. We record it by the next business day and tell the shop, which must stop contacting you within 10 business days. Withdrawing does not recall details the shop or dealer already received.

If a shop tells us your number does not work, we may call it once from an Autoentic phone, only to check.

13. Changes to this policy

We update this page when our practices change. For material changes, we email partner administrators before the change takes effect. For minor edits we update the "Last updated" date at the top.

If Autoentic is involved in a merger, acquisition, financing, reorganization, or sale of substantially all of its assets, personal data may be transferred to the successor entity as part of that transaction. We will notify partner administrators by email before the transfer takes effect, and the successor will be bound to honor the commitments in this Privacy Policy with respect to the transferred data.

14. Contact and jurisdiction

Questions about this policy or about data we hold:

Autoentic LLC
2714 W. Kingsley Rd., Ste. C2
Garland, TX 75041
legal@autoentic.com

This Privacy Policy is governed by the laws of the State of Texas, USA. Any disputes will be resolved in the state or federal courts located in Texas.