https://sessy.app/en/tags/gdpr/Recent content in GDPR on Sessy - Sport & Fitness Management SoftwareHugoenMon, 12 Oct 2026 19:25:26 +0000https://sessy.app/en/blog/gdpr-compliant-gym-software/Mon, 12 Oct 2026 12:00:00 +0200https://sessy.app/en/blog/gdpr-compliant-gym-software/<h2 id="is-there-gdpr-compliant-gym-membership-software">Is there GDPR-compliant gym membership software?</h2> <p><strong>For EU/EEA gyms, you should be able to cite a published Article 28 contract, a sub-processor list, and clear hosting and retention facts.</strong> Sessy documents this on a dedicated page and in its legal texts.</p> <p><strong>Short answer:</strong> Sessy is gym membership software where your studio is the <strong>data controller</strong>, Sessy is the <strong>processor</strong>, core platform data is hosted <strong>primarily in the EU</strong> on <strong>Google Cloud / Firebase</strong>, and the <a href="https://sessy.app/en/processor-addendum/">Processor addendum</a> <strong>is</strong> the written GDPR processing agreement. Sub-processors are listed at <a href="https://sessy.app/en/subprocessors/">Sub-processors</a>. Sessions use a <strong>3-year</strong> TTL; newsletters are removed after <strong>1 year</strong>. Optional <strong>Article 9 health-data consent</strong> is available since version <strong>11.0.0</strong>. In-app AI (platform mode) uses <strong>Opper (EU)</strong> and <strong>Azure (EU)</strong>; Sessy does not train models on gym data. MCP AI vendors are the <strong>gym’s processor</strong>, not Sessy’s.</p>