This register is proposed, not a list of approved production appointments. Contracting legal entities, support and backup countries, provider retention, DPAs and international safeguards must be verified before customer data is enabled.

Proposed application, database and private conversion/scanning hosting. The deployment template selects Frankfurt, but production compute is not provisioned. That selection does not establish all support, control-plane or backup locations.

Proposed DNS/CDN/security and private R2 file storage. A Western Europe R2 location selection does not establish exclusive EEA processing or every replica/support country. Production contractual and transfer details remain unapproved.

Transactional emails, recipient addresses and necessary message/delivery information. Production contracting entity, processing countries, retention and transfer safeguards require verification.

Questions, selected excerpts and necessary context for enabled AI. Contracting entity, training restrictions, abuse-monitoring and retention exceptions, countries and safeguards require approval. A store: false setting is not a zero-retention assurance.

Docling and malware scanning are planned as private hosted services. Self-hosted software is not automatically an additional legal subprocessor; the hosting operator and any actual external data flow remain relevant.

Customer-selected connectors, identity providers and learning destinations depend on the actual enabled arrangement. The customer must authorise scopes and destinations. Beetl-appointed processing vendors remain subject to the DPA even where a customer selects a feature.

Monitoring and live payment arrangements are not approved. Their actual roles, entities, data, locations and safeguards must be added before enablement; no undisclosed provider is authorised by this page.

The DPA governs country approval and applicable EU SCCs, UK instruments and POPIA transfer grounds. South African operator access and onward provider access must be assessed alongside storage location. No completed transfer instrument or adequacy finding is asserted by this draft.

The proposed DPA requires 30 days’ advance subprocessor notice and a reasonable data-protection objection route, with alternatives or affected-service termination/refund if no solution exists. This procedure and the verified public register must be operational before appointment.