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. |
| Optional email address | After payment, you can leave an email address for subscription, renewal and failed-payment messages. You can skip this. News and offers have a separate checkbox, selected on the first request; you can clear it. Emails include an unsubscribe link. Your email address is not sent to AppsFlyer. The address and mailing preference are stored in the billing system. The email service receives the address and message text to deliver the email. The address is not written to app diagnostic logs. |
AppsFlyer: advertising and app use
| 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 | In the Android app, AppsFlyer receives information about installs, app opens and screens, payment steps and their outcomes, device enrolment, purchases and added seats. Purchase events include the plan, term, device count, amount and currency, without your name, email or order number. The SDK receives its install identifier, technical phone and app data, carrier information and the request IP address, which may indicate an approximate country or city. Collection of Android ID, available advertising identifiers and saved TCF consent preferences is enabled; availability depends on the device and system. Google Play installs also provide the install source. The app does not block sharing with AppsFlyer partners; this depends on partner settings in the service. VPN traffic, sites you visit and DNS requests are never sent to AppsFlyer. |
| 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. |
| Android settings | On Android, AppsFlyer anonymization and the block on partner sharing are not enabled. SDK settings do not disable collection of advertising identifiers or AppSet ID; actual availability depends on the system, permissions and included libraries. Saved TCF consent preferences are read if present. Facebook deferred links and detailed SDK logs are disabled. |
| Differences on iPhone | On iPhone, AppsFlyer is used for installs and app opens. This version disables IDFV, collection of your chosen device name, Apple Ads, SKAdNetwork and reading TCF data. AppsFlyer anonymization and the block on partner sharing are enabled. Anonymization happens at the service after it receives the request, not on the phone; it does not mean no data is transmitted. The purchase and screen events described above apply to Android. |
| What the app does not send to AppsFlyer | The app does not send VPN traffic contents, DNS requests, visited website addresses, the selected VPN server, device keys, access codes, payment tokens, order numbers, full card details, your name, phone number or email address to AppsFlyer. The SDK runs in the main app, separately from the VPN tunnel. On iPhone it is also absent from the widget. |
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.
Legal Bases for Processing under the GDPR
We process personal data on the following legal bases:
Performance of a contract — Art. 6(1)(b) GDPR: providing VPN access, managing subscription, devices, access and support.
Compliance with legal obligations — Art. 6(1)(c) GDPR: tax and accounting records, responding to lawful requests, resolving payment disputes and refunds.
Legitimate interests — Article 6(1)(f) GDPR: service security, preventing fraud and abuse, and maintaining reliability.
Consent — Art. 6(1)(a) GDPR: where required, for example for certain optional features or analytics on Android before confirmation of data disclosure. Consent can be withdrawn at any time.
Your Rights under the GDPR
If you are in the EEA, the UK or Switzerland, you have the right to: access your personal data — Art. 15 GDPR; rectify inaccurate data — Art. 16 GDPR; erasure of data — Art. 17 GDPR; restriction of processing — Art. 18 GDPR; data portability — Art. 20 GDPR; object to processing based on legitimate interests — Art. 21 GDPR; withdraw consent — Art. 7 GDPR; lodge a complaint with a supervisory authority — Art. 77 GDPR.
To exercise your rights, write to info@mankrik.com. We will respond within one month; for complex requests, the period may be extended by a further two months.
Rights are not absolute. We cannot delete data that we are required to retain by law, or data necessary for payment disputes, refunds or the protection of rights. We also cannot provide VPN logs, DNS queries or browsing history because we do not store them.
Recipients of Data and International Transfers
We may disclose data to these categories of recipients: AppsFlyer for advertising attribution, measuring installs, app opens and the Android events described above; Google Play for purchase verification, access recovery, renewals, cancellations and refunds; payment providers for processing and verifying payments; email services for delivering messages to the address you leave; Telegram for user support; OpenRouter and Google for AI processing of redacted support messages; hosting and infrastructure providers for hosting LAMPA servers and databases.
Some of these recipients may be located outside the EEA. If data is transferred outside the EEA, we use appropriate safeguards such as the EU Standard Contractual Clauses or rely on an adequacy decision where applicable.
Security
We take reasonable technical and organizational measures to protect data: encryption of purchase tokens, access restrictions, automated checks of the database schema and VPN server settings, absence of VPN connection logs and fields for browsing history and DNS queries.
Children
LAMPA is intended for users aged 13 and over, not for children under 13. If you believe a child below that age has provided us with data, please contact us so that we can review the request and delete that data.
Changes to the Policy
We may update this Privacy Policy. A new version is published on the Mankrik website with an updated effective date. By continuing to use the service after changes, you agree to the updated policy, unless otherwise required by law.
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: info@mankrik.com.
Updated