Getting started
Learn what PIEDAP Consent does, set up a first banner, then follow tutorials for languages, sign-up consent, webhooks and going live.
Start here if you are new to PIEDAP Consent. These pages say what the product does, take you to a working banner and a first consent record, and then walk through what most teams build next. Privacy and marketing teams work in the console. Developers add the banner and connect their servers.
Start with#
- What is PIEDAP Consent says what the product does and what stays with you.
- Set up your first banner uses only the console.
- Put a banner on a test page is the quickstart for developers.
Understand
- What is PIEDAP ConsentWhat PIEDAP Consent does, what it leaves to you, who uses it and where it runs.
- How it worksWho talks to whom, from setting up a notice to proving a consent and answering a rights request.
- Key ideasThe eight ideas a newcomer needs, from project and property to keys and test records, each in a few sentences.
Quickstarts
- Set up your first bannerTake a new project from nothing to a consent banner for visitors in India and the first recorded answer, using the console.
- Developer quickstartPut a consent banner on a local page with a test key, hold one tag until consent, read the choice in JavaScript and find the record.
Tutorials
- Add Indian languagesDraft your notice in the 22 Eighth Schedule languages, approve each one, publish, and check what a visitor in India sees.
- Record sign-up consentRecord what a person ticks on your sign-up form from your own server, and link their email address and phone number to the record.
- Build a privacy pageGive signed-in users a page that lists what they agreed to and lets them withdraw, with two calls from your server.
- Receive your first webhookRun a small receiver, add it as an endpoint in the console, and watch a signed consent event arrive and pass its signature check.
- Go liveCheck your site with a test key, ask for the key to go live, and confirm that it now writes live records.