No-logs policy
This page explains what AgentVPN does not log, what minimal data is needed to deliver access, and how configs are issued after location selection and activation.
1. What we do not log
- browsing history
- DNS query history as a user activity profile
- content of messages, calls or media
- websites visited through the tunnel
- app activity inside Telegram, YouTube or WhatsApp
2. What data may be needed
To deliver access, AgentVPN may process minimal operational data required for access issuance and support in Telegram bot or account flow.
- account or Telegram bot identifier for delivery
- selected plan or trial status
- selected server location before config generation
- payment status from checkout flow
- config/key delivery status
3. Trial and access limits
- 24-hour trial
- up to 3 keys
- bound to one ID or IP
- location must be selected before config generation
4. Config and location logic
- config is generated for selected location
- Amnezia imports the issued config
- Amnezia does not switch countries inside one config
- another location requires another config
Location is selected before config generation. The issued config is tied to that location.
5. What VPN does not guarantee
- VPN does not guarantee access to every website or app
- app stability depends on server, route, network and device
- users should verify IP and test real apps
6. How to verify after connection
7. Next steps
8. FAQ
Do you log browsing history?
No. AgentVPN does not log browsing history and does not build a user activity profile from visited websites.
Why do you need account or Telegram bot data?
This data is used to deliver access information, check trial or plan status, and confirm config issuance.
Is trial anonymous?
Trial access is bound to one ID or IP and uses minimal technical data needed for issuance and delivery.
Can I switch location inside Amnezia?
No. One config is tied to one selected location. A different location requires a new config.
Does VPN guarantee access to all apps?
No. Access and stability depend on server route, local network, app behavior, and device conditions.