TidalWaveNo legal validity or GDPR compliance is claimed. The operator must verify and complete the relevant information before public launch.
Website privacy information
The supplied TidalWave website code uses no analytics, browser local storage, embedded third-party media, or remote fonts. When account features are enabled, an essential HTTP-only session cookie keeps you signed in and protects account forms. Public pages do not start new sessions. Email links open your email application.
Discord accounts and verification
Discord sign-in requests your permanent Discord ID and username, not your email or message history. The website stores these identifiers, account creation time, server-verification status and time, and bot installation records. Discord handles sign-in and server installation authorization. Account verification and installation eligibility are separate from Discord’s own verification or safety labels.
Verification normally uses /verify without a code. Legacy verification codes, if requested through the older endpoint, are stored as hashes and expire after ten minutes. Signed slash-command requests confirm the requesting Discord account and server. Current verification-server membership is checked through Discord before installation. OAuth access and refresh tokens are not stored after the request completes.
Sessions expire after one hour of inactivity or eight hours overall. Codes expire after ten minutes; verification lasts thirty days and current membership is checked again when installing. Hashed rate-limit identifiers and interaction IDs expire on short windows and are removed by scheduled maintenance. Accounts and installation records remain until account deletion; a blocked account’s Discord ID is retained separately until an administrator clears the block. Server logs, backups and Discord’s own retention must still be verified for the deployed service.
You can delete your website account from the account page. This removes the website profile, verification codes and installation records, and invalidates its sessions when next accessed. Existing forum questions and replies remain, with their author shown as Deleted account. It does not uninstall Discord bots or revoke authorizations held by Discord. This describes the supplied implementation and is not a completed legal assessment.
TO BE COMPLETED
- Controller’s full legal identity, address, jurisdiction, and required contact details.
- Actual hosting, access logs, error logs, email processing, recipients, storage locations, backups, retention and deletion processes.
- Applicable legal bases for account, verification, security and installation processing, international transfers, rights procedures, and supervisory authority details.
- Effective date and verification against the deployed website and infrastructure, including Discord and scheduled cleanup.
Forum and project publishing
Forum questions, replies, author usernames, and posting times are public. Signed-in users may delete their own questions and replies; the administrator may moderate discussions and block or delete accounts. Account deletion anonymizes existing contributions. Project files uploaded by the administrator become publicly downloadable only when the project is published. GitHub project import requests public repository metadata from GitHub; website visitors are not signed in to GitHub by this integration.
Service-specific information
Synatra’s existing drafts remain separate. Read the Synatra Privacy Policy and Synatra Terms of Service.
Questions: tobias30yt@outlook.com