Privacy Policy

1. Minimal-data principles

Oculve is designed so the service can be used with a minimal account identifier rather than a real-name profile.

This policy covers customer-portal, billing, and voluntary support or reporting data. It does not turn VPN use into a customer dossier.

2. Data we may process

We keep account data narrow and tied to a specific operational purpose.

• Access code or account identifier
• Current plan, remaining time, and entitlement state
• Aggregate traffic counters needed to enforce plan limits, if your plan has a quota
• Device authorization records such as HWID or equivalent identifiers needed to manage active devices
• Payment confirmation references from processors
• Messages and contact details you choose to send to support, abuse, or security channels
• Optional analytics and performance events only after explicit consent

3. Data we do not keep

We do not keep browsing history, DNS query history, traffic content, destination history, or retrospective per-session activity logs.

We do not build advertising profiles, sell customer data, or require your legal name, physical address, or phone number for ordinary service use.

4. Limited operational measurements

To show account status and enforce plan limits, we may process coarse account-level measurements such as total bytes used, registered-device state, and last device activity visible in the dashboard.

These measurements are not a record of which sites you visited, who you communicated with, or what content you transferred.

5. Payments and processors

Payment processors handle card or crypto settlement under their own terms. We do not store full card numbers or card security codes.

For billing support, we try to work from the minimum needed transaction reference, amount, and approximate payment time.

6. Deletion and reset

Removing or resetting a device deletes the active device authorization record associated with that device from the active control plane.

Closing an account deletes portal-visible account data and active device mappings from our active systems, except for the limited records we must keep for settlement, dispute defense, or legal compliance.

7. Retention

Access and entitlement records are kept while the account is active. After closure, Oculve does not retain traffic, browsing, DNS, device-activity, or user-linked archive records.

If you used a separate payment provider, that provider may keep its own transaction records under its own policy. Oculve's position is that closed accounts should not remain as a user history archive.

Support, abuse, and security correspondence is kept only if you created that record and only for as long as needed to resolve the matter, document the result, or defend against repeated misuse.

Consent choices for optional analytics are stored in browser storage until you change them or clear your browser.

8. Disclosures

Because we do not keep traffic or browsing logs, we cannot hand over records we never created.

If a valid legal request reaches us, the only data available for disclosure is the limited account, billing, or correspondence data actually retained.

9. Analytics and storage

Essential storage is used for sign-in, language, consent state, and service continuity.

Optional analytics and performance telemetry are off by default and load only after you actively opt in. Refusing them does not reduce access to the core service.

10. Your choices and contact

Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability, or information about retained records and recipients by contacting [email protected].

You do not need to send more identifying information than is reasonably necessary for us to verify and answer your request.

For EEA, UK, or Switzerland users, this includes the rights generally associated with GDPR Articles 13 through 22. For users in Turkiye, requests may also be evaluated within the scope of KVKK Articles 10 and 11.