Privacy
policy.

1. Who handles your data

STRATA Fitness operates the STRATA website and account service. Privacy questions and data requests can be sent to stratafitness.official@gmail.com.

The STRATA app, available from the App Store for iPhone and from Google Play for Android, opens the same STRATA account service inside the app. This policy covers the website and both apps; where an app works differently, such as buying Strata+ through Apple or Google Play, this policy says so.

2. Account and fitness-profile data

During a new signup, STRATA temporarily stores the submitted name and email address, a salted scrypt password hash, challenge timestamps and counters, and an HMAC digest of the six-digit verification code. The plaintext password and verification code are not stored in the database. No user account or normal signed-in session is created until the code is accepted.

After verification, STRATA stores your name, email address, account creation time, and salted password hash. It also stores hashed session identifiers, session creation and expiry information, weekly plans, training goals, experience level, available equipment, exercise preferences, optional movement constraints, exercise ratings, and relevant update timestamps. It also records the first time you save a full week (as many days with exercises as the training days you chose), as one date that the owner’s activation count uses; it is in your export and is deleted with your account. Account can show whether a session is current plus its creation and expiry times through a separate one-way public identifier; it does not expose the stored token hash, IP address, or device fingerprint. For a saved Strata+ monthly plan, STRATA stores its title, start date, exercises-per-target choice, weekday muscle-target and rest schedule, imported or copied weekly source choices, generated exercise entries and prescriptions, and update time. Individual ratings are connected to your account in storage but are shown to other users only as exercise-level aggregates. Your Strata+ profile and monthly plan are not publicly displayed.

The shared personal setup for Plan and Nutrition stores age, height, weight, optional body-fat percentage, equation coefficient selected by the user, goal and pace, usual daily movement outside planned workouts, additional weekly activity minutes and its selected intensity, experience, workout days and frequency, session duration, available equipment, optional movement limitations, usual exercises and the maximum sets, repetitions, and load entered for them, calorie-pattern and flexible-day choices, optional macro preference, time zone, and update revision. Older profile versions may retain the prior whole-day activity answer until you explicitly review and save the separated fields. Its private coaching profile can also store the dietary pattern, gluten-free or dairy-free requirements, supported allergen selections, an optional other-or-uncertain-allergy note, favorite-food categories, preferred daily meal count, and optional daily food budget you choose to provide. STRATA derives an account-private weekly training plan, energy estimates, daily calorie and optional macro targets, weight-change scenarios, and requested remaining-day food options from those inputs. The canonical profile—including those food preferences—is embedded in the private weekly coaching snapshot so the inputs behind that generated week remain reviewable. STRATA also stores the calories, optional protein, carbohydrate, and fat values, optional morning weight, and complete-versus-incomplete status you choose to log for a day. Explicitly complete intake and morning-weight observations from the prior 42 calendar dates can be examined to make a bounded adjustment to a newly generated week's energy estimate; incomplete entries remain visible but are excluded from that calculation. The separated activity answers and generated-session estimates are planning inputs, not measured movement or wearable data. Food options are derived when requested and are not stored as meals eaten or as a separate food diary; the daily intake log does not collect actual food spending. These are planning estimates and self-entered records, not a diagnosis, allergy certification, medical nutrition therapy, verified energy expenditure, verified nutrient measurement, or price guarantee, and they are not publicly displayed.

When you use signed-in workout logging, STRATA stores session dates, titles, exercise identifiers, planned prescriptions, actual repetitions, recorded loads and units, timed sets, completion state, rest-timer deadlines, elapsed time, and update revisions. If you choose to complete the post-workout check-in, STRATA also stores your 1–5 answers for difficulty, energy, comfort, and enjoyment. An optional 4–8 week training block stores its title, goal, length, current week, optional lighter week, milestones, progression rule, state, and revision. STRATA may calculate next-session suggestions from comparable completed entries and the check-in you submitted. A low-comfort, low-energy, or highest-difficulty answer can create a pending, account-private plan-adjustment proposal; the proposal records its source workout, proposed set change, status, expected plan revision, and resolution time. It does not change your plan unless you explicitly accept it. Workouts, check-ins, blocks, suggestions, and proposals are scoped to your account, are not publicly displayed, and are removed with account deletion.

If you choose to publish your week, STRATA stores one listing for your account containing its title, optional description, validated structured weekly plan, an internal owner identifier, publication state, your STRATA display name, and creation and update timestamps. Strata+ members can see the title, description, plan, display name, and timestamps. Your email address and internal user identifier are not included in the listing returned to them. Applying somebody else's plan creates a separate copy in your private weekly Plan and does not reveal your identity to its author.

For password reset and account deletion, STRATA temporarily stores a hash of a random one-time link, its purpose, expiry and delivery state, and security-email rate-limit records. The raw link is present in the email delivered by Resend and is processed transiently by your browser and STRATA’s server, but STRATA’s database stores only its hash. A new plaintext password is processed only to create a new per-user salted hash and is not stored. A password reset replaces the existing salted hash and signs out every device.

If you contact support, STRATA stores the name, email, category, subject, message, optional order reference, status, internal support note, response time, and related timestamps. A signed-in request is attached to the account’s stored name, email, and user identifier. Never include a password, verification code, recovery or deletion link, full card number, or API key.

When you request a JSON account export, STRATA reads account-scoped collections and streams workout history in stable pages as a private, non-cacheable download. It does not silently cap the workout collection. Because the download does not hold one database transaction open, account changes made while it is running may appear progressively rather than as one point-in-time snapshot. The export includes your profile, plans, preferences, ratings, workouts and summaries, check-ins, training block and adaptations, coaching profile—including the saved food preferences—weekly coaching snapshots that repeat their canonical profile inputs, calorie, macro, optional morning-weight, and completeness logs, connected-device settings and imported Polar data, trial and limited billing records including STRATA's copy of any Apple or Google Play in-app subscription state, and your support tickets. It excludes password hashes and salts, session and CSRF credentials, verification and one-time-link material, IP or device fingerprints, Paddle customer identifiers and temporary checkout/webhook records, internal administrator and support notes, audit records, and aggregate product signals. The export itself is not retained as a separate server record. Completing account deletion removes both the canonical coaching profile and its private weekly-snapshot copy, together with the remaining coaching records described in the Retention section.

If you create an account or sign in with Google, Google confirms who you are and shares your name and email address with STRATA; STRATA never sees your Google password. STRATA stores Google’s account identifier for you, the email address it shared, and when you linked and last used it. Such an account has no STRATA password until you set one. A Google account is linked to an existing STRATA account only when both have verified the same email address. Your data export lists linked sign-ins without identifiers or tokens, and deleting your account removes them.

3. Subscription and payment information

STRATA no longer offers a free Strata+ trial. For a trial started before 1 October 2026, STRATA keeps the account identifier and the trial’s start and expiry times so access ends on time and the trial cannot be restarted or extended.

Paddle handles checkout, recurring payment, subscription-management, and refund information under its own privacy notice. STRATA receives and stores the Paddle transaction, customer, subscription, price, and product identifiers connected to the account; transaction and subscription status; current billing-period end; a scheduled cancellation, pause, or resumption and its effective time; entitlement, refund, reversal, and relevant event timestamps; and limited reconciliation state needed to provide access, prevent duplicate processing, open account-bound management links, and provide support. STRATA does not receive or store full payment-card or bank-account details. Short-lived Paddle customer-portal URLs are requested only when a signed-in member chooses a billing action and are not stored as account records.

In the STRATA iOS app, Strata+ is sold as an auto-renewable subscription through Apple In-App Purchase, and Apple is the payment processor for those purchases under its own privacy policy. STRATA never receives your Apple Account password or payment-card details. To make sure a purchase unlocks the right account, the app gives Apple your STRATA account identifier as the purchase's account token, and Apple returns it with the purchase. When you subscribe, restore purchases, or open the app, the app sends STRATA the purchase records Apple signed, and Apple sends STRATA signed App Store Server Notifications when that subscription renews, changes, fails to renew, expires, or is refunded or revoked. Apple shares the transaction data needed to grant access, and from it STRATA stores the Apple transaction and original-transaction identifiers, product, App Store environment, purchase and expiry dates, auto-renewal status, any billing grace period, any refund or revocation date and reason, and when the record last changed, linked to your STRATA account. STRATA uses this information only to provide and keep Strata+ access, stop one purchase from unlocking a different account, and provide support. STRATA keeps the identifiers of processed notifications, which contain no account information, for 30 days so a repeated delivery is not applied twice.

In the STRATA Android app, Strata+ is sold as an auto-renewing subscription through Google Play Billing, and Google is the payment processor for those purchases under its own privacy policy. STRATA never receives your Google Account password or payment-card details. To make sure a purchase unlocks the right account, the app gives Google Play your STRATA account identifier as the purchase's obfuscated account identifier, and Google returns it with the purchase. When you subscribe, restore purchases, or open the app, the app sends STRATA the purchase token Google Play issued; STRATA then asks Google Play's Developer API for that subscription's state, and Google sends STRATA a Real-time Developer Notification when the subscription renews, changes, is put on hold or paused, fails to renew, expires, or is refunded or revoked. From Google's answer STRATA stores the purchase token, product and base plan (monthly or yearly), subscription state, whether it is a test purchase, the latest order identifier, any purchase token it replaced, start and expiry times, auto-renewal status, whether the purchase has been acknowledged, and when it was last checked, linked to your STRATA account. STRATA uses this information only to provide and keep Strata+ access, stop one purchase from unlocking a different account, and provide support. Your data export includes the order identifier and subscription state but not the purchase token.

A prior qualifying lifetime purchase may remain mapped to the account as grandfathered access without a current subscription. STRATA retains the related transaction and entitlement information needed to honor, support, refund, reverse, or validate that access.

4. Technical information

The service temporarily uses an IP address for signup, verification, login, resend, password-reset, account-deletion, support-form, rating, administrator account and support actions, and optional product-activity rate limits. This includes limits on requesting, checking, and completing one-time account-action links. Signed-in account export and session-change limits use the authenticated account identifier instead. For support-form protection, STRATA stores one-way hashes of the network address and submitted email with a timestamp; the application database does not store the raw network address in that quota record. For product-activity limits, the app transforms the network address with a new random in-memory HMAC key each server process and does not write that address or hash to the product-count table.

The application assigns each request a validated incoming or new random request identifier and writes a structured operational record containing time, method, requested path without query parameters, response status, duration, and completion state. The application logger omits request bodies and raw query strings and redacts values under sensitive field names. Render and other infrastructure providers may separately process IP addresses, request times, complete request URLs, browser or device headers, and error information to deliver, diagnose, and protect the service.

Authorized administration records the administrator account, affected account identifier where applicable, action, server-generated action-specific reason, result, and time. The administrator can view account identity and status, session counts, plan and rating totals, limited Paddle transaction status, pending deletion status, support requests, and opt-in aggregate product activity counts. The owner overview calculates five distinct-account totals for a first completed workout, a second completed workout, completed workouts whose start times are at least seven days apart, a trial start, and any validated completed Paddle payment record. A separate total counts subscriptions whose current provider period advanced beyond the initial window; it is not a unique-account total or proof of a particular renewal charge. These totals come from existing account, workout, trial, purchase, and subscription records and do not expose workout contents in the overview. A separate metrics view counts customer accounts only, leaving out the owner and STRATA’s review, demo, and test accounts: accounts that saved or logged something each week, sign-ups each week and whether they used Google, the share that saved a full week within seven days of signing up, the share still active four and eight weeks after signing up, paying subscriptions and monthly recurring revenue, and Strata AI use per active member. It shows and exports only these weekly and monthly totals, never a list of people or any plan, workout, diary, or Polar content. The dashboard never displays password hashes, session or action tokens, verification-code digests, payment-card data, database credentials, provider API secrets, or a person-level product activity record.

5. Why information is used

• To verify new signup email addresses and send essential verification, recovery, deletion-confirmation, and support messages
• To create, authenticate, recover, and delete accounts
• To sync profiles, workouts, check-ins, training blocks, coaching choices, nutrition logs, and weekly and monthly plans across devices
• To estimate energy needs, distribute a selected weekly calorie target, generate a new deterministic training week, show illustrative weight-change scenarios, and—when enough complete observations exist—make a conservative trend-informed adjustment for a future week
• To filter and rank requested remaining-day food options against the saved dietary, allergy, calorie, optional macro, meal-count, favorite, and budget choices described above
• To show logged progress and calculate conservative next-session suggestions from comparable entries and a submitted check-in
• When you connect Polar, to show your recovery, sleep, overnight stress signals, heart rate, and Polar workouts, and to offer an optional lighter session
• To hold an optional plan-adjustment proposal for your review and apply it only after your explicit approval
• To publish weekly plans at an account holder's request and let Strata+ members browse and apply them
• To calculate personalized Strata+ results and generate user-directed monthly plans
• To calculate aggregated community ratings
• With your choice, to count coarse product actions and see which parts of the product may need attention
• To provide and manage paid access, monthly or yearly renewal, receipts, cancellation, support, and refunds
• To prevent misuse, enforce request limits, and maintain service security
• To meet applicable legal obligations

Depending on the law that applies, STRATA relies on performing its agreement with you, taking steps you request before entering that agreement, legitimate interests in operating and protecting the service, compliance with legal obligations, or consent where consent is required. You may contact us with a question about the basis used for a particular activity.

6. Providers and external services

STRATA uses Render for application hosting, Turso for database hosting, Resend for essential signup verification, login verification, password recovery, deletion confirmation, and support communications, and Paddle as merchant of record for checkout, subscription management, recurring payments, tax, receipts, and refunds on the website. For Strata+ bought in the STRATA iOS app, Apple processes the payment, renewals, cancellations, and refunds and sends STRATA the signed purchase information described in Subscription and payment information; see Apple's Privacy Policy. For Strata+ bought in the STRATA Android app, Google Play processes the payment, renewals, cancellations, and refunds and answers STRATA's subscription checks as described in Subscription and payment information; see Google’s Privacy Policy. When you connect Polar, STRATA exchanges data with Polar as described in Connected devices. When you sign in with Google, Google shares the information described in Account and fitness-profile data; see Google’s Privacy Policy. When you allow Strata AI, STRATA sends Groq the summary described in Strata AI. To deliver an account or support message, Resend receives the recipient and sender addresses, subject and message content, and related delivery metadata. Resend states that email content and metadata, delivery events, logs, and metrics are retained for 30 days across its standard plans; see Resend’s Privacy Policy and current retention documentation.

Paddle’s checkout software loads on the Pricing page and may receive normal technical request information needed to provide checkout. Choosing a billing action from Profile requests an account-bound Paddle customer-portal session and then sends your browser to Paddle’s secure portal. STRATA serves its display fonts and homepage photographs from the same STRATA origin; loading those assets does not contact Google Fonts or Unsplash. The visible Unsplash credit links, YouTube, research, and other external sites receive normal request information only when you choose to follow their links. Those services apply their own privacy policies.

Strata AI, included with Strata+, runs only when a signed-in member sends it a request. To answer, STRATA sends the language model your message, up to six recent turns of the conversation, and a summary that STRATA prepares from your saved weekly plan, personal setup (such as experience, equipment, movement limitations, training days, and nutrition goal), recent workouts, recent calorie-log and morning-weight averages, and, if you connected Polar, the last few nights of sleep, recovery, and heart-rate readings. It never sends your name, email address, or account identifier. Groq runs the model, as described in Strata AI (Groq) below. STRATA keeps each request in its database only until the answer is ready, and each answer for up to 10 minutes so the page can collect it; logs record only the request type, outcome, and duration. Your conversation stays in your browser tab’s session storage until you close the tab, start a new conversation, or sign out from the Strata AI page, and it is removed if a different account opens Strata AI in that tab. A proposal changes your account only when you choose to apply it.

7. Connected devices (Polar)

Strata+ members can choose to connect their own Polar account from Profile. Connecting starts on Polar’s own sign-in page, and STRATA never sees your Polar password. After you agree, Polar gives STRATA a short-lived access token and a refresh token limited to read-only sleep, Nightly Recharge, continuous heart-rate sample, and training-session scopes. STRATA stores those credentials and their expiry encrypted with AES-256-GCM, together with a random local connection reference, the consent version you accepted, connection and sync times, sync status, and your lighter-session setting. STRATA does not request your Polar profile or store a Polar user number.

While you stay connected, STRATA reads and stores from Polar: for each night, the Nightly Recharge status, ANS charge and its status, sleep charge, average overnight heart rate, heart rate variability, and breathing rate, plus sleep start and end times, light, deep, and REM sleep, interruptions, and sleep score; for each day, the 24/7 heart-rate range, average, number of samples, a resting estimate, and half-hour averages; and for each Polar workout, its start time, duration, available name or sport information, calories, average and maximum heart rate, and cardio load. Polar exposes about 28 days for the shortest ranges STRATA uses, so STRATA keeps its own copy for up to 13 months and keeps the half-hour heart-rate detail for 28 days.

STRATA uses this information only to show your recovery, sleep, overnight stress signals, heart rate, trends, and Polar workouts next to your STRATA training and, if you leave the setting on, to offer an optional lighter session on Train after a poor night. Overnight stress signals compare a night with your own usual range; they are not a diagnosis. Polar data is not shown to other members and not used for advertising. If you also allow Strata AI, the summary it receives includes your last few nights of sleep, recovery, and heart-rate readings, as described in Strata AI (Groq) below; Polar data is never sent to it otherwise. STRATA polls Polar at least daily and refreshes the short-lived access token when needed; Polar AccessLink V4 does not provide STRATA a compatible signed webhook for these connections. Polar processes your data under its own privacy notice.

You can disconnect from Profile at any time. Disconnecting deletes the connection, both encrypted tokens, and all data STRATA imported from Polar; deleting your STRATA account does the same. Polar AccessLink V4 does not provide STRATA a remote deregistration or token-revocation endpoint, so you can separately review or withdraw the Polar-side authorization at account.polar.com. If Strata+ ends, syncing pauses and imported data stays until you disconnect or delete your account. The account export includes your connection settings and imported Polar data, but never either token or the local connection reference.

8. Strata AI (Groq)

Strata AI is an optional Strata+ feature. Nothing is sent to it until you choose “Allow Strata AI”, and you can turn it off at any time from the Strata AI page. When you ask a question, or when the Daily Brief is on, STRATA sends Groq, Inc., the provider that runs the model, a short summary that STRATA builds: your weekly plan, recent workouts, the last few days of sleep, recovery, and heart-rate readings from Polar if you connected it, your calorie diary, your training and nutrition settings, and the conversation you are having. It never includes your name, email address, account identifier, payment details, or your Polar login or tokens.

STRATA's Groq account is set to Zero Data Retention, and Groq states that it does not use customer inputs or outputs to train its models; see Groq's Privacy Policy. Answers are checked by STRATA before you see them, and proposals change nothing until you apply them. Strata AI does not give medical advice; when your readings stay outside your usual range it may suggest checking in with a health professional.

The Daily Brief is stored with that day's summary in your account so it can be shown without asking the model again. STRATA also counts each day's Strata AI requests and model usage to stay within its limits. Both are included in your account export, are deleted with your account, and you can delete stored Daily Briefs at any time from the Strata AI page.

9. Cookies, imports, and device storage

Guest plans, generated homepage week previews and their selected profile, activation decisions and safety copies, week templates, setup choices, workout-recovery drafts, Strata+ Decision Board exercise identifiers, workout rest-duration and automatic-timer preferences, and optional device product insights use browser local storage. Older guest workout logs may also remain on this device; new workout logging and week setup require Strata+ account access. Upgrading does not delete existing device records. Account drafts, activation decisions and backups, setup choices, and Decision Board records are separated by account identifier where applicable; this separation is not encryption. Rest-timer preferences and product insights apply to this browser profile rather than a particular account. Anyone with access to this browser profile or its storage may access these device copies.

The verification hand-off may keep the already-masked destination hint and whether the challenge is for signup or login in this tab's session storage. STRATA removes those values after successful verification or when the challenge is unavailable, and the browser discards them when the tab session ends.

A complete homepage preview remains on the device while you visit signup, verification, or onboarding. Signing in does not upload or save it. After authentication, STRATA compares the preview with the current account Plan and asks you to claim the device week or keep the account week. Only an explicit, security-checked Plan save sends the chosen week to the server. STRATA may keep a device-only safety copy of both versions so an interrupted decision can be recovered.

When an authorized member opens an active workout online, STRATA may store a bounded offline-continuation context with the account identifier, workout draft and revision, last confirmed access boundary, and local update time. This lets the generic offline workout shell reopen only that matching device draft. The context is not proof of current account access: reconnecting requires the same signed-in account, current Strata+ access, and a server-revision check before sync. A conflict is shown for review rather than overwritten. Clearing site data removes the context and unsynced draft.

Local product insights are limited to an allowlist of coarse milestones—such as generating a preview, saving a plan, starting or finishing a workout, or opening an upgrade step—a count, and first and latest day. STRATA also keeps only your latest answer to the optional recommendation check. The browser module discards extra event details and never stores exercise identifiers, recommendation contents, plan contents, set, repetition, load or duration data, page URLs, account identifiers, names, or contact details.

Nothing is sent unless you turn on aggregate count sharing or choose Share counts after a relevant action. That separate choice permits the current action named in the prompt and future actions while the choice remains on. Each same-origin request contains exactly one allowlisted action name and omits referrer information, and STRATA's server—not the browser—adds the UTC day. When you are signed out the request carries no cookie. When you are signed in it carries your account-session cookie and security token so the server can confirm the request is genuine and add it to the signed-in count rather than the anonymous one. To count each action once per account (or, signed out, once per network address) per UTC day, the server keeps a one-way daily key made with a secret that exists only in its memory; the key cannot be traced back to an account or address, and it is deleted after that day. The aggregate rows are keyed only by day and action name and hold a signed-in and an anonymous count, so there is no raw event, cookie, browser, account, page, exercise, plan, workout, or recommendation record to inspect. Only the authenticated primary owner can read those aggregate rows.

These are action counts, not unique people or conversion cohorts. Repeating an action on the same day does not count again, but the same person can count again on another day, and automated traffic can still add anonymous counts, so STRATA uses the totals only as directional product feedback—not as audited traffic, proof of effectiveness, or a person-level journey. Aggregate rows expire within 90 days. Turning sharing off stops future requests; a previously added count cannot be linked back to this device or removed for one person. STRATA does not send these events to a third-party analytics service.

A browser Global Privacy Control or Do Not Track signal switches off both local insights and aggregate sharing. You can also switch each setting off, inspect the exact device summary, copy it deliberately, or clear it below. Signing out or deleting an account does not erase browser-local records. Remove workout drafts through the recovery controls, remove a Decision Board record with its Clear control, use the controls below for product insights, or clear STRATA site data in your browser to remove all local records, including rest-timer preferences. Clearing site data loses guest plans, guest history, local templates, activation previews and safety copies, unsynced drafts and offline authorization, Decision Board choices, device preferences, and product insights; it does not delete account data stored on STRATA's server. Unsaved setup choices stay in this browser; an explicitly saved account profile and week sync across devices.

The login-free planner stores its plan in your browser's local storage on that device. STRATA's server does not receive that guest plan during ordinary guest use. If you explicitly export that plan, sign in to Strata+, locally import the STRATA JSON file, and save or generate a monthly plan from it, the imported choices become part of the private monthly plan stored with your account.

The file picker reads an imported STRATA weekly-plan JSON file locally in your browser; STRATA does not upload or retain the original file as a separate attachment. Only validated choices you explicitly save to your signed-in weekly or monthly plan are sent to the STRATA server. Likewise, publishing a saved week sends validated structured plan choices to STRATA rather than uploading a binary file or attachment.

During signup, STRATA uses a necessary, HttpOnly pre-authentication cookie to associate the browser with its pending verification challenge. It ends with the challenge and lasts no longer than 30 minutes. After verification or login, STRATA uses a separate necessary account-session cookie. The account-session cookie is HttpOnly, SameSite=Strict, and secure in production. It stays valid for seven days; while you keep using STRATA, including in the STRATA app, the server extends that window with the same session so you stay signed in, but never beyond 60 days after you signed in. Neither cookie is used for advertising. The account-session cookie is used for product activity counts only if you turn on aggregate count sharing, and only as described above.

The installed PWA caches public pages and interface files on your device. Its service worker does not cache account APIs, authentication requests, private Strata+ pages, verification responses, password-reset or account-deletion pages, one-time links, saved account Plan or workout data, or the local continuation draft. It may cache a generic offline workout shell, but that shell contains no account information until browser-local storage passes its separate owner and expiry checks. Guest and activation Plan data stays in browser local storage and is not placed in the service worker cache.

10. Sharing, printing, and selling

STRATA does not sell or rent personal data. Information may be shared with the providers listed above, when legally required, or when reasonably necessary to protect users, enforce these Terms, and operate the service. STRATA does not currently use third-party behavioral advertising.

Choosing a monthly-plan share control deliberately passes the generated plan text or file to your operating system's share sheet, a selected app, or your device clipboard. Choosing Download PDF opens the browser or operating system print interface, where you decide whether and where to save or send the output. Those actions can move plan information outside STRATA and make it subject to the selected app, clipboard, printer, storage location, or recipient's practices; STRATA does not share a plan through those controls until you choose the action.

11. Retention

A verification code expires after 10 minutes and its pending signup challenge ends after 30 minutes. Password-reset and deletion links expire after 30 minutes. Used, expired, or abandoned challenges are invalidated and cleaned up. One-way support-form quota records are cleaned up after 24 hours. Opt-in product activity is retained only as day-and-action aggregate counts for up to 90 days. Active account data, private weekly and monthly plans, workouts, check-ins, training blocks, coaching profiles, generated weekly coaching snapshots, and daily nutrition logs, adjustment proposals, preferences, and ratings are retained while the account remains in use. STRATA stores at most one generated coaching snapshot for each calendar week and replaces that week's snapshot if the coaching profile changes. Support requests and administrator audit logs are retained while reasonably needed to answer requests, document account actions, prevent abuse, resolve disputes, and meet legal obligations.

Completing self-service deletion or guarded administrator deletion permanently removes the STRATA user record, sessions, private weekly and monthly plans, workouts and their check-ins, training blocks, coaching profile, weekly coaching snapshots, and daily nutrition logs, connected-device connections and imported Polar data, pending or resolved adjustment proposals, published weekly-plan copies, preferences, ratings, and local Strata+ entitlement, transaction, customer, and subscription mappings, including Apple and Google Play in-app subscription records, through the database's account-deletion cleanup and cascades. Aggregate product activity is not connected to an account and therefore is not an account record that can be located or deleted for one person; it expires within the 90-day limit. A separately submitted support request may retain the sender’s name, email, message, response status and timestamps, and reference after account deletion, while an administrator audit log may retain the deleted account’s internal identifier and action history. Contact STRATA to request review or deletion of a support record where applicable. Global webhook event identifiers that do not identify the account may remain for security and duplicate-delivery prevention. Paddle, Resend, Render, and other providers may retain transaction, subscription, payment, cancellation, refund, delivery, fraud-prevention, tax, legal, or technical records under their own policies and legal obligations. Account deletion does not cancel a Paddle subscription, delete Paddle’s merchant-of-record records, or create a refund; complete those billing actions before deletion. A subscription bought through Apple never prevents deletion, but deleting your STRATA account does not cancel it either: Apple keeps billing your Apple Account until you cancel it in Settings › Apple Account › Subscriptions on your device or at apps.apple.com/account/subscriptions. Apple keeps its own purchase records under its policies. The same holds for a subscription bought through Google Play: deleting your STRATA account does not cancel it, and Google keeps billing your Google Account until you cancel it in the Play Store under Payments & subscriptions › Subscriptions or at play.google.com/store/account/subscriptions. Google keeps its own purchase records under its policies.

12. Your choices and rights

You decide whether to publish a weekly plan and can unpublish your own shared listing from Plan. Account lets a signed-in member review active-session times, sign out one other session or every other session, and download the account-data JSON described above. The current session is protected from the per-session control; use normal Sign out to end it.

A signed-out person can request a password-reset link from the Forgot Password page; STRATA gives the same response whether or not the supplied address has an account. A signed-in user can request a password-reset email or a separate account-deletion confirmation email from the Account page, and STRATA sends it only to the registered address. In the ordinary self-service flow, deletion occurs only after opening the one-time link and typing the required confirmation; merely opening the email never deletes data. In the STRATA iOS app, a signed-in user can instead delete the account immediately by re-entering the account password and typing the required confirmation; no email is needed. An authorized administrator may exceptionally delete a paused non-owner account through the guarded process described below. You may also request access to, correction of, or deletion of account data by emailing stratafitness.official@gmail.com. We may ask for reasonable proof that you control the account. Additional privacy rights may apply under the laws where you live.

13. Security

STRATA uses salted password hashing, hashed session and one-time-link tokens, HMAC-only verification-code storage, short expiry periods, attempt and resend limits, secure production cookies, parameterized database queries, same-origin write checks, and rate limiting. Verification codes permit at most five incorrect attempts, and resend requests have a 60-second cooldown. Password resets rotate the account’s credential version and revoke all sessions so a login racing with an old password cannot survive.

The private administrator area is limited to one verified, permanently bound account selected by server configuration. It opens only with that owner's normal live account session and current credential version; it does not request a separate password, emailed security code, typed command, or operator-written audit reason. Sensitive account changes retain one explicit review dialog plus trusted-Origin, CSRF, JSON-content, request-rate, action-allowlist, revision, and server-side validation. The server generates a bounded action-specific reason for every administrator audit record. The administrator can send self-service links only to the registered address, revoke sessions, pause or restore an account, manage support requests, and directly delete a paused non-owner account. Direct deletion re-checks Paddle and database blockers, revalidates the live bound-owner session and current credential version at the final write, records the successful deletion atomically, and cannot delete the primary owner. It does not cancel a live Paddle subscription or issue a refund, although stale incomplete checkouts may be closed during safety checks. The administrator cannot view passwords, tokens, or provider credentials. No online service can guarantee absolute security. Use a unique password, secure every signed-in device, never share a verification code or recovery link, and contact us if you suspect unauthorized access.

14. International processing

Service providers may process information in countries other than the country where you live. Their contractual, organizational, and legal safeguards apply to that processing.

15. Children

STRATA is not directed to children who cannot legally consent to account-data processing where they live. A parent or guardian should supervise use by minors and make any purchase.

16. Changes and contact

Updates will be posted here with a revised date. Contact stratafitness.official@gmail.com with questions or requests. See the Terms of Service and Refund Policy for related information.