White label โ custom domain, branding, and CSS
Remove Pivra branding, use your own domain, restrict embed domains, and apply safely scoped CSS.
Updated 8 Oct 2026
What's included in white label
Available on Pro and Business plans:
| Feature | What it does |
|---|---|
| Remove branding | Hides "Powered by Pivra" from the widget footer |
| Custom CSS | Override widget styles with your own CSS |
| Custom domain | Serve the chatbot page on chat.yourdomain.com |
| Allowed domains | Restrict which sites can embed your chatbot |
Remove Pivra branding
- Go to Settings โ White Label
- Toggle Remove "Powered by Pivra" branding on
- Save
The "Powered by Pivra" text in the widget footer is immediately hidden.
Custom CSS
In Settings โ White Label โ Custom CSS, paste CSS that targets widget elements. The CSS is injected after default styles, so your rules override them.
Target these stable class names. They are kept across widget updates; other class names inside the widget can change without notice.
| Class | What it is |
|---|---|
.pivra-widget | The whole chat window |
.pivra-header | Header with your logo, name and status |
.pivra-intro | Introduction shown before the visitor's first message |
.pivra-messages | The conversation area |
.pivra-composer | Message box and send button, with the footer |
.pivra-footer | "Powered by" line (hidden on white-label plans when branding is off) |
The launcher button on your website (.pivra-launcher) is outside the chat window, so style it from your own site's CSS rather than here.
Example โ a darker header and square corners on the message box:
.pivra-header {
background-color: #1a1a2e !important;
color: #ffffff !important;
}
.pivra-composer textarea {
border-radius: 0;
}
For safety, Pivra removes markup (anything with <), @import rules, expression(, javascript: and similar script-like values when you save, and again when the widget loads.
Changed in October 2026: the widget was redesigned. Rules written against older internal class names may no longer match; move them to the class names above.
Pivra does not accept arbitrary JavaScript injection in the widget. Add analytics to the customer website through its normal, reviewed tag-management process.
Custom domain setup
Prerequisites
- Access to your domain's DNS settings
- A subdomain you want to use (e.g.
chat.yourdomain.com)
Step 1 โ Set the domain in Pivra
- Go to Settings โ White Label โ Custom domain
- Enter your subdomain:
chat.yourdomain.com - Save
Step 2 โ Add a CNAME record
In your domain registrar's DNS settings, add:
| Type | Host | Value |
|---|---|---|
| CNAME | chat | embed.pivra.ai |
(If your registrar asks for the full domain, use chat.yourdomain.com. with a trailing dot.)
DNS propagation can take up to 24 hours.
Step 3 โ Verify DNS
Back in Settings โ White Label, click Verify DNS after propagation. If successful, the check shows โ with the resolved CNAME.
Step 4 โ Contact support to finalise
Once DNS is verified, email support@pivra.ai with your domain. We add it to the CDN so traffic routes correctly. This is a manual step and is completed within 1 business day.
Allowed domains
Restrict which websites can load your chatbot using the Allowed domains field:
yourdomain.com, app.yourdomain.com, staging.yourdomain.com
Leave blank to allow any site. Subdomains of a listed domain are included. Useful if you want to prevent other websites from embedding your chatbot.
The list is checked against the page your chatbot is embedded in (the widget reports that page's address), so it works with the standard embed and a custom domain. Two limits to know:
- It stops other websites from showing your chatbot. It does not block someone calling the chat API directly.
- Visitors using Firefox on a site that sends no referrer (
Referrer-Policy: no-referrer) cannot chat while the list is set, because the browser does not reveal the page's address.
Was this helpful?
If you have questions or suggestions, email us at support@pivra.ai .