Privacy Policy

1. Scope and operator

This policy describes data handling by the Velora Android application, package com.app.VeloraNet, for Android 8.0 and later. The technical description covers version 2.2.1 (version code 8), based on the developer's information dated November 4, 2026. Name entered when creating the application in Google Play: Velora: Network Diagnostics.

Application operator: Coalescence OÜ. Legal status and registration details: an Estonian OÜ company; registration number: [COMPANY_REGISTRATION_NUMBER]. Country and contact address: Estonia; Coalescence OÜ, Tornimäe tn 5, Tallinn 10145, Estonia (EE). Effective date specified by the owner: November 4, 2026; document version: 1.0. Until these details are completed, this text is a draft for review.

The client is free. The current version has no advertising, in-app purchases, paid features, registration, or application account. A selected VPN provider, server, network carrier, website, or Telegram service may offer separate services, including paid services. Their existence does not mean they are covered by this policy. Relationship to the Velora server service: Coalescence OÜ also owns the Velora website and provides its own VPN service. The free Android application can import configurations from both Velora and third-party providers; the server-access contract and its data processing are governed separately.

2. Profiles, subscription links, and local protection

You add configurations using an HTTPS subscription link, URI, JSON, selected file, camera QR scan, or selected image. They may contain names, server addresses and ports, UUIDs, passwords, tokens, TLS/Reality parameters, WireGuard keys, DNS settings, and routing rules. They are used to import, update, and connect to your selected server.

Saved profiles, original subscription links, their names, allowance and expiration metadata, and TCP test results are kept in private application storage protected with AES-GCM and an Android Keystore key. Required connection parameters are available to the VPN core in memory while connecting. Hardware-backed key storage depends on the device; these protections do not eliminate risks from root access, a compromised OS, or a compromised device.

Authentication parameters are used with the provider's endpoint as required by the selected protocol. Local storage does not mean that the server never receives information needed for authentication. Protocol authentication does not itself mean that all private keys are transmitted to the application developer.

3. Subscription downloads and updates

Following your action and confirmation, the application requests the HTTPS URL you provide. HTTPS redirects to other hosts may occur. Recipients receive the requested URL, including a token in its path or parameters, the IP of the applicable route, the client User-Agent, and ordinary technical metadata. Redirects may involve multiple recipients. This version does not perform regular automatic background subscription updates.

A provider may return configurations and optional Subscription-Userinfo fields: upload, download, total, and expire. The client stores them locally and displays usage, allowance, and expiration. Missing information is shown as unavailable. These values are not the client's independent measurements or verification of service entitlement. Manual updates may replace saved configurations.

4. VPN connections and traffic

After your action, an explanation of VPN use, and Android system confirmation, the application uses VpnService, a foreground service, and the sing-box/libbox core. The core processes routed application traffic on the device for transmission to the selected endpoint. You can stop the connection in the application or notification. Limited reconnection after network changes does not guarantee continuity.

Information visible to the provider depends on the configuration and may include IP addresses, connection times and volumes, destinations, and DNS context. Unencrypted application traffic may be visible on the relevant part of its route. The client does not intercept TLS or decrypt HTTPS. Websites generally see the exit IP of the route being used.

Excluded applications and direct rules may send traffic over the ordinary network. Custom JSON can define its own routing and DNS. Client-generated profiles generally use Cloudflare DoH through the proxy and system DNS to resolve the server address; WireGuard uses the first configured DNS server when provided. Importing a configuration is therefore not a guarantee that every packet is encrypted, that leaks cannot occur, or that you are anonymous. The application has no built-in kill switch; Android always-on VPN and blocking connections without VPN are separate system mechanisms.

During a session, incoming/outgoing counters and available domains, IP addresses, and destinations are held in memory. They may be incomplete because of ECH, encrypted DNS, shared IPs, and protocol behavior. They are cleared when the service disconnects and are not sent to the developer as a separate analytics transmission. Native logging is disabled in generated and imported configurations; this does not promise an absence of OS logs, provider logs, or diagnostic exports.

5. Diagnostics and network recipients

At your initiative, the application performs domain resolution, TCP/TLS address and port checks, HTTPS HEAD requests, and HTTP status, certificate, redirect, and IPv6 checks. The tested server receives the corresponding request, path and query string, source IP, and ordinary network metadata. Response bodies are not retained as diagnostic report content.

The relevant diagnostic uses Google's connectivity endpoint, connectivitycheck.gstatic.com/generate_204. DNS comparison sends the entered domain to the system resolver, Cloudflare (cloudflare-dns.com/dns-query), Google (dns.google/resolve), and Quad9 (dns.quad9.net:5053/dns-query). These recipients also receive network metadata; the visible IP depends on the route. Profile tests open TCP connections to profile servers. Sorting previously saved results makes no new requests. The IPv4/CIDR calculator runs on the device.

6. History, comparison baselines, and exports

Private SharedPreferences retain up to 100 recent diagnostic results: the address/full URL, time, DNS/TCP/TLS/HTTP/IPv6 results, IPs, certificate details, and redirects where available. The oldest records are displaced when the limit is exceeded. No calendar-based automatic deletion period is configured. You can delete individual history entries or clear history; comparison baselines are stored and deleted separately.

History and comparison baselines do not use the profiles' additional AES-GCM container. They rely on the Android sandbox and device protections. Clearing history does not delete baselines, previously generated exports, or recipients' copies.

Text exports are passed to the application you choose using Android Sharesheet. PDFs are generated in cache/exports and shared with temporary content URI access. No application-specific guaranteed PDF cache deletion period is configured. The application does not add VPN passwords or keys as separate report fields, cookies, authorization headers, or response content. However, full entered URLs and redirects may themselves contain tokens and personal information. Review a report before sharing: automatic complete anonymization is not provided. Support does not receive exports automatically.

7. Installed applications, statistics, and settings

Routing selection uses available launcher applications, their names and package names, and accessible previously selected packages. QUERY_ALL_PACKAGES is not requested. Include/exclude selections are stored locally.

If you separately enable Usage Access in system settings, the client reads Wi-Fi and mobile received/sent byte counters by UID for the preceding seven days and available application mappings. A shared UID may combine applications, and data may be delayed. These are not individual page histories or provider billing records. The current code does not send the application list or counters to an analytics server. Clearing Velora data does not remove Android system statistics.

Theme, reconnection settings, selected packages, and guide progress are local. An unsaved routing draft may survive screen recreation on the device; this is not cloud synchronization.

8. Permissions and your choices

INTERNET and ACCESS_NETWORK_STATE support network functions and connection state. VpnService/BIND_VPN_SERVICE is the system VPN mechanism with separate Android confirmation. Foreground service/systemExempted and POST_NOTIFICATIONS relate to an active connection and its notifications; display depends on the OS and user settings.

The camera permission included through ZXing is used for QR scanning at your request. Continuous frame archiving and sending camera frames to the developer are not implemented. Selecting a QR image or configuration file with ACTION_OPEN_DOCUMENT gives access to that selected item, not the entire library. MANAGE_EXTERNAL_STORAGE is not required.

Usage Access is optional. Without camera access, you can use a link, file, or selected image. Without Usage Access, the corresponding statistics are unavailable. Revoking VPN permission stops the service. Current functions do not request location, contacts, microphone, SMS, call logs, or the advertising ID.

9. Support, external services, and telemetry

The current client code contains no advertising SDK, Firebase Analytics, Crashlytics, proprietary telemetry, or automatic developer uploads of history, statistics, or reports. This is not a claim about every action of Android, Google Play, each native component, or your selected provider.

The website, documents, and Telegram open in an external browser/application with its own practices. Contacting @velorvpn_support shares your Telegram profile, message, and selected attachments. According to the operator, support correspondence is kept only in Telegram: the operator does not create a separate archive, export it, or disclose it to other recipients. Telegram access and processing on its infrastructure are governed by Telegram rules; this does not mean Telegram does not process messages. Contact support to request deletion of correspondence or exercise data rights. Support handling arrangements: a support employee has access; correspondence is retained for one year. At the end of that period, the operator deletes the correspondence available to it using Telegram tools; earlier deletion can be requested at @velorvpn_support. Deletion by the operator does not guarantee erasure of copies held by the user or on Telegram infrastructure. Operator legal/privacy contact: Telegram: https://t.me/velorvpn_support; confirmed support channel: https://t.me/velorvpn_support.

Network recipients, the provider, Google Play, and Telegram are not automatically described as the operator's contracted processors. The own server service has separate documents: Coalescence OÜ also owns the Velora website and provides its own VPN service. The free Android application can import configurations from both Velora and third-party providers; the server-access contract and its data processing are governed separately.

10. Retention, backups, and deletion

Profiles and links remain until profile/group deletion, replacement during an update, or clearing application data. History is limited to 100 entries and manual deletion; baselines require separate deletion. Session data remains in memory until disconnection. Settings remain until changed or cleared. PDFs remain until cache/data is removed by the OS or user, without a guaranteed TTL.

Automatic application backup is disabled, and SharedPreferences are excluded from Android cloud backup/device transfer. This does not rule out all manual, OEM, or root backups or exported copies. Irreversible physical erasure of flash storage is not guaranteed.

You can disconnect VPN, delete profiles, history and baselines, revoke permissions, clear cache/data, or uninstall using Android. There is no application account, so there is no separate in-app account deletion feature. These actions do not delete provider records, system statistics, correspondence, or previously shared files and do not cancel a server subscription.

11. Legal bases, rights, and audience

Functional processing supports the actions you choose; a system permission does not substitute for an applicable legal basis. For data received by the operator itself, determining applicable bases, international transfers, and rights procedures takes into account distribution territories: all countries available for distribution through Google Play, including the United Kingdom and Russia, subject to local restrictions and actual store availability. The operator's role and actual practices are also taken into account. This draft does not treat consent as a universal basis or claim an unconfirmed DPO, representative, SCC arrangement, or other procedure.

Where applicable law grants rights of access, correction, deletion, restriction, objection, portability, or withdrawal of consent, you may contact the operator through its confirmed contact. Available rights and exceptions depend on the law and data involved. Do not send passwords, one-time codes, or secret subscription links. Use only the minimum information agreed with support to verify your request. Response deadlines follow applicable requirements, not an invented SLA.

Intended audience, minimum age, and measures for minors: users aged 13 and older. Where applicable law requires a higher age, permission from a legal representative, or other conditions, those requirements apply. The application is not intended for children under 13.

12. Changes and contacts

If features and processing change, the policy must be updated before new practices take effect, with legally required notice and consent where necessary. Version 1.0; the effective date specified by the owner is November 4, 2026. New versions are published on this page with a date and version number; users can check it themselves. Where separate notice or consent is required, website publication alone is insufficient. The Russian and English drafts describe the same processes; translation discrepancies must be corrected without limiting mandatory rights.

Support: https://t.me/velorvpn_support. Channel: https://t.me/VpnVelor. Client terms: /android/en/terms/. Policies and terms for the website, Mini App, and server services are separate documents.

Policy references checked November 4, 2026: Google Play User Data · VpnService · Data safety · GNU GPLv3.