Data residency and PII

Where Stigg stores data, including personally identifiable information (PII), and how to control what’s sent

Does Stigg store PII?

Sending Personally Identifiable Information (PII) to Stigg, such as a customer’s name and email address, is optional, but is beneficial from a user experience perspective for easy identification of customers on the Stigg platform.

When PII is not sent to Stigg, identification of customers is done using the customer ID.

Where is data stored?

Stigg’s infrastructure runs on AWS. Our primary region for data residency is us-east-2 (Ohio), with multi-region failover to us-west-2 (Oregon) in case of a regional incident.

If PII is sent to Stigg, it’s stored securely in this managed infrastructure and served via Stigg’s globally replicated CDN for improved latency.

To support global performance and availability, the CDN replicates mission-critical data from the U.S. to additional regions:

• EU: Germany
• APAC: Mumbai, India

This replication supports low-latency access for customers operating in Europe and Asia, and is relevant for organizations evaluating data residency and geopolitical considerations as part of their compliance requirements.

For SOC 1, SOC 2, and GDPR compliance documentation, see our Security Portal or request access to the Security and Trust Portal.