Skip to content
Security, trust & compliance

Your money stays yours.
Your data stays safe.

Payer collections run through the business’s configured payment provider. The provider manages funds and settlement; Ownvello keeps verified payment records and does not operate a customer wallet.

Settles to your bank Sensitive secrets encrypted NDPA-supporting controls Application audit trail
How we protect you

Application controls and deployment duties

The product controls below apply across plans. Infrastructure items are called out separately because the production operator must configure and verify them.

Funds settle to your bank

Payers transfer into their permanent account linked to your business. Your payment provider handles settlement to its configured destination, under your merchant terms.

No custody · no pooling

Encrypted secrets + HTTPS-ready

Merchant credentials, MFA secrets and retained KYC details are encrypted by the application. Production must also terminate TLS and enable database or volume encryption; those infrastructure controls are deployment requirements, not claims this code can make for every host.

App-level encryption · secure deployment required

Verified, idempotent webhooks

Payment notifications are authenticated, verified with the provider and deduplicated. Reconciliation checks for transactions that may have missed the notification path.

Signed · idempotent · reconciled

NDPA-supporting controls

The platform minimizes retained KYC payloads, sets retention windows, isolates tenants, and records sensitive actions. These controls support compliance work; they do not replace the operator's notices, lawful basis, consent process or legal review.

Minimization · retention · accountability

Role controls + audit log

Owner, admin, treasurer and agent permissions are enforced at the API boundary, and staff impersonation is read-only. Team invitations are not self-service yet. The application exposes audit records as read-only and does not provide an edit or delete route.

Least privilege · read-only impersonation

Backup readiness

The application keeps durable records in its database, but backup frequency, retention and restore testing belong to the production hosting setup. A deployment should not be called production-ready until automated encrypted backups and a tested restore procedure are configured.

Deployment control · restore testing required
The most important part

How fund separation works

Where the money goes is the whole question. Here it is in three steps, with nothing hidden in the middle.

1

Rider pays a dedicated account

Each payer gets one permanent Flutterwave virtual account linked to the business. The same bank details can be used for repeat repayments.

2

It settles to your bank

The provider settles collections according to your merchant configuration, fees and settlement schedule. Ownvello records the verified transactions and their allocation.

3

Ownvello only reads the data

We see that the payment happened, match it to the right contract, update the balance and score, and warn you early. We read the data, we never hold the money.

So if Ownvello disappeared tomorrow, your money would not. It already lives in your bank account, under your name and your CAC registration. We sell the rails and the intelligence, never custody of your funds.
Data protection

Data-protection commitments

We handle real people's names, phone numbers and payment histories. The product supplies technical safeguards, while each operator must document and fulfill its own Nigeria Data Protection Act obligations.

NDPA-aligned controls Lagos, Nigeria configured payment provider rails

Request our data agreement

Minimal PII

We collect only what a contract genuinely needs to run, no harvesting "just in case".

Consent remains the operator's duty

Operators must collect and retain the appropriate notice, lawful basis and messaging consent before using SMS features.

Purpose limitation

Data is used to run and score contracts, never sold, never rented, never repurposed.

Access, correction & deletion requests

Requests must be reviewed through the operator or support so legal retention duties and deletion rights can be applied correctly.

You own your book

Your payers and contracts are yours. Export to CSV any time; leave with your data.

Incident response required

Production operations must include monitoring, escalation and legally appropriate notification procedures.

Trust, but verify.

Ask us anything about custody, encryption or NDPA, or read it yourself. We'd rather you check than take our word for it.

Ownvello supplies software for payment records and operational workflows. Payment processing, virtual accounts and settlement are supplied by the configured provider under its own terms.