Privacy
Your data.
Your decisions.
How the current Stride build handles your information.
Policy identifier 2026-09-09 · Effective 8 September 2026 · Handling and navigation clarified 25 September 2026 · Operated by Afek Banyas. For support or privacy requests, contact afek10@gmail.com.
What Stride uses
Account and profile. Your email is used for sign-in. You can add a first name, optional age and maximum heart rate, a women’s or men’s fitness reference group, sleep target, wake time and time zone to personalize your experience.
Connected health records. With your permission, Stride reads sleep sessions and stages; heart rate, available timestamped and nightly heart-rate variability, and resting heart rate; breathing rate, oxygen saturation, temperature variation and available fitness estimates; steps, active energy and recorded exercise. Google Health can also provide total energy burned. Apple Health can also provide resting (basal) energy; where both Apple energy components are available, Stride can show their total. Availability varies by device and permissions.
Stride requests read-only access to three Google Health categories: activity and fitness, sleep, and health metrics and measurements. It does not connect directly to your Fitbit over Bluetooth or write changes to your original Google Health records.
Information you add. Submitted Journal ratings, optional habits and notes, and planned sessions, are saved to your account. Unanswered journal questions remain unanswered. Unsubmitted Journal edits are drafts on your current device; they are not saved Journal entries or inputs to your account's Journal associations.
Why it is used
Your records support the visible features in the app: sleep views, personal recovery estimates, recorded-activity load, physiological stress estimates, health signals, cardio fitness age, trends, journal associations and planning. Connection metadata and request limits help manage imports, prevent duplicate syncs and protect account access.
Stride's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide or improve the user-facing features described in this policy. Use of information received from the Google Health API will adhere to the Google Health API Developer and User Data Policy, including its Limited Use requirements. This statement is a commitment to those restrictions, not a claim of Google verification or approval.
Apple Health data on your device
In iOS builds supporting Apple Health, you can separately authorize read-only HealthKit access for sleep sessions and stages, heart rate, HRV (SDNN), resting heart rate, respiratory rate, blood oxygen, sleeping wrist temperature, VO₂ max, steps, active and resting (basal) energy, and workouts. These may come from Apple Watch or other apps and accessories that write supported records into Apple Health. Stride reads up to 60 days, including source and device metadata needed to identify readings and avoid duplicates. It does not request clinical records or write, modify or delete HealthKit records.
Stride uses these readings for its visible wellness features and computes estimates on supported iPhone and iPad devices. The imported readings remain in the current app session's memory and are re-read from Apple's protected HealthKit store after reopening. Stride does not upload these readings or their calculated scores unless you explicitly enable Stride AI sharing for your connected health sources. That choice permits relevant summaries and derived scores to be sent through Supabase to Fireworks AI and included in cloud chat and memory, as described below. Apple readings are never sent to RevenueCat, Resend, Google, website hosts or advertising services. Stride does not create its own persistent HealthKit-record cache or iCloud backup. Apple controls storage and any synchronization of the original Health database under your Apple settings. The selected-source preference is saved locally for your Stride account. Profile details, journal entries and plans that you enter in Stride continue to use the account services described elsewhere in this policy.
You choose individual read permissions in Apple's permission sheet and can change them in the Health app. Apple does not reveal whether a missing type was denied or has no records. Disconnect Apple Health, sign-out and successful account deletion remove the imported session view from Stride without altering the original Health records. Disconnecting Stride does not revoke iOS permissions; use the Health app to do that. A later connection requires Stride's disclosure again.
A user-requested export may include the Apple readings currently available in the app session. If you choose to share the exported file, your chosen recipient receives it. Stride does not sell, rent or use Apple Health data for advertising, marketing, data brokerage, insurance or credit decisions, or train generalized AI models with it. Health records are not included in application diagnostic logs.
Free access, subscriptions and consent records
Your access tier. We record adoption of the Free/PRO access policy with your account identifier and acceptance time. This keeps sleep, activity and health signals available without a purchase and determines which additional app features require verified PRO access. Free access uses health data only for the features described in this policy. Where your account has Google Health connection access, Free imports cover permitted sleep, movement and health-signal records; calorie/energy and VO₂ max imports require verified PRO access. Records previously imported while PRO was active can remain stored under the retention rules below, but paid results stay locked on Free. Locked-screen illustrations use decorative example graphics, not hidden personal health results. We do not use health values to target upgrade prompts.
Google Health access requests. When an access request is required, Stride checks your verified PRO membership before accepting it. A subscription does not itself grant connection access or guarantee approval. We store your account identifier, request and decision times, status and account access permission. Supabase and Resend process the request notification and decision email. The operator receives your account email, display name when available, account identifier, account creation time, verified membership status and request details to review the request. These messages do not include health readings, Google credentials or payment details. Access records remain while your account is active and are removed from the active database with account deletion. Queued account-linked messages are also removed; limited delivery records may remain for up to 90 days. Delivered email copies follow the email providers’ retention and deletion processes; contact us for help with a data request. Access permission does not grant PRO features, replace Google consent or guarantee source availability.
Apple processes payments. Stride does not receive your complete payment card or bank account details. Apple handles purchase confirmation, renewals, payment recovery and refund decisions under its own terms and privacy policy.
RevenueCat verifies membership. We use RevenueCat to associate App Store purchase and subscription information with your random Stride account identifier. This includes product and transaction identifiers, purchase and expiry dates, store and sandbox status, trial eligibility, renewal status and billing or refund events. Its SDK can also process technical information such as app and SDK version, device platform and IP address to operate the service. We do not send your Google Health records, Google credentials, journal, wellness scores, name or email to RevenueCat. We do not enable advertising attribution or send advertising identifiers.
Supabase stores access and consent. The backend stores the verified membership status, relevant expiry and verification times, and the versions of the Terms and Privacy Policy you accepted with the acceptance time. Limited subscription event records support reliable processing, reconciliation and abuse prevention. Processed event identifiers, types and times are retained for up to 90 days after processing. Events that need retry or investigation remain queued until resolved; account deletion removes their link to your Stride account. They contain no health records, email address, receipts or payment-card details. Subscription decisions do not rely on the app claiming that a payment succeeded.
Account deletion requests removal of the associated RevenueCat customer record as well as Stride's active account records. Apple retains its own transaction records under its policies; deleting Stride does not cancel an Apple subscription or delete those records. Providers may retain limited records where necessary to comply with law, resolve disputes or protect their services. You can contact us about retained information or your data rights. See RevenueCat's Privacy Policy and Stride's subscription terms.
Optional Stride AI
AI addendum ai-2026-09-19-v2, dated 19 September 2026. Stride AI is an optional wellness chat for supported PRO and trial accounts. After you accept the Terms and Privacy Policy, the app presents a separate optional AI setup. It explains what is shared and offers two clear choices: Enable Stride AI or Continue without AI. No AI permission is selected or granted in advance. Existing users review the AI disclosure before first use or when that disclosure changes. Accepting the general documents alone does not authorize AI sharing. The disclosure explains the information, external AI processing in the United States and retention immediately before your affirmative choice, with a direct link to the provider and data details. One AI sharing choice covers both Google Health and Apple Health, where connected and permitted. Declining leaves your other Stride features available.
What is processed. When you enable AI, your messages, relevant recent conversation and memory, and the account information needed to answer your question are processed. This can include profile preferences, saved journal and plans, permitted Google Health measurements and Apple Health summaries, source and date information, and calculated wellness scores. Health context can include sleep, activity, heart-rate measures and other health signals available in Stride. A request can fetch or refresh a limited range of authorized source records. The assistant has read-only access: it cannot edit your health records, journal or plans. It does not receive sign-in codes, Google credentials, payment details or other users' records. Do not put another person's private information in a message.
Who receives it. Supabase processes the request and stores your AI history and preferences in Stride's account database in Frankfurt, Germany. After your separate AI consent, the minimum relevant conversation and health context is sent directly to Fireworks AI to generate a response with GLM-5.3-Flash using its United States inference route. This involves an international transfer to the United States. Stride does not route these requests through OpenRouter or automatically substitute another inference provider. Health-source permissions and AI sharing consent are enforced separately; connecting a health source alone does not authorize AI sharing.
Stride uses the provider's non-persistent inference configuration and does not opt in to content logging, model training or optimization programs. Fireworks describes prompt and response processing in volatile memory, which may include short-lived prompt caching, and retention of operational metadata such as token counts. This is distinct from the history stored by Stride. We do not promise that all service metadata is immediately erased. See Fireworks data handling.
One AI choice, separate source permissions. Enabling Stride AI after the current disclosure authorizes relevant information from both Google Health and Apple Health for the same wellness-chat purpose. It does not connect either source or grant additional access to its records. Google authorization and Apple HealthKit read permissions remain separate and control which records Stride can access. For Apple Health, permitted readings are read on your device; only relevant summaries and derived scores are sent through Supabase to Fireworks for your request. Shared context can appear in cloud chat history and memory under the retention below. Without AI consent, Apple readings and their calculated scores remain in the local session view. An earlier AI consent does not automatically become consent to this combined scope; the new disclosure requires a new affirmative choice. Withdrawal stops new AI sharing from both sources.
History and memory. Stride stores AI messages and bounded conversation memory, encrypted with an additional application key, for up to 90 days from the underlying content. Summarizing does not restart that period. Older content is excluded from new responses even while scheduled deletion is pending. Memory is a short, fallible summary, not a complete medical record. You can turn memory off or clear it. Removing a conversation also removes memory derived from it. Deleting source data removes memory derived from that source; already written chat replies remain until the conversation is deleted or expires. Expiration and deletion remove active application records; infrastructure backups and logs follow the provider schedules described elsewhere in this policy.
Controls. In Settings → AI assistant, disable AI, hide its floating icon, inspect limits, manage memory, or delete AI data. Hiding the icon only changes its visibility. Disabling AI or withdrawing sharing permission stops new requests; it cannot retract a request already received by the processor and does not itself delete existing conversations. To remove them, use the conversation or all-AI-data deletion controls. Your account export includes retained AI conversations and memory. Reading, exporting and deleting existing AI records remains available after PRO ends. Account deletion removes AI content, preferences and consent records from the active database.
Usage and abuse prevention. Non-content records of request identifiers, times, status, token counts and reserved or charged cost support limits and billing reconciliation for up to 12 months from use. A keyed, one-way subscription identifier prevents repeated trial allowances and is kept for the same period from its last use. These records contain no messages, health readings or Google tokens. Account deletion removes their account link; the one-way trial marker and non-content accounting records can remain until expiry. Deleting conversations or reinstalling does not reset allowances.
Neither Stride nor its AI processing configuration uses connected health information or derived chat content to train generalized AI models, target advertising, sell data, or make insurance or credit decisions. Human access remains limited to the support, security and legal purposes described in this policy. AI outputs may be inaccurate; see the AI terms and AI controls and help.
How we protect sensitive data
Stride treats Google Health records and Google authorization tokens as sensitive data. The following safeguards protect their confidentiality and help prevent unauthorized access:
- Encryption in transit: The app communicates with the hosted backend over HTTPS/TLS. Server requests to Google's authorization and health APIs also use HTTPS/TLS.
- Encryption at rest: Supabase encrypts the hosted database at rest using AES-256, as described in its security documentation. Stride additionally encrypts Google access and refresh tokens and retained AI conversation content with AES-256-GCM before storing them, using separate application encryption keys. The encryption key is held in server secrets separately from the database.
- Access controls: Database row-level security restricts signed-in users to their own records and requires an active session. Google credentials are kept in a private database schema that app users cannot read. Privileged backend keys and Google tokens are not delivered to the app or included in data exports.
- Protected authorization: Google connections use a one-time, expiring authorization state, PKCE verification and an allowlist of return addresses. The backend checks authenticated sessions and limits sensitive requests to reduce replay and abuse.
- Device and browser storage: Native apps use operating-system secure storage for sessions and cached health records. Browser health records stay in memory; browser sign-in storage is described below.
- Limited application logging: Application error handlers log error codes and status rather than health records, authorization codes or tokens. Infrastructure providers may retain request and security logs under their own retention schedules.
No storage or transmission method can guarantee absolute security. To report a suspected data-security issue, contact afek10@gmail.com; do not include health records, passwords or sign-in codes.
Where it lives
Stride's backend. Supabase provides authentication and the database storing your account, imported Google Health records, journal and plans. Access rules restrict each signed-in account to its own records. Google connection credentials are encrypted on the server and are not stored in the Flutter app.
On your device. Native apps use operating-system secure storage for sign-in sessions, cached account records, pending account edits and unsubmitted Journal drafts. Imported Apple Health readings stay in memory and are excluded from this persistent cache. Browser health records stay in memory, rather than persistent browser storage.
Journal drafts and pending edits. On native devices, Journal edits autosave locally for the current account and date. Ordinary sign-out retains these drafts for that account. Discard draft removes the selected day's draft without changing a saved Journal entry. Submitting a check-in saves it to your account when connected; pending account edits can wait locally for reconnection. Successful account deletion starts cleanup of that account's local drafts and pending edits. Interrupted cleanup of Journal drafts, app-owned temporary exports and account notification data is retried when the app starts. Browser drafts remain in memory for the open app and do not have the same restart persistence as native drafts.
Notifications. To manage optional reminders, Stride keeps your notification preferences and the profile context needed to prepare them on this device. It can read recent available records from your selected source to prepare a reminder; the Apple Health handling above still applies. Signing out cancels notification work and retains your preferences for that account. Local notification bookkeeping includes the account, source, notification category, day and delivery or attempt time; it is separate from a cache of imported health readings. After confirmed account deletion, Stride removes that account’s notification preferences and delivery history from this device; if cleanup cannot finish, it is retried.
Exports. An export contains account records, retained AI conversations and memory, and separately labeled pending changes and local drafts. It can also include Apple Health readings available in the current session when you request it. Stride removes its temporary share file after sharing finishes, is dismissed or fails; interrupted cleanup is retried. A copy that you save to Files or share with another app or person remains under your control and is not removed by Stride account deletion.
Browser sign-in. The current tab's session storage holds your sign-in session. A sign-in verifier is stored separately across tabs with a one-hour validity period, so an email link can open in a new tab. It is removed after a successful exchange; expired entries are removed when read. It contains no health records.
Sign-in messages. Supabase Auth and Resend process your email address and one-time sign-in code to deliver authentication messages from signin@strideapp.health. Health metrics are not included.
This website. This website has no analytics scripts or contact form and does not collect health records. Hosting infrastructure may use cookies for access control or security. Ordinary web requests reach the hosting provider, which may process request information such as an IP address.
The published website is hosted by OpenAI Sites, using Cloudflare infrastructure. Stride's account database region is Frankfurt, Germany.
Your choices and controls
You choose whether to connect Google Health and which requested permissions to grant. The current connection requires all three requested read-only permissions. You can decline without connecting. Designated development previews use fictional records and do not upload those records to your real account.
- Export: Open your profile icon, then Settings → Privacy & your data → Export your data for a portable JSON copy.
- Disconnect: Open Settings → Data sources and choose the disconnect action for the source. Disconnecting Google Health stops new imports while existing Stride history remains. Disconnecting Apple Health clears its imported view in Stride; system permission changes are managed separately in the Health app.
- Delete: In Settings, open your name and email card to reach Profile & account → Delete account. After confirmation, Stride revokes Google access and removes the account and associated app records. See the full steps.
Deleting Stride records does not delete the original records held by Google Health. Signing out or uninstalling the app does not delete your server-side account.
We retain your account records while your account remains active. Successful account deletion removes its records from the active database. Infrastructure logs and backups, where present, follow provider retention schedules and are not necessarily erased immediately. Your original Google Health records are unaffected.
Wellness estimates, with context
Recovery compares nightly heart-rate variability and resting heart rate with your prior history and includes sleep context. Baselines require at least seven prior observations. Confidence and missing data are visible in the app.
Sleep performance uses your chosen target. Observed sleep shortfall does not assume what happened on a missing night. Activity load summarizes recorded exercise; it is not a measure of all-day stress or muscular tissue load.
Cardio fitness age compares the median of available VO₂ max estimates in your selected one-day, seven-day or 30-day window with published, sex-specific treadmill fitness references. The reference-group choice is optional and saved in your profile. This is a population fitness comparison, not a validated measure of biological age, cellular aging, remaining lifespan or an aging rate. Wearable estimates and laboratory measurements differ, and the reference population may not represent you.
Stress tracking. Stride uses timestamped heart rate, available HRV and short step intervals to estimate daytime physiological activation. Recorded sleep, exercise, movement and unstable signals are excluded. The formula uses a personal reference, shows its inputs and confidence, and leaves missing observations empty. A heart-rate-only estimate is labeled when suitable daytime HRV is unavailable. These calculations run in the app. The score is an independent wellness heuristic, not a validated measurement of psychological stress, hormones or anxiety. Breathing pauses are optional and do not guarantee a change in the score.
Journal associations compare reported habits with next-day recovery and show uncertainty. An association does not prove causation.
Stride is intended for adults and general wellness. It is not a medical device, does not diagnose conditions and does not replace professional care.
Contact and policy updates
For a privacy question or a request concerning your records, contact afek10@gmail.com.
Any material change to how connected health data is used will need an updated notice and, where required, renewed consent before that use begins.
Stride is independent of Apple, Google and Fitbit. Those names describe intended compatibility, not sponsorship or endorsement.