Gig Central utilizes security protocols to protect your connected email credentials, utilizing secure database encryption and tokenized OAuth integrations.
This guide details encryption standards and mail account safety.
1. Standard Token Integrations (OAuth2)
When integrating Google Workspace or Microsoft 365, we use OAuth2 integrations:
- No Password Storage: The system never asks for or stores your email passwords.
- Access Tokens: Integrations authenticate using API access tokens.
- Simple Revocation: Revoke access at any time directly in Google or Microsoft security settings.
2. Encrypted Legacy SMTP Credentials
For custom email servers that do not support OAuth:
- Secure Database Encryption: Credentials are encrypted before being written to the database.
- On-the-Fly Decryption: The sync worker decrypts credentials only in memory during active connection tasks.
- Automated Purging: Decrypted credentials are wiped from active memory immediately after tasks finish.
3. How It Works (Behind the Scenes)
- Decryption Helpers: The decryption routine retrieves encrypted credentials from the database and decodes them using environment key rings.
- Connection Sweeper: Sync loops in Magic Inbox use these decrypted settings to fetch message updates, updating matching gig logs in the CRM.
4. Best Practices for Email Security
- Prefer OAuth: Connect your email using Google or Outlook OAuth panels rather than legacy password entries.
- Rotate Passwords: If you must use legacy SMTP, rotate your passwords regularly.