An institute holds phone numbers, fees, marks and careers. Compass treats that as the most important thing it stores.
Every workspace walled off
Every table carries the workspace it belongs to, and database rules check it on every read and write.
Automated tests prove one institute cannot read another’s data.
Sign-in and roles
Team members sign in with a one-time email code or Google.
Each person’s role decides which pages and records they see. Removing someone ends their access immediately.
AI that never sees names
Names, phones, emails and ID numbers are replaced with tokens before any text reaches an AI model.
Each workspace sets its own AI budget, and an admin can switch AI off entirely.
A complete audit trail
Every change records who made it, what changed, and the values before and after.
The audit log and timeline are append-only.
DPDP rights, built in
Consent is recorded per channel: WhatsApp, calls, recordings and email.
Admins can export everything held about a person, or erase it in two confirmed steps. Files are deleted; payment records and consents are kept as legal records.
Retention and backups
Call audio is deleted six months after the call. Deleted records are purged after a period each workspace sets (180 days by default).
Database backups are encrypted with AES-256-GCM and checked by restoring them.
Files behind signed links
Documents, résumés and recordings are never public. They open only through short-lived signed links.
Stored keys for connected accounts are encrypted.
Safe integrations
Incoming webhooks from Meta and WhatsApp are checked by signature, stored once and processed exactly once.
Lead intake and payments use idempotency keys, so a retry never creates a duplicate.
Respectful messaging
Automated sequences respect consent and quiet hours.
Exports are recorded in the audit log.
Copies outside Compass, such as WhatsApp chats, Google Calendar events and spreadsheets you exported, are not erased by Compass. The docs explain how to handle them when a person asks to be forgotten.