Privacy Policy
This English text is a translation of the Chinese original provided for convenience. In case of any discrepancy, the Chinese version prevails.
Last updated: October 8, 2026
This policy explains what NepBox (www.nepbox.com, api.nepbox.com) collects, how it is used, how long it is kept and what you can do about it.
1. What we collect
| Category | Details | Source |
|---|---|---|
| Account | Google user ID, email address, display name, avatar URL | Provided by Google after you consent on its authorization page |
| Network address | Source IP when you open the console or call the update endpoint | Cloudflare request headers |
| Service data | Subdomains, A/AAAA record content, update tokens, change entries (old/new address and source IP) | Created while you use the Service |
| Display setting | Light / dark theme | Stored only in your browser’s localStorage, never uploaded |
| Notifications | Telegram user ID and username (only after you link them yourself) | Provided by Telegram after you tap “Start” |
We never ask for your password and do not need it. The Service loads no advertising, analytics or behavioural tracking scripts.
2. How the data is used
- To identify you and keep you signed in;
- To provide DDNS: writing the address from an update request into the matching DNS record;
- To send change notifications: after you link Telegram and enable notifications, subdomain address changes are sent to your Telegram account;
- For security and abuse prevention: rate limiting, spotting abnormal requests, handling abuse reports and debugging.
3. Cookies
The Service uses essential cookies only:
| Name | Purpose | Lifetime |
|---|---|---|
session_token |
Keeps you signed in (HttpOnly, only for api.nepbox.com) | 30 days |
oauth_state |
Prevents the sign-in flow from being forged cross-site | 10 min |
Because no advertising or analytics cookies are used, there is no cookie consent banner.
4. Storage and retention
- Data lives in Cloudflare Workers and the D1 database, which may be located in data centres outside mainland China;
- Sessions expire after 30 days;
- Each subdomain keeps its latest 20 change entries; older ones are deleted automatically;
- Telegram binding data is kept until you unlink it or delete your account;
- Request logs on Cloudflare’s side follow Cloudflare’s own default retention; we cannot delete them earlier;
- Deleting your account cascades to the account, its subdomains, DNS records and change history, removes the Telegram binding, and deletes the corresponding records from Cloudflare.
5. Third parties
- Cloudflare: DNS hosting, Worker runtime, D1 storage and request logs;
- Google: account sign-in (OAuth);
- Telegram: delivering change notifications (only once you have linked an account, and only the notification content itself).
We do not sell or rent your personal data, and we do not use Google user data for advertising. It is not shared with any other third party except where required by law or necessary to handle abuse and security incidents.
6. Security
- Update tokens are generated with a cryptographically secure random number generator; session tokens are stored only as SHA-256 digests, the raw value exists solely in your browser cookie;
- HTTPS is enforced site-wide, and the API is protected by CSRF and rate limiting.
Note that the update token travels as a query parameter of the update URL and may therefore be written into intermediate devices or Cloudflare request logs. Treat it like a password and reset it in the console if you suspect it leaked.
7. Your rights
- View and change your display name on the profile page;
- Link or unlink Telegram and toggle IP change notifications on the profile page;
- View, edit and delete your subdomains and DNS records in the console;
- Delete your account at any time to erase all of the data;
- For anything else — exporting your data or correcting it, for example — contact support@nepbox.com.
8. Minors
The Service is not aimed at children under 14. If you are a minor, please use it with the consent and guidance of a guardian.
9. Policy updates
This policy may be updated; the date at the top of this page shows the latest revision, and material changes are announced on the site or in the changelog.