Contents

Create Your Own Survey Today

Free, easy-to-use survey builder with no response limits. Start collecting feedback in minutes.

Get started free
Logo SurveyNinja

White label

Your client gets a link to a survey — and in the address bar they see surveyninja.io. In the form footer, the service's logo. On the completion screen, an ad for the platform.

For an agency that sells research under its own brand, or a corporation that values a unified communication style, this is unacceptable. White label solves the problem: the platform stays a tool in the background, while the respondent sees only the client's brand.

Definition

White Label — a way of working with a platform in which every mention of the provider's brand is removed from the user interface. The survey opens on the client's domain, displays their logo and colors, and contains no links back to the source platform. The respondent interacts only with the client's brand. White label is used by agencies, resellers, and corporations for which a consistent corporate identity in communications matters more than crediting the tool being used.

What white label includes

White label is not a single setting but a set of parameters, each of which affects how "invisible" the platform is.

Custom domain. The survey opens at an address like survey.yourcompany.com or research.agency.com instead of the platform's standard domain. This is the most visible element: the URL appears in the address bar, in email links, in QR codes. Without a custom domain, every other setting delivers only a partial effect.

Branded design. Logo, brand colors, fonts, background images, button styling — everything is brought in line with the client's brand book. For an agency running several clients, this means a unique visual style for each project.

Removing the platform's logo and links. The "Made with [Platform]" footer, the logo in the header, the link to the provider's website — all of this is hidden. The respondent never sees which tool the survey was built on.

Custom email notifications. Emails with results, confirmations, and reminders are sent from the client's address, not the platform's. Subject line, signature, and design follow the client's corporate style.

Welcome and completion screens. The welcome screen and the "Thank you" screen are fully branded for the client — without any references to the platform.

Who needs it and why

Research agencies. An agency sells the client a finished study, not "a survey on SurveyNinja". The tool is an implementation detail the client should not see. White label lets you build your own product brand on top of someone else's platform.

Corporations with mature branding. Large companies require a unified style at every customer touchpoint. A link to a third-party service in a service-quality survey breaks brand standards. A custom domain and design remove that dissonance.

SaaS resellers. Companies that resell a platform's functionality as part of their own product. The client pays the reseller and sees the reseller's brand — they do not know, and do not need to know, that a specific provider stands behind it.

Educational platforms. Tests and surveys are embedded in a learning environment. A student takes a test inside the platform's ecosystem — jumping out to a third-party domain destroys the sense of a single product.

White label vs. design customization

These are different levels of personalization. Design customization means changing colors, logo, and fonts within the platform's standard domain. Even so, the survey still lives on the provider's domain and may carry its branding in system elements.

White label goes further: it removes any trace of the platform — domain, logo, mentions in emails and screens. This is critically important when the client or respondent must not be able to tell which tool is being used.

An intermediate option is "no logo" or "remove branding": the platform removes its logo, but the domain stays its own. It is cheaper than full white label and covers part of the task.

Technical requirements for a custom domain

Connecting your own domain takes several steps on the client's side:

  1. Having a domain or subdomain you can configure (usually a subdomain: survey.company.com)
  2. Access to the domain's DNS settings to add a CNAME record
  3. Setting up an SSL certificate — either automatically through the platform or manually
  4. Verifying that the configuration is correct in the platform's panel

The process takes anywhere from a few hours to a day, depending on DNS propagation time. Once configured, all of the account's surveys (or those of a specific project) open on the custom domain.

Example: an agency on white label

A research agency runs 12 clients. For each one a separate account is set up in white label mode: custom subdomain, brand colors, the client's logo. The client receives a link like survey.clientbrand.com/s/abc123, and result emails arrive from [email protected]. Respondents see only the client's brand.

Meanwhile the agency manages every survey from a single platform panel — standard tools for creation, logic, and analytics. White label hides the tool from the client's audience but does not change the researcher's workflow.

White label and data security

White label is about appearance, not data storage. Responses are still stored on the platform's servers unless on-premise or a private cloud is used. For clients with data-localization requirements (financial institutions, government bodies, healthcare), white label solves only the visual task — the question of data storage is handled separately through on-premise deployment.

If a client requires both white labeling and hosting data on their own servers, that is already on-premise with a custom domain: the fullest level of control, but one that requires their own infrastructure.

White Label in SurveyNinja

White label is available on the relevant SurveyNinja plans. It includes: connecting your own domain through custom domain setup, full control over the look and feel through appearance settings — logo, colors, fonts, backgrounds, and removing the platform's branding. For enterprise clients with infrastructure requirements, on-premise and private cloud options are available.

White label is when the platform works as an invisible mechanism behind the facade of your brand. A custom domain, branded design, the absence of someone else's logos — all of it creates a single user experience in which the tool is unseen and only the client's brand is visible.

Frequently asked questions

Is a custom domain mandatory for white label?

Technically no — you can remove the platform's logo and change the design while keeping the standard domain. But for full white label a custom domain is essential: the URL is visible everywhere — in the address bar, in mailing links, in QR codes. Without your own domain, the client or respondent will easily see which platform is being used.

How long does it take to connect a custom domain?

From a few hours to a day after adding the CNAME record in DNS. Adding the record itself takes 5–10 minutes if you have access to the domain control panel. The SSL certificate is usually issued automatically within a few minutes after DNS is configured correctly.

Can you set up different white label settings for different surveys in one account?

It depends on the platform. In most systems white label is configured at the account or project level: all of a project's surveys get the same domain and design. For an agency's different clients, separate accounts or workspaces are usually created — each with its own white label.

Does white label affect survey analytics and data?

No. Changing the domain and design does not affect data collection, survey logic, analytics, or export. All responses are collected and stored just as they would be without white label. The only thing that changes is the visual layer the respondent sees.

Are white label and on-premise the same thing?

No. White label is about appearance: it removes the platform's brand from the interface, while the data is still stored on the provider's servers. On-premise is about infrastructure: the platform is deployed on the client's servers, and the data never leaves their perimeter. You can use both approaches at once — on-premise with a custom domain and branded design.

1