Skip to main content
TeeFleet

Legal

Draft for review

Privacy Policy

A plain-language working draft describing how TeeFleet expects to handle account, operational, subscription, and website information.

To put it short…

TeeFleet will never sell your personal information—or hand it out like a bucket of range balls. We only use or carefully share what is needed to run TeeFleet, follow the law, or do something you ask us to do.

Status: Working draft

Updated: September 2, 2026

Review before publishing

This is a general working draft, not legal advice. It should be updated to match TeeFleet's real business, product, payment, hosting, and data practices and reviewed by qualified counsel before customers rely on it.

Section 01

Scope and current status

This draft describes the information practices anticipated for the TeeFleet website, applications, subscriptions, support services, and related business communications.

The current interactive demo uses fictional RideReady data. Changes made inside the demo are intended to remain in the user’s browser and are not production customer records. The final policy must be updated before live accounts, payments, analytics, or hosted customer data are enabled.

Section 02

Information we may collect

The information TeeFleet collects will depend on how an organization configures and uses the service.

  • Account and contact information, such as a name, work email, telephone number, employer, job role, and login credentials.
  • Organization and operational data, including carts, serial numbers, customers, ownership, service history, parts, locations, employees, assignments, notes, and uploaded records.
  • Subscription and transaction information, such as the selected plan, billing contact, payment status, and transaction identifiers. Payment-card details should be handled by the selected payment processor rather than stored directly by TeeFleet whenever practical.
  • Technical and usage information, such as IP address, browser or device details, timestamps, pages viewed, feature usage, diagnostics, and security events.
  • Communications and support information that a person chooses to provide through forms, email, telephone, onboarding, or customer support.

To be finalized: Confirm every actual data field, cookie, analytics service, payment provider, support tool, and file-upload feature before launch.

Section 03

Where information comes from

  • Directly from account users, prospective customers, and people who contact TeeFleet.
  • From an organization’s administrators or authorized users when they create accounts, assign work, or enter fleet and customer records.
  • Automatically from the website and application through essential logs, cookies, and similar technologies once those systems are enabled.
  • From service providers involved in authentication, hosting, payment processing, communications, analytics, or customer support.

Section 04

How information may be used

  • Provide, operate, secure, maintain, and improve TeeFleet.
  • Create and administer accounts, subscriptions, permissions, and customer locations.
  • Process service activity, fleet records, parts workflows, communications, and support requests.
  • Process payments, maintain transaction records, and prevent fraud or misuse.
  • Monitor performance, troubleshoot problems, understand product usage, and develop features.
  • Comply with law, enforce agreements, protect rights and safety, and respond to valid legal requests.
  • Send operational messages and, where permitted, product news or marketing that recipients can opt out of.

Section 05

How information may be disclosed

TeeFleet may make information available to authorized users within the customer organization and to vendors that help deliver the service. Information may also be disclosed when required by law, during a business transaction, to protect the service and its users, or with the person’s or organization’s direction.

  • Cloud hosting, authentication, payment, email, analytics, support, and security providers acting for TeeFleet.
  • Customer administrators and other authorized account users according to the organization’s permissions.
  • Professional advisers, regulators, courts, law enforcement, or other parties when legally necessary.
  • A buyer, investor, successor, or adviser in connection with a financing, merger, acquisition, reorganization, or sale of assets.

To be finalized: Confirm that all vendor agreements, analytics tools, and advertising choices support TeeFleet’s no-sale promise before launch.

Section 06

Cookies and similar technologies

TeeFleet may use cookies or local storage that are necessary for sign-in, security, preferences, and application functionality. If optional analytics or advertising technologies are added, this policy and any required consent controls should identify them and explain the available choices.

Section 07

Retention and security

TeeFleet should retain information only for as long as reasonably necessary to provide the service, meet contractual and legal obligations, resolve disputes, maintain security, and enforce agreements. Retention may vary by record type and customer configuration.

TeeFleet intends to use reasonable administrative, technical, and physical safeguards appropriate to the nature of the information. No storage or transmission method can be guaranteed to be completely secure.

To be finalized: Adopt and document real retention periods, deletion procedures, access controls, incident response, backups, and vendor-security practices.

Section 08

Customer and administrator responsibilities

Business customers decide what operational and personal information their users enter into TeeFleet. Customers are responsible for configuring permissions, providing any required notices, obtaining any required permissions, and ensuring that their use of employee and customer information complies with applicable law.

Section 09

Privacy rights and choices

Depending on location and applicable law, a person may have rights to request access, correction, deletion, or a copy of personal information; to object to or restrict certain processing; or to withdraw consent. Some requests may need to be directed to the organization that controls the relevant TeeFleet account.

TeeFleet may need to verify identity and authority before completing a request. Applicable law may permit or require certain information to be retained or a request to be declined.

To be finalized: Choose a verified privacy-request process and determine which state, national, and international privacy laws apply to TeeFleet and its customers.

Section 10

Children and international use

TeeFleet is a business operations service and is not directed to children under 13. TeeFleet does not intend to knowingly collect personal information directly from children.

If information is processed outside the country or region where it was collected, TeeFleet should use safeguards required by applicable law and describe those safeguards in the final policy.

Section 11

Changes and contact information

TeeFleet may update this policy as the service and legal requirements change. The updated version should be posted with a revised date, and material changes should be communicated when required.

Questions or privacy requests may currently be directed to William Leask at william.leask18@gmail.com or (661) 330-9219.

To be finalized: Replace the temporary contact with the final legal business name, mailing address, and dedicated privacy contact before launch.

Before launch

Final review checklist

  • Insert the legal business name and mailing address.
  • Inventory all collected data, cookies, and vendors.
  • Verify that every vendor and product choice honors the no-sale promise.
  • Set retention, deletion, and privacy-request procedures.
  • Document payment and security responsibilities.
  • Have qualified privacy counsel review the final policy.