Privacy
This page explains what data LAMPA needs for your connection and subscription, how Google Play purchases are verified, what the AppsFlyer measurement service receives, and what information about VPN connections we do not log.
What we do not log or ask you to enter
| The websites you visit | We do not record these on the VPN server or in our database. The server does not keep connection logs, and the database has no field for browsing history. Automated checks in the code enforce both restrictions. |
|---|---|
| The domain names your device requests (DNS) | These are not recorded on the VPN server or in the database either. |
| The address you connect to the VPN server from | The VPN server keeps no connection log: neither addresses nor times. This has been checked on a running server carrying real traffic. Requests from the app itself to our servers and to AppsFlyer are described separately below. |
| When your VPN connection starts and how long it lasts | We do not log VPN connection start or end times. The device list may retain the date of a device’s last activity. AppsFlyer measures app opens separately; those records are not VPN connection logs. |
| Your name or phone number | You do not need to provide a name or phone number to use the app. The service recognizes your device by its key and links its access to a subscription. Buying your own subscription gives you separate access under that subscription. |
| Your full card number in LAMPA | Your payment provider or app store receives your full card number. You do not enter it in the LAMPA interface. The information we need to verify your payment is described below. |
What leaves your device, and why
| The first request to us, before the VPN is on | An app that has never connected asks us for server addresses over your regular network; it needs those addresses before it can connect. At that point, our server sees the address the request came from, as any website would. We check that address only in memory and do not record it; there is no database field for it. |
|---|---|
| Your device key | To connect, your phone creates a key pair and sends us the public key. The device signs requests with its private key, and we verify the signature with the public key. This is how the service recognizes your device. |
| Your device type | Whether the device is an iPhone or Android, so you can tell devices apart in the list. This may also include the date of its last activity, without the time of day. |
| How much data was transferred during a period | The total amount transferred during a period is used to account for server load. It has no breakdown by website or time; the previous period is reduced to a single total. |
| Payment events | Your selected plan, purchase result, subscription period and connected devices are needed to manage access. The payment provider reports a payment event identifier and its result. Your subscription is activated after payment verification. |
| Purchases through Google Play | The app sends our server a token: a technical identifier for the purchase. Google Play receives a technical code linking the purchase to your access. Our server checks the purchase with Google Play to activate or restore access and account for renewals, cancellations and refunds. The token is stored encrypted on our server. Google Play also tells the app your Google Play country so it can choose an available purchase method. |
Measuring app installs and opens
| Why LAMPA uses AppsFlyer | The iPhone and Android apps use the AppsFlyer SDK to count installs and opens, evaluate advertising campaigns and detect fraudulent installs. On Android, measurement starts after you acknowledge the data disclosure in the app; the SDK is not created before then. This version has no separate analytics switch. |
|---|---|
| What AppsFlyer receives | AppsFlyer receives install and app-open information, its own installation identifier, and technical information about the app and device. It sees the IP address a request comes from, which may be used to infer an approximate location, such as a country or city. According to AppsFlyer’s documentation, technical information may include launch time and battery level to detect fraudulent installs. The app does not request your precise location. |
| Installs from Google Play | In the Android version distributed through Google Play, AppsFlyer also receives the installation source and click and install timestamps through Google Install Referrer. These describe how you reached the app, not the websites you visit. |
| The restrictions we have enabled | Advertising identifier collection and data sharing with advertising partners are disabled. On iPhone, IDFV, collection of the device name you set, and Apple Ads and SKAdNetwork measurement are also disabled. On Android, Android ID, AppSet ID, mobile carrier information and Facebook deferred deep links are disabled. Collection of stored TCF advertising preferences and detailed SDK logs are disabled on both platforms. |
| What happens to identifiers | We have enabled an AppsFlyer mode that, according to its documentation, removes personal identifiers and replaces the installation identifier and IP address with hashes on its servers. The request reaches AppsFlyer first. This setting does not mean that data stays only on your phone or that AppsFlyer stores nothing. |
| What the app does not send to AppsFlyer | VPN traffic contents, DNS requests, visited website addresses, your chosen VPN server, device keys, access codes, payment identifiers and results, receipts, your name, phone number or email address. The SDK runs in the main app and is not included in the VPN tunnel process. On iPhone, it is not included in the widget either. |
Our database
We build and maintain LAMPA’s database ourselves. It has no fields for browsing history, DNS requests or VPN connection logs.
Automated checks monitor this database schema and the VPN server settings. These checks do not control AppsFlyer’s systems; its data processing is described separately above.
How long data is kept
| Data transfer totals | The current period and one previous period. Beyond that, a single total is kept without a breakdown. |
|---|---|
| Payment records | We keep the information needed to verify purchases, renewals, cancellations and refunds, and to resolve payment disputes. Turning off the VPN or uninstalling the app does not cancel your subscription or delete these records. |
| Devices | Revoking a device’s access ends its access to the subscription. It does not delete all service records about the device and its purchases. |
Support through Telegram
When you contact LAMPA support through Telegram, @lampasupport_bot opens. If you open support from the app, the app may attempt to obtain a short-lived link from our server that is bound to that installation. If the chat cannot be linked, or if you open the bot directly, it still works without an installation link. Through a current linked session, support can receive a limited current summary of subscription state, devices, recent payments and refunds, app version and service status. That summary contains no VPN traffic, visited sites, DNS requests or connection logs.
Telegram supplies the bot with the profile name and username made available to bots, the numeric chat or user ID, and the messages you send; Telegram itself receives the original text. For an ordinary support conversation, LAMPA does not add the profile name or username to conversation memory or a human-support ticket. Before storing conversation text or sending it to the AI assistant, LAMPA automatically redacts protected identifiers. LAMPA stores the numeric ID, a pseudonymous installation link and the redacted text so an AI assistant or a human support agent can reply. When needed to answer, the AI assistant may also receive the limited linked summary described above. Redacted text may be processed through OpenRouter and Google with zero-data-retention routing; a human support agent may receive a redacted ticket transcript and current support summary in Telegram. Telegram processes the chat itself under its own privacy terms.
AI-assistant conversation memory is kept for up to 90 days. The /forget command immediately deletes that memory and the installation link; encrypted backups may retain them for up to 14 more days. A human-support ticket, if created, is kept by LAMPA for 12 months after its last message, and longer only while a related refund or payment dispute remains open. That period applies to LAMPA storage: copies of messages and summaries that remain in Telegram are handled under Telegram’s terms, and LAMPA cannot always delete them. /forget does not delete subscription, device or payment records and is not general account deletion.
This website
This website does not set cookies. Within an open browser tab, your browser remembers whether you have switched on the lamp shown on the website. This setting stays in your browser and is not sent to us.
Fonts, images and scripts are loaded from our domain. This website has no analytics, tracking counters or advertising pixels.
Following a link to payment, an app store or Telegram opens that service. Its own privacy policy governs the data it processes.
Questions
For help with the app, contact LAMPA support.
Who operates the service and handles app data
The LAMPA service and its app data processing are operated by DRUSTVO SA OGRANICENOM ODGOVORNOSCU MANKRIK DOO BUDVA - OGRANAK BEOGRAD.
Address: BULEVAR MIHAJLA PUPINA 115A, Beograd (Novi Beograd) - 11070, Serbia (RS). The developer name shown on Google Play is Mankrik.
LAMPA support: support@noltrasoft.com.
Updated