Trust and dealer data
Each dealer's shoppers, stock and leads stay with that dealer.
Dealer platforms carry consumer data and send messages for their dealers. These are the design facts behind every module we build, written so your team can repeat them to dealers.
The short version
- Sprint work runs on test inventory and synthetic shoppers.
- Production data stays in your AWS or Google Cloud accounts.
- Production access only as you grant it, revocable at any time.
- Each dealer's inventory, branding and leads stay separate.
- Every text or email to a shopper waits for a person.
- Conversations, tool calls and token cost are logged.
Dealer and shopper data
We build on test inventory and synthetic shoppers, not your dealers' customers.
Sprints run on test data, and the AI Scorecard on your own conversations with names and contact details removed.
How data is handled
- Sprint work runs on test inventory and synthetic shoppers.
- Production data stays in your AWS or Google Cloud accounts.
- In production we work only through access you grant, and you can revoke it at any time.
- Each dealer's inventory, website, branding and leads stay separate from every other dealer's.
AI controls in every module
- Answers about stock and prices come only from the dealer's feed.
- Towing and payment figures are computed by tools, never guessed.
- Every text or email to a shopper waits for a person.
- Conversations, tool calls and token cost are logged per conversation.
- On or off per dealer and per brand.
Evaluation
Quality, safety and cost are measured before launch.
Every Sprint ends with evidence, not a demo alone.
What we test
- Sold units and wrong prices, on your own shopper questions.
- Another dealer's stock or leads returned: tested, and held at zero.
- Prompt injection from listing text and website content.
- Cost per dealer on two models.
For your dealers' reviews
- A security overview and a data-flow sheet for each module.
- Help answering the AI sections of dealer security questionnaires.
- A way to switch the feature off per dealer.
We work within your FTC Safeguards Rule, TCPA, privacy and dealer data requirements. Compliance depends on the complete product, contracts, policies and operating environment; Datics does not present software engineering alone as legal certification.
Regulations
FTC Safeguards Rule and TCPA, in plain terms
Dealers are covered by the FTC Safeguards Rule, and calls and texts to shoppers fall under the TCPA. We work within your Safeguards Rule, TCPA, privacy and dealer data requirements, and design modules so people approve every message. Compliance depends on your complete product, contracts, policies and operating environment, so we never present software engineering alone as certification.
Where we are
Austin, Texas, with US-hours overlap.
Working with us
- Datics AI is headquartered in Austin, Texas, where our CEO is based. Product Review calls run in US Central time.
- A named lead engineer and US-hours overlap on every engagement.
See it on your own platform.
Bring one product, workflow or AI feature. In 30 minutes we tell you which of the three ways to start fits, what it would cost to serve per dealer and what your dealers' data questions will be.
Calls run in US Central time. No generic AI presentation: we discuss your product, users and production constraints.