White-label data collection means your client receives the data under your brand, on your terms, with your name on the invoice. They do not contract with the infrastructure underneath, they do not see it, and in most cases they do not want to.
That arrangement is straightforward commercially and it changes your obligations more than most agencies expect. The moment you put your brand on a dataset, you stop being a company that uses a proxy network and become the data provider of record. Reliability, provenance, compliance and continuity all become yours to answer for.
This guide covers what that means in practice and how to structure one account to carry many clients without them ever touching each other.
One account means one login, not one shared budget
Worth settling immediately, because the phrase is ambiguous and the wrong reading causes real damage.
What works: one Shifter account for your agency, one login, one vendor relationship, one place to see everything, with each client separated underneath it, by its own plan and workspace or by its own sub-account on a shared plan.
What does not work: every client’s collection running through a single shared plan with nothing to tell the clients apart. That version cannot tell you what each client cost, lets one client’s spike consume another’s allowance unnoticed, and makes offboarding a manual disentangling exercise.
The mechanics of the first arrangement, workspaces, roles, sub-accounts and per-plan usage, are covered in sub-accounts and usage tracking for multiple clients. The short version: a plan per client where budgets must be kept apart, a sub-account per client where they share a plan, and a workspace per client wherever billing or client access justifies it.
Selling finished data vs reselling proxy access
Two businesses get called white-label, and they carry different obligations.
Selling finished data. Your client buys a report, a feed or a dashboard. The proxy network is part of your production process, the same as your servers. Everything in this guide is about this model.
Reselling proxy access under your own brand. Your client buys the ability to send their own traffic, and you are the provider they see. Here you need per-customer usage figures, your own limits and billing, and a clear acceptable use policy that your customers agree to. Shifter’s reseller program is built for this: sub-accounts track each of your customers’ traffic in the panel and over the API, and you set prices, limits and billing on your own platform.
Many agencies start with the first and add the second when a client asks to run their own jobs. Keep the two apart in your accounts and contracts, because the responsibilities differ.
What you take on when your brand goes on the data
Five things move onto your side of the line.
Reliability. Your client’s report is due whether or not a portal changed its markup last night. You need monitoring, alerting and a fallback plan, because “our supplier had an issue” is not a sentence a white-label provider gets to use.
Provenance. When a client disputes a number, you have to be able to say where and when it was observed. That means every deliverable carries the market, the vantage point, the timestamp and the collection method. The case for treating that as a first-class field is in the vantage-point standard.
Compliance. Your client’s obligations do not stop at your brand. If they are a data controller and you are processing on their behalf, the responsibilities flow to you.
Continuity. If you lose a source, a market or a contract, the client experiences that as your outage.
Support. You are first line. Your client asks you why the number moved, and the answer cannot be a forwarded ticket.
None of this is a reason not to white-label. It is a reason to price it properly, which is covered below.
Provenance fields every deliverable should carry
A deliverable that can be defended carries a few fields next to every value. One example row from a price-monitoring feed:
| Field | Example |
|---|---|
| Value | 49.99 |
| Currency | EUR |
| Source URL | retailer.example/product/123 |
| Market | Germany |
| Vantage point | Residential exit, Berlin, consumer ISP |
| Observed at | 2026-10-21 09:14 UTC |
| Collection method | HTTP request, sticky session, parsed from product page |
| Client | acme |
Your brand goes on the cover; these fields go underneath. When two clients in the same category ask why their numbers differ, the vantage point and the timestamp are usually the answer.
Compliance does not disappear behind your brand
This is the part most often missed, and the one most likely to surface in a client’s procurement review rather than in your own planning.
If your client is a controller and you are a processor, your data processing agreement will usually require you to disclose subprocessors and to give notice before changing them. Infrastructure you rely on to collect the data can fall within that definition. White-label branding is a commercial arrangement, not a legal shield: it does not remove a disclosure obligation your contract creates.
Two practical consequences. Read your client DPAs before signing them to check what they say about subprocessors, notice periods and audit rights, because those clauses determine how freely you can change your own stack. And keep a current internal record of what your collection depends on, so that when a client asks, the answer takes minutes rather than a week. Larger clients will also send a vendor questionnaire; the questions to expect, and the answers to have ready, are in the security questionnaire your InfoSec team will send a proxy vendor.
Related, and frequently conflated with it: where a request exits is not where your data is processed or stored. A client asking “is our data in the EU” is asking about your pipeline, not about your exit locations. That distinction is set out in data residency is not proxy location, and it is worth understanding before a client asks rather than during the call.
How to structure the agency account
The operational setup is short, and following it exactly is what makes everything downstream easy.
- Give every client its own plan or its own sub-account. A separate plan keeps budgets apart. A sub-account is a label in the proxy username that splits one plan’s traffic by client, reported separately in the panel and over the API, but it shares the plan’s bandwidth and sets no limit of its own. Never run a client’s jobs without one or the other.
- Add a workspace per client where it earns its place. Clients who want their own billing relationship, want visibility into their own usage, or are large enough that their overage should not draw on a shared wallet. Everyone in a workspace sees everything in it, so a client contact only ever belongs in their own workspace.
- Separate credentials per client. Store them per client in your secret manager, give each client’s jobs only that client’s plan or sub-account, and never borrow one client’s to finish another’s job quickly. That single shortcut is how attribution silently breaks.
- Prefix session IDs by client.
sid-acme-listings-04costs nothing and makes your own debugging readable. - Record the vantage point per deliverable, using the fields above.
With the Shifter gateway, the client, the market and the session all live in the credentials against p.shifter.io:443:
customer-USERNAME-subaccount-acme-country-de-city-berlin-sid-acme-de-07-ttl-600:PASSWORD
Omit sid for independent requests and the gateway rotates per request; include it to hold one exit across a multi-step job, with ttl setting how long. The trade-off is in sticky vs rotating residential proxies.
Price the deliverable, not the gigabyte
The most common white-label pricing mistake is reselling bandwidth at cost plus a margin, to clients who are not buying bandwidth. Your client is buying a report, a feed or a dashboard. They have no way to evaluate a per-gigabyte price and no interest in learning.
Price per deliverable, and manage your own margin on the metric that actually drives cost: gigabytes per usable record. A workflow that transfers less but returns blocked or geographically wrong data is more expensive per delivered record than a heavier one that works.
Three habits protect the margin. Review consumption per client weekly rather than at invoice time. Treat a scope change as a scope change, since clients routinely add markets or frequency in an email without expecting a price conversation. And decide in advance, per client, whether overage should flow or the job should pause.
Continuity and offboarding
Plan both before you need them.
For continuity: monitor collection success per client per source, so a degrading source is visible before the client notices. Know which of your deliverables depend on a single source, because those are the ones that break hardest.
Offboarding should be a checklist, not an investigation:
- Retire the client’s credentials and sub-account label from every job.
- Close or transfer the client’s plan.
- Remove the client’s people from the workspace, or leave their workspace if they own it.
- Hand over or delete historical data as the contract says.
If a client owns their workspace, most of this is their action, which is a further argument for that structure with larger accounts.
FAQ
Can I run several clients on one plan if they are small?
Yes, if each client has its own sub-account. The panel and the API then report each client’s traffic separately. What a shared plan cannot do is cap one client’s usage, so a spike from one still draws on the bandwidth the others share. Give clients with large or unpredictable volumes their own plan.
Do I have to tell clients which infrastructure I use?
That depends on your contract rather than on your branding. Many client DPAs require subprocessor disclosure and notice of changes. Check the agreements you have signed.
How many clients can one agency account carry?
One login can belong to many workspaces, switching from the sidebar. The seat limit applies per workspace, not to the number of workspaces you work across.
What should appear in a white-label deliverable?
The data, plus enough provenance to defend it: market, vantage point, observation timestamp and method. Your brand goes on the cover. The method still has to exist underneath it.
What is the difference between white-label data and reselling proxies?
White-label data means you sell finished data under your brand and the network stays part of your production process. Reselling means your customers send their own traffic through access you provide, so you need per-customer usage tracking, your own limits and billing, and an acceptable use policy.
Can my clients see that I use Shifter?
Not through your deliverables. Clients only see Shifter if you invite them into a workspace or give them credentials, which is why client contacts should only ever join their own workspace.
How do I bill each client for collection?
Use each client’s plan, or each client’s sub-account on a shared plan, as the usage figure, and price the deliverable on top of it. Review usage per client weekly so the invoice holds no surprises.
What happens to a client’s data when they leave?
Whatever your contract says. Agree it at signing: hand over, keep for a set period, or delete. Then follow the offboarding checklist above.
The bottom line
White-labelling is a promise that the data is yours to stand behind. Structure the account so that promise is cheap to keep: one agency login across many workspaces, a plan or a sub-account for every client, credentials and session identifiers separated per client, and provenance attached to every deliverable.
Then price the deliverable rather than the gigabyte, watch usage per client weekly, and read your client DPAs before your stack changes rather than after. The network itself is on the residential proxy network page.