Built with a human in the loop — and security as a first principle.
piRevenue handles deal data, contact details and conversation context for revenue teams. Here's how we think about protecting it, and what's still on our roadmap.
Four rules we design every feature against.
Access is scoped to what a role actually needs.
Reps see their own deals and shared team pipeline; access to broader account data is role-based and logged.
Deal data is encrypted moving and stored.
Connections to piRevenue use TLS; stored data is encrypted at rest with provider-managed keys.
Your pipeline is not a data product.
We don't sell customer deal or contact data, and we don't use it to train models for anyone outside your own account.
You can ask us to delete your data.
Account owners can request export or deletion of their organization's data; see our Privacy Policy for details.
Every agent action is logged. Every customer-facing action is approved by a person.
Agents in piRevenue draft, flag and suggest — they don't send, commit or promise anything to a customer without a human clicking approve. That approval is recorded: who reviewed it, what changed, and when.
This isn't just a trust statement — it's the architecture. The audit trail exists so a sales leader can always answer "who said what to this customer, and why" with a real record, not a guess.
Privacy isn't a policy we bolt on afterward.
We design capture and forecasting features to work from the deal context reps already create — not to pull in more personal data than a sales workflow needs. Where a feature would require new personal data, we ask what it's for before we ask how to collect it. Full details live in our Privacy Policy.
Building for markets with real data-residency conversations.
Teams across India, the Middle East, Southeast Asia, Africa and Latin America increasingly ask where their data lives, not just how it's protected. We take that seriously: regional hosting options and data-residency commitments are active roadmap work, and we'll be explicit with customers about where data is processed as those options ship — no vague promises in the meantime.
What we're building next — and what we're not claiming yet.
piRevenue is an early product. We'd rather tell you what's on the roadmap than claim a certification we don't hold.
SOC 2 Type II readiness assessment · ISO 27001 alignment · Regional data-residency options · Third-party penetration testing cadence · Formal security review for WhatsApp/Meta channel integrations, ahead of that roadmap item shipping
Found a security issue? Please report it to security@pirevenue.com — we read every report and will get back to you.
Questions about how we handle your data?
Talk to us before you commit — we'd rather answer now than surprise you later.