DizitalGini is engineered with bank-grade AES-256-GCM encryption, TLS 1.3 transport, stateless AI inference, and strict least-privilege OAuth scopes to ensure your sending reputation and data remain secure.
All sensitive third-party credentials — including Google OAuth refresh tokens, Microsoft Graph tokens, and SMTP App Passwords — are encrypted using AES-256-GCM with internally rotated cryptographic keys.
100% of API communications between client browsers, DizitalGini microservices, and external mail providers strictly enforce TLS 1.3 with Perfect Forward Secrecy and rigorous HSTS policies.
AI prospect research and dual-copy generation pipelines run inside isolated, stateless memory instances. Lead dossiers and campaign copy are never stored in public LLM pools or used to train shared foundation models.
Our OAuth integrations request the minimum necessary write-only permissions (gmail.send for Google, Mail.Send for Microsoft). We never request or possess read or manage access to your private inbox.
Database-level schema partitioning and row-level security isolate each customer organization's prospects, campaign templates, and metrics, preventing any cross-tenant data access.
Disconnecting any connected mailbox instantly purges all stored OAuth tokens and credentials from active databases and memory caches, immediately halting any future dispatches.
When you link a mailbox to DizitalGini (whether through Google OAuth, Microsoft Graph, or custom SMTP), our platform operates strictly on a write-only outbound basis:
gmail.readonly or Microsoft Mail.Read.If you have security questions or wish to report a vulnerability, please reach out directly to our dedicated security desk: