The only AI for dealerships that stores zero customer data.
We ship you the box. Your data never leaves your dealership. Watch it happen live.
Three things every dealer's IT team asks. Three things we built into the architecture.
Where does our customer data live?
On the MakoNode appliance we ship you. Plugs into your network. Stays in your server closet. Your data, your hardware, your control. If you unplug it, we have nothing.
What does Mako's cloud actually see?
Pseudonymous tokens and structured intent classifications. Never a customer name. Never a phone number. Never an email address. Never a message body containing personal information.
What if your AI gets it wrong?
Two independent privacy layers — semantic AI scrub plus deterministic redaction — must both clear before any message leaves your dealership. A third check at Mako Central rejects anything that slips through. Belt, suspenders, and a backup belt.
Meet the MakoNode.
Your sovereign data appliance. We bring it. You plug it in. You own it.
- Mako Certified Tech. A certified Mako technician drives to your dealership and sets it up personally. About 2–4 hours on-site.
- Local data storage. All conversation data, customer records, and consent logs live on your hardware.
- Encrypted outbound tunnel. No firewall changes needed — the box dials home through an outbound-only encrypted tunnel.
- Auto-updating. Nightly security patches. Signed updates verified before installation. Roll back in one command.
- Encrypted nightly backup. To an encrypted cloud bucket you control, with a key you control. Mako can't decrypt your backups.
- UPS recommended. Power outage = service pause. We can supply a UPS to keep you running.
The moment your customer gives you their phone number, our proprietary tokenizer takes over.
Every inbound message flows through our proprietary redaction and tokenization layer running on the MakoNode. When customer data is detected — a name, a phone, an email, anything personally identifiable — the local AI swaps it for opaque tokens before anything is forwarded to Mako Central. The cloud AI reasons on placeholders, not people. Replies come back tokenized too, and the MakoNode rehydrates the real values on your hardware. Your customer's information never leaves your dealership.
Two independent privacy checks. Both have to clear.
Layer 1: AI semantic scrub
- Proprietary on-device language model running locally on your MakoNode
- Understands context: "Ford" in "I'm Ford Henderson" vs. "I want a Ford Mustang"
- Catches subtle customer data: family member references, occupations tied to identity, location hints
- Runs in 200–400ms
Layer 2: Deterministic redaction
- Rule-based hard checks running locally on your MakoNode
- Catches what the semantic layer might miss: 10-digit phone numbers (no exceptions), postal codes, financial identifiers
- Whitelist-driven vehicle recognition: only `2022 Ford F-150` style references pass; "Ford" alone gets treated as a name
- Runs in <50ms
Backstop check at Mako Central
If both local layers somehow miss customer data, Mako Central runs a third check and rejects any inbound containing identifiable information. We don't trust the semantic layer alone. We don't trust the deterministic layer alone. We don't even trust both of them together — we add a server-side backstop. Defense in depth.
When the scrubber catches something ambiguous, the conversation gets smarter.
Sometimes a customer message references a vehicle without enough context. "I saw a Ford you posted on Facebook" — is "Ford" a make name or a person's name? The deterministic layer can't be sure, so it scrubs the reference. Mako's AI then routes the conversation to a disambiguation specialist that politely asks for the stock number — which is a dealer-internal identifier, not customer data. Privacy constraint becomes a UX upgrade.
Mako Central never received: Sarah, Mike, Ford, or 416-555-2847. Your local AI knows all of them.
Architecture choices that competitors can't copy without rebuilding their products.
No SOC 2 needed for customer data
Our SOC 2 scope on customer data is empty because we don't have any. We maintain operational SOC 2 controls for our own internal systems, but customer data audits are trivial — there's nothing to audit.
Right-to-be-forgotten = unplug
A customer requests deletion? Your CRM handles it. Mako has nothing to delete because we never had their data. Compliance scope collapses to "what's on the dealer's box."
OEM dealer-program approvals
Toyota, Honda, GM dealer programs all have data residency rules. The MakoNode satisfies every one of them without exception. Your data never crosses a border, never sits in a multi-tenant cloud, never touches a third-party processor.
Cyber insurance premium drops
Breach impact: a tokenized message log without any way to map back to real people. Underwriters love it. Premiums on our pilots run 40–60% lower than vendors with cloud-stored customer systems.
Don't trust the architecture diagram. Trust the live feed.
Every conversation Mako handles is tokenized at the dealer's MakoNode before it reaches Mako Central. The conversations we receive — already customer data-free — are safe to publish. So we publish them. In real time. Every dealership, every conversation, every tokenized message, public and inspectable.
Watch live.gotmako.aiReady to see Mako in action?
Book a 30-minute demo. We'll show you everything — the appliance, the architecture, the live feed.