CMC regulatory writing software that runs entirely in your browser
Trust Center

The answers your QA and IT reviewers will ask for, in one place.

Where data goes, who we use, how CMCfy maps to 21 CFR Part 11 and EU GMP Annex 11, and the validation documents. Download it as one PDF for your supplier file.

For IT

What leaves your computer, and what never does

ItemWhere it is handledLeaves your computer?
Files you load (Excel, Word, PDF, scans)Read on your computerNever sent
Calculations, pass/fail, statisticsRun on your computerNever sent
Projects, versions, audit trail, lab notebookSaved in a folder your company picksNever sent
Word and PDF reportsWritten on your computerNever sent
CMCfy Writer text (only when you press it)You see and approve the exact text firstSent once to the writing service; no copy kept
Your login and subscriptionHeld by our sign-in and billing providersNo CMC data in them

Every tool page carries a Content Security Policy that blocks all other connections, and shows a live count of network requests. How IT can verify it in minutes.

Providers

The third parties that touch the service, and what each one sees

ProviderUsed forWhat it sees
CloudflareHosts cmcfy.com and app.cmcfy.comPage requests only. Tool pages send no data back.
Anthropic (Claude models)CMCfy Writer, only when a user presses itThe approved text of that one request. CMCfy keeps no copy; not used to train models.
Sign-in and billing providersAccounts and subscriptionsName, work email, company and plan. No CMC data.
Your own cloud account (Enterprise)CMCfy Writer through your Anthropic, AWS Bedrock, Azure, Google Vertex, OpenAI or xAI accountUnder your contract, or switch CMCfy Writer off.

For QA

How CMCfy maps to 21 CFR Part 11 and EU GMP Annex 11

RequirementWhat CMCfy providesWhat stays with you
11.10(a) ValidationAutomated IQ/OQ (21 scripted tests) plus supplier documents VAL-01 to VAL-08You run PQ for your intended use (VAL-10 template)
11.10(b) Accurate and complete copiesWord, PDF and CSV exports; versions read back exactly—
11.10(c) Protection of recordsRecords are plain files in your folder; each version is fingerprintedBackup and retention of that folder
11.10(d) Limiting accessNamed user on every audit-trail entry and signatureAccess to the project folder and computers
11.10(e) Audit trailChained, time-stamped (UTC) entries with old and new values, user and reason; edits outside CMCfy show as alteredReview the audit trail per your SOP
11.10(f)-(h) Operational and device checksRequired steps and blocking checks in each tool; release fingerprint checked by IQ-01—
11.10(i) TrainingA training guide and PDF for every moduleYour training records
11.10(k) System documentationVersioned releases with a manifest; our SOP-01 to SOP-04—
11.50 / 11.70 SignaturesPrinted name, date, time and meaning, bound to the content signed; a signed entry is lockedYour e-signature policy
Annex 11 §4, §11 Validation and periodic reviewEach release is versioned, so you qualify one version and know it will not change underneath youPeriodic review
Annex 11 §7 Data storageNo CMC data on our serversYour storage and backup

The full clause-by-clause assessment is document VAL-08 in the validation pack.

Documents

The validation pack

DocumentTitleOwner
VAL-01Supplier statement and validation summaryCMCfy
VAL-02User requirements specification (baseline)CMCfy, adopted by you
VAL-03Functional specificationCMCfy
VAL-04Risk assessmentCMCfy, reviewed by you
VAL-05 / 06IQ and OQ protocols (automated on the validation page)Run by you
VAL-07Traceability matrixCMCfy
VAL-0821 CFR Part 11 and EU GMP Annex 11 assessmentCMCfy and you
VAL-09 to 11Validation plan, PQ protocol and summary report templatesYou
SOP-01 to 04Our development and change control, defects, release approval and training proceduresCMCfy

The Word documents come with Team and above, or on request during an evaluation.

Change control

Fixed releases, and guidance kept current

Versioned releases

Each release has a date, a build fingerprint and a manifest of every page. The IQ checks the fingerprint, so you qualify one version and know it won't change underneath you.

Guidance kept current

We check every guideline CMCfy cites against the agencies’ own sites. When a new version comes into force, the tools, the review checklists and the training guides are updated within 30 days, and the change is listed on the update log. See the update log.

People sign

CMCfy drafts and flags. Your qualified people review, justify and sign every report.

Reporting a security issue

Write to sales@cmcfy.com (subject "Security"); see cmcfy.com/.well-known/security.txt.

Send this to your QA and IT reviewers

One PDF with everything on this page, ready for your supplier qualification file.

Ask CMCfyClose