Data Processing Agreement
Draft — pending legal review
This page is a draft. It has not been reviewed by a lawyer, is not yet part of the legal terms, and must not be signed or relied on. Items marked [to be filled] are not decided yet.
This agreement applies when a customer organization (the Customer) uses the PhillipCLI hosted service (Tara and Ryoma) and personal data in the content it puts into the service is processed for it.
- Processor:
[to be filled: legal entity name],[to be filled: address] - Customer: the organization that accepts the Terms
- Contact:
[to be filled: contact email] - Hosting region:
[to be filled: hosting region]
1. Roles
For the content the Customer puts into the service (resources, Knowledge base documents, project data, task data, members), the Customer decides the purposes and the Processor processes it on the Customer's behalf. For account and billing data of its own, the Processor acts as a controller, as the Privacy Policy says. Paddle is an independent controller for payment and tax data.
2. What is processed
- Subject matter and purpose: providing the service: sign-in, roles and policies, resources, Knowledge base, project and Flow metrics, notifications, billing.
- Duration: while the organization exists, then as the Data retention page says.
- Data subjects: the Customer's members and invited people, and people named in task data.
- Kinds of data: handle, name, email, avatar, role, sign-in provider identity, audit log entries, task titles, labels, owners and timestamps, usage telemetry (model, token counts, estimated cost, session and task identifiers; no prompts or responses), and resource and Knowledge base content the Customer uploads.
3. Processor's duties
The Processor will:
- process the data only on the Customer's documented instructions, which are this agreement and the Customer's use of the service. If the law requires other processing, the Processor will say so first unless the law forbids it;
- make sure people who access the data are bound to confidentiality;
- keep the security measures in section 4;
- use only the subprocessors on the Subprocessors page, under written terms that give the same level of data protection;
- help the Customer answer requests from data subjects, mainly through the self-service tools: data export, member removal, and organization and account deletion;
- tell the Customer of a personal data breach without undue delay, and within
[to be filled: hours]of becoming aware; - help with data protection assessments and with authorities, where the Customer needs it and as far as reasonable:
[to be filled: cost terms]; - delete or return the data when the service ends, as the Data retention page says (export on request, 30-day grace period, then purge; backups age out within about 4 weeks);
- give the Customer the information needed to show compliance, and allow audits as in section 6.
4. Security measures
As described in the Privacy Policy: session and API tokens are stored only as hashes; SSO client secrets are stored encrypted; each organization's data is isolated at the application and database level; resource packages are signed; the connection uses HTTPS; administrative changes are written to an audit log that does not hold secret content. Further measures: [to be filled].
5. Subprocessors
The Customer gives general authorization to the subprocessors on the Subprocessors page. The Processor will notify the Customer of changes: [to be filled: notice period and method]. The Customer may object on reasonable grounds: [to be filled: procedure].
6. Audits
The Customer may ask for information needed to check compliance and, no more than once a year unless there is a breach: [to be filled: audit terms].
7. International transfers
Data may be processed in [to be filled: hosting region] and in the countries of the subprocessors. Transfer mechanism, such as standard contractual clauses: [to be filled].
8. Liability and governing law
Liability follows the Terms and Conditions: [to be filled: confirm]. Governing law and courts: [to be filled: governing law].
9. Signatures
[to be filled: how the Customer accepts or signs; signatory names and dates]