Skip to main content
Secrets as a Service is Monaris’s programmable privacy framework. You define rules for what stays private, what can be disclosed, and to whom — at the transaction level or account level. The core principle: privacy and verifiability are not opposites. You can keep a payment completely private while still proving it happened.

​
Who this is for

Anyone who wants fine-grained control over their financial privacy on-chain — from freelancers who want basic privacy to businesses that need compliance-ready disclosure capabilities.

​
How it works

Every payment through Monaris is private by default through the Privacy Router. Secrets as a Service adds a layer on top: programmable rules that determine privacy behavior automatically, selective disclosure that lets you prove specific claims without revealing raw data, and compliance mode for regulated entities.

​
Programmable privacy rules

You define rules once. They run automatically on every matching transaction. Examples:
  • “All payments above $5,000 are always private” — amount threshold triggers maximum privacy
  • “All payments to Vendor A are private” — counterparty-based rule
  • “Payroll payments are private — but generate a verifiable receipt” — privacy with audit trail
  • “Private by default — except when I choose to share a proof” — manual override only
  • “All payments private — my Score data is shareable for credit purposes” — privacy with Score portability
Rules can be combined and layered. Business accounts can enforce rules across all team members.

​
Selective disclosure

You can keep a payment fully private on-chain and still:
  • Generate a cryptographic proof that the payment happened — for the recipient’s confirmation
  • Prove the amount was within a range — for a lender checking your income (“earns above $3,000/month” without revealing the exact number)
  • Prove on-time payment — for your Monaris Score calculation
  • Generate a verifiable receipt — for tax purposes
These are two separate controls: what is secret and what is provable. You set each independently.

​
Feature access by plan

FeatureFreePay UserBusiness
Private payments by default✓✓✓
Custom privacy per transaction—✓✓
Programmable privacy rules——✓
Selective disclosure proofs—✓✓
Privacy audit log—✓✓
Team privacy policy——✓
Compliance disclosure mode—✓✓

​
Compliance mode

For regulated entities that need to disclose payment information to regulators on request — without making anything public:
  • Targeted disclosure — share only with the named regulatory authority, not the public chain
  • Full audit log — complete record of every disclosure: what was shared, with whom, when
  • User notification — you are notified before any disclosure is made
  • Privacy preserved — compliance disclosure does not affect your default privacy for any other purpose

​
Privacy and your Monaris Score

Privacy does not reduce your Score. The Monaris Score is calculated from internal verified signals — not from public chain data. Your payments can be completely private on-chain while your Score updates normally in the background.

​
Availability

Programmable privacy rules, selective disclosure proofs, and compliance mode are available in V2. Default private payments are active from V1 for all payments sent through Monaris.

​
FAQ

Do I need to set up privacy rules to be private? No. Privacy is the default. Rules give you additional control over when and how privacy applies — but basic privacy works out of the box. Can a third party see my transactions if I use Monaris? Not by default. Only a proof-of-payment exists on-chain, which is verifiable but not readable. You choose what to disclose and to whom. How does compliance mode work with privacy? Compliance mode is targeted disclosure — you share specific information with a specific regulatory authority. It does not make your data public. Everything else remains private. Can I revoke a selective disclosure proof? Proofs can have expiry dates and can be revoked. Once revoked, the proof no longer verifies for the recipient.