Trust center
How the network is sourced, what we log, and what we do when something goes wrong. Practices written down, rather than badges.
Where the IPs come from
Residential IPs come from upstream residential proxy providers we contract with. We import them into our gateway, check their health every minute, and resolve every destination name at the gateway, refusing private and reserved addresses before a provider is asked for anything.
ISP and datacenter IPs come from providers too, or from proxies we operate ourselves, and they are dedicated: no other ScalarData customer uses the IPs allocated to your account while you hold them. We do not enroll end-user devices or run an SDK.
What we log, and for how long
Enough to bill you, keep the network healthy and answer an abuse report. Nothing about what your requests contain.
- Connection log
- Per hour: which proxy user connected from which client IP to which destination host and port, through which upstream (and the session name sent to it), how many times, and the first and last time. Kept 30 days for abuse handling, also after the account is deleted.
- Daily usage
- Bytes, requests, successful connections and connect time per proxy user, network and city. Billing and the usage page read it; it is deleted with the account.
- Request content
- Never stored. No bodies, page contents, cookies or the credentials you send to third-party sites. HTTPS traffic is relayed without being decrypted.
- Account and billing
- Deleted when you delete the account, except the balance ledger, the dedicated-IP history and the admin audit log, which we keep for reconciliation and abuse handling, the fingerprints of the cards that verified the free credit (so that a card unlocks it once), the connection log above, and the billing records Stripe, Heleket and tax law keep.
- Upstream proxies
- Address, encrypted credentials, health and the exit IP our probe last saw.
Abuse and legal requests
Anyone can report abuse to [email protected]. We acknowledge the report, match the time, destination and the upstream session in the report against our connection log (kept 30 days), and act on what we find: a warning, or closing the account. The reporter hears the outcome. Network operators can ask us to stop routing to their IP ranges; we block connections to those ranges, by address or by hostname.
Requests from law enforcement are reviewed by a person before anything is released. We respond to valid legal process in the jurisdiction that applies to us, provide the minimum the request requires, and notify the affected customer where the law allows. Because we do not store content, what we can provide is limited to the metadata described above.
Security practices
What we do, in plain terms. We will publish audit results here when we have them, and not before.
- Encryption in transit. The dashboard and the API run over TLS. Proxy credentials reach the gateway in clear text, as with most proxy services; use IP whitelisting where that matters. HTTPS you send through the proxy stays encrypted end to end.
- Credentials at rest. Accounts have no password: you sign in with a link sent by email, or with Google where it is enabled. An API key is stored as its SHA-256 hash plus the first few characters the dashboard shows, so the full key cannot be recovered and is shown only once. Proxy passwords are stored encrypted, and payment details are held by our payment processors (Stripe, Heleket) rather than by us.
- Access control. Admin access is a role granted by a script, checked on every request, and every admin change is written to an append-only audit log.
- Change management. Infrastructure is defined in code, CI runs the web app's typecheck, lint, tests and build on every pull request and every push to main, and dependency updates are proposed every week.
- Monitoring. The gateway and the usage worker expose health checks and metrics, and the status page updates every minute.
- Incident response. Customers affected by a security incident are told without undue delay.
- Vulnerability reports. Send them to [email protected]. We acknowledge every report, fix what is confirmed, and credit reporters who want to be credited.
The documents
Everything referenced on this page, in one place.
Read it all, then send a request.
The rules are published so you can check them before you sign up. If something is missing, [email protected] reads every message. ScalarData accounts start with $3 of free credit, unlocked with a $1 card payment, added to your dollar credit, or a crypto payment of $5 or more.