Identity and verification
KYC/KYB information may be used to support verified participation and reduce anonymous signing risk.
SignumEra Start Onboarding Privacy
SignumEra is built for verified agreement execution. That means privacy, identity, document access, and evidence handling must be treated as part of the product, not as an afterthought.
Information we expect to handle
SignumEra may process account information, Microsoft identity information, business verification information, signer and recipient details, document execution metadata, audit events, and evidence package records. The exact information depends on the workflow, verification level, and Microsoft 365 permissions granted by the user or organization.
KYC/KYB information may be used to support verified participation and reduce anonymous signing risk.
When connected, Microsoft access is used to select source documents, prepare execution targets, and write finalized outputs or evidence packages where authorized.
Session events, manifests, hashes, finalization records, and supporting artifacts may be retained to help reconstruct the execution process.
Product principle
SignumEra is designed to work with Microsoft 365 as the customer document environment. The intended model is to select a document from OneDrive or SharePoint, freeze the execution target for the signing room, then write finalized PDFs and evidence packages back to authorized Microsoft storage.
| Area | SignumEra approach |
|---|---|
| Document access | Use Microsoft permissions granted for the workflow rather than asking users to maintain a separate document silo. |
| Verification | Use KYC/KYB to support a cleaner trust layer for serious agreements. |
| Evidence | Maintain records needed to explain preparation, signing, finalization, and evidence package creation. |
| Control | Provide users and organizations with configuration choices as the product matures through beta and production release. |
Beta note
Privacy practices, product screens, and data-handling disclosures may be refined as SignumEra moves through beta hardening. This page will be updated as the beta implementation is hardened and the final production workflows are confirmed.