Security built for the way regulated fintechs actually buy software.
Aithon processes your sales activity — pipeline, communications, meetings — to make your reps smarter. We never touch your end-customer banking data. CRM and email writes happen only as part of campaigns and sequences your reps explicitly run, with scoped OAuth, full audit trails, and admin-controlled enable/disable per integration.
Every connection scoped, admin-consented, revocable.
Aithon authenticates to every source system through OAuth 2.0 with explicit admin consent. Read scopes power intelligence; write scopes are separate, optional, and only used when your reps run campaigns or sequences. No service accounts, no stored passwords, no standing credentials.
| Source | Auth | Access scope | Mode |
|---|---|---|---|
 Salesforce | OAuth 2.0 | Read: accounts, opportunities, contacts, pipeline. Write (campaigns): when a rep runs a sequence, Aithon updates contact engagement, logs activities, and adds rep-approved notes — using a separate, admin-consented write scope. Every write is logged and reviewable in the activity audit. Disable per integration at any time. | Read · Write (campaigns) |
 Outlook | OAuth 2.0 | Read:sales mailbox content & metadata for relationship signals. Write (sequences):when a rep runs a sequence, Aithon sends emails on the rep's behalf using their delegated permission. Drafts can be set to require rep approval before send or auto-send per sequence policy. Every send is logged with the originating sequence ID. | Read · Write (sequences) |
 Microsoft Teams | OAuth 2.0 | Meeting transcripts & metadata via Graph API OnlineMeetingTranscript.Read.All. Per-user delegated permissions; transcripts processed only when the user has consented to the integration. | Read-only |
 Highspot | OAuth 2.0 | Content engagement analytics (which deck was viewed, by whom, when), titles, categories, and the document content itself for retrieval and grounding. Used to power content recommendations and ground AI responses in your enablement library. | Read-only |
Your admins switch off any data category at the source.
Most “privacy controls” in B2B SaaS are post-processing filters. Aithon's are a hard gate at the pipeline boundary — when your admin marks a category Excluded, that data is never loaded into the AI processing layer in the first place.
PRIVACY_FAIL_MODE = closed. Excluded by default rather than processed without authorization.AI Data Eligibility
Choose which data categories the AI processing pipeline is permitted to use. Excluded data is never loaded into AI; existing insights for excluded categories are purged within 24h.
Identity, network, data, application — controls at every layer.
No single control is sufficient on its own. Aithon implements specific guardrails at each layer of the stack so that a compromise at one level does not cascade to the next.
Auth0 · OIDC · JWT
- Org-scoped auth · multi-tenant isolation
- JWT tokens with role claims (admin / user)
- All API requests validated server-side
- No passwords stored — delegated to Auth0
- MFA configurable per organization
VPC isolation
- All services in private subnets
- ALB is the only public-facing endpoint
- Security groups enforce least-privilege ports
- RDS & Redis not publicly accessible
- Private Route 53 for service-to-service
Encryption everywhere
- In transit: TLS 1.3 (ALB · service-to-service)
- At rest: AES-256 — RDS · S3 (KMS) · EBS
- Secrets in AWS Secrets Manager (no env vars)
- OAuth tokens Fernet-encrypted in Postgres
- Backups encrypted · 7-day retention
Secure by design
- Org-scoped queries · no cross-tenant access
- Server-side rendering · no client API keys
- Parameterized queries · no raw SQL
- Input validation (Pydantic) on every endpoint
- CORS restricted to known domains
Multi-tenant by default. Dedicated infrastructure when you need it.
Most customers run on shared infrastructure with logical isolation at every layer. Enterprise customers with stricter requirements can be deployed to a dedicated ECS cluster, RDS instance, S3 bucket, and customer-managed KMS keys.
Multi-tenant
Shared infrastructure with logical isolation. The default for the vast majority of customers.
- Org-scoped queries —
aithon_org_idon every table - Auth0 Organization per customer — JWT-enforced
- Per-org privacy controls & pipeline config
- Encrypted credentials per-user (Fernet)
- No API endpoint returns cross-org data
Dedicated infrastructure
Isolated compute and storage for the strictest security postures. Available as an enterprise option.
- Separate ECS cluster & task definitions
- Dedicated RDS instance
- Isolated S3 data lake bucket
- Separate VPC or dedicated subnets
- Customer-managed KMS keys (optional)
- Independent scaling & maintenance windows
Ready for your security team to take a look?
For a deeper review — integration scopes, threat model, write audit walkthrough, regional residency — book an architecture deep-dive with our team. We'll bring an engineer.