Skip to main content

Trust Center

Privacy, security, AI data use, and company facts

KETTLEBELL MONSTER is the kettlebell ecosystem built from Cavemantraining and IKU education. First released on January 2, 2023 and relaunched in 2026, it brings earlier KETTLEBELL MONSTER web and Android work into a modern, connected app environment built for scale. This page collects the source documents people and answer engines should use when checking how the platform handles privacy, security, AI features, and account rights.

Plain-language facts

Operator
IKU LLC operates KETTLEBELL MONSTER.
Lineage
KETTLEBELL MONSTER was initially released on January 2, 2023. It relaunched in 2026 as a faster, stronger platform built for scale. It brings that earlier web and Android work together with Cavemantraining and IKU kettlebell education built online since 2009.
Payment cards
Web payments are processed by Stripe or PayPal. Purchases inside the iOS and Android apps are billed by Apple and Google Play; KETTLEBELL MONSTER TV subscriptions are billed by the Amazon Appstore or Google Play. KETTLEBELL MONSTER does not store full card numbers, expiry dates, or CVV codes.
Privacy or security question
Email legal@kettlebell.university — the same address published on every legal document.
Location data
The current Privacy Policy states that KETTLEBELL MONSTER does not collect precise GPS location.
Health and training data
Training, recovery, mental-readiness, and fitness-profile fields are used to provide the features a member chooses to use.
AI processing
Current disclosed AI features may use one or more AI providers depending on the feature. Disclosed AI provider processing is not used for provider model training under the disclosed provider terms.

Compared with other kettlebell apps

See how KETTLEBELL MONSTER stacks up against other kettlebell and fitness apps, compared from public sources.

Compare kettlebell apps

Security controls we can describe publicly

KETTLEBELL MONSTER maintains internal security controls covering access management, payment handling, logging, monitoring, backups, vendor review, privacy requests, AI data use, and incident response. We describe these controls at a public-safe level and avoid publishing implementation details that could weaken them.

  • Encrypted connections for app traffic
  • Access controls for accounts and internal tools
  • Limited internal access based on operational need
  • Restricted admin access for authorized personnel
  • Payment processing handled by Stripe
  • Established infrastructure and cloud providers
  • Logging and monitoring for reliability, abuse prevention, and security review
  • Backup and recovery procedures
  • Vendor and subprocessor review
  • Account deletion and privacy request processes
  • AI data-use policy and provider review
  • Internal incident response process

Security details we do not publish

For safety, we do not publish operational details that could help an attacker map the platform. This includes:

  • database schema details
  • internal table names
  • authentication/session implementation details
  • admin route names
  • WAF and Cloudflare rule details
  • monitoring thresholds
  • backup locations
  • secret-management mechanics
  • operational incident playbooks

What this page is for

This is not a replacement for the legal documents. It is a clear navigation page that points to the current source material. If there is a conflict, the active legal document controls.