Starship VPN

Privacy Policy

Published: September 25, 2026

1. General provisions

This policy describes Starship VPN’s approach to personal-data processing when you use the site, app and account. For data-processing questions, contact timelord.company@gmail.com.

2. Data that may be processed

To operate the service, we may process an account identifier, email address when provided, device and platform information, VPN configuration identifiers, access-status data and aggregate traffic-volume data. For payments, an email address for a receipt and order information may be used.

3. Why we use this data

Data is used to create and maintain an account, provide VPN connectivity and support, administer access and payments, protect the service from abuse, and meet legal obligations.

4. Technical site data

To operate the site and prevent abuse, we may process technical events: page address, referrer, campaign-tag parameters, browser language and timezone, screen size, a technical session identifier, IP address, User-Agent and limited page-interaction metrics. Starship VPN is not intended to collect browsing history or user-traffic content.

5. Storage and protection

Data of Russian users is processed and stored using databases located in the Russian Federation. Access to data is limited to what is necessary to operate the service.

6. Your rights

You can request information about processing of your data, correction or deletion, and withdraw consent where processing is based on consent. To make a request, email timelord.company@gmail.com.

Acquisition analytics and probable geography

On first launch, the app registers a random installation identifier independently of sign-in. To measure acquisition, the server processes a temporary Apple AdServices token and stores the result: confirmed attribution, a negative response, a test response or a technical error, along with available campaign, ad group and ad identifiers. The Apple token is not stored in databases or logs. The campaign market countryOrRegion does not indicate the user’s physical location or Apple Account region.

The first source or referral tag is stored separately from Apple Ads and linked explicitly through an authenticated account or referral code. An ordinary App Store link does not guarantee that a tag reaches the app; IP matching is not used. App Store and Apple Account region conditions, including UAE, must be checked separately and do not establish the availability of a particular app.

At installation registration, sign-in and configuration retrieval, a local DB-IP City Lite database estimates the country and available region and city of the network exit. We store the first and latest observations, time, source and certainty level; this analytics does not store raw IP addresses or precise user coordinates. VPNs and proxies affect the result: it is not proof of physical location or a route history. Missing data is reported as unknown.

These records may be linked to an account and aggregate payments and traffic volumes by node to analyse acquisition and service use. This analytics does not collect browsing history or VPN traffic content; this does not exclude the technical site data described above. Unlinked installation results are retained for 30 days from creation; linked analytics is retained until account deletion and deleted with the account.

Geolocation: IP Geolocation by DB-IP (CC BY 4.0).