Understanding Multibrand in DSR

Run DSR for several brands — each with its own Privacy Center, emails, and visuals — from one central workspace.

Many organizations operate more than one brand, product line, or legal entity under a single company. MineOS Multibrand lets you present each brand with its own fully independent, branded experience to data subjects, while your privacy team manages every request centrally in one workspace.

Plan availability

Multibrand is available on the Enterprise plan. If it isn't part of your plan, reach out to your Customer Success Manager.

What's configured per brand

Each brand gets its own data-subject-facing identity:

  • Its own Privacy Center — dedicated URL, form and fields, language selection, custom code, and privacy policy URL.
  • Its own email templates and designs.
  • Its own email sender address — see Set Up a Custom Email Sender Domain.
  • Its own brand visuals — logo and color scheme.

For the Privacy Center specifics, see Multibrand and the Privacy Center.

What stays centralized

Everything operational lives at the company level and is shared across brands:

  • Integrations
  • Privacy rights and their workflows
  • Request management
  • Reporting

How requests are handled across brands

When a data subject submits a request, MineOS associates it with the brand it came in through. Every request, from every brand, appears together on The Requests Page, where you can filter, sort, and view by brand — so your team works from a single queue while still seeing which brand each request belongs to.

Company vs. brand

Your company is your global account identity (Main Settings → General — name and logo). A brand is a client-facing DSR identity (DSR Setup → Brands). To change what data subjects see, edit the brand's name and logo, not the company's.

Managing brands

Brands are created and managed in DSR Setup → Brands. The first brand in an account is the default brand — it always exists, can't be deleted, and is used as the fallback when no specific brand is set (including for API calls without a brand ID). Brand deletion isn't supported, so historical requests always remain accessible.


Did this page help you?