Privacy Policy
Updated: 10/11/2026 · Version 2.0
Operator and data controller: Nave Dror, an Israeli sole proprietor operating PureFlow and developing Momentum Trainer.
1. Information processed
- Account, email and profile details, including timezone and optional athlete information.
- Personal plans, activities, workout types, RPE, nutrition/fueling and wellness records you enter.
- FIT files and their recorded duration, distance, HR, pace, power, cadence, laps, GPS route and device metadata; manual corrections retain original provenance.
- Pilot links/invitations, assigned run/strength plans, reports, actual dates/measurements, notes, goal/question answers, coach responses, optional screenshots and external links.
- Daily pilot check-in scales, pain location/intensity and optional notes; recorded for the athlete’s local date.
- Computed training volume, load/readiness snapshots, report versions and technical usage/error data.
2. Purposes
To provide plans, calendars, activity import, reporting and comparisons; calculate training summaries; maintain history; secure accounts and answer support requests. Missing measurements are not invented. No advertising-data sale or marketing profiling feature was found in the reviewed application.
3. Coach access, sharing and revocation
A provisioned coach receives scoped access through an accepted, active athlete link: assigned plans, execution reports (including notes, RPE, answers and intentionally attached screenshots) and coach responses. Selecting a FIT activity for a report does not grant access to the athlete’s unrelated activity library or original files.
Submitting a pilot check-in shares its answers and note with active linked coaches. The form explains this before saving and has no private/explicit-share toggle. You may leave it unanswered. This is separate from private personal wellness and nutrition records, which are not opened to coaches.
The coach screen shows today and the recent seven days. Authorization is based on an active athlete link and the check-in’s shared flag, not on its creation after that link: previously shared pilot check-ins may be accessible to a subsequently linked coach. Earlier check-ins saved as private remain excluded unless that entry is later edited and shared. There is no blanket access to prior private check-ins or unrelated health/nutrition history.
Garmin health metrics (sleep duration and score, nightly HRV, resting heart rate, average stress and latest Body Battery) received with Garmin’s HEALTH_EXPORT permission are private by default. Only if the athlete turns on “שיתוף מדדי בריאות עם המאמן” can the currently active linked coach see those summary values for the last 14 days; turning it off or ending the link blocks that access at once. Sleep stages, detailed samples and Garmin account credentials are never shared.
Revoking a link blocks subsequent authorized access to its plans, reports and coach check-ins and prevents further reporting through that link. It does not delete the underlying records, remove a recipient’s saved copies, or instantly invalidate a previously issued short-lived screenshot link (currently 60 seconds). The application includes a link-cancellation control; contact support if you cannot reach it.
4. Storage and access
Training and pilot records use authenticated, scoped access rules. FIT originals and report screenshots use private storage; authorized signed links expire. Imported originals, laps and streams are not replaced by user corrections. Administratively privileged infrastructure operations are separate from ordinary athlete/coach access. HTTPS is used on https://momentum.pureflowisr.com. No system is perfectly secure and no certification is claimed.
5. Verified services and audit limits
Lovable Cloud: managed account authentication, database and private file storage receive account/profile information, personal training and nutrition/wellness records you enter, pilot plans, reports, check-ins and responses, original FIT uploads and report screenshots. Authentication handles credentials and account-email operations. Original FIT parsing runs within the application’s server, not through a Garmin API.
Lovable hosting and Cloudflare delivery/runtime: serve the application and process web requests, including network/request metadata, authenticated requests and server-side training operations. Storage locations, backup expiry and underlying subprocessor retention have not been verified for this project; no Israel-only hosting claim is made.
Lovable visitor analytics and error reporting: platform analytics records visits, page paths, referrers, device and country breakdowns and session metrics. Application error hooks forward error messages, stacks and route/context when available; server errors are logged. This is usage/reliability processing, not training-load calculation. We have not verified field-level redaction or all platform retention/cookie settings.
OpenStreetMap Foundation’s tile service: opening a recorded route map requests map tiles directly from tile.openstreetmap.org. The service receives the browser’s network metadata and requested map area/zoom; the route line is drawn locally rather than uploading the full FIT or route trace to this service. Tile requests can still reveal an approximate viewed location.
Email: account confirmation/recovery is handled by Lovable Cloud authentication. No custom Lovable email domain is configured for this project, and no separate app-email sender was found in the implementation. The underlying delivery vendor and the support mailbox’s provider were not verified. An email to support necessarily gives the operator and mail services your address, message and attachments; never send passwords.
AI: no runtime Gemini, OpenAI, Anthropic or Lovable AI model call was found in the current application code/dependencies or reviewed migrations. Training calculations run as ordinary code, not model prompts. Lovable development AI is used to build/maintain the product; development chat, code and debugging material supplied to that environment are separate from routine athlete processing. This audit does not establish every platform subprocessor or guarantee that diagnostic material can never contain personal data.
Garmin and Strava do not receive an automatic training-data feed from this implementation. Opening an optional external Strava link subjects that visit to Strava’s own policy.
6. Retention, deletion and export
Cancelling/skipping a session changes its status. Undoing a manual activity archives it; these actions are not permanent erasure. Editing or removing RPE changes the current value, while prior report versions, end-question answers, correction provenance and superseded load snapshots may remain in history.
Link revocation is an access change, not deletion. Plans, reports, responses, check-ins, FIT files and attachments are not automatically erased when a link ends. There is no implemented self-service full-account purge or guaranteed immediate removal of audit/version records.
For access, export, correction, link revocation assistance or deletion, email navedror@pureflowisr.com from your account address. The operator must verify ownership and assess the records/files and any retention obligations before confirming what can be removed and a timeframe. No verified automated full-deletion workflow or fixed completion deadline is currently implemented. Ask for written confirmation of completed removal and any retained records, backups or provider logs; their retention periods have not been verified.
A one-click full-account export is not implemented. Support can assess an export request; the service does not promise an already implemented complete machine-readable export.
7. Requests and policy changes
Contact navedror@pureflowisr.com for privacy requests in Hebrew or English. This policy is updated on this page; no automated policy-change email workflow is claimed. The service is not intended for children under 16. This is an implementation-based notice, not a claim of legal review.
8. Proposed Garmin access
Official Garmin integration is pending and is not live. Activity and Training APIs are proposed only. There is no current Garmin Connect login, automatic synchronization or live Garmin API connection. Manual entries and user-uploaded FIT files are the current inputs. Use of the FIT SDK does not imply a Garmin partnership, endorsement or certification.
Any future integration requires a separate authorization flow and updated disclosures. No implemented Garmin disconnect or Garmin-data deletion control is promised today.