Skip to content

Legal

Published customer policies and supporting legal documents for the Paycux service. Each page clearly states whether it is effective or still under review.

Template — under legal review. This document is not yet in force. It is a working draft, has not been signed by Paycux, and should not be relied on for a real engagement until a dated, executed version is published.

Subprocessors

Last updated: August 31, 2026 · Draft, not yet in force

A subprocessor is a vendor Paycux authorises to process Subscriber Personal Data on its behalf, as described in the Data Processing Addendum. The exact vendors Paycux will use for each category have not been finalised, so this page lists categories rather than company names — it will be updated with named vendors before the DPA is signed with any customer.

Current categories

CategoryPurposeData categoryTransfer region
Cloud infrastructure — provider to be listedHosting the application, database and backups.All Subscriber Personal Data processed by the Service.Region to be confirmed
Transactional email — provider to be listedSending account, sign-in and notification emails.Name and email address.Region to be confirmed
Error monitoring — provider to be listedCapturing crash and error diagnostics.Technical metadata; limited personal data where it appears in an error.Region to be confirmed
Payment processing — Paddle (Merchant of Record for Paycux's own subscriptions; customers' own Stripe/Paddle accounts stay with them)Billing Subscribers for Paycux's own paid plans.Billing contact details; payment data is handled directly by Paddle.Region to be confirmed
Customer support — provider to be listedManaging support tickets and conversations.Contact details and the content of support requests.Region to be confirmed
Product analytics — provider to be listedUnderstanding aggregate product usage.Usage events; pseudonymised where possible.Region to be confirmed

How we would notify changes

Before adding a new subprocessor, Paycux intends to update this page at least ten (10) business days in advance. Subscribers who want an active notice of changes, rather than checking this page, can ask [email protected] to be added to a notification list once one exists.

Objecting to a new subprocessor

If a Subscriber has a legitimate data-protection objection to a new subprocessor, it can raise it within the notice window above by emailing [email protected]. The parties would then work in good faith to resolve the objection before the new subprocessor starts handling that Subscriber’s data.