Privacy Policy

1. Who operates TerminalEZ

The TerminalEZ owner operates this application and decides its permitted servers and administrator access. Server administrators configure features within their approved servers. Discord operates the platform separately under Discord’s Privacy Policy.

For privacy questions, access, correction, or deletion requests, contact the TerminalEZ owner through the server’s staff or support channel. Ask staff to forward your request privately if you cannot contact the owner directly.

2. Information processed

• Discord sign-in: account ID, username, avatar reference, server memberships, and server permissions returned by Discord’s identify and guilds OAuth scopes. These check your identity and assigned dashboard access. The application does not request your Discord password or the email scope.
• Server setup: server, channel, role, and message IDs; bot profile preferences; plugin settings; message templates; configured image URLs; and the owner’s private access configuration.
• Levels and community activity: user IDs, XP, eligible message counts and activity timestamps, rank-card style and frame preferences, achievements, virtual balances, and reward timestamps.
• Optional submissions: birthday day and month (not birth year), reminder text and delivery times, poll questions and options, giveaway details, and configured graph data.
• Moderation and events: message content and metadata available to the bot for moderation or search; warning reasons, moderator identifiers and timestamps; membership, role, invitation, reaction, and voice-channel events used by enabled features. The bot does not record voice audio.
• Operational information: connection IP addresses for dashboard rate limiting, session identifiers, and diagnostic errors. Hosting services may also process connection metadata for operation and security.

Available data depends on enabled features, Discord permissions, and what you submit. The current bot does not keep a separate database archive of every server message. However, deleted-message logging can copy up to 1,000 characters of available message text into a configured Discord log channel. Deleting the original message does not delete that copy.

3. How information is used

Information is used to authenticate approved administrators, apply server-specific permissions, operate selected moderation and community features, deliver requested messages, and investigate technical problems or misuse. It is not used for advertising, sold to data brokers, or used by TerminalEZ to train AI models.

Optional birthdays and reminders use information you submit for those features. Server-level moderation, activity counting, and logging can process messages or events even when a member has never opened the dashboard. Ask server staff which features are enabled.

4. Sessions, cookies, and browser storage

The dashboard uses an essential cookie named terminalez.sid to identify your login session. Its configured lifetime is up to seven days. The server holds your basic Discord profile, OAuth access token, and security values in session memory. Sessions can end sooner on logout, expiry, or server restart.

IP-based rate-limit records are held temporarily in memory for the applicable limit window. The application does not include advertising cookies or third-party analytics. Browser preview or display preferences, where used, are not a replacement for server-side access checks.

5. Storage, visibility, and other services

The current build stores persistent settings and feature records in a JSON data file controlled by the owner, rather than SQLite. The intended live deployment uses an Oracle Cloud server in Melbourne, Australia. During setup or maintenance, the owner may also hold local development copies.

The owner has operational access to stored records. Approved administrators can access their assigned server’s dashboard features; moderators and support staff may see records through Discord permissions. Ranks, leaderboards, balances, polls, giveaways, and announcements may be visible to other members in the channels where they are posted. Ticket visibility depends on channel permissions, including Discord administrator access.

Discord receives bot messages and actions and stores channel content, including tickets and log messages, under its own policies. Oracle processes hosted data to provide infrastructure. Images requested from Discord’s CDN or a configured external image host can disclose the requesting server’s or viewer’s IP address to that host. Those providers may process data in other countries under their own policies.

No private administrator list is published by these policy pages. Information may also be disclosed where legally required or necessary to respond to a security incident, limited to what is appropriate for that purpose.

6. Retention and deletion

Most persistent feature records currently have no automatic age-based deletion. They remain until the owner removes or resets them. Disabling a plugin, leaving a server, or removing the bot does not by itself erase existing records. The owner must review and remove records no longer needed for the stated purposes.

Completed reminder records are eligible for cleanup after about one day; cleanup occurs when the reminder-completion routine runs, not on a guaranteed daily schedule. Pending reminders remain until processed or manually removed. Messages, tickets, and log copies already posted to Discord remain until deleted there by someone with the necessary permission.

There is currently no self-service deletion command. To request a copy, correction, or deletion, provide your Discord user ID, the relevant server, and the feature or record concerned through the contact route above. We may need to verify the request using your Discord account; never provide your password or token. If a record must be retained for a specific legal or safety reason, the owner will explain the limitation where permitted.

Requests must also be considered for owner-controlled local copies and any backups. This deployment has no configured automatic backup-expiry schedule. Discord’s independent copies and records outside the owner’s control are subject to Discord’s processes. Depending on where you live, you may have additional privacy rights and the right to contact a privacy regulator.

7. Your choices and security

You may decline optional submissions, ask the owner to remove stored feature data, log out, or revoke TerminalEZ in Discord’s authorised applications settings. Revoking dashboard access does not remove server-level bot records. To avoid new server-event processing, discuss feature restrictions with staff or leave the server.

Access checks and security controls reduce risk, but no system guarantees absolute security. Do not put sensitive personal information in reminders, public commands, ticket messages, or image URLs. Report suspected disclosure privately to the owner. The owner is responsible for investigating incidents and notifying affected people and Discord when required.

TerminalEZ is not intended for people below Discord’s minimum age for their country. Contact the owner if you believe information about an ineligible child has been collected.

8. Policy changes

This page will be updated when the application’s data practices change. Material changes will be communicated through the affected server before new processing begins where practicable. The date above identifies the current version.