Secure file sharing with built-in compliance

Don't Let The Wrong Data Leave Your Firm

Sidian DataGuard is secure file sharing that checks every file on the way out. The same checks your most careful reviewer would run, without slowing anyone down.

Starting at $39/month

Avery-intake.pdfReviewing…

Claimant reports the fall at 6:40pm.

Our exposure is worse than the client believes.

SSN 412-55-0190

To: M. Kessler, opposing counsel

ABA 1.6
GLBA
Recipient policyMatched
Redactions2 proposed
Client transfer ruleChecked
Attorney review
Waiting for checks

Partners & affiliations

Pre-flight

Your best attorney's check,run on every share.

Before a file leaves, DataGuard runs the firm's checklist against every page of it. The standard checks ship with the product. The rest are the ones your people already run from memory.

Drive
Microsoft
Clio

Demand_Letter_4471.pdf · 912 pages, read where it already lives

01

File arrives

It comes from where it already lives.

Clio, SharePoint, OneDrive, Drive, Outlook. DataGuard reads it in place. No upload, and no second copy kept in DataGuard.

02

Pre-flight runs

Your firm's checklist, run against every page.

Not keyword matching. It catches the account number on page 12 and the sentence on page 630 that names a minor in plain English, and it runs the checks your firm wrote alongside the ones we ship.

03

Exceptions only

Nine checks pass quietly. Two need a person.

Nobody reviews what cleared. The queue holds only what the checklist could not decide on its own, each with the rule and the check that caught it.

04

Attorney clears

Two decisions, not a 912-page read.

Keep or remove, with the governing rule attached to each one. Removals are burned into the file, not a black box a copy and paste brings back.

05

Cleared to send

The file goes. Control of it does not.

Every check that ran, who wrote it, and who cleared it travel with the file. You can see whether it has been opened, and revoking access stops the link from opening.

One file, every destination

One file.A different document for each person who gets it.

A file going to opposing counsel has privileged passages held back. An AI tool never sees a real value at all. DataGuard reads who the file is going to and applies the rule that governs them. Automatic on every send, and the original never changes.

One field, five destinations

SSN on Avery-intake.pdf

  • Your firm

    The original

    412-55-0190

    Entitled to it

  • M. Kessler

    Opposing counsel

    removed

    Not entitled to it

  • D. Ruiz

    Paralegal

    ••• 0190

    Last four only

  • Case team

    Working this case

    412-55-0190

    Nothing removed

  • ChatGPT

    AI tool

    306-71-4488

    Stand-in values

Avery-intake.pdf1 file
Your firm
M. Kessler
D. Ruiz
Case team
ChatGPT
ToChatGPTAI toolStand-in values

An AI tool. The real values never left.

Name
Riley ChenName swapped for a stand-in, the real value was not sent
SSN
306-71-4488SSN swapped for a stand-in, the real value was not sent
Medical ID
44-9317Medical ID swapped for a stand-in, the real value was not sent
Account
5514-0863Account swapped for a stand-in, the real value was not sent

Claimant reports the fall at 6:40pm.

Privileged sentence heldPrivileged
Avery-intake.pdf1 file
ToYour firmThe original

The file as it sits in your system.

Name
Jordan Avery
SSN
412-55-0190
Medical ID
88-4102
Account
4829-1145

Claimant reports the fall at 6:40pm.

Our exposure is worse than the client believes.

Which rule applies

Decided by who is on the other end, not by the file alone.

The same clinical page is ordinary detail to the case team and a HIPAA disclosure to an outside expert. Send it to a vendor instead and GLBA governs the account number in it. CPRA and PIPEDA come in on the recipients they cover. Your firm's own policy runs in the same pass, beside the rules that ship.

Where the rules come from

Nobody redacts the same file five times by hand.

DataGuard applies the rule for each destination, records which one it applied, and shows what that recipient actually received. Rules are configuration, not code: the regimes that ship are ours to keep current, with the authority cited beside each one, and every version is kept so you can see which one cleared a send. Anything it holds back waits for a partner to clear it.

Off your desk

912 pages. Two things that mattered.

912
pages read
240 arrived as scans
Avery-production-vol3.pdfVol. 3

Intake form lists SSN SSNSSN removed under GLBA and DOB 04/1979.

Adjuster confirmed the reserve was set the same week.

Work productWork product removed under ABA 1.6

SSNp. 412 · GLBA
Work productp. 630 · ABA 1.6

+38 more removed

The productionp. 1 to 912
SSN found on page 412Work product found on page 630

2 a person would have to find. Marked where they sit in the file.

No manual read

The 912-page pass. Every version, every attachment, every export, including the scans.

No rule lookup

The rule for each field. An account number is GLBA. A health identifier is HIPAA. A Québec file is Law 25.

No redaction check

The removal itself. The text leaves the file. Not a black box that a copy and paste brings back.

A person still approves every send. They just don't do the 912-page read.

HIPAAPHIPAGLBACCPAGDPRLaw 25PIPEDA

Everything leaves by one gate.

We connect to what your firm already runs. Nothing moves, nothing migrates.

  • Microsoft 365
  • Clio
  • SharePoint
  • iManage
  • OneDrive
  • Filevine
  • Outlook
  • NetDocuments
  • Google Drive
  • MyCase
  • Gmail
  • Egnyte
  • Teams
  • PracticePanther
  • Box
  • Rocket Matter
  • Dropbox
  • CosmoLex
  • Local upload
  • Network share
  • Relativity
  • Worldox
  • Smokeball
  • Litify
  • Actionstep
  • CASEpeer
  • Neos
  • Tabs3
  • Centerbase

Pre-flight

11 checks · 2 need a person

One gate, whatever it started in.

Your firm writes its rules once, here, instead of setting them up again inside every platform.

  • Passed:CPRAClear
  • Needs a person:HIPAASSN found, page 12
  • Could not run:Tracked changesCan't open attachment

Governed share

Secure link

What goes out

3 removed. The recipient sees a summary of what was taken out and why.

Who has it

  • R. Vance, opposing counselOpened 4:31pm
  • T. Alvarez, paralegalNot opened
Revoke accessRevoking stops the link from opening.

Zero-copy by design.

Your files stay where they already live. DataGuard sits between your people and your data, stores nothing of its own, and never becomes a second place your documents live. Nothing goes to outside services. No OpenAI, no Anthropic.

Courts forgive an honest mistake only if you can show you took reasonable steps. The record is your defensibility.

FAQ

Purview blocks the email and tells you afterwards what was wrong. DataGuard removes the parts that shouldn't go out and lets the send complete. Your team isn't held up. The recipient sees only what was meant to go.

Try it. Or let us show you.

Run DataGuard on a real document and watch a redaction and its record appear. Or book time with our team to see it on your own files.

No setup. See a redaction and its record in under a minute.

Pricing and deployment detail live on the pricing page.