{
  "canonical_url": "https://legal.peopletechrevolution.com/subprocessors",
  "content": "# Subprocessors and Data Locations\n\nThis register records the categories of service provider People Tech Revolution Pty Ltd relies on to run its products: what each category does, the kinds of information it handles, where that processing may take place, and whether it involves customer content.\n\nIt is a register of categories, not a list of company names. Our product architecture is still changing, and a published list of company names would be out of date faster than it could be republished. What is published here is the part a reader can rely on and hold us to: the function performed, the information involved, and the location or region class.\n\nThis register does not promise a permanently complete list of every company we deal with, and it should not be read as one. If you need the identity of the providers engaged for a particular product, for a procurement, due-diligence or regulatory assessment, ask us using the Contact section below.\n\n## How to read this register\n\n**Provider category** describes what kind of service the provider supplies. It is not a company name.\n\n**Customer content** means material a person or organisation submits to a product or generates in it: uploaded documents, images, voice samples, recorded audio and video, messages, and the outputs generated from them. Account details, contact details, request metadata and system logs are personal information but are not customer content, and the table distinguishes the two.\n\n**Processing location or region class** is what we have actually established, not what we would prefer. Where a cell says a location is not established, it means we have checked and the running configuration does not establish one, and we are not supplying a likely answer in its place.\n\n**Last verified** is the date the row was checked against the production configuration that was running, and against the code that makes the call, rather than against a plan, a design document or a supplier's marketing page.\n\n## The register\n\n| Provider category | Purpose or processing function | Information processed | Processing location or region class | Processes customer content | Applies to | Last verified | How changes are notified |\n|---|---|---|---|---|---|---|---|\n| Cloud infrastructure and application hosting | Runs our applications and stores their data: compute, container images, object storage, secret storage, logging and monitoring | Everything our products hold, including account records, uploaded documents and media, generated outputs and system logs | Australia. Deployed in an Australian region | Yes | All PTR and Didymo products | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Managed application database | Stores workspace, account, session, lead and consent records | Account and workspace records, conversation and session records, lead records, consent records | Australia | Yes | Didymo, PTR Labs, PTR AI Studio, PTR Admin | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Web hosting and content delivery edge | Serves our web pages and static files and caches them at network edges | Request metadata: IP address, user agent, requested address | Origin in Australia. The caching edge is operated outside Australia; on the verification date our sites were served from a point of presence in the United States | No. Request metadata only | All PTR and Didymo websites, including this one | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Identity and authentication | Creates and verifies sign-in credentials and sessions | Account identifier, email address, sign-in method, sign-in history | Not established. This service is not pinned to a region by our configuration and the provider does not expose one to us | No | Didymo application and portal | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Generative AI text model service | Generates and analyses text for conversational and assistant features | Prompts, excerpts retrieved from workspace knowledge, persona text, and the generated replies | Australia. Requests are sent to an Australian regional endpoint | Yes | Didymo, PTR Labs, PTR AI Studio | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Speech to text | Converts recorded speech into text | Recorded speech audio and the returned transcript | Split as at the verification date. Didymo sends this to an Australian regional endpoint. PTR Labs and PTR AI Studio send it to a global endpoint that is not pinned to a region | Yes | Didymo dictation, PTR Labs, PTR AI Studio | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Text to speech | Generates spoken audio from text the product supplies | Reply text submitted for synthesis and the returned audio | Global endpoint that is not pinned to a region | Yes | PTR Labs, PTR AI Studio | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Voice cloning and synthesis from a supplied sample | Creates a synthetic voice from a supplied voice sample and synthesises speech in it | The uploaded voice sample of an identifiable person, the resulting voice identifier, and reply text submitted for synthesis | Outside Australia. The provider publishes no region split for this service, so no more precise location is established | Yes | Didymo voice features | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Real-time avatar generation and live conversational media | Generates a speaking avatar and carries the live audio and video of a call | The consented reference photograph, live microphone audio and camera video from the participant's browser, the persona prompt, the transcript, and any recording | Outside Australia. The provider publishes no region split for this service, so no more precise location is established | Yes | Didymo live twin calls | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Customer-authorised file storage and workplace identity connectors | Lets a customer grant access to their own document storage so that files they select can be imported into a workspace | The authorisation grant, basic profile identity from the connected account, and the contents of the files the customer selects | Not established. These are global provider endpoints and no processing region is exposed to us | Yes | Didymo knowledge connections | 2026-08-24 | Named in the product at the point of connection, and by a new dated version of this register |\n| Business email delivery | Sends enquiry and notification email from our forms and services | Sender name, email address, phone number, organisation, and the message text | Not established. No processing region is exposed for this service | Yes. A message the sender writes is their own content | PTR website contact form, Didymo enquiry forms | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Spreadsheet-based internal customer and reporting records | Holds our internal customer-relationship and reporting records | Contact and lead records, and internal commercial records | Not established. No processing region is exposed for this service | No. Contact and commercial records only | PTR Admin | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Authoritative DNS | Answers domain-name lookups for our domains. Web traffic itself does not pass through this provider | Lookup metadata, such as the address of the resolver and the name requested | Distributed anycast network. Not established for any individual lookup | No | All PTR and Didymo domains | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Automated abuse and bot challenge | Presents a challenge that distinguishes automated traffic from a person | The visitor's IP address and a challenge token | Distributed edge network. Not established | No | Didymo public twin pages and enquiry forms | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| E-commerce platform and store hosting | Runs our online store and holds its product catalogue and order records | Order records, billing name and email address, order line items | Not established. The hosting account has not been verified for this register | No. Order and billing records only | The PTR online store | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Payment processing for the online store | Takes payment for orders placed in the online store | Payment and billing details submitted at checkout | Not established. The gateway is configured inside the store platform rather than in our own systems and has not been verified for this register | No | The PTR online store | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Public JavaScript delivery networks | Serve third-party JavaScript libraries used by some of our public web pages | Visitor IP address, user agent and referring page at the moment a file is fetched | Distributed edge networks. Not established | No | The PTR corporate website and its support widget | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Web font delivery | Serves the typefaces some of our pages use | Visitor IP address and user agent at the moment a font is fetched | Distributed edge network. Not established | No | PTR Labs, PTR AI Studio and PTR Admin web pages | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n| Source-code hosting and build pipeline control plane | Holds our source code and coordinates our build and deployment pipeline | Source code, build logs and workflow metadata. Not customer records | Provider control plane, not established. The build jobs themselves run on machines PTR operates in Australia | No | Engineering infrastructure for all products | 2026-08-24 | New dated version of this register; material changes also noticed under the Privacy Policy |\n\n## What this register does not record\n\n**The identity of individual companies.** See the opening of this document. Ask us if you need it for an assessment.\n\n**Contractual position.** This register records what each category of provider does and where. It does not record the contractual terms agreed with any individual provider, including data-protection agreements and restrictions on how a provider may use information. Those are handled provider by provider and are not published here. Ask us if you need the position for a specific provider.\n\n**Integrations that are not switched on.** Our code contains integrations that are not enabled in production. They are deliberately absent from the table, because listing a provider we do not currently call would describe a capability the platform does not have. As at the last verification date, no payment provider is engaged inside the Didymo product itself; the payment row above covers the PTR online store only.\n\n**Providers used purely for internal business administration** that do not process information from our products.\n\n## How we verify this register\n\nEach row was checked against the production configuration that was actually running on its Last verified date, and against the code that makes the call, rather than against an architecture document. Where the running configuration did not establish a fact, the row says so instead of supplying a plausible answer.\n\nRows are re-verified when a category changes and on periodic review. The Last verified date on each row is the date of the check that supports that row, and it is the only date a reader should rely on for it.\n\n## How changes are notified\n\nThis register is versioned like every other document we publish. It carries a document identifier, a version, an effective date and a SHA-256 of its text, and a new version replaces the old one at the same address. The machine-readable registry of every document and version is published alongside it.\n\nA change to a category, to what that category does, to the information it handles, to whether it handles customer content, or to its location or region class, produces a new version of this register with a new effective date.\n\nAdding or removing an individual company inside an existing category does not by itself produce a new version, because this register does not name individual companies. That is a consequence of publishing categories rather than names, and it is stated here rather than left for a reader to discover.\n\nWhere a change is material to the way we handle personal information, notice is also given under the Changes section of the [Privacy Policy](/privacy).\n\nWhere a customer connects their own third-party service to a product, that service is named to them in the product at the point of connection, whether or not it appears here.\n\n## Contact\n\nPeople Tech Revolution Pty Ltd\nABN 66 646 534 858\nAddress: 27/65 Manooka Drive, Cannonvale, Queensland 4802, Australia\nPrivacy email: privacy@peopletechrevolution.com\n\nTo ask which providers are engaged for a particular product, or for the provider information a procurement or regulatory assessment needs, write to that address.\n",
  "content_format": "markdown",
  "document_id": "PTR-SUBPROCESSORS",
  "effective_date": "2026-08-24",
  "last_updated": "2026-08-24",
  "sha256": "7fe43445991969ad3c4677762af4278e9e35725ce9b32801f9d49dcd8ce08c21",
  "status": "published",
  "supersedes": null,
  "title": "Subprocessors and Data Locations",
  "version": "0.2.00"
}