Last updated November 19, 2026

Data processing addendum

This data processing addendum ("DPA") is part of the terms of service between Parra, Inc. ("Parra") and the customer that subscribes to AI Drops for Business ("Customer"). It applies when Parra processes personal data on Customer's behalf that is subject to the GDPR, the UK GDPR, the Swiss FADP or US state privacy laws such as the CCPA (together, "Data Protection Law"). It takes effect when Customer accepts the terms. Email support@getaidrops.com for a countersigned copy.

1. Roles

Customer is the controller of the personal data it puts into the service ("Customer Personal Data"). Parra is its processor, and a service provider under the CCPA. Parra is a separate controller only for the account, billing and website data described in the privacy policy.

2. Subject matter and duration

Parra processes Customer Personal Data to provide AI Drops for Business: delivering summaries of public AI tool updates to the destinations Customer sets up, answering questions in Slack, running training courses, issuing app licenses, and billing and supporting the account. Processing lasts for the term of the subscription and until the data is deleted under section 10.

3. Nature and purpose

Collection, storage, organization, retrieval, transmission to the destinations Customer configures, and deletion, carried out automatically by the service and, for support, by Parra staff who need access.

4. Categories of data and data subjects

Data subjects are Customer's admins, members, invitees, seat holders, course participants, email digest recipients, and Slack users who @mention AI Drops or answer a training quiz in Slack.

  • Names, email addresses and profile pictures of admins, members and invitees, and their roles
  • Slack workspace, channel and user ids and names
  • Email addresses added for email delivery or app license seats
  • The text of questions sent to Ask AI Drops and Customer's saved team description
  • Delivery logs, audit logs of admin actions, course progress, quiz results and certificate names
  • IP addresses and browser details in request logs

The service does not need special categories of personal data, and Customer should not put any into it.

5. Instructions

Parra processes Customer Personal Data only on Customer's documented instructions. The terms, this DPA and Customer's settings in the dashboard are those instructions. Parra will not sell or share Customer Personal Data, use it to train AI models, or use it for any purpose other than providing the service, and tells Customer if it believes an instruction breaks Data Protection Law. If the law requires other processing, Parra tells Customer first unless the law forbids it.

6. Confidentiality

Everyone at Parra who can access Customer Personal Data is bound by a duty of confidentiality and has access only as far as their work requires.

7. Security

Parra keeps these technical and organizational measures in place, and may replace them with measures that protect the data at least as well:

  • All traffic to the dashboard, API and Slack app uses TLS.
  • Slack bot tokens and webhook secrets are encrypted with AES-256-GCM before storage. The key is held as a server secret, separate from the database.
  • API keys are stored only as hashes and shown once at creation.
  • There are no passwords to leak. Sign-in uses Slack, Google or single-use emailed links.
  • The Slack app requests the minimum scopes. It cannot read channel history, messages or files. The full list is on the security page.
  • Inside each account, owner, admin, billing and member roles limit who can change settings and billing. Business plans include an audit log of admin actions.
  • The database runs on Neon and the app on Cloudflare Workers, with the encryption at rest those providers apply.
  • Production access is limited to the Parra staff who run the service.

8. Subprocessors

Customer authorizes Parra to use the subprocessors on the subprocessors page. Parra binds each one to data protection terms at least as protective as this DPA and stays responsible for their work. Parra emails Customer at least 30 days before adding or replacing a subprocessor. Customer may object on reasonable data protection grounds within that period. Parra will then try to resolve the objection, and if it cannot, Customer may end the affected subscription and receive a refund of prepaid fees for the unused period.

9. Assistance

Parra will help Customer respond to data subject requests, mainly through the dashboard, where admins can view, change and delete their team's data. If Parra receives a request directly, it passes it to Customer and does not answer it unless Customer asks. Parra will also give reasonable help with data protection impact assessments and with consultations with supervisory authorities, using the information it has.

10. Personal data breaches

Parra notifies Customer without undue delay, and in any case within 72 hours, after becoming aware of a breach affecting Customer Personal Data. The notice describes what happened, the data and people affected, the likely consequences and the steps taken, and Parra adds details as it learns them.

11. Deletion and return

Admins can download an export of the team's data from Dashboard, Settings at any time, including members, invitations, the Slack connection, destinations, channel rules, the delivery log and the audit log. After the subscription ends, an owner can delete the team in Dashboard, Settings. Deletion is immediate and permanent. It removes the Slack connection and tokens, channels, rules, destinations, the delivery log, the audit log, invitations, seats and course enrollments. If Customer asks Parra to do this instead, Parra runs the same deletion. Personal accounts of individual users, with their course progress and certificates, are kept because a user can belong to more than one team, and are deleted when the user asks. Copies in database backups and logs expire on the providers' retention schedules, and billing records are kept as long as tax law requires.

12. Audits

Parra makes available the information needed to show compliance with this DPA, in the form of written answers to reasonable security questionnaires and documentation of its controls, no more than once a year unless a breach or a regulator requires more. Any on-site audit is limited to what Data Protection Law requires, needs 30 days notice, and is at Customer's cost.

13. International transfers

Parra and its subprocessors process data in the United States. For transfers of personal data from the EEA, the EU Standard Contractual Clauses (Commission Decision 2021/914, Module 2 for controller to processor, and Module 3 where Customer is itself a processor) are incorporated into this DPA, with the optional docking clause and option 2 of clause 9 (general authorization of subprocessors), and Irish law and courts for clause 17 and 18. For the UK, the UK International Data Transfer Addendum to the SCCs applies. For Switzerland, the SCCs apply with the FADP as the governing law for Swiss data. Sections 4, 7 and 8 provide the information for the SCC annexes.

14. Liability and order of precedence

The liability limits in the terms apply to this DPA. If this DPA conflicts with the terms, this DPA wins for matters of data protection. If the SCCs conflict with either, the SCCs win.

15. Governing law

This DPA is governed by the laws of the State of Delaware, USA, except where Data Protection Law or the SCCs require another law.