Trust and security

Built for regulated work.

What happens to your study files, how every change is recorded, and where aCRF Gen stands on 21 CFR Part 11, validation and the FDA's PDF rules — including what isn't in place yet.

Your files

Study metadata, briefly held.

aCRF Gen works on the blank CRF and the EDC study design — form and field definitions. It never needs subject-level clinical data.

What we receiveBlank CRF (PDF), EDC export (CDISC ODM-XML or Medidata Rave ALS), optional SDTM specs, your chat messages
Where it's processedGoogle Cloud, Mumbai (asia-south1); sign-in on Cloudflare
How long we keep itFiles, the generated aCRF and its audit trail are deleted automatically after 7 days
Who can see itOnly your account: sign-in required, access granted per account, and every request is signed for one user's single job
In transit and at restTLS-encrypted in transit; encrypted at rest by Google Cloud and Cloudflare
The AI model

An enterprise model, not a chatbot.

Mappings are proposed by Gemini, called through our own Google Cloud project on Vertex AI. Google's terms for Vertex AI: "Google won't use your data to train or fine-tune any AI/ML models without your prior permission or instruction." By default Gemini caches requests in memory only (not stored), for up to 24 hours. Google's data terms ↗

Vajrra doesn't train any model on your files. Every proposal is checked against SDTMIG variable naming before it is used, and shown to your reviewer with its source.

On the record

Every change, who and when.

Complete audit trail

Uploads, runs, every chat message and every annotation change, removal, addition or move — with the user, the UTC time, and the value before and after.

Tamper-evident

Each entry carries a hash of the one before it. Alter or delete any line and the exported trail says where the chain breaks.

Yours to keep

Download the audit trail as CSV with the aCRF, its review workbook and its FDA PDF check, and file them in your own system.

Submission-ready output

The FDA's PDF rules, checked every time.

Each aCRF ships with a report against the FDA's Portable Document Format Specifications v4.1 for eCTD: PDF version, no security or JavaScript, no PDF annotations, fully embedded fonts, bookmarks with inherit zoom, opening on the bookmarks panel, and Fast Web View. Anything in your own blank CRF that needs attention — such as subset fonts — is called out for you.

21 CFR Part 11 and validation

Ready to fit your validated process.

Part 11 compliance comes from software and your procedures together. Here is what aCRF Gen provides today.

AreaStatusDetail
Audit trail §11.10(e)In placeSecure, computer-generated, time-stamped; previous values kept; tamper-evident
Access control §11.10(d)In placeNamed accounts with verified email, access granted by us, per-job authorisation
Copies of records §11.10(b)In placePDF, Excel workbook, FDA check and audit trail, all downloadable
Validation §11.10(a)Partly21 requirements traced to automated tests, an OQ report for every release; PQ on your own CRFs
Record retention §11.10(c)Partly7 days with us; you keep the downloaded records
Electronic signatures §11.50–300Not yetaCRF Gen produces a draft; sign the final aCRF in your own Part 11 system

Our Part 11 readiness matrix, validation plan, data-handling statement and latest OQ report are available on request.

Not there yet

What we don't claim.

  • No SOC 2 or ISO 27001 certification yet.
  • No electronic signatures in the product yet.
  • Zero data retention with the AI provider (switching off its in-memory cache and abuse-monitoring logging) can be configured on request.
  • The AI model runs on Google's global endpoint; a regional endpoint for data residency is on our roadmap.
Your QA team's questions

Ask for the governance pack.

Data handling, Part 11 readiness, validation plan and the latest OQ report — sent to your QA or IT security team.