Data processing addendum

The terms that apply to the information you keep about your clients in MurmurMill.

This Data Processing Addendum ("DPA") forms part of the agreement between CaskStack, LLC, doing business as MurmurMill, 101 Cooper Street, Santa Cruz, CA 95060, United States ("MurmurMill", "we", "us") and the organization that uses MurmurMill ("Customer", "you"), made up of our terms of service and this DPA (the "Agreement"). It applies where we process Personal Data on your behalf when we provide MurmurMill ("Customer Data"). If it conflicts with the terms about the processing of Personal Data, this DPA applies.

1. Definitions

"Applicable Data Protection Law" means the laws that apply to the processing of Customer Data, including, where they apply, the EU General Data Protection Regulation 2016/679 ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act as amended ("CCPA"). "Personal Data", "controller", "processor", "processing", "data subject" and "personal data breach" have the meanings given in those laws; "Service Provider" and "Contractor" have the CCPA meanings.

"Client Workspace" means the space in MurmurMill for one of your clients, with its posts, files, brand voice, plans, connected LinkedIn accounts and approval links. "Sub-processor" means a third party we engage to process Customer Data. "Standard Contractual Clauses" means the clauses adopted by European Commission Implementing Decision (EU) 2021/914, and "UK Addendum" means the International Data Transfer Addendum issued by the UK Information Commissioner.

2. Roles

2.1 You are the controller (or, if you process on behalf of your own clients, the processor) of Customer Data, and we are your processor (or sub-processor).

2.2 We are an independent controller of the personal data we process for our own purposes: your members' account details, sign-in and security records, billing records, the AI usage ledger, the list of addresses we no longer email, the staff audit log, and website visits. Our privacy policy applies to those.

2.3 You are responsible for having a lawful basis to put Customer Data into MurmurMill, for the authority to connect and publish to each LinkedIn account you connect, for the instructions you give, and for what you publish and send to your clients.

3. Details of the processing

The subject matter, duration, nature and purpose, types of Personal Data and categories of data subjects are in Annex 1.

4. Our obligations

4.1 Instructions. We process Customer Data only on your documented instructions, which are this DPA, the terms and your use of MurmurMill's features, including scheduling a post to LinkedIn and asking for AI drafts, unless the law requires otherwise (in which case we tell you first, unless the law forbids it). We will tell you if we think an instruction breaks Applicable Data Protection Law.

4.2 Confidentiality and staff access. People we authorise to process Customer Data are bound by confidentiality. Within MurmurMill, our staff work in a separate staff area that requires a second sign-in factor. It shows account details, such as names, email addresses, Client Workspace names, statuses and dates, but no post text, brand voice, files, approval comments or AI output. Staff see that content only in a support session. A support session is logged when it starts and ends, is started for a stated reason and a support ticket, lasts at most 60 minutes and is read-only. When one starts we email the organization's owners and admins, and it is listed on the organization's Team page, where an owner or admin can end it. We keep a log of staff actions and support sessions for 400 days. Separately, a limited number of named operators have access to the hosting and database tools used to run MurmurMill. We restrict that access to what is necessary to operate, secure and support the service and protect it with the hosting provider's sign-in controls. We do not use it to read Customer Data except to carry out your instructions or a request for help that needs it.

4.3 Security. We apply the technical and organisational measures in Annex 2 and keep them appropriate to the risk.

4.4 Sub-processors. You give general authorisation for the Sub-processors in Annex 3. We bind each to data protection terms no less protective than this DPA and remain responsible for them. We will add or replace a Sub-processor only after listing it on our sub-processor page and emailing the owners of every organization at least 30 days before it starts to process Customer Data. If you object on reasonable data protection grounds within that period we will work with you to resolve it; if we cannot, you may stop using MurmurMill by cancelling your subscription and asking us to delete your organization, which we do without waiting for the end of the period you paid for. Payments are not refunded, as the terms say.

4.5 Assistance. Taking into account the nature of the processing, we help you respond to data subject requests (your members can delete posts and disconnect LinkedIn accounts themselves, and we carry out other requests you send to privacy@murmurmill.com), and help you meet your obligations about security, breach notification, impact assessments and consulting regulators, to the extent they relate to our processing. We may charge reasonable costs for assistance that goes beyond the features of MurmurMill. If a data subject contacts us about Customer Data, we pass the request to you and do not answer it ourselves unless the law requires.

4.6 Personal data breach. We notify you without undue delay after we become aware of a personal data breach affecting Customer Data, by email to your organization's owners, with the information we have about what happened, the likely consequences and what we are doing; we add detail as we learn it.

4.7 Audits. We give you the information needed to show our compliance with this DPA and allow audits by you or an auditor you appoint, no more than once a year (unless a regulator or a breach requires more), on 30 days' written notice, during business hours, subject to confidentiality and without access to other customers' data.

5. Your obligations

You will give only lawful instructions, make sure you have the rights, authority and notices needed for Customer Data and for each LinkedIn account you connect, keep your members' credentials secure, and assess whether MurmurMill's security fits the data you store. You must not put into MurmurMill data it is not designed for: payment card numbers, government identity numbers, health information and other special categories of personal data, or children's data.

6. Return and deletion

6.1 Your copy. Published posts stay on LinkedIn, in the accounts they were published from. MurmurMill does not yet offer an export of a Client Workspace; if you need a copy of Customer Data, ask at privacy@murmurmill.com and we will provide it.

6.2 Deletion. Your members can delete a post that is a draft, scheduled or failed, with its uploaded files, and can disconnect a LinkedIn account, which deletes its stored tokens. To have your whole organization and all Customer Data in it deleted, email privacy@murmurmill.com: we delete it within one month and confirm in writing what we deleted. Copies in our database backups are overwritten within 7 days after that. Records the law requires us to keep, and the staff audit log (400 days), are not Customer Data and are handled under our privacy policy.

6.3 Ending the Agreement. When a trial ends without a plan or a subscription ends, your organization becomes read-only and Customer Data stays readable to your members. If it is not paid, it is deleted 60 days later, as the privacy policy describes, unless you ask us to delete it sooner.

7. International transfers

7.1 We process Customer Data in the United States. Where Applicable Data Protection Law restricts a transfer of Personal Data to us, the Standard Contractual Clauses (Module Two, controller to processor, and Module Three, processor to processor, where you act as a processor) apply and are incorporated by reference, with the details in Annex 4, together with the UK Addendum for transfers from the United Kingdom and the Swiss adjustments for transfers from Switzerland.

7.2 For transfers to Sub-processors outside the EEA, UK and Switzerland we rely on the safeguards in Annex 3.

7.3 When you schedule a post, MurmurMill sends it to LinkedIn on your instruction, to be published from the account you connected. LinkedIn receives it as a controller in its own right and is not our Sub-processor.

8. California

To the extent the CCPA applies, we are your Service Provider (Contractor). We process Customer Data only for the business purposes in Annex 1 and as you instruct; we do not sell or share it, and we do not retain, use or disclose it outside our direct business relationship with you or for any purpose other than those business purposes; we do not combine it with other data except as the CCPA allows; we will tell you if we can no longer meet our CCPA obligations; and you may take reasonable steps to stop and remedy unauthorised use. We certify that we understand and will comply with these restrictions.

9. Liability and general

Each party's liability under this DPA is subject to the limits in the terms, but nothing in this DPA limits liability to data subjects that the Standard Contractual Clauses or Applicable Data Protection Law do not allow to be limited. This DPA is governed by the law that governs the terms, except where the Standard Contractual Clauses or Applicable Data Protection Law require otherwise. We may update this DPA to keep up with the law or the service; material changes are announced to your organization's owners by email at least 30 days before they apply.

Annex 1: Details of the processing

  • Subject matter and nature. Storing, organising, displaying and deleting Customer Data; publishing posts to LinkedIn at the times you schedule; writing drafts, rewrites, hashtags, alt text, brand voices and plans with AI when you ask for them or turn a weekly plan on; sending your clients the posts you ask them to review and recording their decisions; and security, support and backups.
  • Purpose (business purposes). To provide MurmurMill to you, under the Agreement and your instructions.
  • Duration. For as long as your organization exists, plus the deletion periods in section 6.
  • Types of Personal Data. What you or your members put in or connect: clients' names; the LinkedIn member ID, display name and tokens of each connected account; the text of posts and anything they mention; uploaded images and documents and their alt text; link addresses and the titles, descriptions and preview images of linked pages; brand voice profiles (who the client is, their audience, offer and topics); the sample posts, answers and website text used to draft a brand voice, for the length of that request; plan themes and angles; clients' email addresses entered for approval links; and clients' decisions and comments on the approval page, with the IP address and browser of each request.
  • Special categories. Not intended. See section 5.
  • Categories of data subjects. Your clients, including the people whose LinkedIn accounts you manage; people your clients' posts, files and brand voice mention; and your own members.
  • Frequency. Continuous, for the term.

Annex 2: Technical and organisational measures

  • Access control and separation. Every organization's data is kept separate from every other's in the application, and the separation is covered by automated tests. Members reach a Client Workspace only through their organization: owners and admins reach every Client Workspace in it, and members only those they are assigned to. The one exception is a support session, described below.
  • Authentication. Passwords are hashed; sign-in attempts are rate limited; the session cookie is secure and HTTP-only, and session data is encrypted.
  • Staff access. Staff use a separate staff area that requires a second factor, an authenticator-app code that is checked again every 12 hours. No staff account has a standing view of Customer Data content in the application.
  • Support sessions. A staff member can see Customer Data content only in a support session, which needs a reason from a fixed list and a ticket reference, lasts at most 60 minutes, and is one at a time per staff member. It is read-only: the database refuses every write that a customer page attempts, and AI features are off. The organization's owners and admins are emailed when it starts, it is listed on the Team page, and they can end it at any time. It also ends at expiry, when the staff member signs out, and when their staff access is removed.
  • Staff audit log. Staff actions and support sessions are recorded with who, when, the organization, the reason, the ticket reference and the staff member's IP address and browser, never with Customer Data content. A support session is logged when it starts and ends, not page by page. Entries cannot be edited, and they are deleted after 400 days.
  • Encryption. Encrypted connections (TLS) for all access; LinkedIn tokens, session data and approval-link secrets are encrypted at rest in the application.
  • Approval links. Each link has its own secret, which is stored encrypted, looked up by a hash, expires, and can be withdrawn at any time.
  • Files. Uploaded files are stored privately and served only to signed-in members with access to the Client Workspace, and to staff in a support session.
  • Secrets handling. Query strings, approval-link secrets, passwords, tokens, client comments and authorization headers are removed before data is sent to monitoring; pages fetched for link previews and brand voices cannot reach private or reserved network addresses.
  • Availability and backups. Managed database with backups kept for 7 days; a health check reports whether the scheduler and the queue workers are running; automated tests, a static analysis check and a style check run before changes are merged.
  • Email safeguards. Bounce and complaint suppression, so an address that bounced or complained is not emailed again unless you ask us to remove it after fixing the mailbox.
  • Incident response. Errors are monitored, and breaches are handled under section 4.6.

Annex 3: Sub-processors

As listed on our sub-processor page at the date of this DPA:

Sub-processor Function Location Transfer safeguard
Laravel Holdings Inc. (Laravel Cloud)Application, database and backupsUnited States (US East, Ohio)The provider's data processing terms
Laravel Holdings Inc. (Laravel Object Storage on Cloudflare R2)Private storage of uploaded files and link thumbnailsChosen automatically by the provider; not limited to one regionThe provider's data processing terms
Laravel Holdings Inc. (Laravel Nightwatch)Application monitoringUnited States (US East, Ohio)The provider's data processing terms
Cloudflare, Inc.Network protection and deliveryGlobalThe provider's data processing terms
Amazon Web Services, Inc. (SES, SNS)Email delivery and delivery notificationsUnited States (US East, Ohio)The provider's data processing terms
Anthropic, PBC (Claude API)AI draftingUnited States, and other countries where it or its providers operateStandard contractual clauses in the provider's data processing terms

Annex 4: Standard Contractual Clauses details

  • Parties. Data exporter: the Customer. Data importer: CaskStack, LLC.
  • Module. Module Two (controller to processor); Module Three (processor to processor) where the Customer is a processor.
  • Clause 7 (docking). Included. Clause 9(a) (sub-processors). Option 2, general written authorisation, 30 days' notice. Clause 11(a). The optional independent dispute resolution body is not used. Clause 17. The law of Ireland. Clause 18. The courts of Ireland.
  • Annexes I to III. Annex 1 above for Annex I; Annex 2 above for Annex II; Annex 3 above for Annex III. Competent supervisory authority: the supervisory authority of the exporter's Member State or, where there is none, the Irish Data Protection Commission.
  • UK Addendum. Tables 1 to 3 are completed by the information above; Table 4: neither party may end the Addendum except as it provides.
  • Swiss transfers. References to the GDPR include the Swiss FADP; the Swiss Federal Data Protection and Information Commissioner is the competent authority for those transfers.