1. Definitions
- Data Protection Laws means all laws that apply to the processing of Customer Personal Data under the Terms, including the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and US state privacy laws such as the California Consumer Privacy Act as amended (CCPA).
- Customer Personal Data means personal data contained in Customer Content (as defined in the Terms) that we process on your behalf. It does not include account, billing, and website information that we process as a controller under our Privacy Policy.
- Subprocessor means a third party we engage that processes Customer Personal Data.
- Security Incident means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data.
- "Controller", "processor", "data subject", "personal data", "processing", "service provider", and "supervisory authority" have the meanings given in the Data Protection Laws.
2. Roles and instructions
You are the controller of Customer Personal Data, or a processor acting for your own customers, and we are your processor or subprocessor. You are responsible for having a lawful basis, giving any required notices, and obtaining any required consents for the Customer Personal Data you submit.
We process Customer Personal Data only on your documented instructions. Your instructions are the Terms, this DPA, your project settings, and your use of the Service, including uploads, API requests, and the features and AI models you enable. We will tell you if we believe an instruction infringes Data Protection Laws, and we may suspend that processing until it is resolved. If the law requires us to process Customer Personal Data otherwise, we will tell you first unless the law prohibits it.
We do not use Customer Personal Data to train general-purpose AI models. We may derive de-identified, aggregated Service Data as the Terms describe, and once derived it is no longer Customer Personal Data.
3. Confidentiality
We limit access to Customer Personal Data to personnel who need it to provide, secure, or support the Service, and who are bound by appropriate confidentiality obligations.
4. Security
We implement and maintain the technical and organizational measures in Annex II, appropriate to the risk of the processing. We may update these measures as technology and threats change, provided the update does not materially reduce overall security.
5. Subprocessors
You give us general authorization to engage Subprocessors. Our current Subprocessors are listed on our Subprocessors page. Within 30 days after adding or replacing a Subprocessor that processes Customer Personal Data, we will post the change on that page and notify customers who have asked to receive updates by emailing [email protected].
You may object to a new Subprocessor on reasonable data protection grounds within 30 days after we post the change or notify you, whichever is later. We will work with you in good faith on an alternative, such as a project setting that avoids it. If we cannot reasonably offer one, you may stop using the affected feature or terminate the affected Service and receive a refund of any prepaid, unused credits for it.
We impose data protection obligations on each Subprocessor that are no less protective than this DPA, to the extent applicable to the service it provides, and we remain responsible for its performance of them.
6. Assistance
The Service lets you access, export, correct, and delete Customer Content yourself. Where you cannot do so, we will provide reasonable assistance with data subject requests. If we receive a request directly from a data subject about Customer Personal Data, we will direct them to you and will not respond otherwise unless the law requires it. We will also provide reasonable information to help you with data protection impact assessments and consultations with supervisory authorities about the Service.
7. Breach notification
We will notify you without undue delay, and where feasible within 72 hours, after becoming aware of a Security Incident. We will send the notice to your organization's administrators and include what we know about the nature of the incident, the data and data subjects affected, likely consequences, and the steps we have taken or propose. We will provide more information as it becomes available and take reasonable steps to contain and remedy the incident. Our notice is not an admission of fault.
8. Deletion and return
You can export and delete Customer Content at any time while your account is active. When the Terms end, we will delete Customer Personal Data from active systems within 30 days unless the law requires us to keep it. While the Terms are in force, we may also delete Customer Content after a sustained payment default, with notice and a chance to pay, as described under "Default and deletion of your data" in Section 4A of the Terms. Copies in backups expire on their normal rotation and stay protected under this DPA until they do.
9. Audits
On written request, we will provide the information reasonably necessary to demonstrate compliance with this DPA, such as written responses to security questionnaires and documentation of our measures. If that information is not enough to meet a requirement of Data Protection Laws or a supervisory authority, you may conduct an audit, no more than once a year, on at least 30 days' notice, during business hours, at your expense, under confidentiality obligations, and without access to other customers' data. Audits of Subprocessors are satisfied by their own certifications and reports.
10. International transfers
We are based in the United States, and we and our Subprocessors process Customer Personal Data in the United States and the other locations shown on the Subprocessors page. Where Data Protection Laws require a transfer mechanism for Customer Personal Data leaving the European Economic Area, the United Kingdom, or Switzerland, the following are incorporated into this DPA:
- EU: the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914 ("SCCs"), Module Two (controller to processor) where you are a controller and Module Three (processor to processor) where you are a processor. Clause 7 (docking) applies; under Clause 9, Option 2 (general authorization) applies with the notice period in section 5; the optional wording in Clause 11 does not apply; under Clause 13, the supervisory authority is the one competent for you; Clauses 17 and 18 select the law and courts of Ireland. Annexes I and II of the SCCs are completed by Annexes I and II of this DPA, and Annex III by the Subprocessors page.
- UK: the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner, with Table 1 completed from this DPA, Table 2 by the SCC selections above, Table 3 by the Annexes, and either party may end it as described in Table 4.
- Switzerland: the SCCs as above, read so that references to the GDPR include the Swiss Federal Act on Data Protection, the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner where the transfer is governed by Swiss law, and "Member State" includes Switzerland for the purpose of data subjects bringing claims where they habitually reside.
If the SCCs conflict with this DPA or the Terms, the SCCs prevail. If a transfer mechanism is invalidated or replaced, we will work with you in good faith to adopt a lawful alternative.
11. US state privacy laws
Where Customer Personal Data is subject to the CCPA or a similar US state law, we act as your service provider or processor and will not: sell or share it, including for cross-context behavioral advertising; retain, use, or disclose it for any purpose other than the business purposes in the Terms and this DPA, or outside our direct business relationship with you; or combine it with personal information we receive from other sources, except as those laws permit. We will comply with the obligations those laws place on us, provide the same level of privacy protection they require, and tell you if we can no longer meet them. You may take reasonable and appropriate steps to stop and remediate unauthorized use of Customer Personal Data.
12. General terms
This DPA lasts as long as we process Customer Personal Data. If this DPA conflicts with the Terms on the processing of Customer Personal Data, this DPA prevails. Each party's liability under this DPA is subject to the limitations and exclusions in the Terms, except where Data Protection Laws or the SCCs do not allow that. We may update this DPA to reflect changes in law or the Service; we will not materially reduce its protections without notice, and a signed agreement with us controls over this online version. Questions:[email protected].
Annex I. Processing details
- Data exporter: Customer, as identified in its DocSlurp account. Contact: the organization's administrators.
- Data importer: 17th Street Labs, doing business as DocSlurp, United States. Contact: [email protected].
- Subject matter and nature: hosting, extracting, transcribing, embedding, indexing, searching, summarizing, and answering questions about Customer Content, and the related storage, transmission, and deletion.
- Purpose: providing, securing, and supporting the Service under the Terms.
- Duration and frequency: continuous, for the term of the Terms and the deletion period in section 8.
- Data subjects: Customer's users and any individuals whose personal data appears in Customer Content, as Customer determines.
- Categories of data: any personal data in the documents, media, prompts, and messages Customer submits, which may include names, contact details, identifiers, voices and images, and other content Customer chooses to upload.
- Special categories: none are required. If Customer chooses to submit them, the measures in Annex II apply, and the Terms' limits on regulated data still apply.
- Retention: until Customer deletes the content or project, or as section 8 describes.
- Subprocessors: as listed on the Subprocessors page, for the purposes shown there.
Annex II. Technical and organizational security measures
- Encryption: TLS for data in transit to and from the Service, with HTTP Strict Transport Security; storage encrypted at rest by our hosting and storage providers; AES-256-GCM application-level encryption for stored secrets such as connected-account tokens and signed file access.
- Tenant isolation: every request is scoped to an organization and project, and file access uses short-lived, signed, scoped tokens.
- Access control: hashed passwords, optional sign-in through GitHub, Google, or company SSO, scoped and revocable API keys, role-based organization membership, and production access limited to authorized personnel.
- Application security: a strict Content Security Policy, security headers, request rate limits and spend budgets, input validation, dependency updates, and security review of changes.
- Monitoring and logging: centralized logs, traces, and metrics for detecting errors, abuse, and security events, with limited retention.
- Resilience: regular database backups to separate storage, and restore procedures.
- Data minimization: AI providers receive only the portions of Customer Content a request needs; product analytics never captures page text, media, or typed input.
- Deletion: customer-initiated deletion of documents, projects, and accounts, with removal from active systems as section 8 describes.
- Subprocessor management: vendors are chosen for their security practices and bound by data protection terms.