Security at AegionIQ
Your Salesforce org is mission-critical. Security is not a feature we added — it is the foundation everything else is built on.
OAuth 2.0 — Read-Only Scopes
AegionIQ connects via the Salesforce OAuth 2.0 authorization-code flow. We request only read-only scopes: api (read metadata), refresh_token, and id (basic profile). We never request modifyAllData, full, or web. You can revoke access from Salesforce Setup → Connected Apps at any time.
Metadata Only — No Business Data
We only read Salesforce metadata: Apex classes, Flows, Objects, Fields, Profiles, and Permission Sets. We never read Accounts, Contacts, Opportunities, Cases, or any custom-object records.
Encryption — AES-256-GCM at Rest, TLS 1.3 in Transit
All data at rest is encrypted with AES-256-GCM. All connections use TLS 1.3. OAuth refresh tokens are wrapped with application-level envelope encryption before persistence.
Network — HSTS, CSP, Strict Origin Policies
Strict-Transport-Security with preload, a restrictive Content-Security-Policy, X-Frame-Options DENY, Referrer-Policy strict-origin-when-cross-origin, and no third-party trackers on auth surfaces.
Access — RBAC, Audit Logs, Session Management
Role-based access control with workspace-scoped roles. Every privileged action writes to an immutable audit log. Sessions are short-lived, rotated on privilege change, and revocable from the user profile.
Data Isolation
Each customer's data is logically isolated using tenant-level access controls. Row-level security policies enforce strict data boundaries.
Infrastructure Security
Hosted on enterprise-grade cloud providers. Automated dependency scanning, vulnerability monitoring, and quarterly penetration testing. All infrastructure access requires MFA.
AI / Model Assurance
Powered by Claude (Anthropic). Your metadata is never used to train external models. Anthropic does not retain data sent via the API for training.
NDA-grade assurance
We never use your metadata to train external models, sell it, or share it with third parties outside the sub-processor list below.
Compliance & Best Practices
Salesforce Security Best Practices
Our OAuth integration follows Salesforce's least-privilege scoping, token rotation, and secure-storage patterns.
Data Processing Agreement (DPA)
AegionIQ processes Salesforce metadata (not business records) on your behalf. A standard DPA covering this processing is available on request — contact security@aegioniq.com.
Sub-processors
| Vendor | Purpose | Region |
|---|---|---|
| Supabase | Database, authentication, storage | US-East |
| Anthropic | AI inference (Claude) | US |
| Vercel | Hosting / edge delivery | Global edge |
| Stripe | Billing & payments | Global |
Data Handling
| Data Type | Collected | Retention |
|---|---|---|
| Salesforce metadata (Apex, Flows, Objects) | Yes — read-only | 30–365 days (plan-based) |
| Business data (records, contacts, opportunities) | Never | N/A |
| Salesforce credentials / passwords | Never | N/A |
| OAuth tokens | Yes — encrypted | Until org disconnected |
| Scan results & analysis | Yes | 30–365 days (plan-based) |
| AI Copilot queries | Yes | 90 days |
Responsible Disclosure
If you discover a security vulnerability in AegionIQ, we encourage responsible disclosure. Please report it to security@aegioniq.com. We commit to acknowledging reports within 24 hours and providing a resolution timeline within 72 hours. We will not take legal action against researchers who report in good faith.
For general security questions, contact security@aegioniq.com.