Preserve the original
Server uploads store original bytes in configured R2 storage, with upload metadata and a server-generated SHA-256 hash. A local save is not confirmation that an original reached the server; check upload and export results.
Trust is part of the product
RRP Central is designed around tenant boundaries, original documents, and a history that ordinary edits cannot rewrite.
Server uploads store original bytes in configured R2 storage, with upload metadata and a server-generated SHA-256 hash. A local save is not confirmation that an original reached the server; check upload and export results.
Recorded mutations append audit events, and exports include saved record history and ruleset information. A hash or audit entry does not independently verify that the underlying statement is true or that a signer is who they claim to be.
Database triggers reject ordinary updates and deletes in the audit table. Mutation requests use idempotency keys to handle retries. These controls are not an independent immutable archive and do not prevent a privileged database administrator from changing the schema.
RRP Central keeps your records and shows how they were made. It does not replace your own legal review or the agency that runs your program.
Implemented controls and limits
Portal links grant access by possession and do not independently verify signer identity. Browser encryption covers supported local evidence bytes, not every local record or metadata field. Retention settings calculate schedules; the app has no general automatic record purge or self-service account erasure.
Production configuration, access administration, backups and restore testing, incident response, provider retention and storage regions, and any independent security certification require operational verification. No uptime, recovery, SOC 2, or ISO certification commitment is made here. Review our Privacy Policy and Terms for details.
See the workflow yourself