Processing Roles and Subprocessors
Last updated: 2 November 2026 · Version 2026-11-02
Aurora is the product supplier. The actual hosted deployment determines which external processors, locations and safeguards apply.
Aurora
ACL Aurora Core Labs LTD operates SpecDox under the Aurora brand. Where the company operates infrastructure directly, it is the processor itself; Aurora is not a substitute name for separate external providers.
Paddle
Paddle is the merchant of record and independent controller for checkout, payment, tax and transaction administration. The selling entity appears in your checkout and receipt. See https://www.paddle.com/legal/privacy. Paddle is not listed as a customer-content subprocessor for its sales role.
Google Analytics
Google provides optional analytics for the public marketing website after consent. It is not a required component of processing customer documents. See the Privacy and Cookie Policies.
Hosted deployment schedule
The authorised customer-content subprocessor list must identify each external legal entity, its function, processing location and applicable transfer safeguards in the agreed DPA schedule. That inventory has not been established by this public notice. Ask Aurora for the completed schedule before hosted personal-data processing. Changes follow the DPA notice and objection procedure.
Customer-selected services
Customer-connected GitLab, AI providers and agents receive content according to the enabled workflows. Their role depends on who contracts and instructs them. A customer-contracted integration is not automatically Aurora’s subprocessor; a provider Aurora appoints to process customer content must be included in the DPA schedule.
Purchase support: Paddle · Paddle Buyer Terms · Paddle Refund Policy · Paddle Privacy Notice
Aurora: hello@auroratech.ai