Sub-processors
Last reviewed: 16 November 2026.
A sub-processor is a third party we use to process personal data on behalf of Intentric, in our role as described in the Privacy Policy. This page lists them, with what each does and the data it receives. It is the list the Data Processing Addendum refers to.
Our Sub-processors
| Provider | Purpose | Data involved | Location |
|---|---|---|---|
| Stripe | Payment processing: hosted checkout, subscription billing and sales tax calculation. | Billing contact details, quote, subscription and payment records. Card details are entered at Stripe and do not pass through our systems. | United States |
| OpenAI AI model provider | Generating the responses of Intentric AI: drafting a change from a request, answering questions about your deployments, and writing runbooks. | The text of a request after credential-shaped text has been replaced, and for questions about a deployment, the names and settings of its resources, recent changes, and verification and drift findings. | United States |
| Amazon Web Services Hosting provider | Hosting the service, its database, object storage and secrets store. | All data the service holds, including customer content. Personal data is encrypted before it is stored. | United States regions |
| Web3Forms | Relaying request-access form submissions from this website to our inbox. | What the form collects: name, work email, company, role (optional) and the message you write. | As stated in Web3Forms’ privacy policy |
No other provider processes customer personal data for Intentric. The service sends no email of its own: an organization sends email through a provider it chooses and configures, using its own API key, its own SMTP server, or by signing in to Google Workspace or Microsoft 365, so no email provider is a sub-processor.
Services an Organization Connects
The services below are not our sub-processors. An organization’s administrator chooses to connect them, and they process data for that organization under the organization’s own agreement with the provider. We send them data only to carry out what the organization has set up.
- Cloud accounts: Amazon Web Services, Microsoft Azure and Google Cloud, where approved changes are applied and checked.
- Email delivery: the organization’s own Google Workspace or Microsoft 365 sender, or an email provider or mail server it configures (for example SendGrid, Mailgun, Postmark, Resend, Amazon SES or SMTP), which sends notification email.
- Chat: Slack and Microsoft Teams channels that receive notifications.
- Document storage: an S3 bucket, a Google Drive folder or a OneDrive or SharePoint library that receives a one-way copy of a deployment's definition.
- Source control: the git host an organization binds a deployment's definition to.
- Sign-in: Google, Microsoft, GitHub, GitLab or Bitbucket, or the organization’s own single sign-on provider.
Changes to This List
We will update this page before a new sub-processor starts processing customer personal data, and will post it on this page 30 days before it does, and email customers on request. Customers may object on reasonable grounds, and if that cannot be resolved, may terminate the affected service.
To ask a question about a sub-processor, or to be told of changes, contact us at the address on the Privacy Policy.