1. Who we are
FLEETPROXY ENTERPRISE - FZCO operates FleetProxy for individual and business customers. This policy explains how personal information is handled when you visit our website, use your account or contact us. FleetProxy services are for people aged 18 or over.
2. Information involved
Account and service forms collect information you provide, including your name, email address and authentication information. Support conversations contain the information you send us. Please avoid including information that is unnecessary for your request.
Our website and dashboard send visitor and activity information to FleetProxy, including a visitor identifier and pages visited. Website tracking also sends referrer information, URL query parameters, device category, browser language and interaction information such as selected actions, time on a page and scroll depth.
The dashboard supplies Intercom with account identifiers, name, email address and account creation time for support/chat.
FleetProxy does not currently carry out KYC identity verification.
3. Purposes and recipients
Information is used in connection with your account, purchased services, support and website operation. Our integrations include OVH for hosting, Intercom for support/chat and Google analytics services. Other integrations include Stripe payment services, hCaptcha and Google/GitHub sign-in options.
4. Lawful requests
We may disclose relevant personal data we hold to law enforcement or other competent authorities in response to valid legal requests, where required or permitted by applicable law. Relevant records may be preserved where legally required.
5. Your requests and preferences
Contact support@fleetproxy.io or any official FleetProxy contact channel with a privacy question or a request concerning your personal information. Rights concerning access, correction, deletion and other uses of personal information depend on applicable law. Some records may need to be retained where the law requires this.
Where applicable law provides these rights, you may request access, correction, deletion, restriction or portability of your personal data, object to processing, withdraw consent where processing is based on consent, or complain to a competent supervisory authority.
Email preferences are available in Settings → Email notifications. Save your changes to submit your selected preferences.
6. Cookies and policy information
Our Cookie Policy explains browser storage and the controls available on this website. Acceptance of our Terms of Service is not blanket consent to optional cookies, marketing or every use of personal information.
Updates to this policy are posted on our website with a revised date. Continued use of the service does not by itself provide consent to a new processing purpose.
7. FleetProxy Browser Extension
This section covers the FleetProxy Extension for Chrome, Brave and Firefox.
No account, analytics or tracking. The extension has no sign-in, no analytics, no advertising and no tracking. It does not send your data to FleetProxy.
What is stored on your device. Your saved proxies (addresses, ports, labels, usernames and passwords), your Split Tunnel rules and your settings are kept in your browser's extension storage. They are not synced or uploaded. When the browser supports it, they are encrypted on your device with AES-256-GCM and a device key that cannot be exported. Short-lived connection records (for example recent status messages, host names of sites the proxy could not reach, and the address of a page the Kill Switch blocked) are kept in browser-session storage and cleared when the browser closes. The extension does not keep a browsing history and never reads page content.
Your proxy provider. When you connect, your browser traffic and your proxy login go to the proxy server you chose. That is FleetProxy only if you use FleetProxy proxies. The extension answers a login request only from the exact proxy server you selected, never from a website.
Checks you start. These run only when you start them:
- Check IP contacts api.ipify.org to show the proxy's exit IP. https://www.ipify.org/
- IP details and the identity check can contact IPinfo (ipinfo.io), which returns an approximate location and network for the exit IP. https://ipinfo.io/privacy-policy
- The identity check's optional WebRTC test (unticked by default) contacts Cloudflare's STUN server. If WebRTC protection is off, Cloudflare can see your device's public IP address. https://www.cloudflare.com/privacypolicy/
- Diagnose (Chrome and Brave) sends one plain HTTP request to api.ipify.org through your proxy, after you confirm.
These services see the request from the proxy's exit IP and normal request details such as the time and browser type. They never receive your proxy passwords, browsing history or cookies. Results are not sent to FleetProxy.
Backups and exports. Backups can be encrypted with a passphrase you choose, which FleetProxy cannot recover. Copy and Export put proxy details on your clipboard or in a file only when you click them. The extension never reads your clipboard. Imported FoxyProxy and SwitchyOmega files are read on your device and are not uploaded.
Your controls. You can edit or delete saved proxies at any time. Settings > Reset extension removes saved proxies, settings, rules and the device key. Uninstalling the extension removes its storage. Backups you exported stay wherever you saved them.
Sharing and Limited Use. We do not sell extension data, use it for advertising, or share it with anyone except as described above: your proxy provider receives your proxied traffic and proxy login, and ipify, IPinfo and Cloudflare receive only the checks you start. The use of information received by FleetProxy Extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the extension's proxy features. It is not used or transferred for unrelated purposes, or to determine creditworthiness or for lending.
Children. The extension is not directed to children under 13.
Changes. If the extension's data handling changes, we will update this section before the change is released.

