Privacy Policy

Who is responsible for your data

Andrea Vasapollo operates Lyrafit and is responsible for the personal data described in this policy. Any future change of responsible operator will be recorded here and explained to users. The Google Calendar data section below sets additional limits on any transfer of Google-derived data.

For privacy or legal questions, email legal@lyra.fit.

Information we handle

Depending on how you use Lyrafit, the service can handle:

• Account and profile data: name, email address, profile image, home city, account role, status, and authentication identifiers.
• Member preferences: coaching goals, preferred specialties, delivery modes, languages, coaching area, and availability notes.
• Coach marketplace data: display name, biography, headline, specialties, delivery modes, languages, credentials, experience, location, monthly coaching offer prices and inclusions, optional Instagram or Facebook profile links, profile image, and presentation video or transcript.
• Private coaching data: connections, direct messages, programme templates, assigned programmes, programme versions, programme discussions, and read state.
• Direct payment request data: a coach's requested GBP amount, due date, saved time zone, payment instructions, and manual paid or cancelled status. Instructions can include bank details if the coach enters them. Lyrafit does not process the transfer or verify payment.
• Meeting and calendar data: meeting dates, participants, RSVP state, conferencing details, reminder state, and, when a coach or administrator connects Google Calendar, calendar account and authorisation data needed to read busy time and manage Lyrafit events. The Google Calendar data section below explains this optional connection.
• Coach billing data: subscription status, billing periods, Stripe customer and subscription references, invoice and transaction references, amount, currency, refunds, promotions, and payment events. Lyrafit does not store full card details.
• Operations data: notifications, email-delivery state, profile views, product events, rate-limit counters, moderation decisions, and audited administrator access.

Health and sensitive information

Preferences, messages, programme content, images, and video may reveal health information, an injury, disability, pregnancy, location, or other sensitive circumstances.

Lyrafit is not designed to hold clinical records, and ordinary use does not require medical records. Share only information that is needed for the coaching relationship. Check images and video for other people, notifications, and private background details before upload.

Information that reveals health can receive additional protection under data-protection law. For processing that involves this information, Lyrafit must establish and document the applicable lawful basis, special-category condition, consent experience where required, and whether a data protection impact assessment is needed.

How we use information

Lyrafit uses information to:

• create, authenticate, secure, and support accounts;
• show published coach profiles and operate coach discovery;
• save member preferences and improve relevant search results;
• operate private connections, messages, programmes, and meetings;
• check calendar availability and manage Lyrafit-created Google events when a coach or administrator chooses to connect Google;
• send required service messages and optional notification email;
• send optional direct payment request and reminder email to members who allow it;
• provide and administer coach platform subscriptions;
• prevent abuse, enforce access rules, and record moderation;
• provide product and marketplace analytics; and
• comply with law and protect users or the service.

Messages and programme content are not copied into analytics or notification-email payloads. Analytics use content-free events and aggregates.

Google Calendar data

Connecting Google Calendar is optional. A coach or administrator starts the connection from Integrations and approves the permissions on Google's consent screen. Lyrafit uses the connected account's primary calendar for coaching meetings owned by a coach or verification meetings owned by an administrator.

Data we access and why:

• Google account identity: OpenID and email permissions identify the connected Google account. Lyrafit receives its account identifier and email address, so it can associate the authorisation with the correct Lyrafit account. Other meeting participants see meeting details, not your saved Google connection credentials.
• Availability: calendar.events.freebusy reads busy start and end times for the requested date range. Lyrafit displays these ranges as busy and checks for scheduling conflicts. When rescheduling an existing event, calendar.events.owned also reads event identifiers, status, and transparency to exclude that event from its conflict check. It does not request the titles, descriptions, or attendee lists of unrelated events for that check.
• Lyrafit meetings: calendar.events.owned permits Lyrafit to create, update, and cancel its own events on your primary calendar. Lyrafit sends Google the meeting time, time zone, participant names, attendee email, meeting type, optional agenda, and a private Lyrafit meeting link. Google returns an event identifier and, when available, a Google Meet link. This connection does not import external edits into Lyrafit or provide a general editor for unrelated Google events.

Storage and protection: Lyrafit stores the connected Google account identifier, email address, connection status and timestamps, and an encrypted refresh token in its Convex backend. The refresh token allows the approved connection to work when you are not actively signed in. Access tokens are used by backend requests to Google. Meeting records store the external event identifier, Google Meet link, and delivery status needed to manage the Lyrafit meeting. Server access checks protect private records, transport uses HTTPS, and refresh credentials are not sent to other participants or exposed in the browser. Lyrafit does not store a copy of your unrelated calendar events or a permanent history of Google busy-time responses.

Sharing and restricted use: Google processes Calendar requests, creates Meet links, and sends invitations, updates, and cancellations to meeting attendees. The relevant participants receive the shared meeting information. Convex processes the connection and meeting records as Lyrafit's backend provider. The broader service-provider list in this policy does not mean each provider receives Google Calendar credentials or unrelated calendar data. Google-derived data is used only for the Calendar features described here; it is not sold, used for advertising, used for credit or lending decisions, or used for other unrelated purposes. Google-derived data is not used to train general-purpose AI or machine-learning models. Human access to Google-derived data is limited to specific user-authorised support, necessary security work, legal requirements, or internal use of anonymised aggregates. Any organisational transfer of that data requires your explicit prior consent, subject to applicable law.

Lyrafit's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. These restrictions apply to Google-derived data even where a general disclosure elsewhere in this policy is broader.

Retention, disconnection, and deletion: The saved Google account connection remains while you keep it connected, including when expired authorisation requires renewal. Choose Disconnect under Integrations to stop further Calendar access through Lyrafit. Disconnection attempts to revoke Google's grant and removes the saved Google account connection, including its encrypted refresh token, from Lyrafit's active database even if Google revocation fails. You can also revoke access in your Google Account connections. Revocation at Google alone does not delete Lyrafit's stored meeting history.

Disconnecting does not erase existing Google Calendar events, attendees' copies of invitations, or retained Lyrafit meeting records. Cancel a Lyrafit meeting while the connection is active to send its cancellation to Google. You can manage remaining events directly in Google Calendar. To request deletion of retained Lyrafit records, contact legal@lyra.fit from your account email and identify the request as Google Calendar data deletion. Do not send passwords, tokens, or private calendar contents. See Retention and deletion and Account and Data Deletion for the current account-deletion process and its limitations. Removal from the active database is not a promise of immediate erasure from provider backups.

Lawful bases

Depending on the purpose and the law that applies, Lyrafit relies on:

• Contract: processing needed to provide the account and platform functions requested by a user.
• Legitimate interests: proportionate processing needed to secure, support, understand, and improve the platform, where those interests do not override a person's rights.
• Consent: optional connections or uses where the service asks for a choice and consent is the appropriate basis.
• Legal obligation: processing needed to comply with applicable legal, tax, regulatory, or court requirements.

This general list does not replace the separate condition required when information is special-category data. That condition must be established for the relevant processing.

Who can see information

A published coach profile is public. A member profile and preferences are private to that member and permitted platform administration. Messages, meetings, programmes, and programme discussions are limited to the relevant participants. Direct payment requests and instructions are limited to the connected coach and member. A closed connection stops reminders but retains the request record. Payment instructions can appear in email sent through Resend; they do not appear on public profiles, overview cards, notifications, analytics, or Google Calendar.

Authorised administrators can access retained conversations for a documented support, safety, security, legal, or moderation reason. Lyrafit records this access. Coaches can separately collect or use information outside Lyrafit while they provide their independent service; the coach is responsible for explaining that separate use.

Service providers and disclosures

Lyrafit uses Clerk, Convex, Stripe, Resend, and Google for defined parts of the service:

• Clerk for authentication and account identity;
• Convex for application data, files, realtime updates, and backend processing;
• Stripe for hosted coach subscription billing and its customer portal;
• Resend for service and notification email; and
• Google when a coach or administrator chooses to connect Google Calendar.

Stripe data relates only to coach platform billing. Lyrafit does not receive or process money paid between members and coaches.

We can also disclose information to professional advisers, authorities, courts, or another responsible operator where required by law, necessary to protect people or the service, or part of a lawful organisational transfer. Lyrafit does not sell personal data or share it for third-party advertising.

International transfers

Some providers can process data outside the United Kingdom or European Economic Area. Where data-protection law requires it, Lyrafit must use an applicable adequacy regulation, approved contractual clauses, or another valid transfer safeguard. Contact legal@lyra.fit for information about the providers and transfer safeguards relevant to your data.

Cookies and device storage

Clerk uses cookies or similar storage that is necessary for sign-in, session security, and account access. Lyrafit also stores the chosen light, dark, or system appearance on the device.

The current product does not use advertising cookies or third-party behavioural advertising. It records limited first-party product and marketplace events after use of the service. If optional analytics or advertising tools are added, this policy and the consent controls must be updated before those tools are enabled.

Retention and deletion

Lyrafit keeps information while an account is active and as needed to provide, secure, and document the service. Closing a connection retains its message and programme history. Published programme versions are immutable records. Billing, moderation, security, and audit information can require different retention periods.

There is no single automatic retention period for all of these categories. This policy does not promise a fixed provider-backup erasure period. You can contact legal@lyra.fit to request deletion or ask which records are retained and why. When an account-deletion request is completed, Lyrafit will delete or irreversibly anonymise associated personal data unless a documented legal, fraud-prevention, safety, tax, or dispute reason requires limited retention.

Read Account and Data Deletion for the present deletion status and planned request process.

When an account is deleted, a restricted accounting record of Lyrafit's Stripe subscription payments and refunds can remain until five years after the relevant UK tax year's 31 January filing deadline. It contains dates, amounts, currency and invoice/payment/refund references, with an internal deduplication key, policy and expiry. It excludes the account identifier, profile, coaching content, receipt URLs and payment instructions. Provider references are restricted personal data, not anonymous information. Expired records are removed by scheduled cleanup. Ordinary product and administrator pages cannot access this archive.

Your rights and complaints

Depending on the law that applies, you can have rights to be informed, access and correct data, request erasure or restriction, receive portable data, object to processing, withdraw consent, and complain to a supervisory authority.

Contact legal@lyra.fit about a privacy right. Lyrafit must verify the request in a proportionate way before disclosing or changing account data. UK users can also contact the Information Commissioner's Office.

Security and changes

Lyrafit uses server-enforced access checks, restricted public identifiers, encrypted transport, encrypted Google refresh tokens, rate limits, and audited administrator access. No online service can promise absolute security.

This policy will change when the product, suppliers, controller, or law changes. Material new uses of personal data will be explained before they begin where required.