Subprocessors

This page identifies third-party subprocessors and service providers that WPShift may use to provide, support, secure, and operate the Service. This page should be read together with our Privacy Policy and, where applicable, our Data Processing Agreement. 1. What is a subprocessor? A subprocessor is a third party engaged by WPShift to process personal data on behalf of our customers in connection with the Service. In some cases, a listed provider may act as an independent controller for its own purposes rather than as a subprocessor for customer data in every context. The role of a provider may depend on the specific service used and the nature of the data involved. 2. Why we use subprocessors We may use subprocessors and infrastructure partners for purposes such as: cloud and infrastructure hosting; server provisioning and management; storage and backups; billing and payment operations; email delivery; customer support; artificial intelligence and automated functionality; product analytics and monitoring; error logging and performance diagnostics; communication and operational tooling. 3. Current subprocessors and key providers The following providers may be used in connection with the Service. Hetzner Purpose: Infrastructure hosting, cloud computing, networking, storage, and related services used for WPShift Cloud and other WPShift systems. Data involved may include: Server metadata, IP addresses, infrastructure logs, website and application data, account-linked service information, backups, and operational data necessary to provide hosting and infrastructure services. Location / transfer note: Data may be processed in Hetzner data centers and systems depending on the infrastructure selected and services involved. OVHcloud Purpose: Infrastructure hosting, cloud computing, networking, storage, and related services used for WPShift Cloud and other WPShift systems. Data involved may include: Server metadata, IP addresses, infrastructure logs, website and application data, account-linked service information, backups, and operational data necessary to provide hosting and infrastructure services. Location / transfer note: Data may be processed in OVHcloud data centers and systems depending on the infrastructure region and services involved. DigitalOcean Purpose: Cloud infrastructure, virtual servers, networking, storage, databases, and related infrastructure services used to operate parts of the WPShift platform. Data involved may include: Server metadata, IP addresses, application data, infrastructure logs, account-linked service information, diagnostic information, and other operational data. Location / transfer note: Data may be processed in DigitalOcean infrastructure and data center regions depending on the services used. Paddle Purpose: Payment processing, merchant-of-record or reseller transactions, billing, subscription handling, refunds, tax handling, and transaction support for Paddle-processed purchases. Data involved may include: Billing details, transaction metadata, subscription information, name, email address, billing country, and payment-related records. Role note: For Paddle-processed transactions, Paddle may act as an independent controller or merchant of record for billing-side processing rather than purely as a subprocessor. OpenRouter Purpose: Providing access to third-party artificial intelligence models and AI-related functionality used within the WPShift platform. Data involved may include: Prompts, instructions, generated responses, technical metadata, account or service context included in a request, and other information submitted to AI-powered functionality. Role note: OpenRouter may route requests to third-party AI model providers. The provider processing a request may depend on the model or AI functionality being used. Users should avoid submitting unnecessary sensitive or confidential personal data to AI functionality unless such processing is appropriate for their intended use. Google Purpose: Providing artificial intelligence models and related services, including Google Gemini models, that may be accessed directly or through an AI service provider such as OpenRouter. Data involved may include: Prompts, instructions, generated responses, technical metadata, and information supplied as part of an AI request. Location / transfer note: Processing locations and applicable safeguards may depend on the specific Google service, model, and configuration used. OpenAI Purpose: Providing artificial intelligence models and related services that may be used to power AI-assisted functionality within WPShift, either directly or through a service provider such as OpenRouter. Data involved may include: Prompts, instructions, generated responses, technical metadata, and information supplied as part of an AI request. Location / transfer note: Processing locations and applicable safeguards may depend on the specific OpenAI service and configuration used. Anthropic Purpose: Providing artificial intelligence models and related services, including Claude models, that may be used to power AI-assisted functionality within WPShift, either directly or through a service provider such as OpenRouter. Data involved may include: Prompts, instructions, generated responses, technical metadata, and information supplied as part of an AI request. Location / transfer note: Processing locations and applicable safeguards may depend on the specific Anthropic service and configuration used. Email and communication providers Purpose: Transactional email delivery, service notifications, account emails, support communications, and operational messaging. Data involved may include: Email address, name, message contents, notification metadata, delivery records, and related logs. Analytics and monitoring providers Purpose: Product analytics, error tracking, performance monitoring, uptime diagnostics, security monitoring, and operational logging. Data involved may include: IP addresses, device information, usage events, log entries, browser information, timestamps, identifiers, and diagnostic data. Support and helpdesk providers Purpose: Customer support, ticketing, communication history, troubleshooting, and issue resolution. Data involved may include: Name, email address, support communications, attachments, screenshots, technical information, and issue metadata. 4. AI processing Certain features of WPShift may use artificial intelligence models provided by third parties. Depending on the functionality used, requests may be processed by OpenRouter and/or underlying AI model providers such as Google, OpenAI, or Anthropic. The specific AI model or provider used may change over time as WPShift improves, replaces, or expands its AI functionality. Where reasonably possible, WPShift limits the information sent to AI providers to the data necessary to provide the requested functionality. Customers remain responsible for ensuring that information submitted through AI-powered features is appropriate for processing and that they have the necessary rights and legal basis to submit such information. 5. Infrastructure providers WPShift may use multiple cloud infrastructure providers, including Hetzner, OVHcloud, and DigitalOcean. The provider used for a particular server, website, workload, or WPShift Cloud service may depend on factors such as availability, region, capacity, performance, redundancy, and technical requirements. Not every customer or workload will necessarily use every infrastructure provider listed on this page. 6. Changes to subprocessors WPShift may update this list from time to time as our service providers change or as we add, replace, or remove subprocessors. Where required by applicable law or by contract, we will provide notice of material subprocessor changes. Continued use of the Service may involve the use of newly added or replacement subprocessors where permitted under the applicable agreement and applicable law. 7. International transfers Some subprocessors may process personal data outside your country or outside the European Economic Area. Where required by applicable data protection law, WPShift will use appropriate safeguards for international transfers, which may include adequacy decisions, Standard Contractual Clauses, or other legally recognised transfer mechanisms. The exact processing location may depend on the provider, selected infrastructure region, service configuration, and functionality used. 8. Contact If you have questions about our subprocessors, AI providers, international data transfers, or would like more information, please contact: WPShift Email: info@wpshift.io Website: wpshift.io

Document Info

Actions