The paperwork behind the platform.
Data handling, subprocessors, privacy program, DPA, retention, residency, and cross border transfers, described in one place, in the terms your procurement, privacy, and legal teams already use.
What we hold, why we hold it, and where it lives.
What we process
Source documents you upload, framework artifacts produced from them, generated instructional content, review history, evidence artifacts, and account metadata for the users you authorize.
Lawful basis
Processing is performed on the instruction of the customer as data controller under the master services agreement. We act as data processor. Purpose is bounded to service delivery.
Residency
Production data stays in the customer's region: Portugal for customers in the European Union, the United States, Japan, or Australia. No routine replication across borders.
Retention
Content is retained for the term of the customer agreement plus a defined tail. On termination, data is exported on request and then deleted in line with the schedule in the DPA.
Deletion
Deletion initiated by the customer is honored on documented workflows. Full tenant deletion propagates to backups on the backup cycle schedule, with a written completion notice on request.
No model training
We do not use customer content to train third party foundation models. Where generative components are used, prompts and outputs remain within the customer's tenancy boundary.
Who processes data on our behalf.
Named subprocessors are listed below. The full register (including legal entity, jurisdiction, and processing purpose) is provided to prospective customers on request. Material changes are notified to customers in line with the DPA.
How the privacy program is run in practice.
Knowledge Foundry is registered in Portugal, so our privacy program is operated under the GDPR and Portuguese Law 58/2019, with the CNPD as our lead supervisory authority. A named privacy contact receives requests from customers and, where relevant, from data subjects on customers' behalf. Requests to access, correct, or delete personal information are triaged against a documented workflow with defined response windows.
Customer data is processed in the customer's own region, so most deployments involve no cross border transfer at all. Where a transfer out of the European Economic Area does occur, we rely on an adequacy decision or the Standard Contractual Clauses, and we meet the equivalent transfer rules in Australia (APP 8) and Japan (APPI).
What the DPA covers.
Our DPA is available on request and can be executed alongside the master services agreement. It covers the controller/processor relationship, subprocessor authorization, security obligations, breach notification, mechanisms for cross border transfers, audit rights, and deletion or return of data on termination.
For regulated customers, additional operating obligations can be reflected in schedules to the master services agreement. Examples include DORA for EU financial entities, APRA CPS 234 in Australia, the FSA cybersecurity guidelines in Japan, and HIPAA business associate terms in the United States. Customer legal and procurement teams should raise specific requirements during contracting.
How long we hold data.
Customer content is retained for the term of the customer agreement. On termination, the customer may request a full structured export for a defined window, after which data is deleted from primary systems on a documented schedule. Deletion propagates through backups on the backup cycle interval. A written completion notice is available on request.
Aggregate operational metrics that do not contain customer content or personal information may be retained for purposes of platform integrity beyond the customer term.
How the platform supports each privacy regime.
The Knowledge Foundry platform, and our operational practices around it, are designed to support customer obligations in each market we serve. Collection is limited to what the service requires. Notice is provided through the customer facing privacy policy and, for direct interactions, at the point of collection. Access, correction, and complaint handling are documented and time bound.
- Portugal and the EU: GDPR and Portuguese Law 58/2019, including processor terms under Article 28 and support for data subject requests.
- United States: state privacy laws such as the CCPA as amended by the CPRA, with service provider terms, and HIPAA business associate terms where health information is in scope.
- Japan: the Act on the Protection of Personal Information (APPI), including its security control and third party provision rules.
- Australia: the Privacy Act 1988 and the Australian Privacy Principles, including APP 8 on cross border disclosure.
Where customer end users reside overseas, the customer remains the controller and determines the legal basis for processing. We support the customer's obligations with the documented residency, DPA, and subprocessor register described above.