Privacy without fake legal fog

HashBot is a practical event aggregator, not a surveillance hobby. The goal is to make it easier to find trail, not to build an unnecessarily creepy dossier on half-minds in Central Florida.

What HashBot stores

• Public kennel and event data pulled from public calendar feeds and related sources.
• Basic web request data such as IP-based rate limiting signals needed to keep the API from being abused.
• Chat history for web sessions, limited to recent messages so the assistant can maintain context.
• Session identifiers issued by the server and stored in your browser so the chat widget can pick up where it left off.

What HashBot does not aim to collect

• Account profiles or passwords, because the MVP does not have user accounts.
• Precise device tracking beyond what is operationally necessary for rate limiting and debugging.
• Private messages from kennel groups, private calendars, or anything behind a login wall.

How chat data is used

Web chat messages are used to answer your question and keep short conversation continuity. The system is designed around recent context, not permanent user profiling. If you ask about the next O2H3 hash and then follow up with "what should I bring," the earlier message helps the assistant answer coherently.

Do not put sensitive personal information into the chat. This is a trail helper, not a secure vault.

Third-party services

HashBot may call external services for AI responses and geocoding. Those providers only receive the minimum information needed for that task, such as a chat prompt or a location string to turn into map coordinates.

Updates

This privacy page will change as the product grows. If HashBot adds accounts, subscriptions, or new communication channels later, the policy should become more specific. Until then, the MVP rule is simple: collect the least data that still lets the app work.