Rights & grievances
Give people a place to submit requests. Help your team assign, review and respond.
Available · plan & configuration dependentGive people a real choice. Keep optional tracking off until they agree. Put understandable receipts and a clear evidence trail behind every decision.
Choose how this example website uses optional data. You can change your mind anytime.
Explore the journey from a clear notice to a record people can keep.
A clear, itemised notice connects each purpose to the personal data involved. Optional choices begin off.
notice.version = 14Try a purpose below, save your choice, and watch the example controls respond. The receipt records what you saved.
Fictional business. Browser-only example.
Example choices do not record real consent.
Essential processing keeps the example site working. Optional processing is up to you.
These labels illustrate how integrated scripts follow the saved choice. This example does not run tracking scripts.
On your website, enforcement depends on correctly classifying and integrating optional scripts. Unconfigured tools need separate attention.
Give people more than a confirmation message. Give them an understandable record they can revisit, download, and keep.
Subject receipts are available on every plan when activated for your organisation. An account or email is not required to give consent.
Save a choice in the demo above and it appears here. Explore activity and the steps behind a fictional privacy request.
| Recorded / IST | Session | Outcome | Evidence |
|---|---|---|---|
| 28 Oct · 14:32 IST | session_6e2cv14 · English | Updated | |
| 28 Oct · 14:28 IST | session_3a91v14 · English | Granted | |
| 28 Oct · 14:21 IST | session_b7d0v14 · English | Rejected | |
| 28 Oct · 14:15 IST | session_95fav13 · English | Withdrawn | |
| 27 Oct · 17:44 IST | session_1c44v13 · English | Granted | |
| 27 Oct · 16:09 IST | session_877ev13 · English | Rejected |
Extend the work around consent with focused tools for everyday privacy operations.
Give people a place to submit requests. Help your team assign, review and respond.
Available · plan & configuration dependentKeep nomination records and review authority when someone seeks to act for another person.
Available · tenant-configurableReview recorded age selections and restrictions, with clear self-declaration labels.
Self-declaration · not identity verificationComprehensive processing inventory, DPIA, breach workflows, native mobile SDKs, enterprise SSO and separate verified representative consent remain distinct future capabilities. Their inclusion in the wider vision does not mean they are available today.
Start with your notice and purposes. Add the integration that fits your website, then test that your scripts respect each choice.
Configure your domain, notice and purposes.
Use WordPress, JavaScript or your API workflow.
Check acceptance, rejection, changes and withdrawal.
<script
src="YOUR_SDK_URL"
data-privista-key="YOUR_PUBLISHABLE_KEY"
data-notice="YOUR_NOTICE_KEY"
async>
</script>Understand what the evidence shows, how access is controlled, and where your team’s responsibilities begin.
Evidence should explain
what actually happened.
Check this small sample chain. Then change a record and see what the next check finds.
Actual SHA-256 checks, performed locally. This teaching example is separate from the production ledger and signed receipts.
Receipts use the notice and recorded selections at the time. Missing historical information is clearly labeled.
Tenant context, database controls and application roles govern who can review business records.
Hash-linked records and signed subject receipts support integrity checks. Verification is not a legal-validity certificate.
Receipt references alone do not authorize access. Recovery links only receipts explicitly enrolled by the person.
DPDP implementation is phased. Software supports your privacy operations; your organisation remains responsible for its notices, integration and applicable obligations.
Read the FAQsA banner is one part of the experience. The important questions are what personal data you process, for which purpose, and on what lawful basis.
The DPDP framework addresses digital personal data. A technology label, such as a cookie or pixel, is not by itself the legal test.
Where you rely on consent, provide a clear notice and obtain a specific, informed, affirmative choice. The Act also recognises certain legitimate uses, subject to its conditions.
Publish purposes, collect choices, apply configured script controls and keep evidence. Your organisation determines its lawful basis and the duties that apply.
Compare the choices, the implementation and the evidence. Here is a practical checklist for evaluating a consent solution.
| What matters | What to check in any tool | Privista Consent |
|---|---|---|
| Purpose-level choices | Can people make granular choices and easily change them? | Optional purposes start off; the preference centre supports updates and withdrawal. |
| Script enforcement | Which scripts are actually integrated, classified and controlled? | Configured optional scripts follow the recorded choice, with Consent Mode support. |
| Evidence integrity | Can you inspect and check the historical record? | Hash-linked consent records and signed subject receipts support integrity checks. |
| Receipts for individuals | Can a person view, download and keep their own record? | Subject receipt access, JSON, print and optional recovery when activated for the tenant. |
| Language support | Which languages are included in the selected plan? | English and Indian-language notices, with language capacity determined by plan. |
| Privacy operations | What happens after a person raises a request? | Intake, cases, grievances and nomination workflows with plan and configuration limits. |
Confirm the features, integration requirements and terms for the plan you choose.
Privista is founded by Amal Singh, a Cyber Law & Information Security student at the National Law Institute University, Bhopal.
That perspective informs the product’s focus on clear notices, purposeful choices and understandable evidence—details that matter to the person giving consent and the business recording it.
Meet the founder on LinkedInChoose the capacity your website and team need. Subject receipt access is available across plans when activated.
Loading current plans…
Prices exclude 18% GST. Paid selections create a plan request; activation follows review. Allowances are loaded from the current public catalog.
The questions business owners ask before making consent part of their website.
The banner is the starting point. Privista also provides purpose controls, a preference centre, consent evidence, subject receipts and privacy-rights workflows. Script enforcement depends on correctly classifying and integrating the scripts on your website.
Consent records are linked using cryptographic hashes, so changes can be detected through verification. A valid receipt signature establishes issuer authenticity and integrity. It does not, by itself, establish that consent was legally valid or that an external processor completed an instruction.
Yes. When subject receipts are activated for an organisation, a person can view their receipt, download JSON, print it, and optionally verify an email for recovery. Consent does not require an account or an email. This access is available across subscription plans when enabled.
Privista is software businesses use to collect consent and manage their own privacy operations. The registered Consent Manager under the DPDP framework is a distinct regulated role. Privista does not claim that registration.
Install the JavaScript integration or WordPress plugin, publish the appropriate notice, and classify your optional scripts. Test the initial visit, acceptance, rejection and withdrawal flows. Privista controls integrated scripts; it cannot guarantee that every unconfigured third-party tool follows a choice.
The current age policy supports self-declaration, restrictions and activity reporting. Adult self-declaration is not independent identity verification. Verified parental or representative consent is a separate capability and should not be inferred from an age selection.
This page focuses on working consent and privacy-rights capabilities. Comprehensive inventory management, DPIA, breach workflows, native mobile SDKs and enterprise SSO remain separate roadmap items. Availability also depends on plan, tenant configuration and activation.
The displayed plan window describes administrator dashboard and export visibility. It is separate from evidence retention and subject receipt access. Retention follows a documented tenant policy and applicable requirements; the plan window is not a deletion promise.
Start with consent. Give people control.
Keep a record your team can understand.