Privacy Policy

• Information you provide directly, such as your name, email address, organization, role, messages, demo requests, support case descriptions, customer replies, feedback, and any other details you choose to send us.
• Program access application information, including the founder or creator track you select, coaching role or creator profile, public context, intended usage, evidence links, and acknowledgement choices.
• Account, organization, and service information created when you or your organization use HotRoute web properties, including profile details, setup information, and materials you choose to create, upload, or manage through the service.
• Support and service-history information, including support case status, participants, assignments, customer-visible replies, internal support notes, administrative support events, and troubleshooting context.
• Billing and payment-related information needed to manage subscriptions, invoices, renewals, taxes, fraud prevention, and account records. Payment instrument details may be handled directly by our payment processor rather than stored by HotRoute.
• AI-assisted workflow information when an approved workflow uses a model provider, such as prompts, responses, retrieved product or support context, and request metadata needed to provide, evaluate, secure, or audit the workflow.
• Technical and usage information generated through normal operation of HotRoute web properties, such as IP address, browser type, device information, pages or features accessed, referring pages, timestamps, and security or system logs.
• Information shared with us by your organization or another authorized user when they invite you to collaborate or otherwise use a HotRoute web property.
• Youth, school, roster, parent or guardian, and student-related information when provided through an approved HotRoute workflow by an authorized youth organization, school, district, parent, guardian, or coach/staff representative acting within that already-authorized context.

• Provide, operate, maintain, secure, and improve HotRoute web properties.
• Respond to inquiries, demo requests, support needs, and other communications.
• Create, manage, and support accounts, organizations, and access to HotRoute services.
• Preserve operational context, continuity, and service history across the HotRoute experience.
• Operate customer support workflows, support case history, internal support notes, and customer-visible support communications.
• Process billing, subscriptions, renewals, invoices, taxes, fraud prevention, and related account administration.
• Power approved AI-assisted workflows that help operate, support, secure, troubleshoot, or improve HotRoute, subject to review and security controls.
• Support approved youth, school, roster, player, parent or guardian, and team workflows after the required parent, guardian, school, or district authorization has been established.
• Send administrative, operational, product, support, and policy-related communications.
• Review founder or creator access applications, assess eligibility, follow up about the application, and maintain an operational record of review outcomes.
• Detect, investigate, and address fraud, misuse, unauthorized access, security incidents, or other harmful activity.
• Comply with legal obligations, enforce agreements, and protect HotRoute, our users, and others.

HotRoute may process private customer support cases through approved customer operations tools. Support records may include customer messages, organization context, troubleshooting details, status history, support-admin assignments, and internal notes needed to resolve and audit support work.

• Private support cases may include the information you submit, case participants, case status, assignments, customer-visible replies, and operational metadata.
• HotRoute support admins may create internal notes and administrative events for troubleshooting, continuity, accountability, security review, and support operations.
• Support case access is designed around requester, participant, organization staff, and allowlisted HotRoute support-admin scopes; this policy does not expand those access rights.

HotRoute may share information in the following situations:

• Service providers and infrastructure partners that help us host, store, secure, operate, support, analyze, or maintain HotRoute web properties.
• Your organization and authorized users when your use of HotRoute is tied to an organization, team, staff, or shared account context.
• Parents, guardians, schools, districts, or other authorized organization representatives when needed to provide notice, verify authority, process requests, support student or youth use, or meet legal and contractual obligations.
• Payment processors and billing service providers when needed to manage subscriptions, invoices, taxes, fraud prevention, refunds, chargebacks, or other payment-related operations.
• Model providers when an approved AI-assisted workflow needs prompts, responses, product context, support context, or related metadata to complete the workflow.
• Internal operations or support tools when customer information is manually routed for escalation, incident response, troubleshooting, or customer operations.
• Professional advisors, legal counsel, insurers, auditors, or similar parties when reasonably necessary for legitimate business, legal, or compliance needs.
• Government authorities, regulators, courts, or other parties when required by law or when reasonably necessary to protect rights, safety, security, or the integrity of the service.
• A buyer, investor, successor, or other relevant party in connection with a merger, acquisition, financing, reorganization, or similar business transaction.
• Other parties when you direct us to share information or clearly consent to a specific disclosure.

HotRoute uses service providers and subprocessors to host, secure, operate, support, analyze, bill, and improve the service. Vendor use can vary by feature and launch phase.

• Supabase supports authentication, database, and row-level-security-backed product and support data storage.
• Vercel supports hosting, deployment, operational delivery, and optional public-site analytics after consent.
• Google Analytics supports optional public-site usage measurement after consent.
• Stripe may support billing and payment workflows when subscription billing is enabled.
• OpenAI, Anthropic, or another approved model provider may receive prompts, responses, and relevant context only when an approved AI-assisted workflow uses that provider.
• Email, customer operations, or internal collaboration providers may process contact, support, or incident context if HotRoute uses those tools for communications, escalation, or operations.

• HotRoute public sites use one strictly necessary first-party cookie named hotroute_public_consent to remember whether you rejected optional tracking or allowed analytics on that specific site.
• The consent cookie does not store your marketing profile or broader browsing history. It only stores the preference needed to respect your choice on later visits.
• Optional measurement on the public marketing site and docs site is limited to Vercel Web Analytics and Google Analytics. HotRoute does not currently load advertising pixels, chat widgets, session replay, or similar optional tracking on those public sites.
• HotRoute does not use child or student information for targeted advertising, behavioral advertising profiles, or advertising-pixel audiences.

If you allow analytics, HotRoute may load Vercel Web Analytics and Google Analytics to understand aggregate page usage on the public marketing site and docs site. We treat that measurement as optional and do not activate it before you consent.

You can reopen or change your cookie preferences at any time through the “Cookie Preferences” control in the footer of each public site.

HotRoute may use approved AI-assisted workflows to operate, support, secure, troubleshoot, or improve HotRoute. Those workflows may send a model provider prompts, responses, user-submitted content, organization or team context, support-case excerpts, product metadata, and request metadata when that context is needed for the workflow.

AI output is assistive. HotRoute remains responsible for review, support decisions, and authoritative product actions. HotRoute does not authorize model-provider training on customer content unless that use is explicitly approved and disclosed.

Model-provider retention, abuse monitoring, and review rights depend on the provider, product, and configuration used for the workflow.

We retain personal information for as long as reasonably necessary to operate HotRoute web properties, maintain service continuity, keep appropriate business records, resolve disputes, enforce agreements, and meet legal, security, or operational obligations.

Retention periods can vary based on the kind of information, the context in which it was collected, the sensitivity of the information, and whether the information is tied to an active account, organization, support matter, or legal obligation.

• Account, organization, team, product, and support records are generally retained while the account, organization, customer relationship, or support need remains active.
• Support cases, internal support notes, admin events, audit records, billing records, and security logs may be retained longer when needed for support continuity, legal obligations, accounting, fraud prevention, security, dispute resolution, or operational accountability.
• AI prompts and responses are retained only as needed for the approved workflow, provenance, support continuity, evaluation, abuse review, audit, or security needs.
• Child and student information is retained only as long as reasonably necessary for the disclosed youth, school, team, legal, security, contractual, or operational purpose, then deleted, de-identified, or returned according to the applicable request, contract, or retention rule.
• Backups and provider recovery artifacts may retain deleted information until backup expiry; if information is restored from backup, deletion requests should be replayed or otherwise honored again.
• When information is no longer reasonably needed, HotRoute deletes it, de-identifies it, or limits its retention as appropriate.

HotRoute uses reasonable administrative, technical, and organizational safeguards designed to protect personal information and reduce the risk of unauthorized access, loss, misuse, or disclosure.

No system can guarantee absolute security. If you believe your information or account has been exposed or used improperly, please contact us promptly at sales@hotroute.io.

You can contact HotRoute to ask questions about this policy or to request that we review, update, correct, or delete certain personal information, subject to applicable legal, security, contractual, and operational requirements.

Before acting on account, organization, team, product, support, billing, export, or deletion requests, HotRoute may verify your identity, account ownership, organization authority, and the scope of the request.

Deletion can be limited or delayed when information must be retained for legal, tax, accounting, fraud prevention, security, audit, backup, support continuity, dispute resolution, or contractual reasons. When a service provider acts as a processor for HotRoute, HotRoute will route eligible deletion or return requests to that provider as appropriate.

To make a privacy-related request, email sales@hotroute.io. We may need to verify your identity or authority before we act on a request.

HotRoute may support youth teams, school teams, and under-13 athletes through approved product workflows. Those workflows require the appropriate parent, guardian, school, district, or youth organization authority before HotRoute collects, uses, or discloses child or student personal information beyond the limited information needed to provide notice, obtain authorization, or handle a verified request.

HotRoute is not a general child self-signup service. Under-13 athlete access must be connected to an approved team, organization, parent, guardian, school, or district context, and child or student information must be limited to what is reasonably necessary for the disclosed football, teaching, team, support, security, legal, or operational purpose.

• Under-13 athletes may use approved HotRoute product surfaces only when a parent, guardian, school, district, or other authorized youth organization has provided the authorization required for that use.
• HotRoute does not treat a coach, staff member, or organization admin permission as a substitute for parent, guardian, school, or district authorization unless that model has been approved for the specific workflow.
• If HotRoute needs to contact a parent or guardian before collecting, using, or disclosing a child's personal information, HotRoute collects only the information needed to send notice, obtain consent, or handle the request and deletes that contact information if authorization is not completed within a reasonable time.
• Parents, guardians, schools, and districts may contact HotRoute to request review, correction, deletion, revocation, or prevention of further use or collection of a child's or student's personal information, subject to identity, authority, legal, security, and contractual verification.
• When HotRoute works with schools or districts, student information may be subject to school contracts, district data-protection terms, FERPA, state student-privacy laws, and similar requirements.

If you believe HotRoute has collected child or student information without the required authorization, or if you want to make a parent, guardian, school, district, or student privacy request, contact us at sales@hotroute.io.

We may update this Privacy Policy from time to time as HotRoute grows, launches new web experiences, or changes how it operates.

When we make updates, we will revise the “Last updated” date on this page and, when appropriate, provide notice through the relevant HotRoute web property.

For privacy questions, requests, or concerns, contact:

Absolute Zero LLC
sales@hotroute.io