Skip to main content

Designing your preference center

Everything on this page is done in the dashboard (Consent Management → Preference Centers). None of it is a public API call. To build your own page instead, see the Preference Center API.

A design is a draft you edit and a published copy people see. Publishing is one click, every publish is kept in history, and two people editing at once are warned instead of overwriting each other. A design that was published before these features existed keeps working unchanged.

Start from a design​

New centers start from a ready-made design (six are included, matching the design templates) or from blank. You can duplicate a center, and export a design to a file and import it into another center or another organisation. The file holds the design only, never codes or organisation details, and is limited to 256 KB.

Pages and sections​

A center has up to 8 pages, shown as tabs, a sidebar or steps depending on the template. Each page holds up to 30 sections that you add, reorder by dragging (or with the keyboard) and configure.

SectionWhat it shows
PurposesEach purpose with its data categories, its on/off control and any topics and preferences
RequestsThe person's rights: access, correction, erasure, nomination
GrievancesFiling a grievance and following it
Grievance officerOfficer contact and how to complain to the Data Protection Board
Privacy noticeLink to your full privacy notice
Guardian statementShown for minors
Rich textYour own text
LinksA list of links
DividerA line or space
ProfileQuestions you ask the person
Unsubscribe from everythingOne button to withdraw everything they can withdraw

You also choose the header (logo, title, subtitle, alignment), a footer with text and links, how wide the page is, and behaviour such as which buttons appear and where to send the person after saving (https only).

Rich text allows bold, italic, underline, paragraphs, line breaks, lists, two heading levels and links (https: and mailto: only). Links open in a new tab. Anything else is removed when you save. Each text is up to 4,000 characters, per language.

Required elements​

Some things must always be shown to a person under India's DPDP Act. You decide where they go (which page, what order) and how they look (colours, fonts, spacing, template), but you cannot remove them, hide them, put a rule on them, or change the notice wording they show.

The required sections are: purposes, requests, grievances, grievance officer, privacy notice and the guardian statement. The language selector is part of the page frame and always present.

This is enforced in several places: the editor shows them locked, saving and publishing are refused if one is missing, duplicated or on a hidden page, a check list shows the reason for each, and the page itself restores a missing one instead of showing nothing. Custom CSS cannot hide them either.

Rules​

A page or an optional section can be shown only to some visitors. A rule is "all" or "any" of these conditions:

FieldOperatorsExample
Languageis in / not inShow only to Hindi and Tamil
Countryis in / not inHide from visitors in the EU
Is a minorisShow only to minors
DeviceisShow only on mobile
Consentgranted / not granted for a purposeShow only to people who agreed to marketing

Rules decide what is displayed, nothing else: they never change whether consent is valid. They cannot be put on required sections or on a page that holds one. When the visitor's country cannot be worked out, "country in" is false and "country not in" is true.

Profile questions​

Under Preference Centers → Profile fields you define questions to ask, with a type (text, long text, number, date, email, phone, choice, checkbox), a label per language and whether it is required. A question can be tied to a purpose: the answer can then be saved only while that purpose is granted. Add a Profile section to a page to show them.

Answers are removed when the person is erased and are included in their access request. Your backend can read and write them with the server profile calls, and the profile.updated webhook tells you when they change.

Collection points and region rules​

Collection points (Consent Management → Collection Points) are web forms that collect consent in one step, with the texts, purposes and questions you choose, a list of websites allowed to show them, and a draft and published copy. See Collection points and forms.

Region rules say what the default is for visitors from a country, optionally limited to states: OPT_IN (nothing is on until the person agrees) or OPT_OUT (optional purposes start on until the person declines), whether the banner is shown, and whether consent must be explicit (nothing pre-ticked). The most specific rule wins: a country and state, then the country, then the "everywhere else" rule. A rule is advice for the banner or page; it never changes a decision already recorded. A rule that starts everything on cannot also require explicit consent.

Look and feel​

Colours (separate light and dark sets), font from a list of safe families, button style (filled, outline, pill), corner radius, shadow and spacing. For anything beyond that, use custom CSS.

Your own domain​

You can serve the page from your own host, such as preferences.example.com. Under Preference Centers → Domains:

  1. Add the hostname.
  2. Create the DNS record shown (a CNAME pointing at Bytemonk).
  3. Click Verify. Bytemonk proves you own the name by asking the hostname itself for a token, which also proves the record points to us. Unverified domains are re-checked automatically for 7 days.

Once active, the host identifies your organisation, so links on it need only the token and no orgKey:

https://preferences.example.com/preference-center/#token=<principal token>

A domain can name the design it serves. A domain only identifies your organisation on the public page and calls made by your visitors; it never opens the server API. HTTPS certificates for custom domains are set up with your Bytemonk contact.