Order Call AISecurity & Data Practices
Order Call AI, a d/b/a of Celestial Import LLC · Effective July 18, 2026 · Last updated July 18, 2026
We are a small company and we would rather be precise than impressive. This page states exactly what we do, what we do not do, and what we have not built yet.
We are out of PCI scope
Order Call AI never transmits, processes, or stores cardholder data. Orders are created as open checks and paid in person at the restaurant. The assistant is instructed never to ask for a card number. We are entirely out of PCI scope.
Where data lives
- Database and authentication — Supabase (managed Postgres), United States (AWS us-east-1). Supabase maintains SOC 2 Type 2 and ISO 27001 certifications; their report is available to us on request.
- Web application — Vercel, United States.
- Voice — Vapi handles the call leg and passes audio to a speech-to-text provider and a language model.
The full list, with what each vendor receives, is on our subprocessors page.
Encryption
All traffic is served over TLS. Data is encrypted at rest by our database and hosting providers.
Tenant isolation
Every business record carries the ID of the restaurant it belongs to, and isolation is enforced in the database itself with PostgreSQL row-level security — not only in application code. A signed-in user can read a row only if they hold a membership in that restaurant.
- Requests without a valid session are rejected at the database, not merely redirected in the browser.
- Users cannot add themselves to a restaurant. Membership changes go through authorisation-checked database functions.
- The phone-provisioning fields that route a call to a restaurant are immutable to signed-in users, so one tenant cannot redirect another’s calls.
- Administrative database credentials never leave the server and are never included in anything sent to a browser.
Call data
Every call opens with a recorded notice before audio is captured. We do not create voiceprints and do not identify speakers by voice. We do not use call audio or transcripts to train models, and our vendors are contractually held to the same. See the DPA for the binding version.
Retention: call audio [retention period — pending], transcripts 12 months.
Access control
Access to production systems is limited to authorised personnel and protected by unique accounts. Roles inside a restaurant (owner, manager, staff) determine what a user can change; the database enforces those roles, not just the interface.
Incident response
If we become aware of a breach affecting a restaurant’s data we will notify that restaurant without undue delay and within 72 hours, with what we know, what we are doing, and what they need to do. Report a suspected issue to security@ordercallai.com. We will not pursue good-faith security researchers who report responsibly.
What we have not done
We hold no SOC 2 or ISO 27001 certification of our own, and we have not commissioned an external penetration test. We are a single-founder company; claiming otherwise would be false. What we do have is documented practice, isolation enforced at the database layer, and a deliberately small data footprint — no card data, no biometrics, no model training.