Ezecollect · Security
What's actually true about security here.
No certifications we haven't earned, no vague 'bank-grade' claims. Here's exactly what's in place today, and what isn't yet.
Verified controls
Click a question to expand it.
Five straight answers — including the one about certifications we don't have yet.
Yes. Data is encrypted in transit using TLS, and at rest in the underlying database. This applies to collection records, merchant details, and anything stored by the product — not just the payment step itself.
Access to merchant data and the dashboard is scoped per account — a merchant sees their own collections, not anyone else's. Internal access to production systems is limited to the engineers who need it for a given task, not open by default.
Ezecollect is a UPI collection product — it never asks a shop owner for a card number or bank login. Payment happens entirely inside the shop owner's own UPI app; Ezecollect only receives the confirmation.
Not yet, and we won't claim otherwise. We follow good security practice as a baseline, but we haven't completed a formal third-party audit for any of these certifications. If that changes, it'll be reflected here with real evidence — not before.
Email Connect@bigzimpactglobal.com with details. We don't yet have a dedicated security contact or bug bounty program — if you've found something, a direct email is the fastest way to reach us right now.
Still to come
What we're working toward.
Formal certifications, a published security policy, and a real responsible-disclosure process are all things we want — none of them exist yet. Track status on the roadmap.
Questions about this?