Chính sách bảo mật

Scope and data sources

This policy describes data processing by the SDVN Discord applications listed on this page and the SDVN components that directly support them. Data comes from your interactions, Discord, linked Steam accounts, game servers and SePay transaction notifications.

AI Helper PP is outside this policy’s scope. Ticket bots and other third-party-operated bots are governed by their respective operators’ policies; their presence in the guild does not mean SDVN operates them. Contact SDVN for guidance if you are unsure which application handles your data.

Common data and purposes

Depending on the application, SDVN processes Discord IDs, roles or permissions needed for access checks, relevant channel and message IDs, commands or forms you submit, linked Steam IDs and relevant game data. Purposes include responding to requests, checking access, carrying out authorized game actions, reconciling benefits, providing support and investigating faults or violations. Not every app reads all Discord messages.

[SDVN] — IslePilot

The application uses Discord IDs and Steam links to handle interactions; website components retrieve individual members’ roles as needed. Account links, game events and operational results are stored in SDVN’s database. Game chat is relayed to configured Discord channels and can be read by people with access to those channels. This game-chat relay is separate from the Discord image-moderation pilot described below. Lookup caches are held in process memory; clearing a cache does not delete stored records. The website’s Discord unlink function removes the link only, not all game history or backups.

Automated image moderation

The [SDVN] (IslePilot) application, Application ID 1537856555675025458, is being prepared to use Discord Message Content Intent to assist with moderating images posted by members in Discord channels configured for monitoring. As of this update on 24 October 2026, the pilot is awaiting this permission and monitoring of player-uploaded images has not been enabled. The descriptions below apply when the pilot is enabled; this is separate from AI Helper PP.

1. Purpose of data processing

The system assists in identifying images that may violate community rules, including pornography, sexual content or nudity, severe violence, gore and other image content prohibited by the Discord Community Guidelines or SDVN rules. Detection depends on the deployed model and rules; not all shocking content or violations will be identified correctly. An unflagged result does not establish that an image is safe.

Child sexual exploitation or abuse content is prohibited. However, the pilot is not a dedicated CSAM or age-detection tool. Known or suspected CSAM must be excluded from OpenAI Moderation submissions and handled through appropriate safe reporting procedures. The current manual exclusion list does not replace dedicated child-safety safeguards. Do not copy or resend such images through support email or alert channels; provide message/channel IDs and information needed for reporting.

2. Data received and processed

For new or edited messages with attachments within the monitoring scope, the bot may process the sender’s Discord ID, username and display name; server, channel and message IDs; sent/edited timestamps; attachment ID, name, size, format and necessary metadata; a temporary Discord CDN download URL; image data in memory; classification results, scores, model response identifiers, recording time and processing status.

Original and normalized images are processed temporarily in the pilot’s memory and are not archived in case storage. A case may include a SHA-256 hash when an attachment was downloaded, but does not contain an image copy or signed CDN URL. Discord may deliver text fields in events under the granted permissions; the pilot does not analyze conversation text or store it in moderation case records.

3. Image processing method

The bot software runs on SDVN-managed servers, but image classification uses the OpenAI Moderation API. Image data is therefore transferred to a third-party provider; classification is not performed entirely in-house.

Attachments from Discord CDN within the 8 MiB limit are downloaded into memory for format validation. Supported static PNG/JPEG/WebP images within technical limits may be resized and sent over HTTPS to OpenAI for classification. The pilot does not separately send Discord IDs, usernames, display names, filenames or conversation text as OpenAI input fields; personal data may nevertheless appear within the image itself. OpenAI handles data under its API terms and data controls; see https://developers.openai.com/api/docs/guides/your-data . SDVN does not promise immediate deletion of all provider-processed data.

GIFs, animated images, video, unsupported files, external embeds and processing failures may be referred to staff; they are not treated as successfully classified as safe. Unsupported files are not sent to OpenAI. Links without embeds may not be detected.

The pilot only records cases and alerts staff; it does not automatically delete messages, timeout, kick or ban users. Staff consider context and other evidence before decisions under community rules, and players may request review. If SDVN later introduces original-image archiving or automated sanctions, the policy and relevant notices will be updated before those features are enabled.

4. Data storage and access

For flagged content, review cases or processing failures, SDVN stores metadata records and results to help investigate false positives, review decisions, investigate violations and handle complaints. The pilot does not archive original images, capture Discord screenshots or repost sensitive images in alerts. A case PNG presents metadata; it is not a screenshot or independent evidence of the original image content.

Server-side case access is restricted to authorized people or system components. A private staff channel receives the case reference, sender/channel/message IDs, timestamp and status. The system also stores deduplication state and routine operational logs containing timestamps, statuses and error types; the pilot’s log messages do not include player identifiers or content. These data support administration, review and operation and are not published publicly by the pilot.

Pilot storage is encrypted with AES-256-GCM at the application layer before being written to disk, including JSON/PNG case records, deduplication data, channel-permission audits and credential configuration. The encryption key is kept separately from the data directory, restricted to administrative access and supplied to the running service. Authorized components decrypt data when needed for processing. This is not full-disk encryption, does not cover all data of other SDVN applications or copies at Discord/OpenAI, and does not prevent administrators with root access or key-authorized processes from accessing plaintext. Removing old plaintext files does not guarantee physical erasure of every storage block or copies outside the controlled scope.

5. Retention and deletion requests

Case records and deduplication state are configured for removal after 30 days when the bot next processes work. Cleanup may be delayed while the bot is stopped or idle. The pilot does not archive image copies, so it has no separate image-archive retention period.

The 30-day period does not automatically apply to alerts already sent to Discord, system logs or backups; these do not yet share a uniform deletion schedule. SDVN reviews the need to retain them and handles deletion manually when no longer needed or upon a valid data request, including copies under its control. The absence of a cleanup job is not a basis for indefinite retention. Data at OpenAI and Discord is also subject to those providers’ data-handling practices.

Users may request access, correction, review or deletion by emailing [email protected] with their Discord ID, case reference or message ID and time if available. Do not resend sensitive images. SDVN verifies control of the account, locates relevant records/alerts/logs and explains what was handled or must be retained for a specific applicable obligation. Leaving the server or deleting a message does not automatically erase existing records.

6. Limits on Message Content Intent use

This component uses Message Content Intent to receive attachments in ordinary messages for image moderation in configured channels, not just messages invoking commands or mentioning the bot. Channel-based scope applies to all senders and does not select individuals for monitoring. Admin/internal channels, the alert channel, private tickets and private threads are excluded; DMs are not scanned.

On startup, the bot may check up to 100 messages per channel from the preceding 15 minutes. Public-thread coverage depends on data supplied by Discord; archived threads and the full message history are not guaranteed to be covered. The bot receives images after a message is posted and does not prevent uploads before they appear.

SDVN does not use this component for advertising, unrelated user profiling or collecting conversation text beyond the disclosed needs, and does not use moderation inputs or results to train its own AI models. Other game-management and IslePilot integration features continue through Slash Commands, Discord Interactions and the corresponding game-server integration components.

Anti-cheat staff assistant

The anti-cheat assistant is an internal tool for SDVN staff. It currently runs under the [SDVN-ANTICHEAT] application (Application ID 1563518573320601633) and may be moved to the [SDVN] (IslePilot) application. Players do not send commands to the assistant; it only works with staff.

1. Message reading scope and Message Content Intent

The assistant uses Message Content Intent to read message content in exactly two configured private staff channels (gameplay and server channels). Staff give commands, ask questions and answer proposals (for example "approve", "ban him", "never mind") in natural Vietnamese rather than Slash Commands, so the assistant must read the content to understand the request and to know which proposal is being answered.

The assistant periodically fetches new messages in these two channels through the Discord API and, when answering, reads about the last 30 channel messages as context. It only acts on messages from allow-listed staff accounts; messages from others and from bots are ignored. It does not read other channels, DMs, voice, presence or member lists, and this reading scope is not used for image moderation or any other purpose.

Besides these two channels, the server owner and the co-admin can use the /anticheat slash command of the [SDVN-ANTICHEAT] application in any channel. It does not need Message Content Intent: the assistant only receives the text typed into the command, does not read other messages in that channel, and the answer is visible only to the person who used the command. Anyone else is refused.

2. Data processed

From Discord (the two staff channels only): message text, sender Discord ID and display name, message ID, time and the message being replied to.

Player game data used to detect cheating and report to staff: SteamID, in-game names and name-change history, server played on; dinosaur species and growth; combat history (attacker, victim, ability, distance, damage, time), kills and deaths; position and movement samples for players on a watch list; nesting/egg actions; counts and rates of game-client commands sent to the server, to detect spam or crash exploits. Sources: game-server logs, the SDVN IslePilot database and read-only inspection of the game-server process.

Moderation records: bans, kicks, slays, reasons and evidence summaries, the approving staff member, dinosaur compensation history. The assistant does not use player IP addresses for decisions and does not post IP addresses to Discord.

3. AI and third-party processing

To understand and answer requests, the assistant sends staff message text, sender display name and ID, recent channel context and relevant player and server data to Anthropic (Claude). Some heavy analysis tasks (for example large log or database analysis) may use OpenAI (Codex). Bot tokens, database passwords and server addresses are not included in data sent. Providers process data under their API terms; SDVN does not use this data for advertising, does not sell it and does not use it to train its own AI models.

Moderation commands are carried out through the game servers' admin interface (RCON) and the SDVN IslePilot system; results are checked against the game server itself before being reported.

4. Automated decisions and command authority

Most enforcement needs human approval: the system proposes an action with evidence and the server owner or co-admin approves or rejects it. Only the server owner and the co-admin can order bans/unbans through the assistant; other admins cannot ban through it.

A few very clear patterns are banned automatically: changing in-game name 3 or more times within 30 minutes; flooding game commands known to crash or freeze a server; and certain specific exploit signatures. Every automatic ban is posted with its evidence to the staff channel and notified to the owner and co-admin. The system also rate-limits some abused game commands; this blocks the command only and does not ban. Automated detection can be wrong; players can appeal any ban through the support email and staff will review it.

5. Storage and retention

Data is stored on SDVN-managed servers with access limited to infrastructure administrators: logs of messages the assistant processed and its replies; action logs (requester, SteamID, result); text of requests escalated for deeper analysis; proposals and approval results; the knowledge notes staff teach the assistant (which may mention player names or SteamIDs); analysis results, evidence reports and player watch lists.

As of the update date these categories have no automatic deletion period; game-server system logs are overwritten progressively by size. SDVN reviews and deletes manually when data is no longer needed or on a valid data request; records needed for an active ban may be kept until the ban ends or an appeal is resolved. Messages the assistant posted to Discord are stored by Discord according to the channel's permissions.

SDVN RCON

The application handles administrative interactions, Discord/Steam identifiers, player information and game-event data needed for requests. Lookup data and activity history are stored in player indexes, combat-history databases and logs. Logs may contain the actor, command arguments and server responses. Data access depends on configured roles; player lookups are returned privately to authorized requesters. This application’s support-ticket feature is not currently enabled.

sepay — payments and benefits

The application receives Discord IDs, Steam IDs, benefit packages, amounts, references and transaction details from user requests and SePay webhooks. It stores the original webhook payload, reconciliation history, benefit changes and actors, and event members/time intervals. SePay provides transaction notifications; VietQR receives the bank code, recipient account number, amount and payment reference to generate a QR image. Discord receives interactions, notifications and role updates. Relevant game-administration information may be passed to SDVN game-server configuration. Pending payment requests expire after 30 minutes, but this does not delete transaction records. Removing an event from the list does not erase reconciliation or time-compensation ledgers. Bot data is stored on encrypted storage with access restrictions; this does not guarantee encryption of every log or copy outside that storage.

Sharing and access

Discord processes interactions, notifications and content posted to Discord by the bots. Steam supports account authentication/linking and player-information lookups where used. SePay and VietQR process payment/QR data as described in the sepay section. SDVN components, including bots, the website, benefit systems and game servers, exchange data needed for the relevant functions.

The website uses Cloudflare to relay and protect traffic; Cloudflare and the web infrastructure may process IP addresses, access times, request paths and browser information. The website uses IslePilot software and may load resources from IslePilot services; using that software does not mean the entire player database is sent to the provider.

Function-authorized staff and infrastructure administrators may access data needed for their work. Responses posted in Discord channels are visible according to channel permissions; private responses are limited by Discord’s interaction mechanisms. Support email is processed through Google’s Gmail, including your email address, message and attachments.

SDVN shares data only as needed to provide the service, on your valid instructions, or to comply with binding legal requirements. Providers may process data in other countries, and data held by providers is also subject to their terms and policies.

For the [SDVN] image-moderation pilot, OpenAI receives a normalized image for classification as described above. Result notifications and relevant identifiers are sent to a private Discord staff channel; original images are not reposted.

For the anti-cheat staff assistant, Anthropic (Claude) and, for some tasks, OpenAI (Codex) receive staff message text, channel context and relevant player data as described in its section above; answers are posted back to the private staff channels on Discord.

Data, log and backup retention

SDVN retains data according to the needs of the relevant functions and applicable legal requirements. Data no longer needed for a function is reviewed for deletion or reduction of identifying information. When a valid data request is received, SDVN checks relevant active records, logs and copies.

RCON combat history is configured to remove records older than 15 days during ingestion. Lookup caches exist only within the process and are distinct from persistent player indexes. Pending sepay payment requests expire after 30 minutes; expiry changes request status and does not delete transactions, webhooks or benefit history.

Player indexes, account links, transactions, original webhooks, reconciliation ledgers, events and some logs currently have no uniform automatic deletion period. They may remain until manually handled. SDVN assesses retention when handling deletion requests, when a function ends or when data is no longer necessary; the absence of automation is not a reason to retain data indefinitely.

Website daily backups are configured for cleanup after 7 days. Web access logs are configured to rotate at 25 MiB, with a 72-hour age limit for rotated files. These are configured limits for specific categories, not a guarantee that all data is erased at the same time; cleanup may not run while a service is stopped.

Manual backups, migration copies and other components’ copies are outside the website’s 7-day period and currently have no uniform automatic expiry. When handling deletion, SDVN identifies copies under its control, deletes data as appropriate or restricts use of data that must be retained by law, and explains what remains. Restoring data requires reconsidering previously completed deletion requests.

Safeguards

The systems include function-specific authorization checks, restricted access to configuration files and certain internal services, and component-specific credential protection. These measures do not mean that every database, log and backup is encrypted. Administrators need to continue reviewing access and data retention; no measure guarantees absolute security.

Access, correction and deletion requests

Email [email protected] with the subject “SDVN — Data request”, the app name, relevant Discord ID or Steam ID and the data you want to access, correct or delete. Provide only necessary identifiers, not passwords, tokens or one-time codes. SDVN may verify control of the account before disclosing or changing data.

SDVN Community administrators receive requests through this email. After verification, SDVN checks relevant components and uses manual handling where automated tools are unavailable. SDVN replies with the outcome, retained data and reasons, or the next step if more information is needed. Requests are handled promptly in accordance with applicable obligations; this is not a promise of instantaneous system-wide deletion.

Unlinking an account or leaving the guild does not automatically erase all game history, payments, logs or backups. For Discord API Data, SDVN handles correction/deletion requests and data no longer needed in accordance with Discord’s terms; retention exceptions are limited to what law requires. Other data may need limited retention to meet legal duties or resolve a valid dispute; SDVN explains the basis and scope rather than applying a blanket exception.

Deleting data needed for a function may make that function unavailable. SDVN cannot directly erase copies controlled by other users or third parties and will direct you to them where appropriate. Deletion is not reported as complete when data has only been hidden, disabled or partly deleted.

Policy updates

SDVN will date updates and announce material changes through community channels. When an app is added or its data processing changes, the relevant list and descriptions must be updated before this policy is used for review submissions.