SailBot
Privacy Notice
Who is responsible
Cameron Read, doing business as Read's Digital Media Services in Florida, United States, operates SailBot and is responsible for this notice. Questions and privacy requests can be sent to contact@readsdigitalms.com.
Scope
This notice explains how SailBot and the SailBot web dashboard handle information received through Discord and related service operations. Discord separately handles Discord accounts, communications, checkout, and other platform activity under Discord's own privacy terms. The general Read's Digital website is covered by the website Privacy Notice.
Information SailBot receives
Depending on the features used, SailBot receives Discord server, user, channel, role, message, interaction, and entitlement identifiers; server configuration and permission-related information; and information submitted through profiles, applications, events, crews, in-game Guild features, and configuration flows. Submitted information can include time zone, availability, activity preferences, playstyle, descriptions, application answers, and private Custom Server access details.
We receive this information from Discord, from server administrators and organizers, and from users who interact with SailBot. Operational logs may include timestamps, command or interaction names, error details, and identifiers needed to investigate reliability or abuse. We design logs not to include message text, voice audio, passwords, payment-card numbers, or private Custom Server access details.
Dashboard sign-in and sessions
The SailBot dashboard uses Discord OAuth with the identify and guilds permissions. When a person signs in, Discord provides the person's Discord user ID, username, display name, avatar, server list, and server permission information. We use that information only to authenticate the person and show SailBot servers that the person is authorized to manage.
The dashboard stores the Discord access token, refresh token, basic profile, and a request-verification token inside an encrypted, secure, HTTP-only session cookie. These credentials are not written to SailBot's database or exposed to browser scripts. The session lasts no longer than seven days, may refresh during that period, and is cleared from the browser when the person signs out. Discord may separately retain authorization records under its own policies. Dashboard changes to server settings are stored in SailBot's existing server-configuration records.
Activity tracking defaults
Message and voice activity tracking is enabled by default for a configured server unless a server administrator disables it. For message activity, SailBot records that a non-bot message occurred, together with the server, user, channel, and time; the activity feature does not use or store the message text. For voice activity, SailBot records the server, user, channel, session time, and duration; it does not record voice audio.
Leaderboards are disabled by default. If a server administrator enables them, a member must separately opt in before that member appears on a leaderboard. Disabling activity tracking stops new activity records but does not immediately erase records already collected; a deletion request can be made as described below.
Why we use information
We use information to respond to commands and interactions; authenticate dashboard users; verify server-management permission; display and update authorized server settings; provide profiles, events, crews, Guilds, applications, reminders, temporary resources, activity statistics, and paid entitlements; prevent abuse; troubleshoot failures; maintain security; respond to support and privacy requests; and comply with legal obligations.
Who receives information
Information may be displayed within the Discord server and feature context in which it is used. For example, authorized organizers may review an application, event participants may receive permitted event information, and opted-in members may appear on an enabled leaderboard. Server administrators control many roles and permissions, so users should understand their server's rules before submitting information.
Discord provides the application platform and subscription checkout. Railway provides application hosting and database infrastructure. Those providers process information under their own terms and privacy practices. We may also disclose information when reasonably necessary to comply with law, protect a person or the service, investigate abuse, or complete an action requested by the affected user. We do not sell personal information or use SailBot data for third-party targeted advertising.
Payments
Discord and any applicable app marketplace process checkout and payment details for Guild Plus. SailBot receives entitlement information needed to determine whether a server has paid access. Read's Digital does not operate a separate payment form and does not receive or store customers' full payment-card numbers.
Current retention status
Automated deletion is not currently enabled in SailBot's production configuration. As a result, we do not represent that existing records are automatically deleted on the target dates below. Until automated deletion is enabled and verified, information may remain beyond those targets unless it is manually deleted following a verified request or is removed during an authorized operational cleanup.
The planned automated targets are: 30 days after collection for message and voice activity records; 90 days after resolution for resolved applications; 90 days after completion, cancellation, expiration, or closure for terminal events and crews; within 24 hours after event completion or cancellation for private Custom Server access details; and 30 days after SailBot is removed for inactive server data and settings, unless the bot is reinstalled first. These targets do not become operational promises until this notice is updated to confirm that production deletion is active.
We may retain the minimum information reasonably necessary for an active event, support request, security investigation, dispute, fraud prevention, enforcement of these terms, or legal obligation until that need ends. Service-provider logs and backups may persist for their configured recovery or security periods and may not be removed immediately from every copy.
Your choices and requests
A server administrator can disable new activity tracking through SailBot's settings. Members can choose whether to opt in to an enabled leaderboard. A user may request access, correction, or deletion by emailing contact@readsdigitalms.com with the user's Discord ID and relevant server ID, if available. A server owner or authorized administrator may request removal of server-scoped data.
We may ask for reasonable verification before acting. We will respond within 30 days by completing the request or explaining its status, any information needed, and any permitted reason that some information cannot yet be deleted. A request cannot require us to alter another person's records improperly or remove information still reasonably needed for an active shared feature, security matter, dispute, fraud prevention, or legal obligation.
Security
We use access controls, separated development and production environments, managed secrets, and other reasonable technical and operational safeguards. No online service can guarantee absolute security. Please do not submit sensitive information that SailBot does not need, and contact us promptly if you believe information has been exposed or misused.
Children
SailBot is not directed to children under 13 and must not be used by anyone who does not meet Discord's minimum age requirement. If you believe a child provided information in violation of that requirement, contact us so we can investigate and take appropriate action.
Changes and contact
We will update this notice when SailBot's features, providers, data practices, or production-retention status materially change. The effective and last-updated dates above will identify the current version. Questions, requests, or complaints can be sent to contact@readsdigitalms.com.