Isolation enforced by the database
Every business table carries row-level security in Postgres, set for each transaction. The application connects with a role that cannot bypass it, so one workspace can never read another’s rows.
Trust
Your buyers’ data, locked to your workspace.
A developer’s CRM holds phone numbers, budgets, KYC and payments. proprev keeps them isolated by the database itself, shows each person only what their role needs, and records consent before anything is sent.
Six things that are true today.
Each one is built into the product, not promised in a policy.
Eight roles, scoped to the project
Admin, Sales Manager, Sales Executive, Tele-caller, CRM Executive, Marketing, Finance and Channel Partner. Access can be limited to your own leads, your team, a project or everything, with deny rules on top.
Sign-in and session controls
See every session and revoke any of them. Exports, refunds, payouts, KYC and settings ask for your password again. Per-user IP allow-lists, and a page that shows the workspace’s security posture.
Consent per channel, with no way around it
Calls, WhatsApp, SMS and email each carry their own consent record. Every message passes one gate, and a test in the codebase fails if anything tries to skip it. Refused sends are recorded, not lost.
An audit log for what matters
Sign-ins, security events, setting and feature-switch changes, approvals and AI usage are all recorded and reviewable on screen.
Money records that hold
The ledger is append-only. Receipts are numbered without gaps and corrected, never edited. Issued cost sheets and demand letters are frozen.
DPDP
Built for India’s data protection law.
The Digital Personal Data Protection Act asks you to hold consent and answer a buyer’s requests about their data. proprev keeps both inside the product, next to the lead they belong to.
- Consent, recorded per channelEach buyer’s permission for calls, WhatsApp, SMS and email is kept as its own record, with where it came from.
- Requests handled in the productAccess, correction and erasure requests are raised, tracked and completed from Settings → Privacy requests.
- A legal hold for financeErasure keeps the statutory finance records the law requires you to retain.
- A data package on requestExport what proprev holds about a buyer, when they ask for it.
- Opt-outs that stickSTOP and unsubscribe are honoured on every later send, through the same consent gate.
Every message follows the rules.
- DLT fields on every SMSTemplates carry their DLT ids, and a marketing SMS without one is refused.
- Approved wording for first contactCold and first messages use your approved templates only.
- A person in the loopAI replies wait for a person to send them, unless you set a campaign to Auto. Then they go out only within WhatsApp’s 24-hour reply window.
- Calling hours respectedOutside calling hours the product says so, and quiet hours and frequency caps can be switched on per workspace.
AI with a hand on the switch.
- Every AI feature ships switched offEach one is turned on separately, per workspace.
- One gate for every model callCalls are logged in a spend ledger that does not store prompts.
- No model scores your leadsThe interest score is arithmetic you can read, with every point shown.
- Output is checked or thrown awayAnything a model returns must pass the product’s own validators whole.
Privacy policy
How proprev collects, uses and protects personal data, our two roles under the DPDP Act, and how to exercise your rights.
Read the privacy policyTerms
The terms that govern use of proprev: the free CRM, paid modules, your data, AI features and your responsibilities.
Read the terms of service