SwingFlow

Privacy Policy

Information about personal data collection and processing.

Privacy Policy

This Privacy Policy explains how personal data is collected, used and protected on the platform operated by SWINGFLOW, in accordance with the General Data Protection Regulation (GDPR).

Transparency revision: July 22, 2026 — analytics revision 5. This revision describes a separate analytics choice and does not amend accepted agreements.

Transparency revision: September 29, 2026 — SwingFlow leaderboard. This revision describes how the SwingFlow leaderboard is displayed and does not amend accepted agreements.

Transparency revision: September 29, 2026 — requests to access a player's profile. This revision describes who decides when another coach or organization asks to follow a player who is already followed, what each workspace sees of the player's single profile (read-only or coaching), how several coaches work together (shared workspace), and does not amend accepted agreements.

1. GDPR role allocation

  • 1.1. Data of coaches, Player users, and parents or legal guardians who subscribe to Player for their child (account, authentication, billing, commercial relationship, support, security, legal compliance): SwingFlow acts as data controller.
  • 1.2. Student data and related coaching data (including imported data, observations, biomechanical data, and follow-up documents): the Coach / Customer acts as controller; SwingFlow acts as processor and processes such data only on documented instructions from the Coach / Customer acting as data controller.
  • 1.3. Processing carried out by SwingFlow as processor is governed by the DPA concluded with the Customer, in accordance with Article 28 GDPR.
  • 1.4. Data created by a Player user for autonomous personal use is processed by SwingFlow as controller, unless it is explicitly attached to follow-up determined by a coach acting as controller.
  • 1.5. In case of ambiguity, role qualification is assessed according to processing purpose: platform management purposes for coach and Player data (controller), coaching purposes determined by the Customer for student data (processor).
  • 1.6. For Newsletter Studio quotas, billing and security, SwingFlow acts as controller. For a campaign decided by a Coach / Customer, that Customer acts as controller and SwingFlow as processor responsible for execution.

For student data, SwingFlow centralizes, hosts, and organizes data generated through coaching activities and documents imported by the Coach / Customer. SwingFlow does not generate primary biomechanical or performance measurements.

Contact: SWINGFLOW, French simplified joint-stock company with a sole shareholder (SASU) with share capital of EUR 1,000.00 - SIREN 104 852 777 - RCS Blois - intra-community VAT FR50104852777 - 23 Route de Vannes, 41600 Souvigny-en-Sologne, France - contact@swingflow.fr

2. Collected data

Data that may be collected includes:

  • identification data (name, email and, for student or Player profiles, declared date of birth),
  • professional data,
  • connection data,
  • student-related data entered and imported by the coach,
  • personal data imported or generated by a Player user for autonomous use,
  • FFGolf data when provided by the user or required for a requested official feature: licence number, club, handicap index, scores, synchronized results, matching metadata, and dated score/index history; a licence number is not required to create an account or student profile,
  • technical data used to link a student profile to an account: internal profile, workspace and account identifiers, non-reversible cryptographic fingerprints of the limited-use link and temporary resume context, status, and creation, expiry, acceptance or revocation dates; the link secret is never persisted; a temporary resume secret may be stored only in a short-lived, secure, HttpOnly cookie during sign-in, while only its non-reversible fingerprint is retained server-side,
  • data relating to Coach Codes, Player attributions and associated commercial credits,
  • Player progression data: XP, level, league, avatar frame and position in the SwingFlow leaderboard,
  • data about requests to access the profile of a player who is already followed: requesting workspace and coach, identity entered for the request (last name, first name, email, licence number, playing hand), workspace following the player, person asked to decide (player, parent or workspace), address recorded on the student's account, or provided by the requesting workspace, to which the request was sent when nobody had activated their access yet, and where applicable its correction or dispute by the workspace following the student, number of attempts to confirm the date of birth, decision, sharing choice, and dates of sending, reminder, answer, cancellation or expiry,
  • Player subscription data when a parent subscribes: link between the paying parent's account and the beneficiary child's Player workspace, related student profile, statement of legal-guardian status and subscription date; the paying parent's email is used for billing and subscription reminders,
  • contractual records: age bracket calculated from the declared date, role, journey source, document versions, server timestamp, parental-authorization status, and technical link to the relevant invitation; the full date of birth is not copied into this record and no identity document is collected for this purpose alone,
  • usage analytics preference: choice, notice version, language, and date; on public pages without an account, the statement that the user is 15 or older is stored only in that browser with the choice; only after valid permission, a pseudonymous internal identifier, sanitized path, visual structure and interactions from a selectively masked replay, interface titles, labels, help text, and error messages needed to diagnose display and usability issues, explicit product actions, and limited technical metadata,
  • golf school organization data when the module is used: groups, time slots, attendance, absences, contacts, reminders, registrations, and administrative or billing follow-up information entered by the coach or organization,
  • Newsletter Studio data: confirmed email address, language, account and workspace identifiers, activation status, audience, campaign content, quota and subscribed add-on, unsubscription, delivery, bounce and, where available, open and click data,
  • payment data (processed exclusively by Stripe).

No full payment card data is stored by SwingFlow.

Unless otherwise agreed in writing through an integration, the Golf School module is not a service for collecting student fees or payments: financial follow-up information entered by the Customer is operational follow-up data.

3. Purposes of processing

Data is processed to:

  • provide access to the platform and its features,
  • manage subscriptions and payments,
  • allow a parent or legal guardian to subscribe to, pay for and manage their minor child's Player subscription, and send them the related billing documents and reminders,
  • manage the Player offer, Coach Codes, student reductions and coach commercial credits,
  • complete the canonical player profile and apply the age thresholds required for Player, Parent and usage-analytics journeys,
  • establish evidence of accepted documents and verify intervention by a parent or legal guardian before a minor's Player subscription,
  • enable matching with FFGolf results, result synchronization, display of retrieved rounds, and dated score and handicap-index history,
  • where the Golf School module is enabled, allow management of groups, schedules, attendance, reminders, and administrative follow-up decided by the coach or organization,
  • calculate Newsletter Studio rights and quotas, mandatorily filter activated accounts and objections, execute campaigns decided by the Customer and provide available delivery metrics,
  • display the SwingFlow leaderboard of players ranked by total XP: other players and a student's coaches see the first name, last-name initial, profile photo, league, level and XP of a player aged 15 or over; for a player under 15 or whose age is not recorded, only the initials of the first and last name appear, without photo; the full last name is never shown and a blocked player does not appear,
  • handle requests from another coach or organization wishing to follow a player who is already followed: the request is addressed to the player if they have an account, to a linked parent if the player is under 15, or otherwise to the workspace following the player; no data is shared without approval; the decision-maker chooses between read-only access (viewing the player's follow-up without being able to change it; once the single profile is enabled, viewing the player's whole profile, except drafts and messages, with the ability to add calendar events) and coaching (the requester receives a profile of the player in their workspace to coach them; once the single profile is enabled, they can add to the player's profile), coaching being possible only if no other coach or organization already coaches the player; to work together on a player, coaches create a shared workspace, whose administrator sets everyone's rights; the workspace following the player is informed of the approval; without an answer, the request expires after 30 days; read access granted to a member of an organization ends when they leave that organization,
  • when no player or parent has activated their access yet, contact the address recorded on the student's account (the player's, or a parent's for a player under 15) to ask for their agreement on behalf of the requesting workspace; the person confirms the student's date of birth before activating their access or linking as a parent, then decides; the workspace already following the student is informed of the request,
  • when no address is recorded, the requesting workspace may provide the student's or a parent's address; the workspace already following the student sees it and may correct it for 7 days; without a correction, or if it is disputed, SwingFlow support checks the address before anything is sent,
  • a parent may hand their child's coaching over to the requesting workspace; the previous workspace's sheet is then archived and that workspace loses access,
  • when a coach proposes to share a player's follow-up read-only with another coach, only the holder of the student's account accepts or declines that share and may remove it at any time: the player if they activated their account and are not under 15, otherwise a linked parent, from their parent space; without a holder, the share stays pending,
  • once the single profile is enabled (for all workspaces at once), present a player's single profile to every workspace that coaches them and to every coach with read-only access: identity, handicap and history, calendar, events and results, sent reports, tests, training, measurements and media, whichever workspace entered them, excluding report drafts and messages; each workspace alone keeps the right to edit and delete its own documents (reports, assessments, analysis files, assigned tests and training), while the shared data of the profile (identity, handicap, calendar, results) can be edited by the workspaces that coach the player,
  • provide user support,
  • ensure security and proper operation of the service,
  • measure, only with valid permission, sanitized pages and explicitly authorized product actions in order to improve SwingFlow,
  • observe, only with valid permission, a selectively masked replay of navigation and interactions in order to identify usability issues,
  • measure, only with valid permission, aggregated technical performance and rendering-quality indicators,
  • execute coach instructions regarding student data under the DPA.

Artificial intelligence features are also governed by the AI Addendum available at /en/ai-addendum.

4. Legal basis

  • 4.1. Where SwingFlow acts as controller (coach, Player and paying Player parent data), legal bases are: (a) contract performance; (b) compliance with legal obligations; (c) SwingFlow's legitimate interest, limited to security, fraud prevention, operational continuity, technical improvement of the platform and coach code management.
  • 4.2. Where SwingFlow acts as processor (student data), the legal basis for processing is determined exclusively by the Coach / Customer acting as controller.
  • 4.3. SwingFlow's legitimate interest is not relied upon as an autonomous legal basis for student data processing performed on behalf of the Coach / Customer.
  • 4.4. SwingFlow processes student data only on documented instructions from the Coach / Customer acting as data controller and in accordance with the DPA.
  • 4.5. SwingFlow does not exploit, profile, sell, or analyze student data for its own purposes. Such data is processed only to provide the Service to the Coach / Customer and to execute documented instructions.
  • 4.6. The Coach / Customer is responsible for informing students and, where a student is a minor, for ensuring that it has the necessary legal authority, including parental or legal guardian consent where required by applicable law.
  • 4.7. Optional usage and performance measurement relies exclusively on consent. Declining or withdrawing does not affect signup, sign-in, payment, or use of SwingFlow.
  • 4.8. Logs strictly required for security, fraud prevention, and technical operation remain separate from optional analytics tools. Depending on their purpose, they rely on contract performance or SwingFlow's legitimate interests.
  • 4.9. For a Newsletter campaign decided by the Customer, the legal basis for the communication and any required notice or consent are determined by the Customer. An active SwingFlow account does not, by itself, constitute consent to commercial marketing.

5. Hosting and sub-processors

SwingFlow notably relies on the active or conditional sub-processors listed in the public sub-processor register.

  • Supabase (Application hosting, database, authentication, object storage)
  • Stripe (Payments, billing, subscription management)
  • Vercel (Deployment and application hosting)
  • Microsoft Azure Document Intelligence (OCR and document analysis for selected imports)
  • OpenAI (Generation, rewording, structuring, assisted analysis, synthesis)
  • Brevo (Transactional emails, Customer-directed Newsletter campaigns, delivery metrics and unsubscription management)
  • Vercel Analytics et Speed Insights (Optional aggregated audience and site performance measurement)
  • PostHog Cloud EU (Optional product usage measurement and selectively masked session replay)

The public sub-processor register is available at /en/subprocessors.

6. Retention

Data is retained for as long as needed for the relevant purposes and legal obligations. Main retention periods are as follows:

Data categoryIndicative retention period
Coach account dataAgreement term then 3 years after the end of the business relationship
Autonomous Player account and profileLifetime of the account; deletion or anonymization when it is closed, followed by technical backup purge within 90 days
Billing data10 years from the close of the relevant accounting period
Payment dataProcessed by Stripe; SwingFlow does not store full payment card data
Security logs6 to 12 months depending on the security purpose
Support dataDuration of request handling then 3 years
Contractual records and parental authorizationsTerm of the relevant relationship then the applicable limitation period, generally 5 years
Usage analytics preferencesChoice valid for 6 months; local preference deleted or requested again at expiry; account evidence retained for the relationship then the applicable limitation period, generally 5 years
Optional usage analytics dataSelectively masked PostHog replays: 30 days; other PostHog events: 12 months on the current free plan; Vercel Web Analytics: 12 months; Speed Insights: 30 days
B2B prospecting data3 years after the last active contact
Student dataTerm defined by the Coach / Customer acting as controller; deletion or return under the DPA
Customer Newsletter drafts and campaignsTerm defined by the Coach / Customer acting as controller and agreement term; deletion or return under the DPA and technical backup purge within 90 days
Customer Newsletter suppression list3 years from the objection or its latest renewal
Technical backupsMaximum purge within 90 days after logical deletion

7. Security

SwingFlow implements reasonable technical and organizational measures to protect data against unauthorized access, loss, alteration, or disclosure.

8. Data subject rights

  • For processing where SwingFlow is controller, access/rectification/erasure/restriction/objection/portability requests can be sent to contact@swingflow.fr.
  • For student data processed under Coach / Customer instructions, requests should primarily be sent to the Coach / Customer acting as controller.
  • SwingFlow assists the Coach / Customer with rights handling under the DPA and may redirect requests to the relevant controller.
  • Data subjects also have the right to lodge a complaint with the CNIL.

9. Transfers outside the European Union

Some providers or support operations may involve data transfers outside the European Union or the European Economic Area. Where this occurs, SwingFlow ensures that a valid transfer mechanism applies, such as an adequacy decision or, failing that, the European Commission's Standard Contractual Clauses, supplemented where necessary by risk-adapted additional measures.

10. Preferences, trackers, and optional measurement

SwingFlow uses no advertising trackers. Storage strictly required to remember your choice is used only to respect your preference and remains active even when optional measurement is declined.

PostHog EU Cloud, Vercel Analytics, and Speed Insights are loaded only after explicit permission and approval of their configuration by SwingFlow. On public pages without an account, allowing includes a simple statement that the user is 15 or older, without requesting a date of birth. For a signed-in account, eligibility calculated by SwingFlow from information already available remains authoritative. When no choice exists, an error occurs, or a known user is under 15 without verified joint permission, these tools remain disabled.

For a user under 15, optional measurement remains disabled until a separate joint analytics permission from the student and a holder of parental authority is available and verified. A Parent authorization relating to Player access is not analytics permission.

After valid permission, PostHog may record a selectively masked replay of navigation and interactions. On public pages, sign-in, sign-up, and authenticated areas, interface titles, labels, help text, and error messages may remain readable to identify display and usability issues. Values entered in fields and editable content remain masked. Names, email addresses, phone numbers, dates of birth, FFGolf licence numbers, student identities and data, and report, message, note, and document content remain masked or blocked. Media is blocked, and Auth routes that may carry secrets are never recorded. Console, canvas, external frames, network bodies, and network headers are not recorded. Replays are retained for 30 days. Autocapture, surveys, and automatic error collection remain disabled.

Only paths without sensitive parameters, visual structure, interface text needed to diagnose display and usability issues, interactions, explicit actions, and limited technical indicators may be transmitted. No visitor name, email address, or phone number, age bracket, legal guardian, FFGolf licence, student identity or data, raw Coach Code, Stripe identifier, account, report, message, note, or document content, token, or raw URL is sent for this purpose.

In the browser, only sanitized public pages, CTAs, and generic sign-up form views or submissions are allowlisted. Server-side product events apply the same choice and remain limited to individually reviewed transitions and intentions in a closed allowlist; granting permission does not reactivate any unreviewed historical application event.

Analytics revision 5 keeps a still-valid permission given under revision 4: the service-improvement purpose, the tools used, the retention period, and private-data protections remain unchanged. Interface text needed to diagnose display and usability issues may now remain visible on sign-in, sign-up, and in authenticated areas. Older permissions remain outdated. A previous refusal that is still valid, including a revision 4 refusal, remains honored and does not trigger a new prompt.

The choice is valid for six months and can be changed at any time from the “Manage my preferences” button. Withdrawal immediately stops new browser sends; if server recording fails, measurement remains disabled and SwingFlow asks the user to retry without blocking the product.

11. Policy changes

This policy may be amended to reflect service or regulatory changes. The applicable version is the one published on the website on the consultation date.

12. Governing law

This Privacy Policy is governed by French law.

Back