Data protection
- Data is encrypted in transit (TLS 1.2+) and at rest.
- Credentials and signing secrets are isolated from application data.
- Sandbox and production run as separate, isolated environments so evaluation never touches live data.
Security & Trust
Paprel is infrastructure teams build their financial system of record on. This page is a straight account of how we protect data, keep the ledger correct, and what our compliance posture is today — including what is in place and what is on the roadmap.
We keep this page current as our posture evolves.
Compliance posture — stated plainly
We design controls aligned with SOC 2 principles and with the double-entry standards used in GAAP and IFRS reporting. We are not making certification claims we have not earned: formal certifications are on our roadmap, and we will publish them here when they are in place. Until then, we share our current control posture, security documentation, and a DPA directly with teams during evaluation. If a specific certification or control is a gate for you, tell us early and we will be candid about where we are.
Responsible disclosure
If you believe you have found a security issue, email us and we will respond to good-faith reports. We do not pursue researchers who report responsibly and give us reasonable time to address issues.
Security contact
[email protected]Who you are dealing with
Paprel is operated by a registered legal entity with clear company and compliance contacts for diligence.
Legal entity
NEXARA GLOBAL PTE. LTD. (operating as Paprel)
Company registration
UEN: 202516221H
Registered address
68 Circular Road, #02-01 Singapore 049422
Legal & compliance
[email protected]Security review
Bring your security and finance reviewers. We will walk through architecture, controls, and documentation in detail.