Mobile app privacy

Account and existing plans

We process your account identifier, email address and optional display name to authenticate you and check access to your purchased plans. Plan identifiers, assigned proxy endpoints, traffic allowances and expiry dates are used to configure and authorize connections. Sign-in tokens are stored in protected device storage.

Sign-in opens your browser. If you choose an identity provider, it handles that sign-in and returns the account details needed by QuanticData. Browser sign-in has its own website cookie choices. The native app does not include advertising or a payment checkout.

VPN and connection data

On Android the app uses VpnService to route other apps' traffic, including background traffic, through the proxy you select. The app asks for your agreement and the system VPN permission before connecting. The connection between your device and the QuanticData gateway is encrypted.

The gateway processes your source IP, destination addresses, DNS requests and network traffic needed to forward the connection. The proxy provider for the selected plan processes that traffic to deliver the connection. Internet destinations receive the traffic you request through the proxy. Transport through a proxy does not make an unencrypted website request encrypted to its destination.

The gateway application does not store browsing payloads or build a browsing-history database. Infrastructure access and security logs are separate: requests to the app API can include a source IP, time, requested API route and outcome. These records are used for operation, rate limiting and abuse prevention. We do not sell your VPN traffic or use it to target advertising.

Connection checks process the proxy's exit IP and response time. IP locality is an estimate derived from an IP database; it is not your phone's GPS location. No GPS permission is requested. The locality lookup uses a database on our server, rather than sending each IP to the database publisher.

You can disconnect in the app. With tunnel protection enabled, a failed proxy may leave Internet traffic blocked until you disconnect. Your device may then use its normal Internet connection.

Profiles, history and shared workspaces

Saved profiles, preferences and recent connection-quality history are stored on your device. History can include exit IPs, response times and interruptions. Workspace names, selected plans and endpoints, targeting, membership and invitations are stored on QuanticData's servers to make sharing work.

When you invite someone or accept an invitation, the workspace configuration and relevant account identity become visible to its authorized members. Owners can revoke access. Do not include sensitive information in a workspace name.

Optional features and support

Optional diagnostic and usage collection requires a separate choice in Account and an available server feature. Such events contain technical codes, app version and limited interaction information, rather than passwords, proxy credentials, page contents or browsing destinations. Controls may be unavailable in the beta; no events are sent merely because a control is displayed.

Remote notifications also require an available service and your opt-in. If enabled, installation identifiers, notification preferences and push tokens are processed by QuanticData, Expo's push service and the platform delivery service, such as Firebase Cloud Messaging on Android. Service and promotional preferences are separate. The local Android connection notification does not require remote push registration.

You can preview a diagnostic summary and choose whether to share it. Opening an email draft does not send it. Messages you send to support, including deletion requests, are processed to resolve your request. Optional external browser tests, such as DNS or WebRTC checks, send network information to the test website only when you choose to open it.

Retention and deletion

• Account and workspace data remain while needed to provide your account, until you remove them or a verified deletion request is processed. Required billing, dispute and security records are handled separately.
• Local connection history is bounded to seven days and 80 events per history, with a limit on stored histories. Profiles remain until removed or the app's local data is cleared.
• Traffic forwarding is processed during the connection. The gateway does not persist browsing payloads. API access logs rotate daily with 14 rotated files retained; security incident evidence can be retained longer while an incident or legal obligation is unresolved. System service logs are also limited by system storage capacity, rather than a guaranteed maximum number of days.
• Invoices and payment or dispute records may be retained for statutory accounting and legal obligations after account deletion. We restrict their use to those obligations. Support explains applicable retained records when handling a deletion request.

Uninstalling the app does not delete your QuanticData account. Request account and associated data deletion without installing or signing in to the app.

Purposes, service providers and your rights

We process account and connection data to perform our service contract; security data for legitimate interests in keeping the service safe; optional marketing or analytics under your consent; and statutory records to meet legal obligations. Service providers include hosting and network infrastructure, authentication and email services, proxy network operators and, when enabled, notification delivery services. We may disclose records where required by law. For international processing, applicable contractual and legal safeguards are used.

You may request access, correction, export or deletion, withdraw optional consent, or object to or restrict processing where applicable. Contact hello@quanticdata.io. You may also complain to your data protection authority. The service is intended for business and professional use, not children under 16. We update this page when app processing changes.