Sub-processors

A sub-processor is a third-party service that may store or process data on our behalf to deliver Tempus 7. This page lists every sub-processor we currently use, what they do for us, and what categories of data flow through them.

Last updated: 2026-05-18. We will update this page at least 14 days before adding a new sub-processor that has access to tenant data.

Current list

Amazon Web Services (AWS)

• Role: primary infrastructure — application hosting (EC2), database (Aurora PostgreSQL), file storage (S3), secrets storage (Secrets Manager), backup vaults, transactional email infrastructure (SES, see below).
• Region: us-east-1 (Northern Virginia)
• Data accessed: all tenant data — account information, business records, files, audit logs. Encrypted at rest with AWS-managed keys; encrypted in transit with TLS 1.2+.
• Why: AWS is the underlying infrastructure for the entire platform. Replacing this would mean replacing Tempus 7.
• Privacy policy: aws.amazon.com/privacy

Microsoft Corporation

• Role: transactional email delivery during beta, via Microsoft 365 and the Microsoft Graph API. Account-related emails (invitations, password resets) and in-app notifications to outside project participants are sent through this path.
• Data accessed: recipient email address, sender domain, subject line, and email body content (which may include project names, contact names, and links into the application).
• Why: Amazon SES production access for this account is currently provisioning. Once SES is fully enabled, transactional email will route through AWS and Microsoft will no longer have email-content access. We will update this page when that transition completes.
• Privacy policy: privacy.microsoft.com

GoDaddy

• Role: DNS hosting and domain registration for tempus7.com.
• Data accessed: DNS records only. No tenant data flows through GoDaddy.
• Privacy policy: godaddy.com/legal/privacy-policy

Stripe (when subscription billing is enabled)

• Role: payment processing for subscription tiers. Not yet active — the beta is free of charge for invited tenants.
• Data accessed: billing contact name and email, organization name, payment method details (handled directly by Stripe — we never see card numbers).
• Privacy policy: stripe.com/privacy

What we don't use

For transparency, here's the long list of common SaaS sub-processors that we have not integrated:

• No third-party analytics (no Google Analytics, no Mixpanel, no Segment, etc.)
• No third-party advertising or marketing platforms
• No third-party error monitoring services (Sentry, Rollbar, Datadog — error data stays inside our own AWS account)
• No third-party customer-data platforms or CRM integrations
• No third-party live-chat widgets
• No third-party AI training data flows — your business data is never used to train AI models

How we choose sub-processors

We add a sub-processor only when its function cannot be self-hosted at our scale without unreasonable cost or risk (e.g., transactional email deliverability, payment processing). Each candidate is evaluated on data minimization, security posture, and contractual data-protection terms.

Questions

For sub-processor inquiries or to request notification of changes ahead of time: privacy@tempus7.com