The underlying policy of Akca Network is that we never store any activity logs of any kind. We strongly believe in having a minimal data retention policy because we want you to remain anonymous.
Last Updated: January 3, 2026The underlying policy of Akca Network is that we never store any activity logs of any kind. We strongly believe in having a minimal data retention policy because we want you to remain anonymous.
However, in some situations we might process your personal data if you, for example, are making payments through our NFT marketplace, or are sending an e-mail for support. In those cases, we might process your personal data and the General Data Protection Regulation ("GDPR") and other data protection laws may apply. For more information please read our Privacy Policy.
We want you to remain truly anonymous. When you use Akca Network, we do not ask for any personal information – no username, no password, no email address, no phone number. Instead, you mint an NFT (Genesis Pass or AkcaPass) on the Solana blockchain. This NFT is your access key and the only identifier needed to use Akca Network.
This is a fundamental difference that sets us apart from traditional VPN services.
Answer: We cannot know this information. The Solana blockchain is public and anyone can verify NFT ownership, but we have no way to know how many unique individuals own our NFTs or who they are. One person could own 100 NFTs, or 100 people could own one NFT each - this information is unknowable to us by design.
When you connect to Akca Network, our servers only verify your NFT ownership on the Solana blockchain. Here's what we process:
nft_mint_address | verification_timestamp | connection_status
BvGH...3KmN | 2024-12-16 15:23:41 | verified
This data exists only in temporary memory (RAM) and is never written to disk. When your session ends, this information is immediately erased.
The following information exists on the Solana blockchain (publicly visible to anyone):
This data is not stored on our servers. It exists on the public Solana blockchain. We only read it to verify access.
Since Akca Network uses NFT-based access, there are two payment scenarios:
When you mint a Genesis Pass or AkcaPass directly from us:
Payment method:
What we store:
For SOL payments (on-chain, public data):
transaction_signature | nft_mint_address | amount_sol | timestamp
5KmN...7xBC | BvGH...3KmN | 0.5 | 2024-12-16 10:00:00
This data is not stored on our servers. It exists on the public Solana blockchain. Anyone can verify these transactions, but they cannot link them to your real identity.
Legal basis: Legitimate interest (providing the service)
Retention: Permanent (blockchain is immutable)
GDPR status: Blockchain transactions are public and not under our control
No third-party payment processors = No payment data leaks
If you buy an NFT from another user on Magic Eden, Tensor, or any marketplace:
This is a key advantage: Once an NFT is minted, it can change hands unlimited times without us ever knowing. The original buyer could sell to 50 different people, and we would have no way to track this.
We log nothing whatsoever that can be connected to an NFT holder's activity:
[Interface]
PostUp = echo "No logs, by design" > /dev/null
PostDown = echo "Still no logs" > /dev/null
[Logging]
Level = NONE
Storage = /dev/null
Answer: Each VPN server validates NFT ownership with our central API in real-time. When a user connects, the server checks:
Everything is performed in temporary memory (RAM) only. None of this information is permanently stored to disk. We cannot tell you how many connections your NFT had 5 minutes ago because that data no longer exists.
We want to ensure everyone using Akca Network experiences a reliable and stable service.
We use Fail2ban on our WireGuard servers to prevent brute-force attacks and abuse. This works by maintaining a temporary RAM-only list (tmpfs) of malicious IP addresses that:
Answer: No. We do not log customers with valid NFTs. This protection is limited to bad actors trying to exploit the system with invalid NFT addresses or attempting to overload our servers.
Our infrastructure collects aggregated, anonymized metrics for service reliability:
- Total active VPN connections across all servers
- CPU load per server
- Total bandwidth per server
- Memory usage
- Server uptime
We log the sum total of these statistics to monitor the health of each VPN server. We ensure the system isn't overloaded and monitor for potential attacks, bugs, or network issues.
We also monitor the real-time state of total connections per NFT (maximum 5 simultaneous connections). As we do not save this information, we cannot tell you how many connections your NFT had in the past.
$server_name [$time_local] $request $status
Our support team answers questions and resolves issues for users who email contact@akca.network or submit problem reports through our app.
Please consider the following:
When you submit a bug report through the Akca app, we collect:
Note: Email addresses are personal data under GDPR. If you email us, we process it according to our Privacy Policy.
If you need support but want to stay anonymous:
The Akca app automatically checks for updates to ensure security. This sends:
We keep aggregate counters on:
This data cannot identify individual users.
If we implement split tunneling on mobile apps, the app will query your device for installed applications to let you choose which apps bypass the VPN. This list never leaves your device.
If we release browser extensions or integrated browsers:
Akca Network OÜ is incorporated in Estonia and operates under:
Estonian law does not require VPN providers to log user activity. Should any authority request user data, we will:
Because of our no-logs policy and blockchain-based authentication, we cannot identify individual users even if legally compelled to do so. We cannot disclose data that we do not have.
For complete information about how we handle data: