A plain description of what DocketBridge stores and where. We don't claim any certification.
| Data | Where it lives |
|---|---|
| Matter content | DocketBridge is built as pass-through: it reads from your docketing system and writes to your calendar or billing system, without keeping a separate matter database. During the pilot, we confirm in writing where your data is stored, how long it is kept, and how calendar connection tokens are protected, before you upload anything. |
| Duplicate-protection keys | Short-lived hashed (SHA-256) keys in Redis, kept 30 days so the same entry is never posted twice. |
| Audit log | A log of each sync and each approval, acknowledgment and rejection, with the person's name. Patent and SSN-style numbers are redacted in logs. |
| Uploaded notices and exports | During the pilot, we confirm in writing where your data is stored, how long it is kept, and how calendar connection tokens are protected, before you upload anything. |
| Calendar / Clio connections | Connected through each provider's sign-in. During the pilot, we confirm in writing where your data is stored, how long it is kept, and how calendar connection tokens are protected, before you upload anything. |
| API keys | Stored hashed with bcrypt. |
DocketBridge can run in your firm's own private cloud, data center, or on your own computers.
If the duplicate-protection store is unavailable, syncing stops instead of risking double entries.
Syncs never delete calendar events on their own.
DocketBridge does not hold SOC 2, ISO or other certifications, and makes no compliance claims. Questions? Contact us.
Send us a docketing export. We'll run a Deadline Audit and walk you through the findings — free.