ProWriter
Security & compliance

Built for regulated work.

ProWriter encrypts your data, keeps each project's reference library separate, never trains models on your content, and logs every change in an audit trail. This page summarizes how, so your IT, QA and compliance teams can review it quickly.

HIPAA21 CFR Part 11

Data protection

AreaWhat we do
Encryption at restAES-256
Encryption in transitTLS 1.3
Secure messagingEnd-to-end encrypted channels and direct messages, with keys held on your device. We cannot read your channels.
Project isolationYour reference library is scoped to your project and never shared with other users.
Model trainingWe never use your inputs or outputs to train models.
Data sharingWe do not sell, rent or share user-uploaded data with third parties.
AI chat recordsDeleted when you navigate away from a document.
Security testingRegular third-party security tests.

Compliance and audit

HIPAA & BAA

HIPAA-grade infrastructure. A Business Associate Agreement (BAA) is available on the Enterprise plan.

21 CFR Part 11

An audit trail is built into every document and notebook entry. Every change is logged in an immutable record, and your QA lead can export it on demand.

Grounded drafting

Generated text draws only on documents you upload, and each claim traces to a source in your library.

Your responsibility

Part 11 compliance depends on the software and on how your organization validates and uses it.

Export

Documents export to Word (.docx) and PDF.

Data residency

US regions for Enterprise. Custom retention policies and export for eDiscovery.

Access and enterprise controls

  • Role-based access for every project and document
  • Locked sections within shared documents
  • Shared libraries and team review with a full audit trail
  • Enterprise plan: SSO, SCIM, BAA and dedicated support