Skip to content
Teamy Logo

Privacy Policy

Last updated: March 4, 2026

1. Overview

This Privacy Policy explains how Teamy ("we," "our," or "us") collects, uses, shares, and stores information when you use the Service.

This policy should be read together with our Terms of Service.

2. Information We Collect

2.1 Information You Provide

  • Account information from Google sign-in when Google OAuth is enabled (such as name, email address, and profile image)
  • Club, team, role, roster, and membership information
  • Content you create in the Service (announcements, calendar entries, tests, submissions, files, attendance, forms, and similar content)
  • Tournament and hosting information you submit
  • Billing metadata needed to manage subscriptions
  • Messages sent through contact forms or support channels

2.2 Information Collected Automatically

  • Basic request and device metadata (for example IP address, browser type, and user agent)
  • Session and preference cookies (for example auth session, theme, and last visited club)
  • Application and API logs used for operations, debugging, abuse prevention, and security
  • Usage and performance analytics data (for example Vercel Analytics and Speed Insights in the authenticated app)

2.3 Payment Information

Payments are handled by Stripe. We do not store full payment card numbers in our database. We store limited billing and subscription metadata needed to operate paid features, such as Stripe customer IDs, subscription IDs, subscription status, and period end dates.

3. How We Use Information

We use information to:

  • Operate and provide the Service
  • Authenticate users and manage accounts
  • Support collaboration, communication, and tournament workflows
  • Process subscriptions and billing
  • Provide optional AI-assisted features when requested by users
  • Monitor reliability, detect abuse, and improve security
  • Analyze product usage and improve features
  • Respond to support requests and legal obligations

4. Information Sharing

We do not sell personal information for money. We may share information in these cases:

  • Within your organization: Data is visible to authorized users based on product permissions and roles
  • Public pages you publish: Certain tournament or organizer information may be publicly visible if you choose to publish it
  • Service providers: Google for authentication, Stripe for billing, Resend for transactional email, OpenAI for optional AI features, and Vercel analytics/performance tooling
  • Webhook processors: Some inbound forms (such as contact or demo requests) may be forwarded to Teamy-managed Discord webhook channels
  • Legal reasons: To comply with law, legal process, or valid government requests
  • Safety and abuse prevention: To protect rights, safety, and platform integrity
  • Business transfers: In connection with a merger, acquisition, financing, or asset sale

File access depends on feature type. Some uploads (such as media and certain background images) are stored under public URL paths and may be accessible to anyone who obtains the URL. Other uploads (such as attachments, forms, form submissions, and note sheets) are stored in private paths and served through authenticated download routes.

5. Cookies and Similar Technologies

We use cookies and local storage for authentication, settings (such as theme and last visited club), analytics, and product performance. Most browsers allow you to control cookies, but disabling cookies may impact functionality.

6. Data Retention

We keep information for as long as reasonably necessary to provide the Service and for legitimate business or legal purposes. Retention periods vary by data type and use case.

  • Account and workspace data is typically retained while accounts are active
  • Operational and security logs are retained for limited periods
  • Billing metadata may be retained for accounting, audit, and legal obligations

7. Security

We use technical and organizational safeguards designed to reduce risk, including authentication controls, role-based access checks, input validation, and security headers.

In production deployments, transport security depends on HTTPS and hosting configuration. Security controls reduce risk but do not eliminate it, and no method of transmission or storage is completely secure.

8. Children and Student Data

Teamy may be used by schools, teams, and youth organizations. Organizations that use Teamy are responsible for providing required notices, permissions, and consents for their users, including minors, as required by applicable law.

If you believe information from a child was provided without required authorization, contact us and we will review and address the request.

9. Your Choices and Requests

Depending on your location and relationship to the data, you may request access, correction, export, or deletion of certain information.

To submit a request, contact us at teamysite@gmail.com. We may need to verify your identity or authority before acting on a request.

10. International Access

Teamy is operated by a U.S.-based team. Depending on your location and provider infrastructure, your information may be processed in the United States and other countries where our service providers operate.

11. Changes to This Policy

We may update this Privacy Policy from time to time to reflect product, legal, or operational changes. We will post the current version on this page and update the "Last updated" date.

12. Contact

Questions about this Privacy Policy or privacy requests can be sent to:

Email: teamysite@gmail.com