Legal

Terms of Service and Formal Privacy Disclosures for Tabletop Time.

Terms of Service

Last Updated: May 1, 2026

Welcome to Tabletop Time. By using this service, you agree to these basic terms. If you disagree with them, please do not use the site.

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.

Formal Privacy Disclosures

Last Updated: May 1, 2026

Tabletop Time is a free, open-source personal project built by Christopher Melson. While we operate on a "Zero Tracking" philosophy, here are the technical realities of how data is processed:

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

If you choose to link Discord or Telegram for session recovery, we receive basic authentication tokens from those services. We do not pull your friend lists, message history, or other profile data.

Data Rights & Contact

Because we do not use accounts, we cannot verify your identity to process manual data deletion requests for event sessions. To remove session data, either ask your Event Host to delete the event, or wait for the automated 24-hour server purge. For general policy questions, please open an issue on our GitHub Repository.