An inventory grounded in the application's integrations. Contracting entities, active regions and transfer safeguards require deployment verification.
The inventory below identifies providers referenced by the code, rather than certifying that every optional feature is active. A production register must identify the actual contracted entity, processing/support locations, relevant DPA, transfer mechanism and effective date. An infrastructure provider may be a processor for our account data and a subprocessor for customer workspace data.
Workspace administrators decide whether to use optional AI, messaging, maps and external webhooks. Customer-supplied webhook recipients are chosen by the customer and must be assessed by it. Changes to approved subprocessors follow the notice and objection procedure in the executed DPA; this public list does not replace individual notice.
Paddle acts as an independent controller for its merchant-of-record transaction processing under its own notice. Payment and tax data entered into checkout do not make Paddle the processor for your work-order database. Its transaction terms and actual contracting entity are shown at checkout.
Paddle: Buyer terms · Privacy notice
