Security
Data Protection
How Docshark handles your data. Encryption, privacy-minimizing analytics, retention windows, and secrets handling.
Encryption
- In transit. Everything moves over TLS; there is no plaintext path to the service.
- At rest. Documents, field values, and records are stored encrypted.
- Secrets, webhook secrets are encrypted at rest and displayed exactly once, at creation. Lose one and you rotate it, it cannot be recovered by design.
Privacy-minimizing analytics
Viewer analytics are built to measure documents, not people:
- No raw IPs. Viewer IP addresses are stored only as SHA-256 hashes; the raw address is used at request time to derive a region, then discarded.
- Country-level location. Geo data is a country, not a coordinate.
- Hashed user agents. Device fingerprints come from the user agent's hash, not from tracking tech.
Retention
- Analytics roll off per plan. 14 / 90 / 180 / 365 days on Hobby / Starter / Team / Business. See exports and retention.
- Completed envelopes. Sealed PDFs, certificates, and audit evidence persist with the envelope record; they are your documents of record and remain downloadable.
- Deleted content. Deleting a document, room, or link removes it and its dependent data; the audit record of what happened to it is what trails are for.
Access inside Docshark
- Workspace members see your org's data under their permissions; viewers, signers, and room visitors see only what a link or invitation exposes. Never the workspace itself.
- Team library content is shared with your organization; personal library content is yours alone until you share it. See library.
Data requests
Signers and visitors whose data sits in your Docshark records can exercise their privacy rights through you (the data controller). The DSAR flow supports exporting or removing a person's data from your records. Handle requests through your workspace; Docshark processes on your instruction.