Testing & Troubleshooting

Testing your Privacy Center

Test the draft before publishing

Use the View → View draft version button to open your saved draft in a new browser tab. A yellow banner confirms you're viewing the draft, not the live form. Test your form fully here before clicking Publish.

Always save your changes with Save draft first — the draft preview reflects your last saved state, not unsaved edits.

Test the live form

Use View → View published version (or click View directly when all changes are published) to open the live form as data subjects see it. Use this to confirm the published version looks and behaves as expected after publishing.

Test conditional logic

To test display logic, go through the form as a data subject would:

• Select the parent element's answer that should trigger a child element, and confirm the child element appears
• Select a different answer and confirm the child element is hidden
• Test edge cases — multiple conditions, chained conditions, and AND logic

If a child element isn't appearing when expected, check:

• The parent element appears above the child element in the form
• The correct answers are selected in the condition rule
• The condition hasn't been automatically removed due to a reorder — check for the numbered badge on the Edit logic button

Test the authorized agent flow

Add the Data subject element with at least one Authorized Agent type, then on the form select an Authorized Agent option and verify:

• The agent email input appears
• The document upload field appears
• Submitting with the same email for both the data subject and the agent is blocked with a validation error

Test multiple choice and the "Other" option

If you've enabled the Use "other" toggle on a Multiple choice element, select "Other" on the form and confirm the free-text "Specify your answer" input appears below the options.

Test format rules

If you've configured format rules (regex) on a Short answer, Mobile number, or URL element:

• Enter an invalid value and confirm your custom error message appears
• Enter a valid value and confirm it passes without error

Test prefilling, URL parameters, and rights filtering

To test prefilling, append query parameters directly to the draft URL (e.g. ?draftId=...&firstName=Jane&[email protected]) or to the live URL. Verify:

• Prefill parameters (firstName, email, countryCode, etc.) correctly populate the corresponding fields
• privacyRightId preselects the correct right
• supportedRight limits the visible rights to only those specified
• Custom parameters (e.g. source=footer) are stored as custom fields on the submitted request in your Requests page

Test custom CSS

After injecting CSS via the Custom code tab, open the draft preview and verify styles are applied correctly across the form. Pay particular attention to:

• Mobile layout — open on a mobile device or use your browser's mobile emulator to confirm nothing is broken at smaller screen sizes
• Hover and focus states on inputs, dropdowns, and the Submit button
• The selected state on rights cards

See CSS Customization Reference for the full list of available selectors.

Test the CMP integration

If you've wired the Privacy Center to the Mine CMP using MINE.onRequestSubmitted, test the integration end-to-end:

1. Open the Privacy Center draft or live form
2. Submit a Do Not Sell request
3. Open your browser's developer console and run MineCMP.getConsent() to confirm the Marketing consent category has been withdrawn

Test multiple languages

Switch the language using the dropdown in the top-right corner of the live or draft form. Verify:

• All elements display correctly in each enabled language
• No elements fall back to English (US) unexpectedly — this indicates a missing translation
• RTL languages (Arabic, Hebrew) display correctly

Test custom domain

If a custom domain is configured, open the Privacy Center at that domain and verify:

• The form loads correctly
• SSL is active (the browser shows a secure padlock)
• The URL does not redirect unexpectedly

Test on mobile

Open the Privacy Center on a mobile device or using your browser's mobile emulator to verify the layout renders correctly across screen sizes.

Submit a test request

Submit a request through the live form using a real email address to test the full end-to-end flow:

1. Fill in the form and submit
2. Check your email for the verification message
3. Click the verification link and confirm the request appears in DSR → Requests with the correct status and field values

---

Common issues

Changes aren't showing on the live form You have unsaved or unpublished changes. Click Save draft, then Publish. Confirm the status indicator shows All changes published.

A conditional element isn't appearing The condition may have been removed after a reorder. Open the element, check whether Add logic or Edit logic appears in the sidebar, and re-add the condition if needed.

An element is showing in English despite a translation being set The translation may not have been saved. Open the translation panel for that element, confirm the translation is filled in, and click Save draft.

Auto-translate overwrote my manual translations Auto-translate always overwrites existing translations — there is no way to recover overwritten content. Always run auto-translate first and make manual edits afterward.

Auto-translate for the whole form returned an error This can happen with large forms. Translate element by element instead — open each element's translation panel and use the Auto-translate button there. Per-element auto-translate is more reliable for complex or lengthy forms.

The Privacy Center URL returns an error page The Privacy Center has never been published. Click Publish in the builder to make it live.

A language isn't appearing in the form dropdown The language toggle may be off in the Languages tab. Go to DSR → Privacy center → Languages, enable the toggle for that language, save, and publish.

A right is missing from the Privacy Center The right may be toggled off in the Privacy rights tab, or disabled in DSR Setup. Check both DSR → Privacy center → Privacy rights and DSR → DSR setup → Privacy rights.

The URL slug shows "URL is already taken" Only the last part of the URL — the slug — must be unique across all Privacy Centers. For example, in https://your-brand.privacy.saymine.io/your-brand, only the slug at the end needs to be unique. Choose a different slug and click Publish new URL.

Publish button shows a "save draft first" dialog You made changes on the current tab but clicked Publish without saving first. Click Save draft, then Publish again.

A right didn't save its new order after reordering After reordering rights in the Privacy rights tab, click Publish to make the new order live. If the order appears to revert, try reordering again and publishing immediately after.

CSS not applying as expected CSS injected via the Head code panel may be overridden by the Privacy Center's own styles. Use your browser's developer tools inspector to identify the correct selector and specificity. Add !important sparingly to override specific properties. See CSS Customization Reference for confirmed selectors.

The CMP integration isn't firing after form submission Check the following:

• The code is in the Footer code panel, not Head code
• MineCMP.onReady() wraps the MineCMP.withdraw() call
• The privacyRightId value in your condition matches exactly (e.g. 'donotsell', not 'do-not-sell')
• The Mine CMP snippet is loaded on the same page as the Privacy Center

The embedded iframe shows a blank page or error The Privacy Center may not be published yet, or the URL in the iframe snippet is outdated after a slug change. Copy the current URL from the URL tab, update the iframe snippet on your website, and confirm the Privacy Center is published.

Format rules are blocking valid input The regex pattern may be too restrictive or may not account for all valid input formats. Test your pattern at regex101.com using real examples before deploying. Remember that the pattern is applied as a JavaScript regex.

You need something the Privacy Center builder doesn't support If you need functionality that isn't available through the Privacy Center configuration — such as custom form behavior, advanced styling, or specific integrations — contact your Customer Success Manager. Many needs can be addressed through custom code injected via the Custom code tab. See Custom Code for what's possible.