River Bot
Privacy Policy

Your data, explained.

Draft for the implementation in this package · Updated October 26, 2026

This policy describes the supplied website integration and inspected bot source. The operator must confirm its actual hosting, logs and retention settings before launch.

1. Who operates River Bot

River operates River Bot. Privacy and deletion contact: Riverdogs009@gmail.com.

2. Discord data

The bot uses Discord user, server, channel, role and message identifiers, server settings, and records needed by enabled community tools. Depending on configuration, moderation, welcome, ticket, giveaway and custom-command modules process related content and events. The website integration stores the target server ID and the authorized Discord owner ID supplied by the operator.

3. TikTok account data

When you authorize TikTok, we receive an application-specific account identifier, granted scopes, access and refresh tokens, and token expiry information. We fetch your display name and public video metadata such as video ID, title, description, creation time and share URL. We do not request private videos, direct messages, follower statistics or permission to publish content.

4. Why we use it

We use data to associate an authorized account with the correct server, maintain API access, identify public videos, send requested notifications, prevent repeat delivery and diagnose service errors. Your display name and public video links may be shown in the configured Discord channel.

5. Credentials and sessions

The supplied backend encrypts TikTok credentials at rest using AES-GCM with a separate secret key. Client secrets and tokens stay on the server. Short-lived invitations and session identifiers are stored as hashes. An essential Secure, HttpOnly cookie maintains your connection-management session for up to one hour; no advertising or analytics scripts are included in this site.

6. Retention

Connection credentials and the associated profile identifier remain until disconnection or an operator deletion. Invitations and OAuth state expire after 10 minutes; sessions expire after one hour. Expired authentication records are cleaned during subsequent integration requests, so physical deletion may occur after expiry. Disabled integrations reject access even before cleanup.

The existing bot stores server settings and persistent delivery records until the operator deletes them; this package does not impose an automatic retention period on that separate database. Hosting logs and backup retention depend on the operator’s selected provider settings and must be documented before launch. We do not promise that deleting active records immediately erases provider-managed backups.

7. Disconnect and delete

Disconnecting deletes active website credentials, connection data, invitations and sessions for the server and attempts to revoke TikTok authorization. If TikTok cannot confirm revocation, you are told to revoke access in TikTok as well. Discord messages and the bot’s delivery history are not automatically deleted by disconnection. Request those separately through Riverdogs009@gmail.com.

We may verify your identity and server authority before acting on requests. Where applicable, you may request access, correction or deletion, object to processing, withdraw consent or contact a privacy regulator.

8. Service providers

The intended deployment uses Cloudflare Pages and D1 for the website, encrypted integration data and request processing; PebbleHost for the separate Discord bot; Discord for community interactions and notifications; and TikTok for authentication and authorized API data. These providers may process technical information such as IP addresses and request metadata under their own policies and in other countries. No advertising data sale is implemented.

9. Security and limitations

We restrict sensitive data to backend processing, use HTTPS, validate OAuth state and limit requests. No system is perfectly secure. Do not share private connection invitations or session cookies. The operator must protect deployment access, encryption keys, backups and bot credentials.

10. Policy changes

We update this page when data practices change. The date above identifies the latest revision. Contact Riverdogs009@gmail.com with questions.