1. Scope of This Policy
This Privacy Policy applies to information processed in connection with the Proxly mobile app, website, help requests, subscription management, service delivery, product analytics, and operational security. It is meant to describe what categories of information may be processed, why they are processed, how they may be shared, and what choices users generally have.
Because Proxly is a VPN product, we aim to be especially careful about clarity. Users reasonably expect privacy-focused tools to explain what is and is not collected, how connection-related operations work at a high level, and how support and billing data are handled separately from routine use of the core service.
2. Information You Choose to Provide
Some information is provided directly by you. For example, you may submit your name, email address, message content, or billing context when you contact support, ask a product question, request help with a subscription, or report an issue. If the app later introduces account-specific recovery, waitlist, or support features, you may also choose to provide identifiers needed to complete those requests.
We use this information to respond, troubleshoot, maintain service records, improve support quality, and follow up on requests you initiated. We ask that users avoid sending unnecessary sensitive information through contact forms or email.
3. App, Device, and Operational Data
Like most mobile services, Proxly may process limited technical and operational data needed to deliver the app and keep it stable. Depending on the feature and environment, this may include app version, device model, operating system version, preferred language, coarse region, crash events, performance diagnostics, subscription status signals, feature state, or anti-abuse indicators.
In a VPN environment, operational systems may also need to process connection-related metadata sufficient to establish sessions, route traffic, prevent abuse, monitor server health, manage capacity, detect failures, and investigate service incidents. Proxly is designed to minimize collection of information that is not reasonably needed for those purposes.
This policy is written to describe categories of processing at a practical level. If the product later makes more specific no-logs or logging-minimization claims in marketing or in-app disclosures, those claims should remain consistent with actual operations and with this policy.
4. Information Related to Purchases and Billing
If you buy a subscription, start a trial, restore a purchase, or request billing help, Proxly may receive transaction status, plan tier, renewal state, order identifiers, country or storefront information, and similar purchase-related signals from the payment platform or app store managing the transaction.
We generally use billing-related information to activate access, validate subscription status, answer support questions, address abuse or fraud, and maintain internal records. Sensitive payment card details are typically handled by the payment provider or app store, not by the website pages used for the landing experience.
5. How We Use Information
Proxly may use information for the following business and service purposes:
- Providing and maintaining VPN connectivity and related app features.
- Authenticating purchases, restoring entitlements, and managing subscription access.
- Monitoring service reliability, crash behavior, latency, outages, and infrastructure health.
- Preventing abuse, spam, fraud, automated misuse, or attacks against the service.
- Improving onboarding, usability, support quality, and product performance over time.
- Responding to support inquiries, refund requests, or account-related questions that you submit.
- Meeting legal, regulatory, tax, security, or compliance obligations where required.
6. What We Do Not Intend This Policy to Permit
Proxly is positioned as a privacy-oriented service, so this policy is not intended to quietly authorize broad repurposing of user information for unrelated advertising, hidden profiling, or resale of browsing behavior. We do not write this page as a blanket permission slip for unlimited collection.
Instead, the policy is meant to describe a restrained operating model: use the least amount of information reasonably needed to run the app, secure the infrastructure, manage subscriptions, and help users who request assistance.
7. Sharing of Information
We may share information with third-party providers that help us operate the service, but only where reasonably necessary for the role they perform. Depending on the stack in use, this can include hosting providers, analytics vendors, customer support tools, email services, crash-reporting vendors, payment or subscription processors, infrastructure security vendors, and app store operators.
We may also share information:
- When required by law, regulation, subpoena, court order, or other valid legal process.
- When we believe disclosure is reasonably necessary to protect users, investigate abuse, or defend the service.
- In connection with a merger, financing, asset sale, acquisition, or other business restructuring, subject to applicable confidentiality and data-handling expectations.
8. Data Minimization and Retention
We aim to retain information only for as long as it is reasonably needed for the purpose for which it was processed. Retention periods may vary depending on whether the information relates to service operations, crash diagnostics, subscription handling, customer support, legal requests, fraud review, or recordkeeping.
Some information may be deleted on short cycles, while other records may be retained longer where needed to enforce agreements, resolve disputes, detect misuse, satisfy accounting obligations, or comply with applicable law. When information is no longer reasonably needed, we aim to delete it, anonymize it, or otherwise de-identify it where appropriate.
9. Permissions and Device Controls
The app may request device permissions that are relevant to specific features, such as notifications for service messages or account-related reminders. Any permission prompt shown by the app should relate to an understandable feature purpose, and users can generally manage those permissions through device settings.
Denying a permission may affect how a feature works, but users should not be forced into granting permissions that are unrelated to the core function being requested.
10. Security Measures
We use administrative, technical, and organizational safeguards designed to protect data against unauthorized access, misuse, accidental disclosure, alteration, or destruction. These may include access controls, separation of responsibilities, infrastructure monitoring, credential management, service hardening, and restricted support workflows.
No internet or mobile system can be guaranteed to be perfectly secure. Users should also protect their own devices, app store accounts, passwords, and recovery channels, because product security works best when provider controls and user hygiene reinforce each other.
11. International Use
Proxly may be used from different countries and may rely on vendors or infrastructure that operate across jurisdictions. As a result, information may be processed in locations where privacy rules differ from the place where you live. Where cross-border processing occurs, we aim to use safeguards that are appropriate for the service and the legal frameworks that apply.
12. Your Choices and Requests
Depending on where you live and how the service is structured, you may have choices related to permissions, marketing communications, support submissions, diagnostics participation, or deletion and access requests. We encourage users to review device controls, app store settings, and any in-app privacy controls that may be offered.
- You can stop using the app at any time by uninstalling it.
- You can manage permissions such as notifications through your device settings.
- You can contact support if you want help with privacy, billing, or data-related questions.
13. Children’s Privacy
Proxly is not directed to children and is not intended for use by children below the age threshold that applies under relevant law without appropriate authorization. If you believe a child has submitted personal information through the website or support flows, contact us so the situation can be reviewed.
14. Changes to This Policy
We may update this Privacy Policy to reflect product evolution, legal obligations, vendor changes, operational practices, or clarifications to how the service works. When we update the policy, we will post the revised version on this page and revise the effective date.
15. Contact
Questions about privacy, data handling, or this policy can be sent through the contact form on the main site: Get in Touch.