Free AI-Assisted

Sample Pseudonymization Tool

Convert sample names into short pseudonym IDs with encrypted local vault storage, CSV de-identification, and IRB audit logs. Built-in AI agent assistant support.

Need help with bioinfo analysis? See our bioinformatics services.

Key facts

Key facts about Sample Pseudonymization Tool
FactValue
Primary functionClient-side sample pseudonymization & CSV de-identification
ID formats6 or 8 Crockford Base32 chars; optional prefix; optional study salt
De-identification modesReversible (AES-256-GCM local vault) or Irreversible (HMAC-SHA256 hash)
Encryption specAES-256-GCM, PBKDF2 key derivation (100k iterations), browser localStorage
Data privacyZero server upload; 100% local browser execution verified in DevTools
Metadata handlingCSV column mapper preserves all non-identifier metadata columns intact
Storage & Export500 entry vault limit; de-identified CSV, master key CSV, .vault backup, IRB audit log
AI assistantBuilt-in; helps configure ID schema, parse CSV columns, and interpret audit logs

What it does

Labs often store subject and sample keys in unencrypted spreadsheets, risking compliance breaches if shared. Hand-rolled ID schemes cause cross-project collisions, and hospital pseudonymization tools require IT infrastructure that academic labs lack.

Sample ID Vault removes regulatory risks by pseudonymizing sample names locally inside your browser. On the Generate tab, paste names or upload a CSV. The interactive column mapper isolates identifier columns while preserving clinical and experimental metadata. You choose 6- or 8-character Crockford Base32 IDs, an optional prefix like PAT-, and an optional study salt for multi-center synchronization. Reversible mode encrypts mappings with AES-256-GCM (PBKDF2, 100k iterations), while irreversible mode applies a one-way HMAC-SHA256 hash.

The Lookup tab decrypts individual IDs or batch CSVs using your session password. The Vault tab features a searchable audit table, row deletion, password-encrypted .vault backup files, and one-click IRB compliance audit logs that verify execution metadata without exposing raw sample names.

Why researchers use it

  • Eliminate unencrypted master key spreadsheets vulnerable to accidental data leaks
  • Protect patient privacy using zero-upload local AES-256 browser encryption
  • Synchronize deterministic pseudonyms across multi-site teams using shared study salts
  • Retain non-identifier clinical metadata columns when exporting de-identified CSV files
  • Generate audit-ready IRB compliance logs with cryptographic verification checksums
  • Restore encrypted vault backups across devices without IT department assistance

Best for

  • Preparing patient cohort datasets for external CRO or core facility analysis
  • Separating participant identifiers from genomic or phenotypic data before repository submission
  • Managing biobank sample aliquots with short, human-readable, unambiguous alphanumeric IDs
  • Collaborating on multi-center clinical studies that require identical pseudonyms without central servers
  • Generating password-encrypted local key archives for IRB protocol compliance reviews

When to use this vs alternatives

Choose Sample ID Vault when you need lightweight, local sample pseudonymization with CSV metadata retention and IRB audit exports without LIMS or hospital IT. If your lab requires longitudinal clinical data capture, multi-user role-based permissions, or integrated electronic data capture, REDCap or OpenSpecimen is a better fit. For formatting clean gene tables before de-identification, use Safe Table Bio.

What makes it different

Unlike unprotected spreadsheets that risk HIPAA or GDPR violations or complex platforms like REDCap that demand server hosting and IT administration, Sample ID Vault delivers instant, zero-trust browser pseudonymization with built-in AES-256 encryption, CSV column preservation, and cryptographic IRB audit logging.

Researchers switch to Sample ID Vault because traditional workflows force a trade-off between security risks and software complexity. Generic ID utilities lack encrypted storage or compliance exports, while hospital pseudonymization suites require weeks of IT onboarding. Sample ID Vault combines zero-cloud privacy with instant, audit-ready pseudonymization.

How to get started

  1. Open the workspace; the Generate tab opens by default.
  2. Click Load example to test five sample names, or paste your sample list into the text area.
  3. Configure your ID format (6 or 8 chars), optional prefix (e.g. PAT-), and optional study salt.
  4. Select Reversible mode, enter a session password, and click Generate IDs.
  5. Copy the pseudonym table, download Key CSV for master records, or export De-identified CSV.
  6. Use the Lookup tab with your password to re-link IDs later, or visit Vault to export a .vault backup and IRB log.

Frequently asked questions

Are my patient or sample names uploaded to any cloud server?
No. Sample ID Vault operates with a strict local-first, zero-trust architecture. All pseudonym generation, AES-256-GCM encryption, and vault storage execute entirely inside your web browser. Sample names and encryption passwords are never transmitted across the network. You can verify this at any time using browser developer network tools.
What is the difference between reversible and irreversible pseudonymization?
Reversible mode encrypts the mapping between original names and generated IDs using AES-256-GCM with a PBKDF2 password-derived key. You can decrypt and recover original names in the Lookup tab using your password. Irreversible mode applies a one-way HMAC-SHA256 hash. Once the browser session ends, original names cannot be recovered under any circumstances.
How do multi-center research teams generate identical IDs offline?
Multi-center teams can synchronize pseudonyms without a central server by entering the exact same study salt phrase and ID configuration (length and prefix) across sites. Because the underlying generator is deterministic given identical inputs and salt, all participating labs produce matching pseudonyms offline without exposing master key files.
What metadata is included in the IRB compliance audit log?
The IRB compliance audit log exports a structured JSON or TXT report containing execution timestamps, total record counts, ID schema parameters (length and prefix), a truncated hash of the study salt, and a cryptographic checksum of all generated pseudonyms. Crucially, raw sample names and patient identifiers are excluded to maintain strict privacy compliance.
What happens if I clear my browser cache or switch devices?
Encrypted vault data is stored in your browser local storage (localStorage). Clearing site data will erase the local vault. To prevent data loss or transfer mappings to another device, navigate to the Vault tab and click Export Vault to download an encrypted .vault file. You can import this file on any device using your original password.
Can I use an AI agent with Sample ID Vault?
Yes. The built-in workspace assistant helps configure ID settings and map CSV columns. External agents can connect via [API & MCP](/tools/developers) using pepkio_sample-id-vault to execute generate, lookup, and audit log functions programmatically while preserving client-side data privacy boundaries.

Client source code & registry

Last updated . Pepkio builds free lab calculators alongside bioinformatics CRO services.