Legal

1. The Service is Provided "As-Is"

Tabletop Time is a free, personal project. While we strive to keep the service fast and reliable, we do not guarantee 100% uptime. The service is provided "as is" and "as available" without warranties of any kind. We reserve the right to modify, suspend, or shut down the service at any time without notice.

2. Acceptable Use

This tool is built to help people schedule games. You agree not to:

• Use the service for any illegal purposes.
• Spam the system with automated bots or generate a volume of events that degrades server performance for others.
• Include malicious links, hateful content, or illegal material in your event titles or descriptions.
• Attempt to reverse-engineer or compromise the security of the hosting infrastructure.

We reserve the right to block IPs or delete events that violate these rules or threaten the stability of the platform.

3. Donations

If you choose to support Tabletop Time via Ko-fi, we are incredibly grateful. Please note that donations are entirely voluntary gifts to help cover server and development costs. They do not constitute a purchase of goods, premium services, or service-level agreements (SLAs), and are non-refundable.

4. Open Source & Self-Hosting

The code for Tabletop Time is open source and available on our GitHub repository. If you choose to deploy your own self-hosted instance using our Docker image, you are solely responsible for its operation, security, and legal compliance. We provide no official support or warranties for self-hosted instances.

5. Limitation of Liability

To the maximum extent permitted by law, Christopher Melson and Tabletop Time shall not be liable for any direct, indirect, incidental, or consequential damages resulting from your use of the service. If a server glitch deletes your event and your group misses out on a game of Root or a Magic draft, we apologize for the inconvenience, but we are not legally or financially liable.

6. Changes to These Terms

We may update these terms occasionally to reflect changes in the project. Continued use of the site after updates constitutes acceptance of the new terms.

Data We Collect

We only store the data you explicitly provide to make the app work: proposed event times, display names, and availability votes.

Donation Records & Public Shoutouts

If you generously choose to support the project financially via Ko-fi, you control what is shared. If you make a "public" donation, we store your provided name, transaction ID, amount, and message, and proudly display your name and message on our homepage ticker to thank you. If you mark your donation as "private" on Ko-fi, our system simply drops the webhook data and we do not store your record in our database at all. Unlike event data, public donation records are retained long-term and are not subject to the automated server purge.

Server Logs

Like almost all websites, our hosting infrastructure temporarily logs standard request data (such as IP addresses and browser types) solely for security, performance monitoring, and DDOS prevention.

Optional Integrations (Discord & Telegram)

If you choose to link Discord or Telegram, here is exactly what we store: your user ID and username on the participant and event records you link, plus the server ID, channel ID, and pinned message ID for any event a host connects to a channel. If you change your direct message setting, we store that choice with your platform user ID (and nothing else) so the bots respect it. We never store your access tokens, and we never read your friend lists, message history, or other profile data.

Our bots send direct messages for these purposes and nothing else: magic login links you request (including an organizer's manager login link), waitlist promotion and removal notices, finalize results for events you joined, and quorum alerts to the organizer. If you linked Telegram or Discord, you can turn off these direct messages from your My Events page; login links you request are still sent, and group or channel posts are not affected. Automated posts in a connected group or channel are the live dashboard, a short announcement with the event title and link when a host connects a Discord channel, a notice in a Telegram group asking for the Pin Messages permission if the bot cannot pin the dashboard, a short "updated their availability" post when someone votes (naming that voter, at most once per person per hour), slot changes, dashboard edits for location changes, finalize announcements, cancel and delete announcements, and the voting or session reminders the organizer enabled. We do not send promotional messages, and we never contact you outside of these functions.

This linked identity data is deleted together with the event by the automated cleanup (see Data Rights below for the schedule), and you can delete it yourself at any time.

Data Rights & Contact

If you linked Discord or Telegram, you can delete that data yourself: open the Privacy & Data page while logged in with that platform and use "Unlink" under Linked Accounts. This immediately removes your platform identity from every participant record, every event you manage, and any pending login links.

For anonymous event data (names and votes entered without any linked account), ask your Event Host to delete the event, or wait for the automated cleanup. Events are deleted one day after they end (a one-shot one day after its chosen slot, a campaign one day after its last session), drafts one day after their last proposed time, and cancelled events one day after cancellation. Self-hosters can change these with the CLEANUP_RETENTION_DAYS_* variables. No third-party analytics run on the hosted site. For anything else, including deletion requests we should handle manually, open an issue on our GitHub Repository and we will respond there.