This list identifies the sub-processors Pixop engages to process Personal Data on behalf of its customers. It is incorporated by reference into the Pixop Data Processing Agreement (§7.1) and, through it, into the Pixop Terms of Service (§9.2), and it is the list referred to in the Pixop Master Service Agreement, Annex D §D5. This page is its permanent address; cite it by version and date.

Scope matters. Pixop supplies more than one product, and a provider listed here does not process data for every product. Read the entry for the product you use.

Each entry in full below.

Amazon Web Services

Legal entity. Amazon Web Services EMEA SARL, Luxembourg.

What it processes. Cloud infrastructure, databases, storage, media processing and telemetry services used by the applicable Pixop products, including Pixop Platform / FILE, Pixop Pulse and applicable Pixop Prime deployments. Input and processed video are stored in AWS S3; persistent application data for Pixop Platform / FILE is held in AWS RDS.

Where. eu-west-1 (AWS Europe, Ireland), within the EEA, unless a different region is agreed in writing.

Transfers. None required for processing within the EEA. Access by Pixop personnel or a sub-processor from outside the EEA is a transfer and is addressed in DPA §12. Where a different region is agreed, the mechanism stated in that agreement applies.

Intercom

Legal entity. Intercom R&D Unlimited Company, 124 St Stephen’s Green, Dublin 2, Ireland.

What it processes. Support chat, and the support and diagnostic material you supply through it: screenshots, submitted content samples, logs and diagnostics, together with the contact details of the person raising the request.

What it is not. Intercom is not part of the enhancement pipeline. No Customer Content is processed through it except where you deliberately supply a sample in a support request, and no Pixop Prime or Pixop Pulse component runs on it. Our separate use of Intercom for website and prospect chat, before any customer relationship exists, is our own processing as controller and is described in the Privacy Policy rather than here.

Where. United States. Note that the contracting entity is Irish but the service is hosted in Intercom’s United States region, so support material supplied through chat is stored outside the EEA.

Transfers. EU-U.S. Data Privacy Framework. Intercom is certified under the Framework and the parties rely on that certification for transfers to the United States. Intercom’s data processing agreement further provides that if the Framework ceases to be a valid transfer mechanism, the EU Standard Contractual Clauses are deemed incorporated and apply in its place, so a mechanism is in force either way.

Salesforce / Heroku

Legal entity. Salesforce EMEA Limited, Heroku platform.

What it processes. Application hosting for the legacy Pixop Platform / Pixop FILE service only. Processes application and job metadata required to operate that service, including processing jobs, user accounts, teams and organisations, and billing and account records. Video files are not stored on Heroku, and Heroku is not used by Pixop Prime or Pixop Pulse.

Where. United States and European Union.

Transfers. EU Standard Contractual Clauses for the United States element.

What this list does not cover

Pixop Prime. The Heroku platform is not used by Pixop Prime. No Pixop Prime application, API, control plane, processing service or media-processing component runs on Heroku, and no Pixop Prime Customer Content or operational data passes through it. For a Pixop-Managed Deployment of Pixop Prime, Amazon Web Services is the only sub-processor.

Pixop Pulse. Pixop Pulse, Pixop’s licensing and telemetry service, runs entirely on Amazon Web Services. It receives the limited outbound operational telemetry from Pixop Prime instances and provides the associated licence-validation, usage-accounting and operational-visibility functions. No Pixop Pulse component runs on Heroku.

Video enhancement. Pixop’s enhancement is performed by Pixop’s own machine-learning models. Pixop does not use any third-party artificial-intelligence or machine-learning service to process Customer Content.

Pixop’s own processors. Providers that process Personal Data for Pixop’s own business purposes - payment and billing, website analytics, newsletter delivery, website and prospect chat, and security, audit and compliance records - are not sub-processors under a customer Data Processing Agreement, because Pixop determines the purposes of that processing and acts as controller in respect of it. They are described in the Pixop Privacy Policy. This includes Pixop’s payment processor.

Note on chat, because one provider sits on both sides. Intercom serves two purposes that fall differently. Chat with website visitors and prospects is Pixop’s own processing and belongs in the paragraph above. Support material a customer supplies through chat once the relationship exists - a screenshot, a sample, a log - is processed on that customer’s instructions, and for that purpose Intercom is a sub-processor and is listed above.

Changes to this list

Pixop gives at least thirty (30) days’ prior notice of an intended addition or replacement of a sub-processor, by email, account notice or another durable electronic notice. A customer may object within that period on reasonable and documented data-protection grounds, and the process in the Data Processing Agreement then applies.