Privacy Policy

During account creation, login, demo requests, contact requests, payments, and service operations, we may collect names, emails, phone numbers, school names, roles, message content, usage records, device data, and browser information.

Information related to students, parents, staff, locations, attendance, orders, and payments may be stored when users configure and operate the service.

Collected information is used to provide accounts, customer support, demo scheduling, workspace operations, security checks, payment processing, feature improvements, and legal compliance.

Information submitted through contact and demo request forms may be delivered to [email protected] for follow-up.

FitLift does not sell, rent, or share personal information with third parties or affiliates for marketing or promotional purposes, including lead generation.

We share information with hosting, email, authentication, payment, and customer support providers only as needed to operate the service on our behalf, not for their own marketing or promotional use.

Information may be disclosed when required by law, to protect rights, to respond to security incidents, or at the user's explicit request.

Mobile information, including phone numbers, will not be sold or shared with third parties or affiliates for marketing or promotional purposes.

Text messaging opt-in data and consent are excluded from all other sharing categories described in this policy. We share this information only with messaging service providers, such as Telnyx and mobile carriers, as necessary to operate and deliver the SMS service. We do not share SMS opt-in data or consent for any unrelated purpose, including marketing, advertising, lead generation, or third-party analytics.

FitLift applies reasonable technical and administrative safeguards such as access controls, authentication, transport protection, and operational monitoring.

Because internet-based services cannot be absolutely secure, users should maintain strong passwords and appropriate staff permissions.

Information is retained for as long as needed to provide the service, resolve disputes, maintain security, support accounting, and meet legal obligations.

After account deletion or contract termination, some information may be retained for limited periods for legal, backup, audit, and abuse-prevention purposes.

Users may request account updates, access changes, data deletion, or marketing opt-out related to personal information.

Privacy requests may be submitted through the contact page or [email protected].

FitLift provides tools that allow academy operators to manage student and family information. Operators are responsible for managing notices and consents for information they collect.

Applicable privacy and children's privacy laws may apply to information related to children or minors.

This policy may be updated as the service, law, or operating practices change. Material changes will be communicated through appropriate means.

FitLift uses OpenAI to generate chatbot answers and conversation summaries. Requests send your message, relevant recent messages, conversation summaries and, when needed, excerpts from the same conversation and information retrieved within your access permissions. FitLift stores messages, answers, summaries, timestamps, usage and related audit records to provide conversation history, support and security.

The public FitLift assistant uses public product information. School website assistants use approved public school information; signed-in family assistants may use linked students' attendance, belts, classes and membership terms. Owner assistants may use authorized business reports and limited student lists. Chat tools are read-only. Do not include passwords, full payment details, health information or unnecessary information about children in messages.

School owners can review their school's customer conversations, including guest and portal chats, for customer support; transcript access is logged. Owner assistant conversations are separate from the customer inbox. Guests cannot restore chat history. Closing a guest chat ends access but does not delete the stored conversation.

School guest chats are retained for the site's selected period of 1–30 days; public FitLift chats default to 30 days, family portal chats to 90 days and owner chats to 180 days. Portal and owner periods depend on service configuration. These periods run from conversation creation. Expired conversations become inaccessible and are removed by an hourly cleanup task with their messages, summaries and conversation audits. Daily usage totals are kept separately for about 93 days.

Signed-in users can delete their own authorized conversations; school owners can handle deletion of customer conversations. Guests can contact the school or [email protected] to request deletion. OpenAI has separate retention rules; disabling response storage does not guarantee zero retention by the provider.

• OpenAI API data controls

AI assistance during registration and website generation sends your description, business details and website preferences, such as language, audience, style and colors, to OpenAI to create suggested descriptions, page text and layouts. Generation may also include a reference website structure or previous layout. When configured, generation can run during website setup after you submit these details.

Saved preferences and website drafts remain in FitLift for editing and operation under the retention rules above; they are not covered by the chatbot retention periods. Generation alone does not publish the website. Review generated content before saving or publishing, remove unnecessary personal information and obtain permission before publishing other people's information. Published content is accessible to website visitors. AI output can be inaccurate.

FitLift uses Stripe for platform subscriptions and, where a school connects Stripe, student membership and shop payments. Depending on the transaction, Stripe receives payer contact details, billing information, amounts, currency, order or subscription references and identifiers needed to associate the payment with the correct school or account.

Payment credentials are entered through Stripe's payment interfaces. FitLift stores Stripe references and operational payment records, such as payment status, invoices, subscriptions and refunds, rather than full card numbers or security codes. Stripe Connect setup also involves information submitted to Stripe to verify the school's business and enable payments.

Stripe's own privacy and retention rules apply to its processing. Disconnecting an integration or deleting a FitLift account does not automatically erase records that Stripe retains. Contact [email protected] for FitLift payment-data requests and use Stripe's privacy channels for information it controls.

• Stripe Privacy Policy

When you choose Google sign-in, FitLift receives identity information in your sign-in token, including your name and verified email, to create or authenticate your account. Google Maps receives map requests, IP address and browser information when loaded. Address suggestions send your typed search and connection information to the configured address provider (by default, Photon at photon.komoot.io). Map loading is explained in the Cookie Policy.

Depending on service configuration, Resend or the configured SMTP provider receives recipient addresses and email content for account, support and school messages; Telnyx receives recipient phone numbers and SMS content for enabled messaging. Hosting and storage providers process service records and uploaded files. Where enabled, Cloudflare processes domain names and website traffic to provide custom domains, delivery and security.

External providers may process information outside your country, including in the United States. Processing locations, retention and applicable transfer arrangements depend on the provider and service configuration. Contact [email protected] for details or a privacy request. Optional cookie choices do not authorize AI submissions, payments or messaging; each feature's data use is described separately here.

• Google Privacy Policy
• Resend Privacy Policy
• Telnyx Privacy Policy
• Cloudflare Privacy Policy