Submit a formal request
Use dedicated request paths when you want to ask for access, deletion, correction, portability, objection, or consent withdrawal.
Manage privacy choices in one place.
This page is designed as a CMP-ready privacy center pattern for Power Switch HQ. It centralizes tracking choices, communication preferences, and rights-request paths so users can find and change settings with less friction. In production, these settings should sync with your banner logic, consent records, and downstream systems.
Analytics
Allow site measurement for visits, CTA clicks, and form performance.
Marketing emails
Receive optional product updates, launch notes, and announcements.
Sale or sharing opt-out
Indicate that personal information should not be sold or shared where applicable.
Limit sensitive info
Indicate that sensitive personal information should be limited where the right applies.
Preferences updated in this front-end demo. Connect these choices to your CMP, consent logs, analytics tags, CRM, and request workflows before production use. This page is intended to mirror the same choices surfaced in the landing-page banner.
Manage California-specific choices
Use separate pages for opt-out of sale or sharing and for limiting sensitive personal information where those rights apply.
What still needs backend wiring
A real implementation should log consent, preserve preference history, honor universal opt-out signals where applicable, and sync choices across analytics, advertising, CRM, and support systems.
What users should expect after submission
A production workflow should acknowledge receipt, assign a request reference, explain verification steps, and communicate the expected response timeline for the applicable law. The confirmation pages in this version are placeholders for that more complete process.
Plan the backend path before launch
A production privacy workflow should determine which law applies, what verification level is appropriate, what deadline applies, and which systems or vendors must be included in the response. Treat the form page as intake, not the full compliance engine.
Prepare for denied-request escalation
If your business is subject to laws with appeal rights, your workflow should explain how a denial can be challenged, who reviews the appeal, what timing applies, and how the consumer can contact the relevant regulator if the appeal is denied.