Privacy Policy

1. Introduction

IKU LLC (“IKU”, “we”, “our”, or “us”) operates KETTLEBELL MONSTER™ (the “Service”). This Privacy Policy explains what personal information we collect, how we use it, who we share it with, and your rights over your data. By using the Service, you agree to the practices described in this Policy.

IKU LLC is a United States company. All persistent user data is stored on servers in the United States (US-West region, Northern California). If you access the Service from outside the US, your information will be transferred to and processed in the US. For information about cross-border transfer safeguards, see Section 11.

2. Information We Collect

2.1 Information you provide directly

• Account information: Name, email address, and password (or OAuth token if you sign in via Google or Facebook).
• Profile information: Display name, username, avatar, bio, training style, kettlebell collection, and other optional profile fields you choose to complete.
• Training data: Workout logs, timer sessions, personal bests, weights used, scores, rates of perceived exertion (RPE), and other training activity you record.
• Mental readiness data: Self-reported stress, focus, motivation, confidence, and emotional load values (0–100 scale) submitted through our MIND features, as well as optional reflection notes and mental pattern assessments.
• Recovery data: Self-reported body-part recovery status, symmetry assessments, and movement readiness inputs you submit through our RECOVER features.
• Fitness profile data (optional): Height, body weight, resting heart rate, maximum heart rate, basal metabolic rate, weight classification, muscle mass category, and lifestyle/activity level.
• Community content: Posts, comments, photos, and videos you share in CONNECT.
• Payment information: If you subscribe to a paid plan or purchase content on our website, your payment is processed by Stripe or PayPal, depending on the payment method you choose at checkout. We do not store your full card number, expiry, or CVV. We retain only the last four digits and card type for display purposes (Stripe), or the PayPal transaction and subscription identifiers (PayPal). Stripe and PayPal store your complete payment details under their own privacy policies: Stripe, PayPal. If you purchase inside the KETTLEBELL MONSTER iOS or Android app, the purchase is billed by Apple or Google Play; we receive a purchase token or transaction identifier to confirm the purchase, never your payment details. Subscriptions in KETTLEBELL MONSTER TV are billed by the Amazon Appstore or Google Play, as described in the KETTLEBELL MONSTER TV section below.
• Creator information: If you become a creator, we collect additional information including your bio, certifications, specialties, social media links, and payout details (bank account information for Stripe Connect, encrypted at the application level).
• Communications: Messages you send to us for support, feedback, or error reports.

2.2 Information collected automatically

• Usage data: Pages visited, features used, and time spent on the Service. We use Cloudflare Web Analytics to understand aggregate usage patterns and improve the Service. Cloudflare Web Analytics is privacy-first: it does not use cookies, does not track individual users, and does not collect personal data. Analytics data is processed on Cloudflare's infrastructure. We do not use this data for advertising or behavioral profiling.
• Device and browser data: Browser type, operating system, screen resolution, and language preferences.
• IP address: Used for security, fraud prevention, and infrastructure (CDN routing). We also store it against the record of your visit so we can count visits accurately, recognise repeat visits within a day, and see which country our visitors come from; those visit records are deleted automatically after 180 days (see Section 9). We do not track precise GPS location, and we do not use your IP address to build an advertising profile or to identify you across other companies’ websites.
• Error reports: When errors occur, we automatically collect error messages, stack traces, and UI interaction breadcrumbs to diagnose issues. Sensitive data (passwords, card numbers, tax information) is automatically redacted before storage.
• Cookies and similar technologies: See Section 6 below.
• Marketing campaign attribution data: When you arrive at the Service via a link we have placed in a marketing campaign (for example, a Google, Instagram, Reddit, Pinterest, Microsoft, or Quora advertisement), we record the campaign identifiers (UTM source, medium, campaign, content, term) from the URL, the landing page you arrived on, and the referring domain. Where you have accepted cookies, this information is stored in first-party cookies on your device. Where you are located outside the European Economic Area, the United Kingdom, Switzerland, Quebec, Brazil, South Korea and Thailand and have not declined cookies, we may instead record the same campaign identifiers against the visit itself on our own servers, without storing anything on your device, and — if you create an account or place an order during that same visit — associate them with your account or order. We rely on our legitimate interest in measuring which campaigns bring people to the Service (Article 6(1)(f) GDPR) for that server-side record, and you can object to it at any time in Settings → Privacy & Data or by emailing us. We do not do this if you have declined cookies, if your browser sends a Global Privacy Control signal, or if you are in a location listed above, where we act only on cookies you have accepted. For Reddit Ads campaigns, after you accept analytics cookies, we may also load the Reddit Pixel and send limited conversion events through Reddit Conversions API, including event type, event time, page or purchase metadata, IP address, user agent, screen dimensions, a hashed internal user identifier, and — when you are signed in — a cryptographic hash (SHA-256) of your account email address, which Reddit uses to match the event to a Reddit account. That hash cannot be read back into your email address, but it is still personal information about you because it lets Reddit recognise you. We never send your email address in readable form, and we do not send Reddit your phone number, training logs, health or wellness data, or payment card details. For TikTok Ads campaigns, after you accept analytics cookies, we may also load the TikTok Pixel — on our production site only — and send TikTok page-view events, product-view events identifying the shop product’s page slug, an account-creation event when you complete signup, and a purchase event when you complete an order, including the purchase value, currency, and product identifier. These events may include your IP address and user agent. We do not send TikTok your raw email address, phone number, training logs, health or wellness data, or payment card details, and, unlike Reddit, we do not send TikTok any hashed version of your email address. The TikTok Pixel does not load if your browser sends a Global Privacy Control signal or if you have not accepted analytics cookies, and we do not yet send TikTok any events from our own servers. On our starter-kit funnel page only — the only page where a Pinterest tag runs on the Service — after you accept analytics cookies, we also load a Pinterest tag with Pinterest’s own automatic enhanced match feature enabled. That feature is operated by Pinterest, not by us: whenever it is enabled, Pinterest’s own script can detect and send Pinterest a one-way hashed version of information you have typed into a visible field on that page — for example an email address, phone number, name, or location — independently of what our own code tells the tag to send. Our own code passes the tag only a page-view event and, on that page, a category label for the guide or plan you requested (for example “guide_email”); it does not pass Pinterest your address, name, or any other field value directly, and we do not enable Pinterest’s external-identifier matching. The Pinterest tag does not load if your browser sends a Global Privacy Control signal or if you have not accepted analytics cookies, and there is no server-side Pinterest conversions call.
• Referral attribution data: Members and affiliates can share referral links that carry a referral code. When you arrive on one, we record that code so the person who referred you gets the credit. This happens in three ways, and which ones apply to you depends on your choices and your location. For the current visit: the code is kept in a session-only cookie, described in Section 6.2, that is gone when you close your browser. In the European Economic Area, the United Kingdom, Switzerland, Quebec, Brazil, South Korea and Thailand this happens only after you accept cookies; anywhere else it happens when you land on the link, even if you have declined cookies. If you accept cookies: the code is also kept in a longer-lasting cookie — 90 days by default, and 30, 60 or 120 days depending on the affiliate — so a referral still counts if you come back later. Outside the European Economic Area, the United Kingdom, Switzerland, Quebec, Brazil, South Korea and Thailand, and only if you have not declined cookies and your browser is not sending a Global Privacy Control signal: we may also record the code against the visit on our own servers, without storing anything on your device. If you then create an account, we may store, once and permanently, which affiliate referred you and when — this is what allows an affiliate to be paid if you upgrade to a paid plan later, within that affiliate’s window. Outside the locations listed, we rely on our legitimate interest in running and correctly paying a referral programme (Article 6(1)(f) GDPR); inside them, we act only on cookies you have accepted. Connecting a referral to your signup depends on the session cookie in Section 6.2: if your browser blocks cookies entirely we cannot make that connection, and we never infer it from your IP address instead. We do not tell the affiliate who you are. You can object at any time by emailing us, and you can ask us to erase the referral recorded on your account without affecting the account itself.
• Campaign performance totals: When you arrive from one of our advertising campaigns, the campaign name travels in the web address and, if you sign up or place an order during that visit, we add one to a running daily total for that campaign (visits, signups, orders, and order value). These totals are counts only — they are not linked to you, your account, or your order, and we do not share them with advertising platforms. We use them solely to judge whether our advertising is worth what we spend on it.

2.3 Information we do not collect

We do not collect: precise GPS location, phone numbers, or information from children under 13. We do not receive government identification documents or numbers, or biometric identifiers (such as fingerprints or face scans). If you choose Identity Verification, those are collected by Stripe, not by us, as described in Section 5A.

We do not read any data from Apple Health, Google Health Connect or Garmin Connect. If you choose to, the app can save a workout you finished to Apple Health (iPhone) or Health Connect (Android); Section 5 explains exactly what is saved. Heart-rate and activity data from a wearable reaches us only when you upload an activity file yourself or connect a supported device account, as described in Section 5.

3. How We Use Your Information

We use your information to:

• Provide the Service: Operate your account, display your training history, run timers, track scores, and power community features.
• Personalize your experience: Remember your preferences, calculate training streaks, and display relevant content.
• AI-powered guidance: Our Compass feature uses artificial intelligence (Anthropic Claude API) to generate personalized workout suggestions based on your training level, streak, mental readiness band, and recovery status. This processing uses aggregated metrics only (not raw check-in values). AI-generated responses are not stored by the AI provider beyond 30 days and are not used to train AI models. You can use the Service without this feature.
• Process payments: Manage subscriptions, process purchases, and facilitate creator payouts via Stripe and PayPal; confirm purchases made through the Apple App Store, Google Play and the Amazon Appstore.
• Send essential communications: Account confirmations, password resets, billing receipts, subscription renewal reminders, and critical account notifications.
• Send optional communications: Product updates and feature announcements, only if you have opted in to receive them. You can opt out at any time from your notification settings.
• Gamification: Calculate XP, levels, badges, and leaderboard positions based on your activity.
• Measure marketing campaign effectiveness: Record which advertising campaigns bring people to the Service so we can decide where to invest our marketing budget. See Sections 2.2, 4.2, and 6 for details. For Reddit Ads, this may include consent-gated browser Pixel and server-side Conversions API events used to measure visits, signups, and purchases.
• Security and abuse prevention: Monitor for unauthorized access, enforce our Terms of Service, and protect the platform.
• Improve the Service: Analyze aggregate, de-identified usage trends. We do not build individual behavioral profiles for advertising.
• Legal compliance: Fulfill legal obligations, respond to lawful requests, and protect our rights.

We do not sell your personal information to third parties. We do not build profiles about you for advertisers. We run marketing campaigns on advertising platforms (see Section 4.2) to reach people who may be interested in kettlebell training, and we measure how those campaigns perform. For every platform except Reddit, TikTok and Pinterest, that measurement uses only first-party data we collect on our own site (campaign identifiers in the URL), and we transmit nothing about you to the platform.

Reddit, TikTok and Pinterest are the exceptions, and only if you consent. If you accept analytics cookies, we send Reddit limited conversion events including — for signed-in members — a scrambled (SHA-256 hashed) version of your email address, so Reddit can match the event to a Reddit account; we send TikTok limited page-view, product-view, signup and purchase events, with no version of your email address; and, on our starter-kit funnel page only, Pinterest’s own automatic enhanced match feature can send Pinterest a hashed version of what you type into a visible field on that page (Section 2.2). Because these platforms may use that for their own advertising purposes, California law treats it as “sharing” personal information for cross-context behavioral advertising, and we treat it that way too rather than argue for a narrower label. Our own code never sends your email address in readable form, and never sends your training logs, health or wellness data, phone number, or payment card details to any advertising platform. You can stop it at any time: decline analytics cookies, withdraw your consent through the cookie banner, use our Your Privacy Choices page, or switch on Global Privacy Control in your browser — any one of those stops it immediately. Full detail is in our CCPA Notice, Section 5.

If we extend conversion measurement to other advertising platforms (for example, Meta Conversions API or Google Enhanced Conversions), we will update this Privacy Policy at least 14 days before that change takes effect, provide an opt-out mechanism, honor the Global Privacy Control (GPC) browser signal, and treat such transmissions as a “share” under the California Consumer Privacy Act.

4. How We Share Your Information

We share your information only in the following circumstances:

4.1 Service providers

We share data with trusted vendors who help us operate the Service. Each provider processes data only as instructed by us and in accordance with their own privacy policies:

• Supabase — Database hosting, user authentication, and file storage. All user data is stored on Supabase-managed infrastructure in the US-West region (Northern California). Privacy Policy
• Stripe — Payment processing, subscription management, and creator payouts via Stripe Connect. Stripe receives your email, name, and payment details when you make a purchase. If you pay by card or PayPal, we may use the name given at payment to help us check that the name on your profile is real. It is never shown on your profile. If you choose Identity Verification, Stripe Identity collects your ID document images and a selfie and performs the face comparison; see Section 5A. Privacy Policy
• PayPal — Payment processing and subscription billing for purchases made on our website with PayPal. PayPal receives your name, email, and payment details when you pay with PayPal. Privacy Policy
• Apple, Google Play and the Amazon Appstore — Billing for purchases made inside our iOS app, our Android app and KETTLEBELL MONSTER TV respectively. The store handles your payment details; we receive only a purchase token or transaction identifier to confirm the purchase. Apple Privacy Policy · Google Privacy Policy · Amazon Privacy Notice
• Polar — If you connect your Polar Flow account, we retrieve your exercise files from Polar with your authorization (see Section 5). Privacy Notice
• Amazon Web Services (SES) — Transactional email delivery from the US-East-1 (N. Virginia) region. AWS receives recipient email addresses and message content. Privacy Policy
• Cloudflare — CDN, DDoS protection, DNS, web hosting (Cloudflare Pages), video hosting (Cloudflare Stream), image hosting (Cloudflare Images), and bot protection (Cloudflare Turnstile). Cloudflare processes IP addresses, request metadata, and browser characteristics for security purposes. Privacy Policy
• Anthropic — AI personalization for the Compass guidance system. Anthropic receives aggregated, non-identifying user metrics (training level, streak count, mental readiness band) to generate recommendations. Anthropic does not use API data for model training and deletes inputs/outputs within 30 days. Privacy Policy
• Cloudflare Web Analytics — Privacy-first website analytics to understand aggregate usage patterns (pages visited, referrers, device types). Cloudflare Web Analytics does not use cookies, does not track individual users, and does not collect personal data. Analytics data is processed on Cloudflare's infrastructure as part of our existing Cloudflare service. Privacy Policy
• LiveKit Cloud — Real-time video infrastructure for live training sessions and events. When you join a live video session, LiveKit receives your participant identity token, audio/video streams, and connection metadata (IP address, user agent). LiveKit does not store session recordings unless explicitly enabled by the host. Privacy Policy
• Printful — Print-on-demand fulfillment for physical merchandise. When you order physical products, Printful receives your name, shipping address, and order details to fulfill and ship your order. Privacy Policy
• Lulu — Print-on-demand book publishing and fulfillment. When you order printed books, Lulu receives your name, shipping address, and order details. Privacy Policy

4.2 Advertising platforms (marketing measurement only)

We run marketing campaigns on the following advertising platforms. We use their APIs to download aggregated performance data for our campaigns (clicks, impressions, spend, conversion counts) so we can measure return on marketing investment. We do not upload your personal information to most of these platforms. The exceptions are Reddit Ads, TikTok Ads, and Pinterest Ads, described in the list below. When you click one of our ads, the platform itself may set its own cookies in your browser under its own privacy policy; that processing is performed by the platform as an independent data controller and is outside the scope of this Privacy Policy.

• Google Ads — Search and YouTube advertising. Privacy Policy
• Meta Platforms (Instagram advertising) — Instagram-only placements via the Meta Marketing API. Facebook-feed advertising is not used. Privacy Policy
• Reddit Ads — Sponsored posts and display advertising on Reddit. Privacy Policy
• TikTok Ads — In-feed and other paid advertising on TikTok, including a consent-gated TikTok Pixel that we load only after you accept analytics cookies, on our production site only, described in Section 2.2. Privacy Policy
• Pinterest Ads — Promoted Pins via the Pinterest Marketing API, and, on our starter-kit funnel page only, a consent-gated Pinterest tag with Pinterest’s automatic enhanced match enabled, described in Section 2.2. Privacy Policy
• Microsoft Advertising (Bing) — Search advertising. Privacy Policy
• Quora Ads — Promoted answers and display advertising on Quora. Privacy Policy

Other than the consent-gated Reddit Ads, TikTok Ads, and Pinterest Ads measurement described above, none of these platforms act as our processor or sub-processor for the data governed by this Privacy Policy, because we do not share your data with them. They are data sources from which we retrieve our own aggregated campaign metrics.

4.2a Our own TikTok accounts (publishing and account analytics)

IKU LLC publishes its own kettlebell training videos to the company’s own TikTok accounts. To do this, our staff connect those company accounts to our internal administration tools using TikTok Login Kit and TikTok’s developer APIs. This integration is used only by IKU LLC staff, only for the company’s own accounts. Members never sign in to the Service with TikTok, and we do not access, collect or receive any member’s TikTok account or TikTok data through it.

What we receive from TikTok, and why. When a company account is connected, and only with that account’s authorization (TikTok permissions user.info.basic, user.info.profile, user.info.stats, video.list and video.upload), we receive:

• the account’s TikTok identifier (open ID), display name and profile picture, which we store to label the account in our tools, and its username, which we check (and do not store) to confirm the correct company account was connected;
• an access token and a refresh token, which allow our tools to act for that company account until the connection is removed;
• the account’s follower, following, like and video counts, and, for each of the account’s own videos, its title, cover image, publish date and view, like, comment and share counts, which we use to measure how our own content performs.

We use the video.upload permission only to send our own videos to our own accounts’ TikTok drafts; a member of our staff then adds the caption we write and publishes the post in the TikTok app. We receive only totals for our videos: we do not receive the identity of anyone who views, likes, comments on or shares them, and we do not collect personal information about TikTok users.

Storage, security and retention. This information is stored in our own database, hosted by Supabase in the United States (see Section 4.1). The tokens are accessible only to our server-side systems, never to the Service’s web pages or apps, and are not shared with anyone. We keep a connection, including its tokens, until our staff disconnect the account; disconnecting deletes the stored connection and its tokens from our database. Performance totals already collected are kept as part of our marketing records. The authorization can also be withdrawn at any time from within TikTok, by removing our app’s access in the TikTok account’s settings, after which our tokens no longer work.

Data that TikTok itself processes is governed by TikTok’s Privacy Policy. Questions about this integration can be sent to privacy@kettlebell.university.

4.2b YouTube API Services

KETTLEBELL MONSTER uses YouTube API Services, which are provided by Google. By using the YouTube features of the Service described in this section, you are also agreeing to the YouTube Terms of Service. Google’s handling of your information is governed by the Google Privacy Policy. We use YouTube API Services in the ways described below.

Our own YouTube channel. IKU LLC publishes its kettlebell training videos on its own YouTube channel, Cavemantraining™. Our staff connect that channel to our internal administration tools with Google sign-in, and we use it to upload our videos, set thumbnails, manage playlists and captions, read our own videos’ details and performance statistics, and check our channel memberships as described below. The access tokens for our channel are stored in our own database, are usable only by our server-side systems, and are not shared with anyone. This use concerns our company’s channel only; it does not access your YouTube account.

Checking your channel membership. If you are a member of our YouTube channel, you can choose “Connect YouTube” on kettlebell.monster/youtube and sign in with your Google account. You authorize read-only access to your YouTube account (Google permission “youtube.readonly”), which we use once, only to read the identifier of your YouTube channel. We then ask YouTube, using our own channel’s access, whether that channel is a current member of our channel and at what membership level, so that we can show you the member benefits available to you. We do not read your videos, subscriptions, playlists, watch history or any other YouTube data. We do not request ongoing access and do not store your Google access token. The result of this check is shown to you on the page and then discarded; we do not store it or share it with anyone.

Keeping our member list up to date. When this feature is enabled, once a day our servers will use our own channel’s access to retrieve the list of current members of our YouTube channel from YouTube. For each member we will store their YouTube channel identifier, display name, membership level, and the dates their membership started and, where applicable, ended. We will use this information only to: (a) let our founder know about new members so he can welcome them; (b) confirm who is entitled to member benefits on KETTLEBELL MONSTER, such as discount vouchers; and (c) identify memberships that have ended, so those benefits can be withdrawn. We will not use it for advertising and will not share it with anyone. Because the list is refreshed every day, the information we hold will never be more than a day out of date, and when a membership ends we will delete that member’s record within 30 days of noticing it.

YouTube videos on our pages. Some pages of the Service show videos using YouTube’s embedded player. When a YouTube video loads, YouTube (Google) may place or read cookies and similar technologies on your device and collect information about your viewing, under the Google Privacy Policy. The embedded player is content served by a third party; we do not receive the information YouTube collects this way.

Your choices, revocation and deletion. You can remove KETTLEBELL MONSTER’s access to your Google account at any time on the Google security settings page at https://security.google.com/settings/security/permissions. You can also ask us at any time to delete any YouTube-related information we hold about you by emailing privacy@kettlebell.university with the Google account or YouTube channel you used; we will delete it as soon as possible and within 7 days. If you revoke our access through Google, we will delete any YouTube API data we hold about you within 30 days. Questions or complaints about how we handle YouTube data can be sent to the same address, or by post to IKU LLC, Attn: Privacy, at the address in Section 14.

4.3 Authentication providers (user-initiated)

If you choose to sign in via Google or Facebook, those providers share your email, name, and profile picture with us during authentication. We do not share your activity data back to those providers.

4.4 Creator data

If you purchase creator content or join a Tribe, the creator can see your display name. Creators cannot see your email address, payment details, or private activity data.

4.5 Legal requirements

We may disclose your information if required by law, court order, or government authority, or if we believe disclosure is necessary to protect our rights, prevent fraud, or ensure the safety of any person.

4.6 Business transfers

If IKU LLC is acquired, merged, or sells substantially all of its assets, your information may be transferred to the successor entity subject to the same privacy protections described here.

4.7 With your consent

We will share your information in any other circumstances only with your explicit consent.

5. Sensitive Health and Wellness Data

Some data you provide may be considered sensitive under privacy laws, including:

• Fitness biometrics (height, weight, heart rate)
• Mental readiness self-assessments (stress, motivation, focus, confidence, emotional load)
• Recovery status and body-part assessments
• Workout logs and physical performance data

How we handle sensitive data:

• All sensitive data fields are optional. You can use core features of the Service without providing any health or wellness data.
• We process this data only to provide the features you choose to use (workout tracking, mental readiness tools, recovery tools).
• We do not share sensitive health data with third parties for their own purposes.
• We do not use this data for advertising or profiling.
• You can delete this data at any time by deleting individual entries or by requesting account deletion.

For users in the European Union, our lawful basis for processing health-related data is your explicit consent, which you provide when you voluntarily submit this information through the relevant features. You may withdraw consent at any time by ceasing to use these features and requesting deletion of your data.

For users in Washington State, in accordance with the My Health My Data Act, we collect consumer health data only with your consent and do not sell consumer health data.

Wearable and heart-rate data. You can add heart-rate and activity data to your training history by uploading an activity file (.FIT or .TCX) exported from your watch, or by connecting your Polar Flow account, in which case we retrieve your exercise files from Polar with your authorization. We store the file and the heart-rate samples, averages and zone summaries derived from it on our own servers with the providers described in Section 4.1, use them only to show you your own training data and analysis, never share them with third parties for their own purposes, and delete them when you delete the import or your account.

Apple Health and Health Connect. We read nothing from Apple Health, Google Health Connect or Garmin Connect. When you tap save on a workout you finished, the app asks for your permission and then saves that workout to Apple Health (iPhone) or Health Connect (Android) on your device: the type of workout, its start and end time, its name and notes, and, where we measured them, your effort rating, the timing of its work and rest intervals and active calories. You can withdraw that permission or delete those workouts at any time in Apple Health or Health Connect. Once saved, that copy is held by Apple or Google under their own privacy terms; we do not receive it back, never use health data for advertising and never share it with anyone. Automatic sync from Garmin Connect is not available.

5A. Identity Verification (optional)

Identity Verification is an optional paid product. If you buy it, you can verify that you are who your profile says you are, and a “Verified” mark is shown on your profile and people cards. Nothing else in the Service requires it.

Who does what. The verification is carried out by Stripe Identity (Stripe, Inc.). In Stripe’s own flow you photograph a government-issued photo ID (passport, driving licence or national ID card) and take a selfie. Stripe checks that the document is genuine and compares your face with the photo on the document. That comparison uses biometric identifiers (measurements of your facial features). Stripe asks for your consent to this in its flow, and we also ask for it on our page before you start.

What we receive and keep. We never receive your ID document, your selfie, the details printed on your ID, or any biometric data. We receive only the result: whether you were verified, the date, and a Stripe reference number for the verification. If an attempt fails, we also receive Stripe’s short reason code (for example “document expired”) so we can help you retry; it is kept only in our error logs (Section 9). We keep the result and the reference for as long as your account exists, or until you ask us to remove your Verified mark.

What Stripe keeps, and for how long. Stripe stores the images and details from your ID and selfie on our behalf, and we instruct Stripe to delete that copy as soon as your result is final (Stripe completes the deletion within 4 days). Stripe also keeps certain verification data for its own purposes, such as fraud prevention and meeting its legal obligations, as an independent controller under the Stripe Privacy Policy. Stripe deletes the biometric identifiers created for your verification within one year, or sooner if you withdraw your consent. Stripe may also ask whether it can use your data to improve its verification technology; that is a separate, optional choice you make with Stripe. Stripe processes verification data in the United States. More: how Stripe handles ID verification data.

Legal basis. For members in the EEA, UK and Switzerland, the face comparison is processing of special category data and relies on your explicit consent (GDPR Art. 9(2)(a)); showing the Verified mark relies on our contract with you (Art. 6(1)(b)). For California residents, biometric information is sensitive personal information; it is used only to provide the verification you asked for and is never sold or shared for advertising. This section is also our written policy on the retention and destruction of biometric identifiers for the purposes of Illinois, Texas, Washington and Colorado law: we never possess them, and Stripe destroys them within one year.

Your choices. You may decline before or during the Stripe flow; nothing is collected and, if you have already paid, see the Refund Policy. You may withdraw consent, ask us to remove your Verified mark, or ask us to delete our record at any time by writing to privacy@kettlebell.university; withdrawal does not affect a verification already completed and removing the mark does not trigger a refund. To withdraw consent from Stripe or ask Stripe to delete the data it holds for its own purposes, write to privacy@stripe.com. Identity Verification is available only to members aged 18 or over.

6. Cookies and Tracking

We use cookies and similar technologies to operate the Service.

6.1 Essential cookies (always active)

These are required for the Service to function and cannot be disabled:

• Authentication session tokens (secure, HTTP-only)
• Cookie consent preference
• A short-lived security cookie (10 minutes), set only when you choose “Connect YouTube”, used to protect the Google sign-in against forgery (Section 4.2b)

6.2 Functional cookies (set only after you accept cookies)

These support optional features and, with one exception noted below, are set only after you have accepted cookies via our cookie banner.

• Lasting affiliate referral cookies (90 days by default, and 30, 60 or 120 days for some affiliates, used to attribute a referral to the correct affiliate on a later visit)
• Marketing campaign attribution cookies (first-party UTM cookies, 45 days for last-touch, 180 days for first-touch, used to measure which campaigns bring people to the Service — see Section 2.2 and the Cookie Policy for details)
• Advertisement click identifiers from Google, Meta (Instagram) and Microsoft (180 days), which record that a particular advertisement click brought you here so we can measure whether our advertising works. We keep these on our own systems and do not send them to those platforms — see the Cookie Policy for details
• The exception: two session-only referral cookies that remember whose referral link you arrived on, and are deleted when you close your browser. In the European Economic Area, the United Kingdom, Switzerland, Quebec, Brazil, South Korea and Thailand these wait for your consent like everything else above. Anywhere else they are set when you land on a referral link, even if you have declined cookies, because local rules allow cookies by default and their only job is to let a referral you just clicked count if you sign up or buy during that visit.

6.3 What we do NOT use

We do not use Google Analytics, Facebook Pixel, or any general cross-site retargeting pixels, beyond the three consent-gated exceptions described in Section 4.2. We do not build a persistent fingerprint of your device: the only device-derived value we use is the one-way, daily-changing visit code described in Section 6.5, which cannot follow you across days or across other companies' websites. Our aggregate usage analytics (Cloudflare Web Analytics) are entirely cookieless. We do not share your cookie data with advertising networks. We do run marketing campaigns on advertising platforms and measure which campaigns bring people to the Service — see Section 2.2, Section 4.2, Section 6.5, and the Cookie Policy for details. Embedded YouTube videos, the Reddit Pixel, the TikTok Pixel, and the Pinterest tag are exceptions to that: when a YouTube video loads (Section 4.2b), or after you accept analytics cookies for a Reddit Ads, TikTok Ads, or Pinterest Ads campaign (Section 4.2), those platforms may set their own cookies, receive the limited events, or make the automatic hashed matches described there.

6.4 Managing cookies

You can manage cookies through your browser settings. Disabling essential cookies may prevent you from using the Service. For a detailed breakdown of our cookies, see our Cookie Policy.

6.5 Measurement that does not use cookies

Some measurement works without storing anything on your device, so that we can still count visits when you decline cookies or your browser blocks them:

• Visit stitching: to count one person reading three pages as one visit rather than three, our server derives a short code from your IP address, your browser's user-agent string and the current date. The code is one-way, cannot be reversed into your IP address, and changes every day, so it cannot follow you from one day to the next. This is the same technique used by privacy-focused analytics tools such as Plausible and Fathom.
• A visit identifier held in the page: if your browser blocks cookies entirely, we keep a random identifier and the campaign identifiers you arrived with in the memory of the page you are viewing, and add them to links within our own site so the next page knows it is the same visit. Nothing is written to your device, the identifier is discarded when you close the tab, and we never add it to links pointing at other companies' websites.

Outside the European Economic Area, the United Kingdom, Switzerland, Quebec, Brazil, South Korea and Thailand, and only where you have not declined cookies and your browser is not sending a Global Privacy Control signal, we may use these to associate the campaign you arrived from with an account you create or an order you place during that same visit. See Section 2.2.

7. Push Notifications

If you opt in to push notifications, we store a device token to deliver notifications to your browser. You can disable push notifications at any time from your notification settings or your browser settings. We do not share push notification tokens with third parties.

8. Data Security

We implement industry-standard security measures including:

• Encryption in transit (TLS 1.2+) for all connections
• Secure, HTTP-only authentication cookies
• Row-level security on our database
• Cloudflare DDoS and bot protection
• Content Security Policy (CSP) headers
• Automatic redaction of sensitive data in error logs
• Encryption of creator payout details at the application level

Payment card data for website purchases is handled exclusively by Stripe and PayPal, both PCI-DSS Level 1 certified. We never store, process, or transmit full card numbers on our servers. In-app purchases are billed by Apple, Google Play or the Amazon Appstore, which never share your card details with us.

However, no method of transmission over the internet is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.

If you discover a security vulnerability, please report it responsibly to security@kettlebell.university.

9. Data Retention

We retain your personal data as follows:

• Account data: For as long as your account is active.
• Training logs, mental readiness data, recovery data: For as long as your account is active, or until you delete individual entries.
• Community content: Until you delete it or until your account is deleted.
• Payment and billing records: Up to 7 years after the transaction, as required for tax and legal compliance.
• Identity Verification: The result, date and Stripe reference for as long as your account exists or until you ask us to remove your Verified mark; the record of your consent for as long as your account exists and three years after. The ID and selfie copy Stripe holds for us is deleted as soon as your result is final (Section 5A).
• Error logs: Automatically purged on a rolling basis.
• Push notification tokens: Until you disable notifications or delete your account.
• YouTube channel members: The result of a “Connect YouTube” membership check is not stored. When the daily member list described in Section 4.2b is enabled, each member’s record will be refreshed daily while the membership is active and deleted within 30 days after we notice the membership has ended, or within 7 days of your deletion request.
• Raw analytics and campaign attribution sessions: Automatically deleted 180 days after the session ends. This includes the IP address recorded against the visit. Aggregated, non-identifying daily totals (counts, averages, campaign roll-ups with a minimum bucket size that prevents re-identification) may be retained indefinitely for historical reporting.
• Campaign attribution stored on your account or order: The campaign identifiers associated with your account or an order are retained for as long as the account or the order record is retained, and are deleted when your account is deleted. You can ask us to erase them at any time without affecting your account.
• Referral attribution stored on your account: If you signed up through a referral link, we keep a record of which affiliate referred you, and when, for as long as your account exists — it is what allows that affiliate to be paid correctly over time. It is deleted when your account is deleted, and you can ask us to erase it sooner without affecting your account. Records of commissions already paid are kept for up to 7 years with our other financial records, as tax law requires.

If you delete your account, we will delete your personal data within 30 days, except where we are required to retain it by law (such as billing records for tax purposes). Aggregated, anonymized data (such as total workout counts) may be retained indefinitely as it cannot be linked back to you.

10. Your Rights

Depending on your location, you may have the following rights regarding your personal data:

• Access: Request a copy of the personal data we hold about you.
• Correction: Request that we correct inaccurate or incomplete data.
• Deletion: Request deletion of your account and personal data. You can initiate this from Settings → Privacy & Data.
• Data Export: Request a machine-readable export of your data (JSON format). You can initiate this from Settings → Privacy & Data.
• Objection: Object to certain processing of your data, such as optional communications.
• Withdrawal of consent: Where processing is based on consent, you may withdraw consent at any time without affecting the lawfulness of processing before withdrawal.
• Restrict processing: Request that we limit how we use your data while a concern is being resolved.

To exercise any of these rights, contact us at privacy@kettlebell.university. We will respond within 30 days. We may need to verify your identity before fulfilling a request.

10.1 California residents (CCPA/CPRA)

California residents have additional rights under the California Consumer Privacy Act and the California Privacy Rights Act:

• Right to know: You can request the categories and specific pieces of personal information we have collected about you.
• Right to delete: You can request deletion of your personal information, subject to certain exceptions.
• Right to opt out of sale or sharing: We do not sell personal information. We do “share” personal information for cross-context behavioral advertising in three limited cases: the Reddit, TikTok and Pinterest measurement described in Section 3, and only if you have accepted analytics cookies. You can opt out at any time through our Your Privacy Choices page, by declining or withdrawing analytics cookies in the cookie banner, or by switching on Global Privacy Control in your browser — we honor that signal as a valid opt-out request and act on it automatically, whatever you chose before. We honor an opt-out for at least 12 months and apply it to any further collection or sharing. Opting out costs you nothing: it does not change your account, your purchases, your prices, or any feature of the Service.
• Right to limit use of sensitive personal information: We use sensitive personal information (health and wellness data) only to provide the features you have requested. We do not use it for purposes beyond what is necessary to provide the Service.
• Non-discrimination: We will not discriminate against you for exercising your privacy rights.

For full CCPA/CPRA details, see our CCPA Notice.

10.2 European Union residents (GDPR)

For information about our lawful bases for processing, cross-border transfer safeguards, and your rights under the GDPR, see our Data Protection page.

11. International Data Transfers

Your personal data is processed and stored in the United States. If you access the Service from outside the US:

• Your data will be transferred to the US, which may have different data protection laws than your jurisdiction.
• For transfers from the European Economic Area, United Kingdom, or Switzerland, our service providers maintain appropriate safeguards including Standard Contractual Clauses approved by the European Commission.
• You may request information about these safeguards by contacting privacy@kettlebell.university.

12. Children’s Privacy

The Service is not directed to children under 13. We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided us with personal information, please contact us at privacy@kettlebell.university and we will delete it.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the revised Policy at this URL and update the effective date. For material changes, we will notify active users via email or an in-app notice at least 14 days before the change takes effect.

14. Contact

For privacy-related questions, requests, or complaints:

IKU LLC
Attn: Privacy
15442 Ventura Boulevard, STE 201-1081
Sherman Oaks, CA 91403, USA
Email: privacy@kettlebell.university

Inactive Account Content Management

If your paid subscription ends, IKU retains your core account data — including your profile, training history, achievements, course progress, and purchases — indefinitely as part of the free tier. These are not affected by your subscription status.

However, content that requires ongoing storage and infrastructure resources — including but not limited to community posts and comments, uploaded files, assessment videos, and images — may be archived or removed at IKU's sole discretion, based on platform operational needs. Factors that inform these decisions include storage costs, database volume, CDN bandwidth, and community content quality.

IKU will make reasonable efforts to notify you via email before any such action is taken regarding your content. We typically send up to three courtesy notices over a 60-day period following the end of your subscription.

This policy does not apply to content associated with active paid subscriptions or to core account data that falls within the free tier.

Data Access Requests

You may request a copy of the personal information we hold about you. We will provide this information in a human-readable summary format. This summary includes the categories and substance of your personal information but is not provided in a machine-readable or portable format, as portability is not required under applicable law (including the California Consumer Privacy Act). You may submit a data access request through Settings > Privacy in your account, or by contacting us at the email address listed below.

Public Profile Visibility

KETTLEBELL MONSTER™ allows you to set your profile to "public" or "private" in your account settings (Settings > Privacy). This setting controls the overall visibility of your profile page.

When your profile is set to public:

• Your profile is accessible via your personal URL (/u/your-username) to anyone on the internet, including visitors who are not logged in.
• Your profile may appear in KETTLEBELL MONSTER™ platform search results when other users search for people.
• Your profile page may be indexed by external search engines such as Google, Bing, and others. This means your public profile information could appear in search engine results.
• You control which specific information appears on your public profile through per-field visibility toggles in Settings > Privacy (for example, bio, experience level, training style, workout activity, badges, and more).

When your profile is set to private:

• Your profile page is not accessible to others and returns a "not found" response.
• Your profile does not appear in platform search results or people directories.
• Search engines cannot index your profile.

To remove your profile from search engine results, set your profile to "private" in Settings > Privacy. Note that previously indexed pages may take time to be removed from search engine caches, depending on each search engine's crawl schedule.

Certain spaces within KETTLEBELL MONSTER™ — specifically MIND and RECOVER — are always private regardless of your profile visibility setting. Content and activity within these spaces is never shared publicly or included on your profile page.

CONNECT Community Content

Posts, comments, photos, and videos you share on CONNECT are public content visible to all registered members and may be indexed by search engines.

When you post on CONNECT, you acknowledge that:

• Your posts are public and will remain visible even if you later change your profile visibility to private.
• Setting your profile to private prevents you from creating new posts but does not remove existing posts from the feed.
• You can delete any of your individual posts at any time through the post menu.
• Account deletion removes all your posts and associated data within 30 days.

KETTLEBELL MONSTER TV

KETTLEBELL MONSTER TV is our app for Amazon Fire TV and Android TV. It works without an account: there is nothing to sign up for and nothing to sign in to. This section describes what that app collects, because it differs from the rest of the Service.

An identifier for your TV. The first time the app runs, it generates a random identifier and stores it on the TV. It is not derived from your device, is not linked to a KETTLEBELL MONSTER account, and cannot be used to identify you. Uninstalling the app, or clearing its data, removes the identifier; the app generates a new one if you install it again.

How the app is used. The app sends us, against that identifier: which screens you open; which workouts you start, complete, or mark as a favourite; the choices you make when starting a session; how far each video played and whether playback stopped early, with technical details such as how much of the video had loaded; and that a purchase or restore was requested, including which plan. It also sends the app version and the platform it runs on. We use this to see which workouts are watched and whether playback works reliably on TVs, and for nothing else. It is stored on our own servers with the providers described in Section 4.1, is never shared with anyone, and is never used for advertising.

Payments. Subscriptions in the TV app are sold and billed by the store the app came from — the Amazon Appstore or Google Play. We never receive your card details, and the store does not give us your name or email address. When you subscribe or restore a purchase, the store gives the app a receipt or purchase token; our server sends it back to the store to confirm the subscription is real and active, and issues the app an access token that stays on your TV. Apart from error logs when that check fails, we keep no record of the purchase on our servers. You manage or cancel the subscription from your Amazon or Google Play account.

What we do not collect on TV. No account details, no name or email address, no location, no crash reports from the device, and no payment information.

Retention and your rights. Because we hold nothing that identifies you, we cannot find records for you by name or email address. Removing the app’s data on your TV ends any link between you and the records already stored, which are kept only in that unlinked form. The rights in Section 10 otherwise apply, and you can reach us at privacy@kettlebell.university.