FAQ
Public answers designed for the website (no secrets, no internal endpoints).
If you have an investor copy, keep it private and share selectively.
FAQ (Public)
What is iRNDOM?iRNDOM is a privacy control plane for data in motion . It replaces sensitive identifiers with Safe Labels™ before data leaves your boundary, so outbound data is safe by default.
What problem does it solve?Most breaches and leaks happen where data is used (vendor systems, logs, compromised accounts), not in transit. iRNDOM reduces blast radius by making outbound copies useless.
How is this different from encryption?Encryption protects transport and storage. iRNDOM protects usage: vendors and outside systems only see Safe Labels™, so stolen outbound data does not contain real identifiers.
How is this different from masking?Masking often leaks structure and patterns. Safe Labels™ preserve workflow compatibility without exposing raw identity.
Do vendors break if they only see Safe Labels™?Most workflows can operate on Safe Labels™. If a narrow use case requires originals, restoration can be permitted only in controlled internal zones with audit.
Does this require changing our vendors?No. iRNDOM sits in your outbound request path. Vendors receive the same payload shape, but sensitive identifiers are converted into Safe Labels™.
How hard is integration?Typically: (1) put iRNDOM in the outbound path, (2) define sensitive fields, (3) set zones and policies, (4) validate with test calls.
Can iRNDOM work with AI / LLM workflows?Yes - it's especially useful before sending data to external AI services so identifiers never leave your boundary in raw form.
Is there an audit trail?Yes. Decisions can be logged with consistent proofs for security review and compliance evidence.