Who we are. ipvolt is operated by the individual or individuals who run ipvolt, who are the controller of the personal data described on this page. ipvolt is not yet a registered company; we will give you their names and postal address on request. Contact: hello@ipvolt.com.
Customer accounts, payments and proxy services
This section covers the customer service at ipvolt.com/beta.
Your account. We store the username we issue you, a securely hashed password, your account role and settings, a label we use to identify your account internally, and records of API keys you create (a hash of each key, its name, a short display prefix, its expiry and last use, never the full key). We do not need your name, email address or postal address to run your account. If you email us, we keep that correspondence.
Signing in. An essential session cookie keeps you signed in. It lasts at most 8 hours and ends after 1 hour of inactivity. To stop password guessing, we keep keyed hashes of the connection address and username used to sign in, and delete them after one day. The dashboard uses no analytics or advertising cookies. Alert preferences you choose stay in your browser.
Payments. When you top up with cryptocurrency, we record the invoice (amount, coin, network, rate and payment address), the blockchain transactions that pay it (transaction ID, block and amount, plus the sending address on Ethereum-compatible networks, Solana and Tron), how it was credited, and any review or refund decision. Blockchain transactions are public and permanent: we cannot change or erase what a blockchain records. To read blockchains and prices, our servers query blockchain data providers and Coinbase's public price service. Those requests contain public addresses and transaction data, not your account details.
Balance and orders. We keep a ledger of your balance, the services you order, renewals and refunds. Our infrastructure partner, which supplies the mobile devices, receives only internal reference numbers for your orders, not your username or contact details. Connection credentials for your devices are stored encrypted.
Proxy traffic. Mobile proxy traffic travels directly between you and the device operated by our infrastructure partner and does not pass through ipvolt's servers. The partner and the mobile carrier process connection data under their own policies. For metered proxies that run through our gateway, we record for each session the account, credential, protocol, start and end time and the data transferred. We do not record the websites you visit or the content of your traffic, and our application logs exclude destinations and credentials.
Why we use this data. To provide the service, handle payments and answer your messages under our contract with you; to keep the financial records the law requires and answer lawful requests from authorities, under our legal obligations; and, in our legitimate interests, to secure the service, limit sign-in attempts, prevent fraud and abuse, handle abuse reports and handle disputes. You need to give us the account and payment information above to use the service. We do not make decisions about you based only on automated processing that have legal or similarly significant effects on you.
How long we keep it. Payment, ledger and refund records are kept for as long as accounting and tax law requires, and the system is designed so that they cannot be altered. Account and order records are kept while your account is open and for up to two years after it closes, then deleted or anonymised, unless we need them for a legal claim. Server logs are kept for up to 90 days, and database backups for 14 days. Support emails are kept for up to two years after our last exchange or after your account closes, whichever is later. Abuse reports and our decisions on them are kept for up to two years.
Who receives it. Service providers that process data for us: Hetzner (server hosting in Helsinki, Finland), Cloudflare (network and security services in front of ipvolt.com, including the customer dashboard) and Namecheap Private Email (our support mailbox). Others that receive limited data and use it under their own policies: our mobile infrastructure partner (devices and connectivity), mobile carriers (connection data), and blockchain data providers and Coinbase (public blockchain and price data, without account details). We disclose data when the law requires it, or to deal with abuse under the Acceptable Use Policy.
Transfers outside the EEA and UK. Some of these providers, including Cloudflare, Namecheap, Google and some blockchain data providers, are based in or process data in the United States or other countries outside the EEA and UK. Where a provider is certified under the EU–US Data Privacy Framework (and its UK Extension), we rely on that; otherwise we rely on the standard contractual clauses in its data processing terms. You can ask us for a copy of the relevant safeguards at hello@ipvolt.com.
Abuse reports. If you report abuse, we use your report and contact details to investigate and reply, in our legitimate interest in preventing misuse of the service. We may share the relevant parts with our infrastructure partner or the customer concerned, but not your contact details unless you agree.
Your rights. You can ask for a copy of your data, for its correction or deletion, for its use to be restricted, or to receive data you gave us in a portable format, and you can object to uses based on our legitimate interests. We may need to keep financial records after a deletion request. Contact hello@ipvolt.com. You can also complain to the data protection authority where you live or work.
Affiliate applications and referrals
Affiliate applicants provide a name, email, public website or profile and a description of their audience. We use these details to review applications and operate the affiliate program. Approved affiliates also provide payout details. Account access and financial records are restricted; applications do not enroll anyone in the customer waitlist or a marketing mailing list.
A referral link asks before setting a first-party referral cookie. If you accept, it remembers the first accepted referral for the duration shown, up to 90 days. You can continue without it or clear it from the affiliate page. Optional analytics consent is separate. A new signup can be associated with the referral, and a verified customer account and eligible payments can later be linked for commissions.
Affiliates see aggregate signup counts and their own commission and payout records, not referred customers' email addresses or account details. Refunds and payout reconciliation are retained in a financial audit trail. Unconverted referral records are removed after expiry by scheduled cleanup. Affiliate sessions use an essential cookie with an eight-hour maximum and a one-hour idle timeout. For access, correction or deletion requests, contact hello@ipvolt.com; financial records may need to be retained for accounting obligations.
Early-access signups
When you join, ipvolt stores your email address, signup date, the form you used and the wording you agreed to. If you answer the optional use-case question, we store that answer too. We use this information to manage early access and send the notification described beside the form.
Submitting an email address does not automatically subscribe you to advertising or enable website analytics. Contact hello@ipvolt.com to ask about your information or request removal from the list.
Optional Google Analytics
If you accept analytics, Google Analytics helps us understand visits to our public pages, useful content and completed signups. Events can include the public page visited, campaign labels, form interactions, broad device information and approximate location. Google also receives technical connection information needed to process those requests.
We do not send your signup email, the text you type into forms, private account content or login credentials as analytics events. Advertising personalization and session recordings are not enabled by this integration.
Google processes the analytics information on its infrastructure, which may include processing outside your country. Read how Google uses information from sites that use its services.
Cookies and your choice
Analytics is off until you choose to accept it. If enabled, Google Analytics uses first-party cookies to distinguish visits and sessions. Our integration limits those cookies to up to 13 months; your browser may remove them sooner. We remember your analytics choice in this browser for up to six months.
Use the Cookie settings control to change your choice. Rejecting analytics stops future collection by this integration and removes its analytics cookies. It does not undo information already sent. Clearing browser storage also clears your saved choice. Essential server requests still take place when you load a page or submit a form.
Hosting and access
The website and signup database run on infrastructure hosted by Hetzner. The project team uses restricted application access to operate the site and manage early access. Operational security controls process connection information to protect forms and services.
When you submit the early-access form, Cloudflare Turnstile checks for automated abuse using browser and connection information. We do not include your signup email in the verification request. This security check works independently of optional analytics. Read the Cloudflare privacy policy.
Our signup limits use keyed hashes of connection addresses and normalized email addresses. These rate-limit records expire within one hour and are removed on the next request; they are separate from your signup record.
For a privacy question, contact hello@ipvolt.com. Please avoid sending passwords or other secrets.
Scraper bandwidth report viewer
The report viewer on the scraper bandwidth report page parses the scrapescope report files you choose in your browser, inside an isolated frame on the page. Those files are never uploaded: the frame cannot make network requests, and the page around it never reads the report.
If you accept optional analytics, that page records only fixed labels: that a report was opened from a file, a drop or the bundled sample and whether it parsed; that two runs were compared; that a share card was downloaded; that an install command was copied; and that the link to the homepage was used. Hostnames, byte counts, prices and file names are never sent. Without an analytics choice, nothing is recorded.
Proxy Toolkit MCP
The local toolkit package processes documentation queries and structured diagnostic fields on your machine. Do not include passwords, proxy credentials, private URLs or full logs in a prompt or tool argument. The local package reads proxy credentials only from the configuration you explicitly provide.
The local package does not send automatic usage telemetry or run a route check at startup. Your MCP client or a third-party gateway may process or retain its own requests; consult its privacy settings and policy.
The hosted toolkit processes the documentation queries and structured diagnostic fields you submit to return a result. Do not include passwords, proxy credentials, private URLs or full logs in a prompt or tool argument.
An optional local route check contacts our fixed diagnostic endpoint through your configured proxy and returns the connection address observed for that request to you. We use temporary, hashed connection identifiers for rate limits, with a 60-second expiry. We do not retain tool arguments, response bodies, proxy credentials or the returned address in toolkit operational logs; those logs contain tool name, status, duration and version information.
Calls to the MCP and diagnostic endpoints are not website Google Analytics page views.