Anonymize Section 16 Form 4 filings for insider-trading compliance review – CCPA/HIPAA-compliant de-identification per 15 USC §78p

Section 16 of the Exchange Act, codified at 15 USC §78p, requires officers, directors, and ten-percent shareholders to disclose beneficial ownership changes on Form 4 within two business days. These filings pair named insiders with exact transaction dates, security types, and share counts. anonym.legal pseudonymizes insider identities for compliance-monitoring studies and audit-committee reviews without altering the transactional record.

When this applies

Apply this workflow when Form 4 filings are aggregated for compliance-pattern analysis, shared with outside counsel during insider-trading investigations, or reviewed by audit committees assessing Section 16 compliance under Reg S-K §229.405.

  1. Upload Form 4 filings — individually or as a batch export from EDGAR — to anonym.legal in XML, PDF, or structured CSV format.
  2. The engine identifies the reporting person's name, CIK number, and relationship to the issuer on the cover page of each form.
  3. Each reporting person is assigned a consistent pseudonym across all Form 4s in the dataset, preserving time-series linkage of an insider's transaction history.
  4. Transaction data — security title, transaction date, code, price, and resulting beneficial ownership — is retained as structural content for pattern analysis.
  5. Issuer identifying data is optionally pseudonymized if multi-issuer datasets are being analyzed without revealing which company is under review.
  6. The reversible mapping is stored encrypted with US data residency.
  7. The pseudonymized Form 4 dataset is exported for compliance-team or counsel review.

What you provide

  • Form 4 XML exports from EDGAR or PDF copies of individual filings
  • Scope of review: specific reporting persons, a defined time range, or all Section 16 filers for an issuer
  • Instruction on whether issuer identity should also be pseudonymized

Limitations & cautions

  • anonym.legal does not assess whether Form 4 filings are timely or whether the disclosed transactions trigger short-swing profit liability under §78p(b); those determinations require securities counsel.
  • EDGAR-sourced Form 4 XML may contain non-standard formatting from third-party filing agents that requires pre-processing before upload.
  • Pseudonymizing the reporting person's CIK does not eliminate the risk of re-identification from transaction-specific details in very thin insider populations.
  • The tool does not prepare, amend, or file Form 4 or Form 5 with the SEC.

FAQ

Can the workflow track a single insider's transaction history across multiple Form 4s?

Yes. By assigning a consistent pseudonym across all forms for the same reporting person, the workflow preserves the time-series linkage of an insider's trades without disclosing the individual's name.

Is derivative-security transaction data preserved after pseudonymization?

Yes. Table II derivative-security transaction data — option grant dates, exercise prices, expiration dates, and resulting ownership — is retained as structural content; only the named insider's identity is pseudonymized.

Can this workflow support a post-transaction compliance audit of Section 16 timeliness?

Yes. Pseudonymizing the Form 4 dataset while retaining transaction dates and filing dates allows compliance teams to run timeliness analyses for the full insider population without holding individually identified transaction data in non-secured review environments.

Securities & Corporate Disclosure

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.