Collect what a feature, support request, or security control actually needs.
Privacy without the fog.
What data can enter the system, why it is used, where third parties fit, and what choices you have.
Private keys and delivery endpoints belong in protected environment configuration.
Personal information is not sold or rented to advertisers.
DATA MAP / CURRENT
What can move through YSF Utils.
Categories vary by the features you actually use.
| Category | Examples | Primary purpose |
|---|---|---|
| Discord account data | User ID, username, avatar and authentication state | Sign-in, account features, permissions and support |
| Discord server data | Guild IDs, names, icons and permissions when requested | Server selection, integrations and authorized management |
| Service configuration | Settings and records required by enabled YSF Utils features | Operate bots, workflows and customer-requested functionality |
| Contact submissions | Discord username, user ID, selected service and project message | Reply to support, purchase and development requests |
| Security signals | Request metadata, rate-limit events and technical logs | Abuse prevention, debugging, reliability and incident response |
| CAPTCHA data | Verification tokens handled with the CAPTCHA provider | Confirm that contact submissions are legitimate |
Scope & principles
This policy covers the YSF Utils website and services we operate.
YSF Utils aims to collect and use only the information reasonably needed to run, secure, support, and improve the service you choose to use. This policy describes the main categories of data and the reasons they may be processed.
We do not sell personal information or rent it to advertisers. We also do not use a Discord login as permission to access unrelated information outside the scopes and functionality required by the service.
Information we process
The exact data depends on which product or account feature you use.
Some information is provided directly by you, some comes from Discord or another connected platform after authorization, and some is generated automatically when the service receives a request or records an operational event.
The data map below is a practical overview. A specific bot, integration, or commissioned system may require additional fields when they are necessary for the requested functionality.
How information is used
Data should have an operational reason, not just be collected because it is available.
We may use information to authenticate users, determine permissions, operate bot and website features, deliver support, fulfill project requests, maintain account and service settings, prevent abuse, investigate errors, and improve reliability.
Where practical, technical metrics may be aggregated or separated from direct user identifiers. We do not use contact-form details or Discord account data for unrelated third-party advertising profiles.
Providers & disclosures
Some processing depends on infrastructure and platform providers.
YSF Utils may send or expose limited data to providers that are necessary to operate a feature — for example Discord APIs, hosting infrastructure, database services, CAPTCHA verification, or another integration explicitly used by a product.
We may also disclose information when reasonably necessary to comply with law, respond to valid legal process, investigate fraud or abuse, protect users or infrastructure, enforce agreements, or complete a business transition subject to appropriate safeguards.
Retention & deletion
We keep data for as long as it has a valid operational, security, support, or legal purpose.
Retention periods can differ by data type. Session data may expire quickly, while account settings, purchase records, configuration data, abuse-prevention records, or project communications may need to remain longer. We aim to remove or anonymize information when it is no longer reasonably needed.
Removing a bot or signing out does not necessarily erase every historical record immediately. You can contact us to ask about deletion or a specific record; we will assess the request against technical, security, contractual, and legal requirements.
Cookies & local storage
The website uses browser storage for core functionality and user experience.
Authentication may rely on secure cookies so the server can recognize a signed-in session. The site may also use local storage for limited client-side state such as cooldown timing or interface preferences.
Security-sensitive authentication values are designed to be handled server-side or in protected cookies rather than exposed as ordinary page content. Browser controls can clear cookies or local storage, although doing so may sign you out or reset site preferences.
Security
We use layered controls, but no internet service can promise absolute security.
Controls may include server-side authentication, permission checks, secure transport, restricted administrative interfaces, rate limiting, CAPTCHA, validation, logging, secret environment variables, and provider security features.
If you believe a YSF Utils account, integration, webhook, server configuration, or website surface has been compromised, contact us promptly with enough detail to investigate.
Your choices & requests
You can ask questions about information connected to you.
Depending on where you live and the circumstances, you may have rights to request access, correction, deletion, restriction, objection, or a copy of certain personal information. We may need to verify identity and authority before completing a request.
Some requests may be limited where retention is necessary for security, fraud prevention, dispute handling, contractual obligations, or applicable law. We will explain when a request cannot be fully completed.
Age & connected platforms
YSF Utils is not intended to override the age rules of Discord, Roblox, or other services.
Users must meet the age and account requirements of the platforms they connect to YSF Utils. If you are a parent or guardian and believe information about a child has been handled inappropriately, contact us so the situation can be reviewed.
International processing
Online providers may process information in more than one country.
YSF Utils and its infrastructure providers may process or store data in locations different from your own. Privacy protections and legal requirements can vary by jurisdiction. Where required, providers may use contractual or other safeguards for international transfers.
Policy updates & contact
This page is the current public record of our privacy practices.
We may update this Privacy Policy when services, providers, security practices, or legal obligations change. The effective date at the top of the page identifies the current version.
For privacy questions, access or deletion requests, or a concern about how information is handled, use the verified Contact page or the official YSF Utils support channels.
PRIVACY REQUEST
Need access, correction, or deletion help?
Send enough information for us to identify the relevant account or service without posting private credentials.