Below: what we've actually shipped, what's on the roadmap with realistic dates, and the full sub-processors list. We'd rather be straight with you than scatter trust badges we haven't earned.
Every control on this list is live in the codebase as of today. You can ask for the code path on any of them and we'll show you exactly where it's implemented.
shipped
TLS 1.3 on every customer-facing endpoint via Cloudflare. Origin-to-Cloudflare encrypted over Cloudflare Tunnel — no public-facing ports on the application host.
shipped
AES-256-GCM for Meta access tokens, OAuth refresh tokens, payment provider credentials, and other tenant secrets. Database disk is full-disk encrypted (LUKS on the host).
shipped
PostgreSQL and Redis bind to localhost only. The application is the sole network client; nothing else can reach the database from outside the host.
shipped
Every state-changing action — login, password reset, billing change, tenant suspension — is recorded append-only with user, IP, user agent, and a before/after snapshot. PII redacted on capture. 90-day retention by default.
shipped
Self-hosted exception tracker captures unhandled errors from API + web client, with PII redaction at the field level. Spike + regression alerts fire to founder over WhatsApp within 10 minutes.
shipped
Every contact, conversation, message, and template is tagged with a tenantId. All queries are filtered by tenant at the route + service layer. There is no cross-tenant data path in the application.
shipped
YinPsi servers never see card data. Razorpay (PCI DSS Level 1) and Stripe (PCI DSS Level 1) handle every payment flow. We receive tokenised customer + subscription identifiers only.
shipped
Every Razorpay + Stripe webhook is persisted with a provider-issued event id. Re-delivered webhooks are idempotent; no double-charges, no duplicate subscription state.
This list is the complete one. If a vendor isn't on it, they don't process your data. Each row links to that vendor's public DPA so you can review their commitments directly.
| Vendor | Purpose | DPA |
|---|---|---|
| Meta Platforms, Inc. | WhatsApp Cloud API — the channel itself | View |
| Razorpay Software Pvt Ltd | Subscription billing for India customers | View |
| Stripe, Inc. | Subscription billing for global customers | View |
| Cloudflare, Inc. | DNS, CDN, DDoS protection, Cloudflare Tunnel | View |
| Amazon Web Services | Transactional email (SES) + offsite backup (R2 alternative) | View |
| OpenAI | AI Inbox Copilot + Voice transcription (Phase 1+) | View |
| Anthropic | Premium AI reasoning model (Phase 5+) | View |
| Sarvam AI | Indic-language ASR + TTS for voice agents (Phase 5+) | Coming Q3 |
| ElevenLabs | Voice agent TTS (Phase 5+) | View |
We notify customers via WhatsApp + email 30 days before adding a new sub-processor that touches PII.
Honest about what we don't have today. If something below is a hard requirement for your org and the date doesn't work, email us — we move things up for paying customers who ask.
Responsible disclosure goes to [email protected]. We acknowledge within 24 hours, fix within reasonable time, and credit you in the changelog if you'd like to be.
Built on Meta WhatsApp Cloud API
Direct integration with the official Meta Business Platform — no unofficial bridges or reverse-engineered protocols.
Encrypted in transit and at rest
TLS 1.3 on every endpoint via Cloudflare. AES-GCM for Meta access tokens and payment credentials at rest.
PCI-secured payments
Razorpay (PCI DSS Level 1) and Stripe (PCI DSS Level 1) handle every card. YinPsi servers never see card data.
Your data, your dashboard
Per-tenant data isolation. Export everything via API. Delete your workspace and the data is gone within 30 days.
Independently auditable. SOC 2 Type II on the 12-month roadmap.
Read our security practices →