Signing documents should be simple. Verifying their integrity and evidence should be too.
RPSIGN was born from the routine of a law firm to organize contracts, powers of attorney and declarations into electronic workflows with clear criteria for authentication, document integrity and evidence recording, according to the modality applied to each act.
Illustrative interface of the RPSIGN dashboard.
A platform designed for people who need to trust their own process
RPSIGN was designed to associate documents, policies and relevant events with verifiable technical evidence. The goal is to allow integrity, history and authentication method to be assessed based on what was actually recorded in each workflow.
Document lifecycle control
The architecture organizes documents, versions, participants, policies and workflow events in a structure controlled by RPSIGN, with private storage and organization-level isolation. External services, when used, are integrated according to the purpose and the applicable policy.
Evidence, not promises
The evidence architecture was designed to associate with each workflow the records actually produced by the modality used — such as document integrity, events, authentication method and other technical data permitted by the applicable policy.
Born from legal practice
It was conceived around common legal-practice needs — powers of attorney, legal-fee agreements and declarations — with attention to the signature modality, available evidence and the formalities each act may require.
A direct workflow, with defined stages and criteria
The workflow is structured into clear stages, with records and controls defined according to the modality, the applicable policy and the resources actually used.
See the full step-by-stepDocument submission and preparation
The document, its participants and the rules applicable to the workflow are organized according to the purpose of the act and the selected signature modality.
Signer verification
The modality may combine different authentication and evidence mechanisms, such as email, SMS, WhatsApp, document validation or other controls, when those resources are enabled for the workflow.
Integrity and recording
RPSIGN uses SHA-256, an organization-specific chained ledger and HMAC-SHA-256 authenticated checkpoints to strengthen integrity verification and detect inconsistencies incompatible with the recorded chain.
Completion evidence
Records produced by the workflow may form technical completion and audit documents according to the modality used. These evidence documents are not ICP-Brasil digital certificates, notarization of signatures or notarial authentication.
We say exactly what we protect — nothing more
We prefer precision over impressive claims. See the technical mechanisms that structure integrity, administration and evidence in RPSIGN.
Cryptographic ledger
Organization-level SHA-256 hash chain, with HMAC-SHA-256 authenticated checkpoints.
Multi-factor authentication
Mandatory MFA/TOTP for administrative accounts, with sessions protected by opaque tokens.
Versioned policies
Signature and authentication rules are versioned, preserving historical versions linked to the corresponding events and documents.
Privacy by design
The platform design considers purpose, necessity, minimization, access control and retention. When sensitive personal data such as biometrics are used, they require specific safeguards and an assessment appropriate to the concrete operation.
A commitment to transparency
RPSIGN does not present itself as a Certification Authority, Time-Stamping Authority, service approved by the ITI or an organization certified under ISO 27001. The evidentiary weight of a signature depends on the modality, the evidence actually collected and the circumstances of the case. When the applicable modality is a qualified electronic signature, it uses a digital certificate within ICP-Brasil. The corresponding integration depends on the technical components actually enabled in the workflow. Details at Security, Privacy and Evidence.
Technology conceived from legal practice
RPSIGN was conceived from concrete needs of a law firm, especially the organization of legal-fee agreements, powers of attorney, declarations and other documents that require traceability, integrity and clear authentication criteria.
That origin guides the platform design: combining operational simplicity, preservation of evidence and respect for the legal and technical requirements applicable to each signature modality.
Need information about RPSIGN?
Use the contact channel for institutional questions, support, privacy or other matters related to RPSIGN.
I want to talk about RPSIGNDeveloped by ADDON — Intelligence, Software and Automation
Custom software engineering, without off-the-shelf platforms or rigid models.
Any questions about how RPSIGN works?
Talk directly to the team responsible for RPSIGN.