Book a Demo
See how StoreForce connects your people, data, and execution,
turning everyday retail in to exceptional results.
Book A Demo
4.9 Rating StoreForce ESS
Book a Demo
See how StoreForce connects your people, data, and execution,
turning everyday retail in to exceptional results.
Book A Demo
4.9 Rating StoreForce ESS
Subscribe to Our Newsletter!
Stay up to date with the latest in retail execution.
Subprocessor List
Subprocessor List
Subprocessor / ervice | Processing Location(s) | Processing |
|---|---|---|
| Microsoft Azure | Germany West Central (EU); Central US, East US and East US 2 (USA); Australia East (Australia). Specific customer-data processing location depends on the customer workload and Azure resource configuration. | Cloud hosting of StoreForce applications, databases, file storage, backups, disaster recovery and related customer workloads; processes customer and employee personal data. |
| Google Cloud Platform | EU: europe-west3 (Frankfurt) and EU multi-region for archive; US: US multi-region; Australia: australia-southeast1 (Sydney). Location depends on the StoreForce production environment. | Google Cloud Storage used by the StoreForce Media Library Service (MLS) to store customer-uploaded media and related files. Media may contain customer personal data, including images of identifiable individuals. |
| Zendesk | AWS US West (Oregon), USA | Support/help-desk processing: names/emails, ticket content, comments, logs, screenshots and attachments. |
| Twilio SendGrid | US Global/default and EU regional, depending on routing/configuration | Transactional email delivery: recipient data, message content and delivery/event data. EU regional sending is configured for StoreForce/ThinkTime EU use cases. |
| Assembled | United States - Assembled application data is hosted in AWS us-east-1. The executed StoreForce DPA lists current authorized subprocessors in the United States. | Zendesk-connected support and AI processing. Assembled stores ticket events/history, metadata, agent/user information, and ticket descriptions/comments/message bodies. Free-form ticket content may contain customer names, email addresses and other personal data. AI Copilot and AI Chat Agent process ticket/knowledge-base content for AI responses. |
| Atlassian Jira Cloud | Not set; current AWS US East (N. Virginia) | Escalated support issues for dev/deployment; may contain full support-ticket content, PII, logs and attachments. |
| Tempo Structure | Not set; supports Germany / EU / US | Reads Jira issue fields; stores Structure-specific data. Jira changelog storage disabled by StoreForce. |
| New Relic | United States - StoreForce uses the New Relic US data region (one.newrelic.com). Global support/operational access may occur. | Application performance monitoring, logging, traces, synthetics and operational diagnostics. StoreForce application/microservice logs are confirmed to contain customer names and email addresses; other personal data may also appear depending on application logging. |
| Rapid7 | United States - StoreForce Rapid7 data region confirmed internally. | Security monitoring, vulnerability/threat detection and related security telemetry. Rapid7 services may process endpoint, server, cloud application and log data. |
| Atlassian Statuspage | United States - AWS US West (Oregon / us-west-2), with failover to AWS US East (N. Virginia / us-east-1) | Status and incident communications. Stores and processes customer subscriber information, including customer name and email address, when users subscribe to StoreForce Statuspage notifications. |
| Manus | United States and Singapore, based on Manus' current public data-location statement | AI-assisted creation of customer Quarterly Business Review (QBR) presentations using data exported from the StoreForce application. Inputs may include customer employee/user names, email addresses, screenshots, usage information and other individual-level personal data. |
Subprocessor / ervice | Processing Location(s) | Processing |
|---|---|---|
| Microsoft Azure | Germany West Central (EU); Central US, East US and East US 2 (USA); Australia East (Australia). Specific customer-data processing location depends on the customer workload and Azure resource configuration. | Cloud hosting of StoreForce applications, databases, file storage, backups, disaster recovery and related customer workloads; processes customer and employee personal data. |
| Google Cloud Platform | EU: europe-west3 (Frankfurt) and EU multi-region for archive; US: US multi-region; Australia: australia-southeast1 (Sydney). Location depends on the StoreForce production environment. | Google Cloud Storage used by the StoreForce Media Library Service (MLS) to store customer-uploaded media and related files. Media may contain customer personal data, including images of identifiable individuals. |
| Zendesk | AWS US West (Oregon), USA | Support/help-desk processing: names/emails, ticket content, comments, logs, screenshots and attachments. |
| Twilio SendGrid | US Global/default and EU regional, depending on routing/configuration | Transactional email delivery: recipient data, message content and delivery/event data. EU regional sending is configured for StoreForce/ThinkTime EU use cases. |
| Assembled | United States - Assembled application data is hosted in AWS us-east-1. The executed StoreForce DPA lists current authorized subprocessors in the United States. | Zendesk-connected support and AI processing. Assembled stores ticket events/history, metadata, agent/user information, and ticket descriptions/comments/message bodies. Free-form ticket content may contain customer names, email addresses and other personal data. AI Copilot and AI Chat Agent process ticket/knowledge-base content for AI responses. |
| Atlassian Jira Cloud | Not set; current AWS US East (N. Virginia) | Escalated support issues for dev/deployment; may contain full support-ticket content, PII, logs and attachments. |
| Tempo Structure | Not set; supports Germany / EU / US | Reads Jira issue fields; stores Structure-specific data. Jira changelog storage disabled by StoreForce. |
| New Relic | United States - StoreForce uses the New Relic US data region (one.newrelic.com). Global support/operational access may occur. | Application performance monitoring, logging, traces, synthetics and operational diagnostics. StoreForce application/microservice logs are confirmed to contain customer names and email addresses; other personal data may also appear depending on application logging. |
| Rapid7 | United States - StoreForce Rapid7 data region confirmed internally. | Security monitoring, vulnerability/threat detection and related security telemetry. Rapid7 services may process endpoint, server, cloud application and log data. |
| Atlassian Statuspage | United States - AWS US West (Oregon / us-west-2), with failover to AWS US East (N. Virginia / us-east-1) | Status and incident communications. Stores and processes customer subscriber information, including customer name and email address, when users subscribe to StoreForce Statuspage notifications. |
| Manus | United States and Singapore, based on Manus' current public data-location statement | AI-assisted creation of customer Quarterly Business Review (QBR) presentations using data exported from the StoreForce application. Inputs may include customer employee/user names, email addresses, screenshots, usage information and other individual-level personal data. |
Maximize Every Customer Visit
StoreForce is built by retailers for retailers. Speak with our team to improve store performance
and uncover missed revenue opportunities across your stores.
Speak To A Retail Expert
4.9 Rating StoreForce ESS
Subscribe to Our Newsletter!
Stay up-to-date with StoreForce