Privacy Policy
Last updated:
This Privacy Policy explains how Reio Põldmaa, the owner and operator of noobtunnel, collects, uses and handles personal information when you use the hosted noobtunnel website, account system, networking services and related support at noobtunnel.top (the “Service”). It also explains the choices available to you and how to contact us about your information.
1. Who we are and what this policy covers
The hosted Service is owned and operated by Reio Põldmaa. In this policy, “we”, “us” and “our” refer to Reio Põldmaa as the service operator. You can reach us at admin@byenoob.com or through the details on our Contact page.
The Service includes the control panel, device agents, private mesh networking, tunnel relays, authoritative DNS, public service publishing and subscription management. A point of presence, or “POP”, is a location running infrastructure used to deliver these services.
This policy does not govern independently operated noobtunnel installations or websites and applications published by other users. Their operators are responsible for their own privacy practices.
2. Information we collect
Account and authentication information
We store your username, email address where provided, email verification status, a password hash, account role, subscription or account tier, account creation time and most recent successful sign-in time. We also store authentication information needed for sessions, verification and recovery, API tokens and device enrollment. Passwords are stored as hashes rather than as readable account passwords.
If Discord login is enabled and you choose to use it, Discord provides your account identifier, email address and email verification status. We store the Discord identifier to recognize your linked account and use the verified email for new registrations. Discord access and refresh tokens are not stored in the account registry. During sign-in, a temporary secure cookie holds the information needed to complete the login or account-linking request.
Device and service configuration
Information you provide or your devices report can include device names, public keys, assigned mesh addresses, advertised routes, operating system and agent version, connectivity status, domains, DNS records, backend targets and published service settings. If you configure DNS automation, the Service stores the provider credentials needed to carry out the actions you request.
Connection, usage and security information
Operating the network involves processing IP addresses, connection and request times, hostnames, request paths, response codes, traffic totals, usage allowances, tunnel handshakes, account events and diagnostic errors. Configured IP intelligence providers may supply country estimates and security or reputation signals. URLs and request paths can contain information supplied by you or visitors to a published service; avoid including credentials or other sensitive information in them.
Subscriptions and payments
If you purchase a paid subscription, Stripe handles checkout and payment management. noobtunnel stores the customer, checkout and subscription identifiers and status information needed to manage access, such as the paid-through date and cancellation status. Payment details entered on Stripe-hosted pages are handled by Stripe rather than stored as full card details in your noobtunnel account.
Support and correspondence
If you contact us, we process the contact details, messages and supporting information you choose to send. Please remove passwords, session cookies, API tokens, enrollment credentials and private keys from support messages, screenshots and logs.
3. How we use information
We use the information described above for the following purposes:
- Creating and managing accounts, authenticating users and devices, and processing verification or recovery requests.
- Connecting devices, routing and relaying traffic, publishing services, managing DNS and maintaining network status.
- Measuring usage, applying account allowances and maintaining subscription access.
- Diagnosing faults, maintaining reliability, identifying misuse and responding to security incidents or abuse reports.
- Sending service-related messages and responding to support or privacy requests.
- Understanding country-level demand and planning infrastructure, including additional POP locations.
- Meeting applicable legal obligations and addressing disputes concerning the Service.
Some information is necessary to provide the functions you request. If you do not provide it, or ask us to stop processing information needed for those functions, we may be unable to provide the relevant part of the Service.
4. Country for POP planning
After a successful sign-in to the dashboard or an account-protected published resource, we use the connection IP address and the configured IP intelligence provider to estimate your country. We store the latest available two-letter country code with your account. Service administrators can view that code to understand where demand exists and help choose future POP locations.
This feature does not add a city, street address, coordinates or raw login IP address to your account profile, and does not create a country history. Connection records and IP intelligence caches are separate from this account field and are covered by the other sections of this policy.
Accounts without a recorded country remain empty until a successful sign-in and a successful lookup; we do not backfill countries from historical logs. A failed or unavailable lookup does not prevent sign-in and leaves any previously recorded country unchanged.
VPNs, proxies and errors in IP databases can affect the estimate. It is not proof of where you live, your nationality or your physical location. You can contact us about access, correction or deletion of the country recorded with your account.
5. Cookies and browser storage
The hosted dashboard uses a noobtunnel_session cookie to maintain an authenticated session. Account-protected published resources can also use a sign-in cookie scoped to their own hostname. These cookies support authentication and access to the functions you request.
The interface also uses browser storage for preferences, such as a saved network topology layout. This is separate from the account information stored on our servers. The interactive API documentation holds entered authorization in page memory and does not persist it across page reloads.
You can remove or block cookies and clear browser storage through your browser settings. Removing the session cookie signs you out in that browser; blocking it can prevent session-based features from working. Clearing preference storage resets the saved interface choices. These actions do not, by themselves, delete your account or server-side records.
6. Access to and sharing of information
Access to connection logs through the dashboard and API is only available to their respective mesh owners. For network operation, account management, troubleshooting and support, service operators may also access relevant information directly on the underlying infrastructure. Information may also be processed by services involved in delivering the features you use:
- Infrastructure providers: servers, network connectivity, databases and recovery infrastructure used to host the Service.
- Email delivery providers: recipient addresses and message information required for verification, recovery and other service messages.
- Discord: if you choose Discord sign-in or account linking, Discord processes the authorization request under its own privacy practices.
- IP intelligence providers: IP addresses submitted for country estimates and configured security or reputation checks.
- Stripe: information needed for checkout, billing and subscription management.
- DNS and certificate services: domains, DNS configuration and the information needed to publish records and issue or renew certificates.
When you publish a service or DNS records, the public endpoint and published records are intended to be accessible to others. If you share an API token or enrollment credential, its recipient may be able to access data or change settings within that credential's permissions. Use the narrowest permissions needed and revoke credentials you no longer intend to share.
We may disclose relevant information when required by applicable law or a valid legal request, or where necessary to investigate misuse, respond to a security incident or protect the rights and safety of people using the Service. Providers may also handle information under their own privacy notices; contact us if you need more information about the providers involved in your use of the Service.
7. Where information is processed
The Service operates across infrastructure locations. Account and configuration data can be replicated between POPs to support availability and recovery. Selecting a publishing POP does not mean that all account information, operational records or backups are confined to that location.
Infrastructure and service providers may process information in countries other than your own, where data protection rules can differ. The available POP locations are shown on the website. Contact us for information about the processing locations and providers relevant to your account.
8. How long information is kept
Retention depends on the type of information and why it is needed. There is not a single fixed deletion period that applies to every category of data.
- Account and configuration information: kept while needed to provide and manage your account and services. The country field is part of the account record and is removed from that record when the account is deleted.
- Connection, usage and security records: may remain separately for troubleshooting, network operation, abuse prevention, investigation and recovery. Deleting an account does not automatically erase every operational record associated with earlier activity.
- Billing and correspondence: may need to be kept to manage payments, answer requests, resolve disputes or meet applicable record-keeping obligations. Stripe maintains its own records under its policies.
- Backups: may retain earlier copies separately from the active system for recovery; a change or deletion in the active system does not necessarily remove every backup copy immediately.
For information about the retention applicable to your data, or to request deletion, contact us. Some information may need to be retained where an applicable legal obligation or an ongoing security matter requires it.
9. Security and network privacy
The Service uses measures such as password hashing, authentication checks, scoped API permissions and encrypted connections to protect access and network operations. No internet service or storage system can provide an absolute guarantee of security.
WireGuard encrypts private mesh traffic between its tunnel endpoints. Public service publishing has a different trust boundary: HTTP traffic is handled by the proxy, and HTTPS may terminate at a POP before the request continues to your backend. Backend encryption and access controls are separate configuration choices. Do not assume that a published resource has uninterrupted end-to-end encryption or the same privacy characteristics as private mesh traffic.
noobtunnel is not presented as a no-logs anonymity service. Keep your own devices and backend services secure, protect your credentials and contact us promptly if you suspect unauthorized access.
10. Your choices and privacy rights
You can manage supported account and service settings in the control panel and revoke API or enrollment credentials you no longer need. For access, correction or deletion requests that are not available in the interface, email admin@byenoob.com.
Depending on the law applicable to you and the processing concerned, your rights may include obtaining a copy of your information, correcting inaccurate information, requesting deletion, restricting processing, objecting to processing or receiving a portable copy. Where processing relies on consent, you may have the right to withdraw that consent. You may also have the right to complain to the relevant data protection authority.
Please describe the request and, where possible, contact us from the email address associated with your account. We may need to verify account ownership before disclosing information or making changes. We will handle requests in accordance with applicable law and explain any applicable limitations.
11. Other websites and published services
A website or application published through noobtunnel is operated by its own owner. That operator may collect visitor information, set cookies and keep application logs under a separate privacy policy. Links to other websites, payment pages and external services are also subject to the relevant operator's practices. Review their notices before providing information to them.
12. Changes and contact details
We may revise this policy as the Service or its data practices change. The current version is published on this page with its last-updated date. We will provide any additional notice required by applicable law.
For questions about this policy or requests concerning your information, contact Reio Põldmaa at admin@byenoob.com. See also our Contact page and Terms & acceptable use.