MatterSeal data processing agreement
This agreement is part of the MatterSeal hosted terms of service. It applies whenever Pangur Labs hosts MatterSeal for your firm.
Between Pangur Labs LLC, a Washington limited liability company ("Pangur Labs", "we"), and the law firm or lawyer that subscribes to hosted MatterSeal ("Firm", "you").
1. Roles
You decide what information goes into MatterSeal and why. We process it only to provide MatterSeal to you. Under US state privacy laws, you are the business (or controller) and we are your service provider (or processor). In professional-responsibility terms, we are a nonlawyer service provider your firm uses, and this agreement records the assurances your rules expect from one.
"Firm Data" means everything your people, your Google account or your engine put into hosted MatterSeal: matter records, the mail, events and documents it works with, notes, drafts, contacts, and the audit log. Your clients' confidential information is Firm Data.
2. Where Firm Data is kept
- In your Google account. Your mail stays in Gmail, events in Google Calendar and documents in Google Drive. MatterSeal reads and organizes them through the MatterSeal Google app you sign in with.
- In a Google Cloud project we run for your firm alone. The engine, its matter records, its working copies and its backups are in a Google Cloud project we set up for your firm and no one else, in the United States (Google's us-west1 region, Oregon). We pay Google for it. No other firm's data is in it.
We won't move Firm Data outside the United States without your written consent.
3. What we do with Firm Data
We process Firm Data only:
- to provide, secure, support and update MatterSeal for you, as our terms and documentation describe;
- as you instruct through MatterSeal's settings (for example, turning mail sorting or AI on or off); and
- as the law requires, after telling you if the law allows.
We don't sell Firm Data, share it for advertising, use it to train AI models, or combine it with other firms' data. We may count things (seats, sorted emails, storage used) to bill you and run the service; those counts contain no content.
4. Who at Pangur Labs can reach your project
- Automated systems set up, update, back up and watch over your project. They work on Firm Data without a person reading it.
- Support access. When your firm wants our help, your account owner or an admin turns on Pangur Labs access in Settings > System status, for 24 or 72 hours, and can end it early with End now. It lets us view your engine's service logs, its running state, its scheduled and background work, and its monitoring. It never opens your database, your documents or your mail. It ends by itself when the time runs out. Each grant and each end is written to your firm's audit log, and the app shows who gave access and until when.
- Firm Data itself (your matter records, documents and mail) is opened by a person at Pangur Labs only when your firm asks us to for a specific problem, to stop an active security threat to your firm or the service, or when the law requires it. We tell you each time, unless the law forbids it.
- What we can technically do. We run the Google Cloud organization your project lives in, so our administrators could give themselves access to your project outside these steps, and our setup service owns your project so it can build and update it. We use that power only as this section allows. Google's Cloud Audit Logs record any such access, and we'll show you those records for your project on request.
- Everyone at Pangur Labs who can reach the service is bound by confidentiality, signs in with two-step verification, and gets only the access their work needs.
5. Subprocessors
You authorize the subprocessors on our subprocessor list. We hold each to written data-protection terms at least as protective as this agreement, and we're responsible for their work.
We'll email your account owner at least 30 days before adding or replacing a subprocessor. If you object on reasonable data-protection grounds, we'll talk it through. If we can't resolve it, you may end your subscription and we'll refund prepaid fees for the rest of the term.
Services you choose under your own account, such as your AI provider on your own key or your own Zoom app, aren't our subprocessors. Your agreement with them governs them. The hosted engine sends them data only when you turn those features on.
6. Security
We keep the safeguards in Annex B and keep them current. We may change them, but we won't make them less protective overall.
7. Security incidents
If we confirm that Firm Data was accessed, disclosed, changed or lost without authorization, we'll tell your account owner without undue delay and within 72 hours of confirming it. We'll say what we know (what happened, which data, what we're doing) and keep you updated. We'll help you meet your own duties to notify clients, regulators or others. We won't notify your clients ourselves unless you ask or the law requires it.
8. Requests from others
If anyone (a court, an agency, an opposing party) asks us for Firm Data, we'll send them to you and tell you promptly, unless the law forbids it. If we're compelled to answer, we'll give only what is legally required and ask for confidential treatment, including any privilege claim you ask us to raise. We'll publish a count of such requests once a year.
9. Helping you
We'll help you, at no extra cost, to:
- answer your clients' or individuals' requests about their information (MatterSeal lets you find, export and delete it);
- answer reasonable questions about how MatterSeal handles data, so you can meet your duties of competence, confidentiality and supervision and tell clients what your rules require; and
- deal with a security incident.
10. Checking on us
We'll answer reasonable written security questionnaires once a year, and after any incident. When we have an independent security report (such as SOC 2), we'll share it under confidentiality. If the law or your regulator requires more, we'll work with you on a reasonable review.
11. When the subscription ends
- Take it with you. For 30 days after your subscription ends, you can export everything (Settings > Backups) or move the Google Cloud project into your firm's own Google Cloud organization, so the same engine keeps running under your own billing as self-hosted MatterSeal. Once it has moved, we remove every permission we held on it.
- Then we delete it. After those 30 days, or sooner if you ask in writing, we delete the project. We destroy its secrets and backup keys first, so nothing left behind can be read, and send you a written confirmation. Google then purges the deleted project within about 30 days. If your firm locked its backups, Google keeps the project until those backups reach the end of the period you set (90 days by default), but with their keys destroyed they can't be opened.
- Your mail, events and documents in your own Google account stay there. Remove the MatterSeal Google app from your Google account permissions to end its access.
- We keep billing records and our correspondence with you as section 4 of our privacy policy describes. We confirm deletion in writing on request.
12. Health information
If your firm turns on health information mode, MatterSeal sends no mail to the email classifier, and matters marked as holding health information get no AI unless your firm confirms it has a business associate agreement with its AI service.
13. General
This agreement lasts as long as we process Firm Data for you. If it conflicts with the hosted terms, this agreement controls on data protection. The hosted terms' limitation of liability applies to this agreement. Washington law governs it.
Annex A: The processing
| Purpose | Providing hosted MatterSeal: organizing a law practice's email, calendar, documents and deadlines into matters |
| Whose information | The firm's people, clients, opposing parties and counsel, courts, witnesses, and anyone else in the firm's mail, calendar, documents and matter records |
| What information | Names, contact details, email and attachments, calendar events, documents and filings, matter details, notes, deadlines, and whatever else the firm puts in. It can include confidential, privileged and sensitive information, including health information. |
| How long | The subscription, plus the 30 days in section 11, plus backup expiry |
| Where | United States |
Annex B: Safeguards
- One project per firm. Each hosted firm has its own Google Cloud project, its own database, its own storage and its own keys. No firm's data is in another firm's project.
- Encryption. All connections use TLS. Google encrypts everything at rest. Keys and sign-in grants your firm adds are sealed with a key held in your project. Backups are encrypted and signed with keys in your project.
- Least access. The engine runs as its own service account with only the permissions it needs. Your account owner is not given control of the project, only what Settings > Firm setup needs (adding the recovery kit and locking backups). Pangur Labs support access is read-only, time-limited and set out in section 4.
- Sign-in. People at your firm sign in with their Google accounts. Pangur Labs staff accounts use two-step verification.
- Backups. Hourly backups go to a storage bucket in your project with a retention period, which your firm can lock so nobody, including us, can delete a backup early.
- Logs. The engine keeps an audit log of who did what in your firm. Service logs record health and errors.
- Updates. Engine updates come only from Pangur Labs' release feed, and the updater rolls an update back if it fails.
- People. Everyone at Pangur Labs with access is bound by confidentiality and follows section 4.