Privacy Policy

1. Information We Collect

Travian Bot collects data needed to run Discord alliance coordination, web dashboards, billing, hosted bots, support, and optional AI features. Depending on which features your Discord server uses, this may include:

• Discord account and server data: Discord user IDs, usernames, display names, avatar URLs, server IDs, server names, channel IDs, role IDs, owner/admin IDs, command usage, button/modal/select-menu interactions, and permission/configuration choices.
• Travian game data: In-game names (IGNs), alliance membership checks, Travian server URLs, village coordinates, player and village associations from public Travian map.sql files, troop overview text submitted through secure links, tribe, village, troop totals, farm-list entries, artefact assignments, and planner inputs.
• Message and action data: Defence, resource push, alliance push, fake attack, artefact, linked-channel, translation, ranking, suggestion, support, application, contract, announcement, and setup/welcome workflow content when that content is submitted to the bot or required for the feature to work.
• Transcripts: When enabled, generated action or coordination channels may be converted into HTML transcripts containing message content, timestamps, author display information, embeds, reactions, and attachments linked from Discord.
• Web and access data: Secure access tokens, planner share IDs, edit tokens, extension tokens, OAuth state/session records, application session records, IP addresses used for rate limiting or protected pages, browser requests to our API, and local browser drafts saved by the planner in your device storage.
• Email data: Email addresses for request notifications, one-time passcode verification records, customer mailbox records, notification preferences, and email addresses supplied through Discord OAuth for alliance applications.
• Billing and licensing data: License keys, redemption state, purchaser/owner Discord IDs, subscription IDs, transaction IDs, product/price IDs, subscription status, scheduled changes, cancellation/resume/refund records, referral codes, coupons, vote-credit redemptions, and payment-webhook records needed to provide paid access.
• Hosted bot data: Hosted bot owner ID, Discord application ID, bot user ID, bot tag, bot avatar URL, target server ID, encrypted bot token, transcript domain, subscription status, startup/stop state, and last error information.
• Administrative and safety data: Blacklist and ban records, maintenance actions, audit/report records, support and suggestion histories, chargeback review data, and limited operational logs needed to diagnose abuse, errors, billing issues, and service reliability.

2. How We Use Information

We use the collected information to:

• Configure Discord servers, roles, channels, verification, welcome flows, self-service role panels, announcements, DM preferences, and access controls.
• Create, manage, lock, unlock, track, remind, close, and audit defence, resource push, alliance push, fake attack, artefact, and other action channels.
• Verify Travian players, show villages, maintain troop dashboards, manage farm lists, track artefact assignments, and provide planner/share/edit links.
• Relay linked-channel messages, translate selected content, send request notifications, manage support tickets, suggestions, alliance applications, contracts, and feedback.
• Process subscriptions, license keys, hosted bot setup, trial/vote credits, refunds, chargeback reviews, and premium feature limits.
• Run optional AI-assisted parsing, translation, image understanding, setup guidance, and clarification workflows when users submit content to those features.
• Prevent abuse, enforce Terms of Service, rate limit endpoints, troubleshoot errors, preserve security, and keep the service reliable.

3. AI Processing

Some features send user-submitted text or images to Xiaomi MiMo to parse Travian requests, troop reports, screenshots, linked-channel translations, setup questions, and other optional assistant workflows. Submitted content may include Discord message text, Travian screenshots, pasted troop overviews, coordinates, player names, and related Discord user/server identifiers used for rate limits and context.

Xiaomi MiMo processes this content under its own terms and privacy policies. Travian Bot does not ask users to submit Travian account passwords, Discord passwords, session cookies, or private game-login credentials.

4. Data Retention and Controls

Retention depends on the feature:

• Transcripts: HTML transcripts are automatically deleted after 14 days. Transcript generation can be disabled or enabled by server administrators with /disable-transcript and /enable-transcript. Transcript generation fetches up to 500 recent channel messages.
• Temporary access links: Troop submission links expire after about 10 minutes and are single-use. Troop admin dashboard links expire after about 1 hour. Planner edit tokens expire after about 30 minutes. Alliance application OAuth state and session records expire automatically.
• Server configuration and feature records: Guild configuration, verification mappings, action tracking, troop submissions, planner shares, artefact state, suggestions, support tickets, application records, rankings, billing, license, hosted bot, email-notification, and safety records are retained while needed to provide the feature, support the server, comply with billing obligations, prevent abuse, or resolve disputes.
• Local browser data: The planner may save drafts in your browser storage. You can clear this through your browser controls.
• Discord content: Deleting messages or channels in Discord may not delete records already required for bot operation, audit, support, billing, safety, or configured transcript retention.

Server administrators can disable selected features, clear some dashboards such as troop submissions, reset configuration, revoke or regenerate certain links/tokens, and request deletion or correction where feasible.

5. Data Storage and Security

Operational data is stored in our database, file storage, and server-side service records. Hosted bot tokens and alliance application OAuth tokens are encrypted before storage. Access is limited to authorized bot processes and administrative maintenance. We use rate limits, security headers, tokenized links, permission checks, and role-based Discord access controls to reduce unauthorized access.

No system can be guaranteed perfectly secure. Users should avoid submitting Travian passwords, Discord passwords, private cookies, recovery codes, banking credentials, or other credentials to bot commands, web forms, support tickets, transcripts, or AI features.

6. Sharing and Third-Party Services

We do not sell personal information. We share or transmit information only as needed to operate the product, provide requested features, process payments, comply with law, prevent abuse, or protect the service.

Travian Bot depends on third-party services including:

• Discord: The bot operates inside Discord and uses Discord APIs, OAuth, messages, roles, users, servers, webhooks, and attachments. Discord's own policies apply to your Discord account and Discord-hosted content. See the Discord Privacy Policy and Discord Terms of Service.
• Travian public data: The service fetches and caches public map.sql files and official calendar/server metadata from Travian domains to power map, village, verification, and planning features.
• Paddle: Billing, checkout, subscriptions, customer login, payment webhooks, cancellations, resumes, refunds, adjustments, and hosted bot subscriptions are processed through Paddle. Payment information is handled by Paddle, not by Travian Bot directly.
• Xiaomi MiMo: Optional AI features may send submitted content to Xiaomi MiMo. Xiaomi processing is subject to the Xiaomi MiMo Open Platform Privacy Policy and Xiaomi MiMo Open Platform User Agreement.
• Email infrastructure: Email notification, customer mailbox, one-time passcode, and application-decision features use Travian Bot-managed mail infrastructure and may transmit email metadata and message content through normal email delivery systems.
• Top.gg and other public integrations: Voting credit features may check vote status or redemption state with external services where needed.

7. Your Choices

You can stop using the bot, remove it from a Discord server, disable optional features, opt out of announcement DMs, disable email notifications, disable transcripts, avoid AI-assisted features, or ask a server administrator to remove feature-specific records where the product supports it. For data tied to Discord itself, use Discord's account and server controls.

For access, correction, deletion, or privacy concerns, email [email protected]. Include the relevant Discord user ID, server ID, and feature context so we can locate the record.

8. Contact

For privacy concerns or data requests, email [email protected].