Consent Docs
Open console

User guide

Everyday tasks in the console for privacy, marketing and support teams, from the first notice to records and rights requests.

For privacy, marketing and support teams

Use this guide for everyday work in the console. It covers the Overview and its charts, purposes and consent forms, languages, regions and publishing, then records, rights requests, cookie scans and breaches. It is written for privacy, marketing and support teams, and none of the tasks need code.

Start with#

The Overview and records

  • Read the OverviewChoose the period and the records to count, read what each chart on the Overview counts, and open the records behind a figure.
  • Customise your dashboardAdd, change, move and resize the charts on your Overview, keep several dashboards, start from a starter and download a chart.
  • Read a recordOpen one consent record and read what the person agreed to, when, on which form, and whether its proof is intact.
  • Find a personSearch Records by email address, phone number or user id to list every consent record held for one person, across the whole project.
  • Verify a receiptExport a signed receipt for one consent record, and check that a receipt someone gives you is genuine and unaltered.
  • Withdraw or eraseWithdraw one consent for a person who asks you to stop, or erase a person's identifiers from every consent record you hold for them.
  • Export recordsDownload the consent records that match your filters, or one person's records, as a CSV file for a report, an audit or your own analysis.
  • Import consent from a fileBring consent your organisation collected earlier into Records from a CSV file, check every row, then write them as sealed records.

Purposes and forms

  • Add purposesAdd the reasons you use personal data to the purpose registry, from the library or your own, so consent forms can ask about them.
  • Add partnersList the companies that receive data for a purpose, and let visitors switch each one on or off in the preferences.
  • Create a formStart a consent banner, privacy notice or email opt-in form as a draft, and choose the purposes it asks about.
  • Write the noticeWrite the heading, body, buttons and links of a consent form, and add what a notice shown in India must carry.
  • Change the lookSet where the banner sits, its colours, font and buttons, and check the result in the real preview before you publish.

Languages and regions

  • Add a languageOffer a consent form in another language by typing the wording or filling it from the standard wording library.
  • Translate and approve a languageDraft a language with the translation service, have it read, and approve it so it goes out with the next version.
  • Choose regionsDecide which consent form visitors from each country or state see, starting from a law preset or a rule of your own.
  • Preview as a visitorCheck which form, law and language a visitor from any place gets, without touching your site or recording anything.

Publishing

  • Publish a versionFreeze a form's draft as a numbered version so visitors see it, and fix what stops a form from publishing.
  • Ask visitors againChoose whether people who already answered are asked again when you publish a new version of a consent form.
  • Update the privacy policyPublish a new version of a privacy policy, say whether it changes what people agreed to, and bring the forms linked to it up to date.
  • Approve a publicationRequire a second person to approve each published version, then request, approve or decline a publication.
  • See version historyList a form's published versions, what changed in each one, and whether returning visitors were asked again.
  • Send a legacy noticeSend one published notice to people who consented before the DPDP Act, through your own mailer or SMS system, and keep proof of who was sent it.
  • Track a campaignRecord what your sender delivered, read who answered a notice campaign, send new links to people who have not, and export one person's evidence.

Rights requests

  • How people askThe three ways a rights request reaches you, and what each one means for the Requests queue and for checking who is asking.
  • Handle a requestOpen a rights request, carry it out on the person's consent records with one button, and close it before its deadline.
  • Log a requestAdd a rights request that reached you by email, phone, post or a support ticket, so its deadline is tracked with the others.
  • Requests for someone elseLog a rights request from a parent, a lawful guardian or a nominee, record the document you checked, then carry the request out.
  • Record or cancel a nominationRecord the nominee a person names in a nomination request, change or cancel the nomination later, and see where it shows.

Cookies and breaches

  • Scan your siteScan a site to see which cookies, storage keys and third-party hosts it sets before and after a visitor accepts, and rescan on a schedule.
  • Publish a cookie declarationGive each cookie and storage key a purpose, then add the cookie declaration to your cookie policy page so visitors can read it.
  • Run the DPDP checkCheck your site and your set-up against India's DPDP Act and Rules, read each result, and download the report for a reviewer.
  • Record a breachRecord a personal data breach, watch the 72-hour deadline for the report to the Data Protection Board, and copy the two drafts.

↑↓ to move, Enter to open