Signals are fragmented
Website intent, lead events, calls, messages, and operational history often live in separate queues.
About ID Privacy AI
AI customer operations that finish the work—and show their work.
We are building the operating layer between a customer signal and a completed next step: shared context, controlled execution, visible outcomes, and a clear role for people.
Our operating belief
The best AI workflow is one the operating team can understand and own.
- Understand the customer signal
- Decide inside defined rules
- Execute through connected tools
- Preserve human control and evidence
Why we exist
Customer context should not disappear between the signal and the action.
Teams already have channels, systems, and customer data. The hard part is coordinating them into work that is timely, controlled, and visible.
Actions cross system boundaries
The useful next step may require context, permission, a customer conversation, and a connected-system operation.
People inherit the exceptions
When automation stops, the team needs the prior context, a clear owner, and an obvious next action.
How we build
Accountability is a product behavior.
It has to appear in the workflow definition, the operator experience, and the record left behind after an action.
Complete the next step
A useful agent should move the customer journey forward through an approved action—not stop at a plausible response.
Keep people in control
Operators need clear ownership, takeover and handback, action limits, and a reliable path for exceptions.
Make outcomes inspectable
Conversations, decisions, tool activity, delivery state, failures, and costs should be available to the team responsible for the work.
Expand from evidence
Start with one bounded workflow, establish its baseline, and add scope only after the operating team can verify the result.
Automotive first
A demanding environment for connected customer work.
Automotive brings together complex systems, time-sensitive journeys, brand expectations, and store-level operating ownership.
The journey crosses systems
A single request can involve a website, phone call, customer record, inventory source, scheduler, and multiple store teams.
The action matters as much as the answer
Reading availability, submitting a request, confirming a booking, and changing an appointment are different operations with different controls.
Every exception needs an owner
Safety concerns, disputes, uncertain information, unavailable systems, and high-value moments require an intentional human path.
Automotive program experience
Experience across distinct retailer and program contexts.
Explore how the same control model can be applied to different brand and dealer-group operating needs.
Team
Built by automotive, AI, data, and platform operators.
The leadership team brings the domain and technical perspectives needed to move a workflow from a promising demo into accountable operation.
Albert Thompson
Founder & CEO
Automotive technology founder focused on the systems, partnerships, and operating realities behind dealership customer journeys.
Dr. Shaoor Munir
Chief AI Data Officer
PhD in Privacy-Preserving AI from UC Davis. Leads the platform’s agent architecture, data systems, and applied AI controls.
Su-Lin Velin
COO
Automotive operator and go-to-market leader focused on turning program strategy into repeatable customer and retailer outcomes.
Emeka Kalu-Uma
CTO
Technology leader with experience at Meta, Spotify, and the BBC. Leads the platform and infrastructure behind production workflows.
Muaz Maqbool
VP of AI
M.S. in Machine Learning from Georgia Tech. Leads AI orchestration, evaluation, and production model systems.
Bring us the workflow your team wants to improve.
We will map its customer signals, systems, permitted actions, handoffs, and evidence with the people who operate it.