Privacy notice
StarMe DNS has no advertising or third-party behavioural analytics. It keeps limited first-party aggregates to understand which pages and features are useful, alongside the network and in-game data needed to run the service.
Last updated: 31 July 2026
Who operates the service
StarMe DNS is operated and maintained by Buutyful, who is the controller of the data described here.
For a privacy request, get in touch through the StarMe DNS Discord.
Data the service handles
- Network and security data
- IP addresses, DNS queries, request times and paths, connection results, protocol errors, and abuse-control events.
- First-party engagement aggregates
- Daily counts for known public pages and feature groups, response/error totals, fixed latency histograms, and an approximate visitor count. The analytics aggregates contain no raw IP address, cookie, referrer, search term, query string, or visitor-level browsing history.
- Game and player identifiers
- WFC user and profile IDs, friend codes, trainer names and IDs, game and device details, language and region, and a MAC address only where a migration or game request provides it.
- Service activity and content
- Pokémon deposits and trades, Battle Tower teams and results, Poké Bank entries, Mystery Gift delivery state, rankings, and moderation or ban records.
- Optional notifications
- A browser push endpoint and keys, linked trainer identifiers, delivery state, and a management credential stored in that browser.
There is no general website account, and the service does not require a real name, email address, or advertising profile to play.
Why it is used
- To provide the DNS, WFC, exchange, battle, storage, gift, and notification features you request.
- To preserve game identities and trade history so returning saves continue to work.
- To diagnose failures, secure the service, enforce limits, moderate misuse, and maintain reliable operation.
- To understand which StarMe DNS pages and features are useful after visitors arrive, without building visitor profiles or duplicating search-query analytics from Google Search Console.
The legal bases are providing the requested service (GDPR Article 6(1)(b)), the operator's legitimate interests in security, continuity, and moderation (Article 6(1)(f)), and consent for optional browser notifications (Article 6(1)(a)). Notification consent can be withdrawn with the browser toggle or site settings.
What can be public
Using public exchange and ranking features can make an in-game trainer name, offered or traded Pokémon, battle team, score, rank, or room visible to other visitors. StarMe DNS does not intentionally publish IP addresses, MAC addresses, notification credentials, or WFC migration details.
How long it is kept
- WFC connection attempts and service activity logs are normally removed after 14 days and are also capped by row count.
- Expired or rejected identity migrations are normally removed 14 days after expiry or rejection.
- First-party page and feature aggregates are normally removed after 180 days and are also capped at 10,000 daily aggregate rows.
- Scheduled database backups roll off after 30 days.
- Game identities, trade and battle history, public records, active notification links, and moderation records remain while needed for service continuity, the feature requested, abuse prevention, or legal claims. They may be removed or de-identified when no longer needed.
Providers and sharing
Data is not sold. It may be handled by infrastructure providers such as DigitalOcean, by the push service selected by your browser when notifications are enabled, and by authorities when legally required.
The Competitive Teams page's fonts and sprites are served directly by StarMe DNS and do not make third-party asset requests. Discord, GitHub, and other external sites receive data under their own policies only when you follow their links.
Cookies and browser storage
StarMe DNS does not use advertising, profiling, or analytics cookies, so it does not show a consent banner. First-party engagement analytics are computed on the server as aggregate counts and do not set browser storage. Other first-party browser storage is limited to:
- Credentials needed to manage browser trainer notifications.
- Short-lived StarMe Assistant cooldown and rate-limit timestamps.
- A card-layout preference selected by the visitor.
You can remove these items through browser site settings. Removing notification credentials may require linking the browser again.
Your choices and rights
Depending on the situation, you may ask to access, correct, delete, restrict, or receive your data, object to legitimate-interest processing, or withdraw notification consent. Some identifiers may be needed to find the relevant game record and verify that it belongs to you.