Data architecture
Per-user scoping
Pranan associates inbox data, settings, relationship context, and drafts with the authenticated user and applies application-level access controls.
Connected-account tokens
Google OAuth access and refresh tokens are encrypted before storage. Secrets are not exposed in the browser.
Encryption in transit
The Pranan web application and provider APIs are accessed over HTTPS.
What we store
Pranan stores the email content and metadata needed to classify conversations, learn writing patterns, build relationship context, and create drafts for review.
Human review
Pranan creates drafts for review. It does not request the gmail.send scope and never sends email on your behalf. The gmail.modify scope it uses to create drafts and apply labels would technically allow sending; Pranan does not use it that way.
Never-draft list
Stop Pranan drafting for a specific contact. Their mail is still synced, stored, and classified, so keep conversations that must never pass through an AI service out of the connected mailbox.
Compliance posture
SOC 2 status
Pranan is not currently represented as SOC 2 certified. Contact us for the current readiness status and available evidence.
Privacy requests
Access, correction, export, and deletion requests can be started in the app or sent to privacy@pranan.ai.
Data deletion
Deletion requests follow the process and timelines described in the current Privacy Policy.
Service providers
The full list of service providers, what each one processes, and where, is in section 6 of the Privacy Policy.
Security reviews
For enterprise reviews, send your requirements and questionnaire so we can confirm which controls are currently available.
Data access
Account holders can request a structured export of the data associated with their account.
Have a security review?
Send us your security questionnaire. We will confirm receipt and provide the current evidence available for review.