This Privacy Policy applies to Guild Tags Indexer (the “Bot”), a private Discord application operated by Riyo. The Bot is not offered for public installation and is used only in Discord servers explicitly authorized by the operator.
Data used by the service
The current Guild Tags Indexer workflow builds an index from publicly accessible Guild Tag listings and publishes those entries to an authorized Discord forum. The index may contain:
- Guild Tag name and Guild Tag icon URL.
- Discord guild ID and guild name.
- Discord invite code associated with the indexed guild.
The scraper currently obtains this index data from nelly.tools/tags and stores the resulting dataset locally for the operator’s indexing workflow.
Discord data
The Bot connects to Discord using a bot account and accesses the configured server and forum channel so it can create and archive index posts. The current publishing workflow does not provide public commands, does not maintain user profiles, and does not intentionally store ordinary Discord message content or member lists.
Discord may deliver technical event data to the connected bot as part of operating the Discord connection. Data that is not required by the indexing workflow is not intentionally persisted by Guild Tags Indexer.
Local operational data
- The scraped Guild Tag dataset is stored locally in a JSON file used by the publishing process.
- A local progress file stores the last processed index so publishing can resume after an interruption.
- Guild Tag icons may be downloaded to a temporary local file before being attached to a Discord forum post. The temporary file is deleted after the post attempt completes.
- Runtime logs may include operational information such as guild or tag names, progress, and error details for troubleshooting.
How data is used
- To build and maintain the private Guild Tags index.
- To create and archive Guild Tag entries in the configured Discord forum channel.
- To resume interrupted indexing jobs and diagnose operational errors.
- To maintain service security and comply with applicable law or Discord platform requirements.
Sharing and sale of data
Guild Tags Indexer does not sell personal information and does not use indexed data for advertising. Indexed entries are published only into Discord locations chosen by the operator. Discord necessarily receives the content uploaded or posted through its API. The source website and any network or hosting providers involved in normal service operation may also process ordinary request metadata under their own policies.
Retention
The local index may be retained while it is useful for the private indexing project. Posting progress is retained only as needed to resume the publishing job. Temporary downloaded icon files are removed after use. Runtime logs and other operational records are kept only as long as reasonably necessary for troubleshooting, security, or legal obligations.
Data deletion and correction requests
A guild owner, administrator, or other person with appropriate authority may request removal or correction of an indexed guild entry. The operator may ask for reasonable verification that the requester is authorized to act for the relevant guild. Instructions are available on the Data Deletion page.
Security
Reasonable technical and organizational safeguards are used to protect bot credentials and locally stored operational data. No internet-connected system can guarantee absolute security.
Third-party services
Guild Tags Indexer depends on Discord and currently uses public Guild Tag listing data from nelly.tools. Those services operate independently and have their own terms and privacy practices. Guild Tags Indexer is not affiliated with or endorsed by Discord or nelly.tools.
Changes to this policy
This policy may be updated when the Bot’s implementation, data sources, legal obligations, or Discord platform requirements change. The “Last updated” date on this page will be revised when material changes are published.
Contact
Questions, correction requests, deletion requests, or privacy concerns can be sent to the operator using the contact methods listed on the Support page.