Compliance library

Customer assurance

Service providers and data transfers

Which providers support PacketSafari SaaS, when optional providers are used, and how the provider set changes for on-premises deployments.

Customer summaryCustomer information published
Security
Identity, access, audit, incident, and deployment-boundary information
Privacy
Data categories, retention, deletion, rights requests, subprocessors, and transfers
Deployment
Separate responsibilities for PacketSafari SaaS and customer-operated on-premises environments
Contact
contact@packetsafari.com for contractual or deployment-specific questions
Scope The exact control boundary depends on the selected deploymentLast updated July 24, 2026

Current providers

The current public service-provider list names the providers used in PacketSafari's active service paths:

  • Amazon Web Services (AWS): cloud hosting, deployment artifacts, and outbound product email through AWS SES
  • hosting.de: PacketSafari mailbox infrastructure
  • Paddle: checkout, subscriptions, payment processing, and billing activation
  • OpenAI: hosted AI processing when PacketSafari's default cloud AI provider is enabled

GitHub and Google are used only when their optional sign-in integrations are enabled. Customer-configured AI and SMTP providers apply only to deployments where the customer selects those services.

SaaS and on-premises differences

Managed SaaS uses the providers required for the hosted service and the features the customer enables. On-premises customers operate their own infrastructure and can select the storage, network egress, mail delivery, identity provider, and OpenAI-compatible AI endpoint. This can reduce or change the providers involved in the data path.

Contract and transfer information

Provider regions, data categories, transfer safeguards, and contractual terms depend on the purchased service and enabled features. Contact contact@packetsafari.com to confirm the applicable provider set and contractual terms before purchase.

The signed customer agreement and any applicable DPA govern subprocessor and notification commitments.