Skip to content

Privacy Policy

What we collect from customers and visitors, what we store about the proxies that carry the traffic, what we deliberately do not collect, and how to exercise your rights.

Effective date: 2026-11-03

1. Who this policy covers

This policy explains how ScalarData handles personal data about customers and their team members who use the dashboard, the API and the proxy networks, and about visitors to scalardata.ai. Section 5 describes what we store about the upstream proxies that carry the traffic. ScalarData is the controller of the data described here.

2. What we collect from customers

Account data

Name, email address, company name, proxy user names and the settings you configure in the dashboard.

Billing data

A token for your payment method (we never see the full card number), billing address, invoices and transaction history. For a card payment that puts your free credit on hold, Stripe Radar's risk level and score for that payment, which we keep with the account. For a card that verifies an account for the free credit, Stripe's fingerprint of the card (an identifier Stripe derives from the card number, not the number itself), so that each card unlocks the free credit of one account only. For a crypto payment, the Heleket invoice's identifier, amount, status and payment link and what it bought; the wallet and the transaction stay with Heleket.

Connection metadata

A connection log, per hour: which proxy user connected from which client IP address to which destination host and port, through which upstream proxy and with which session name sent to it, how many times, and the first and last time. Daily usage per proxy user, network and city: bytes, requests, successful connections and connect time. When a sign-in at the gateway fails, the gateway's log records the client IP address and the reason.

Support and website data

Messages you send to support, including through the contact form (name, work email, company, monthly traffic estimate, network of interest and message); standard server logs for scalardata.ai (IP address, browser, pages requested); and the cookies listed below.

Cookies

  • Login session. Keeps you signed in to the dashboard. Set when you log in and removed when you log out or the session ends.
  • Language (NEXT_LOCALE). Remembers the language you chose. Kept for 1 year.
  • Cookie choice (sd_cc). Stores whether you accepted or declined analytics and attribution cookies. Kept for 1 year.
  • First-touch attribution (sd_ft). Remembers where you came from, as described below. Kept for 90 days, and set only after you accept in the cookie notice.

Website analytics and campaigns

On the public website (not in the dashboard) we count visits with Umami, an analytics tool we run on our own servers, so no third party receives the data. Umami itself sets no cookies and stores no IP address, and it honours Do Not Track. For each page view it records the page's address with its campaign parameters (utm_*) only, since any other parameter, such as an advertiser's click ID, is removed before anything is sent; the page title; the referring page without its query; the browser, operating system and device type; the screen size and language; and the country, region and city, which it looks up from the IP address at the time without keeping the address. When you first arrive from a campaign link or from another site, and you accept in the cookie notice, our own first-party attribution cookie keeps where you came from for up to 90 days: the utm_* parameters, the referring site's host (not its full address), the page you landed on and when. When you ask for a sign-in link, the same details are also held for at most a day under a one-way hash of your email address (never the address itself), so that they reach your account if you open the link in another browser. If you sign up, they are saved with your account, so that we can see which campaigns bring customers and what they buy.

3. What we do not collect

We do not log or inspect the content of requests or responses that pass through the gateway. We do not store request or response bodies, page contents, cookies, or the credentials you send to third-party sites. Traffic you send as HTTPS is relayed without being decrypted. We do not build profiles of your targets for any purpose other than abuse investigation and the aggregate statistics needed to run the network, and we do not use third-party advertising trackers on the website.

4. Why we use it

  1. To provide the Service you signed up for (performance of a contract).
  2. To prevent fraud and abuse, for example with Stripe Radar, which assesses the fraud risk of card payments (our legitimate interest, and in some cases a legal obligation).
  3. To bill you and to keep accounting records (contract and legal obligation).
  4. To investigate abuse reports and respond to lawful requests (legitimate interest and legal obligation).
  5. To send service notices about your account. Marketing email is sent only with your consent, and every message has an unsubscribe link.
  6. To improve the Service, using aggregate statistics that do not identify anyone.

5. Upstream proxies

The exits that carry your traffic are proxies run by upstream providers we contract with, or proxies we operate ourselves; we do not enroll end-user devices or run an SDK. For each upstream proxy we store its address, the credentials we use with it (encrypted), its network, country and, where known, city and ASN, its health, and the exit IP address our health check last saw. For dedicated ISP and datacenter IPs we also keep the exit IP address at the time each one was allocated to an account and released from it.

We do not receive the names or any other details of the people whose connections a provider uses; what they agree to is governed by their arrangement with that provider. The sourcing page describes how upstream proxies are added and checked.

6. How long we keep it

DataKept for
Connection log30 days, also after the account is deleted, then deleted.
Daily usageWhile the account exists, then deleted with the account.
Account dataUntil you delete the account; it is deleted with it.
Balance ledger, dedicated-IP history and admin audit logKept after the account is deleted, for reconciliation and abuse handling.
Card fingerprintsKept after the account the card verified is deleted, without the link to it, so that the card cannot unlock the free credit again.
Billing recordsAs long as tax and accounting law requires.
Support messagesSupport tickets are kept with the account and deleted with it. Messages you send us by email, and the copies of the answers we email you, are kept in our support mailbox as long as we need them to handle your request. Any of them is deleted sooner if you ask.
Website and gateway server logs30 days, then deleted.
Website analytics (Umami)Kept as visit statistics for as long as we run the website; the records hold no IP address, no cookie and nothing that links them to an account.
Where your account came from (campaign)With the account, and deleted with it. The cookie that carries it until sign-up expires after 90 days, and the copy held for a sign-in link after a day.

Where data is subject to a legal hold or an open abuse investigation, we keep it until the matter is closed.

7. Who we share it with

  1. Processors. Hosting providers, our payment processors, email delivery and support tooling. They act on our instructions under contract. The current list is included with the signed Data Processing Agreement and is available on request.
  2. Upstream proxy providers. The destinations and traffic you route through the gateway, which they relay to the address the gateway resolved. Plain HTTP is readable by them; HTTPS stays encrypted end to end.
  3. Law enforcement and legal process. We disclose the minimum required by a valid request, and we notify affected customers where the law allows. Because we do not store content, what we can provide is limited to the metadata listed above. The Trust center describes how requests are handled.
  4. Business transfers. If ScalarData is acquired or merges, your data may transfer to the successor under this policy.

We do not sell personal data, and we do not share it for cross-context behavioural advertising.

8. International transfers

We operate from Estonia. The exit IPs are in South Korea, our upstream providers may process traffic elsewhere, and some of our processors are located elsewhere. Where personal data leaves the European Economic Area, the United Kingdom or Switzerland, we rely on an adequacy decision or on standard contractual clauses (with the UK addendum where relevant). Copies of the clauses are available on request.

9. Your rights

Under the GDPR and UK GDPR

You can ask for access to your personal data, have it corrected or erased, restrict or object to its processing, receive a portable copy, and withdraw consent where processing relies on it. You can also complain to the supervisory authority where you live or work.

Under the CCPA and CPRA

California residents can ask what personal information we hold and how it is used, ask for it to be deleted or corrected, and ask us not to sell or share it. We do not sell or share personal information as those terms are defined, and we will not treat you differently for exercising a right. An authorized agent may act for you with written permission.

How to exercise them

Email [email protected] from the address on your account. We may ask you to confirm your identity before acting. We respond within the period the applicable law sets, and we will tell you if we need longer and why.

10. Security

Traffic to the dashboard and API is encrypted in transit; HTTPS you send through the gateway stays encrypted end to end. Credentials are hashed or encrypted at rest, and production access is limited to the engineers who need it. The Trust center lists these practices in more detail. No system is perfectly secure; if we learn of a breach affecting your data we will tell you without undue delay.

11. Children

The Service is not for anyone under 18, and we do not knowingly collect data from children.

12. Changes to this policy

When we change this policy we update the effective date at the top. If a change materially affects how we use your data we will email the address on your account before it takes effect.

13. Contact

Privacy questions and requests: [email protected].

Read the rules, then try the network.

Every account starts with $3 of free credit, unlocked with a $1 card payment, added to your dollar credit, or a crypto payment of $5 or more. Sales can walk through any of these documents with you before you commit.