Privacy Policy
Last updated: 6 November 2026 · Version 1.3
This policy explains how Guided Boost PSA handles personal data when you visit BodyMarc, sign in, subscribe, listen to lessons or contact us. Acknowledging this policy is not consent to optional tracking or marketing.
1. Controller and contact
Guided Boost PSA is the controller of personal data used to operate BodyMarc at bodymarc.com. Our address is ul. Domaniewska 37, 02-672 Warsaw, Poland. NIP: 5214177112 (PL5214177112); KRS: 0001261827; REGON: 54554673100000.
For privacy questions, rights requests and account support, email [email protected] or write to our postal address. BodyMarc is intended for people aged 18 and over. Contact us if you believe a child has supplied data contrary to this restriction.
2. Data we process
Account and authentication data: your email address, account identifier, role, status, language preference, verification and sign-in records, session records and request-security information. Sign-in uses emailed codes. Codes and session tokens are protected using cryptographic digests in the application database; the email provider necessarily processes the code message when delivering it.
Subscription and payment data: customer and subscription references, checkout and billing status, period dates, amounts, currency, invoices, cancellations, refunds and dispute information. Stripe collects the payment and billing details needed at checkout. BodyMarc does not receive your complete payment-card number or card security code.
Listening and service data: module, lesson and audio identifiers, saved playback position, completion status, selected playback speed and the last selected lesson. These records are associated with your account so that you can resume and use your subscription.
Communications and technical data: support correspondence, delivery information, referral or coupon information where supplied, and technical records needed to operate and secure the website. Hosting, delivery and security providers may process IP addresses, browser information, request details and error logs. Affiliate participants also have agreement-version, acceptance, referral, commission, invoice and payout records.
We do not ask you to provide health histories or medical information to use BodyMarc, and listening activity is not a medical assessment. Please avoid sending sensitive health information unless it is necessary for your request. If you do, we will limit its use to handling that request under an applicable legal basis and any additional condition required for sensitive data.
3. Purposes and legal bases
We use account, authentication, listening, subscription and support data to provide the service and perform our contract with you or take steps you request before entering it (GDPR Article 6(1)(b)). Providing an email address is necessary for account creation and email-code sign-in. Payment information required by the seller is necessary for a paid order.
We process records needed for accounting, tax and other legal obligations under Article 6(1)(c). Where appropriate, we rely on legitimate interests under Article 6(1)(f) for security, fraud prevention, fault diagnosis, proportionate service administration, handling complaints and establishing or defending legal claims. Our interests are operating a reliable service and protecting users and our business.
Optional third-party analytics, advertising tracking and any marketing requiring consent rely on your separate consent under Article 6(1)(a) and applicable device-access and electronic-marketing rules. A legitimate-interest basis does not replace consent where consent is required. Refusing optional tracking will not prevent sign-in or paid access.
4. Cookies, local storage and service preferences
The site uses the essential __Host-bodymarc_session cookie for sign-in, with a current lifetime of up to seven days, and __Host-bodymarc_browser for browser-bound authentication and request security, with a lifetime of up to 30 days. Session access can end sooner on sign-out, expiry or revocation. These cookies are Secure, HttpOnly and SameSite=Lax.
When you choose a language, we save English or Polish in the functional __Host-bodymarc_locale cookie for up to 180 days. It is Secure, HttpOnly and SameSite=Lax and contains no account identifier. After successful sign-in, your saved browser choice becomes your account language; if this browser has no saved choice, we use your account language. The cookie is also renewed after successful sign-in. You can change your choice in the header or in Profile. Signing out keeps the browser language; clearing cookies removes it from that browser. A language-specific link controls that visit without changing your saved choice. This preference does not enable optional marketing tracking.
Saved listening progress and playback preferences are stored with your account on our server rather than used as advertising identifiers.
You can remove cookies or browser storage through browser settings. Blocking essential cookies can prevent sign-in. A cookie’s browser lifetime is different from the retention of associated server records.
Cookie settings in the footer lets you accept or reject optional marketing cookies and change your choice later. We store your versioned choice in bodymarc.consent.v2 in local storage for up to 180 days. No optional tracking is enabled by browsing, signing in or purchasing. Google Analytics is not currently activated. An additional bodymarc.meta-events.v2 local-storage record keeps up to 500 opaque event identifiers for up to 180 days to avoid duplicate conversions.
5. SendGrid and necessary service emails
Twilio SendGrid delivers sign-in codes and necessary service messages sent through our email system. It receives the recipient email address, message contents and the technical information needed for delivery and abuse prevention. The current sign-in email integration disables open and click tracking.
Necessary sign-in, billing, security and support messages are separate from optional promotional emails. We will only send optional marketing where the applicable permission requirements are met, and provide a way to unsubscribe. Unsubscribing from marketing does not stop necessary account or transaction messages.
6. Stripe and payment responsibilities
Stripe processes checkout, recurring payments, subscription administration, payment security and related billing records. We send the identifiers and order information needed to create and reconcile your checkout and subscription, and receive the status and billing information necessary to administer access.
Stripe may act as an independent controller for some payment, fraud-prevention and legal purposes. With Stripe Managed Payments, the seller or merchant of record named at checkout also has its own legal and privacy responsibilities. Their privacy information applies to their processing; visiting Stripe checkout does not remove our duty to explain our own use of the data.
7. Google Analytics — planned, with separate consent
We intend to use Google Analytics to understand website traffic and interactions. It is not currently activated in the BodyMarc application. Before activation, we will provide an appropriate Analytics consent choice and disclose the actual configuration, cookie lifetimes and retention settings.
If you choose to allow it, Google and the relevant Google group entities may process page views, interactions, referral and campaign information, browser and device information, approximate location and online identifiers. Network communication involves processing IP information; Google states that GA4 does not log or store individual IP addresses.
We will not send sign-in codes, private account or checkout links, email addresses, full payment details or sensitive health information to Google Analytics. Any advertising features or additional integrations will need an appropriate assessment, disclosure and consent. Refusal or withdrawal will not affect account or subscription access.
8. Meta Pixel — only with separate marketing consent
BodyMarc supports Meta Pixel for advertising measurement, enabled only when a BodyMarc Pixel identifier has been configured and you explicitly accept marketing cookies. Until then no Meta script or tracking request is loaded. Reject optional cookies keeps it disabled. You can withdraw consent at any time using Cookie settings in the footer.
With marketing consent, the integration can send PageView for the public homepage and programme offer, ViewContent for the general membership offer, CompleteRegistration after the first verified sign-in, InitiateCheckout when you submit a valid checkout form, StartTrial after verified trial access, Purchase for a Stripe-confirmed settled payment and Subscribe for the first settled monthly payment of a subscription. Purchase amounts use the actual amount paid in USD, including any tax within the price. Opaque event identifiers prevent repeated browser delivery; no email, account ID, invoice ID or subscription ID is sent. Marketing consent must predate the action, and conversion retrieval is limited to the past 24 hours. Conversion events can be sent on the plain Profile page; no Profile PageView is sent. The script is not loaded on lesson, article, login, authentication or billing URLs, or URLs containing query strings or fragments. Automatic event detection and advanced matching remain disabled. Meta receives the current generic page URL, timestamps, browser/device information, IP address and cookie identifiers. Meta may set _fbp and, when applicable, _fbc cookies with a usual lifetime of up to 90 days. Withdrawal revokes consent, removes accessible Meta cookies and reloads the page to unload the script. Browser blocking or leaving the website can prevent delivery; previously shared data cannot be undone by withdrawing consent.
For EEA users, Meta Platforms Ireland Limited is generally the relevant Meta entity. Where the Business Tools terms create joint controllership, that arrangement applies to the collection and transmission stage; Meta’s subsequent processing is governed by its own responsibilities. Meta is not simply our processor for every purpose.
Email-based advanced matching, automatic event detection, customer-list uploads and server-side Conversions API sharing are not enabled by this integration. Refusing marketing cookies does not affect sign-in or paid access.
9. Other necessary recipients and international transfers
We do not sell or rent your personal data or provide our customer database to unrelated businesses for their own marketing. Apart from the services described above and consent-based tools if activated, access is limited to people and providers who need it to operate the service, meet legal obligations or handle claims.
Infrastructure includes Scaleway hosting and database services, private storage and backups, and Cloudflare network delivery and security. Authorised personnel and necessary technical contractors may access data for their tasks. Accountants, legal advisers, payment counterparties or competent authorities may receive information where necessary for their role or required by law. Affiliate dashboards show aggregate referral and financial information rather than referred customers’ email addresses or listening activity.
Some providers and their subprocessors may process information outside the EEA, including in the United States. Where required, transfers rely on an applicable adequacy decision or appropriate safeguards such as the European Commission’s Standard Contractual Clauses, with additional measures where necessary. The mechanism depends on the provider and transfer. Contact us for information about applicable safeguards and how to obtain a copy.
10. Retention and security
Account, listening and preference data are retained while needed to provide your account and resolve its closure. Cancelling recurring billing does not automatically delete an account or listening history. You can request deletion, subject to lawful retention exceptions.
Sign-in codes expire after ten minutes. The application’s routine cleanup removes expired session records and sign-in challenges older than one day. Service logs, access evidence and other necessary records have separate retention purposes; an expired code does not mean all associated records immediately disappear.
Billing, accounting and affiliate financial records are retained for the statutory periods that apply. Support and security records are kept as long as reasonably necessary for the issue, investigation or claim. Relevant criteria include the relationship’s duration, applicable limitation periods, outstanding disputes, legal obligations and whether information can be deleted or anonymised. We do not promise a fixed deletion timetable that is not implemented.
Backups remain protected until their normal replacement cycle. We use restricted access, encrypted connections and other appropriate technical and organisational safeguards. No internet service can guarantee absolute security.
11. Your privacy rights
Subject to the applicable legal conditions, you can request access, correction, erasure, restriction and portability of your data. You can object to processing based on legitimate interests on grounds relating to your situation, and object to direct marketing at any time.
You can withdraw consent for consent-based processing without affecting its lawfulness before withdrawal. Agreeing to the Terms or acknowledging this policy is not consent to analytics, advertising or marketing. Where optional tracking is introduced, it will be off until a valid choice allows it, and you will be able to change that choice.
Send requests to [email protected]. We may need proportionate verification of your identity. We normally respond within one month; any lawful extension and its reason will be explained.
You may complain to the President of Poland’s Personal Data Protection Office (UODO), or the competent authority where you live, work or believe an infringement occurred. You do not have to contact us first.
BodyMarc does not use solely automated decisions producing legal or similarly significant effects within the meaning of GDPR Article 22. Subscription access is administered using payment and entitlement records; contact us to have a disputed access decision reviewed. Any future Meta advertising profiling is described separately above.
12. Changes to this policy
We will update this policy when processing changes, including before introducing optional tracking. Material changes will be brought to your attention where appropriate. Publishing a new policy does not replace fresh consent where required. The current version remains available through login notices and the website footer.