Privacy notice

The saved bike-to-bike workflow reads the two selected local passports and transfer history. Before a plan, installation record or measured keep/revert save, it compares their current selected payloads inside the existing database transaction. A conflict retains this tab's view and pauses writes for an explicit reload. Final measured coordinates and matching history commit together. Stop and the existing discard action check only the selected journal and do not write passport coordinates. This is an action-time check, not continuous monitoring or physical verification.

The existing device draft separately holds the frozen plan, references, workflow choices and raw unfinished readings in browser storage under its existing 30-day window. It is not in the IndexedDB transaction. A draft-save or cleanup error does not undo a confirmed journal save; a separate manual retry touches only the draft. A draft found changed is retained rather than silently replaced. Reload replaces the unsaved view with saved work and may lose readings that could not be saved. Leaving requests cancellation of a pending transaction, but cannot recall a completed commit. No new storage key, upload, automatic clipboard or recipient is added; other browser or external copies retain their own boundaries.

Settings prepares the complete archive or the separate recovery copy without raw videos only after your choice. Saved database records are read together; inventoried browser keys and unfinished workflow drafts are captured separately for the complete archive only. A fixed-code worker on this site's origin encodes optional videos and builds the JSON file in this browser. Preparation does not upload, send or automatically download the archive, and adds no database records or browser-storage keys.

The prepared file and its inventory stay in this tab's memory. The inventory shows collection counts, exact byte size, timestamps and included or excluded browser state; it does not display or validate every private value. The complete archive can contain identifying fit measurements, reduced pose records, optional raw videos, bike history, metadata, preferences, consent receipts and drafts. The no-video copy excludes every raw video and its playback links, browser keys and drafts, but the remaining records can still identify a person. Neither copy is encrypted or anonymous.

Cancel, discard, reload or leaving stops preparation and removes the prepared copy from the screen. An already queued readonly database read can still finish; late results do not start a download. A separate Download action uses the prepared bytes; a startup failure retains them for manual retry. Download started is not confirmation of file storage or recipient delivery. Copies already started, retained by the browser or OS, or synced from a download folder cannot be recalled by discarding this review. The existing archive schema, local recovery validation and size limits remain; browser preferences, consent receipts and drafts are not restored.

The separate dropper mode keeps a technical receiving frame/configuration and source, an explicit arithmetic reference and 2–4 complete configuration declarations only in page memory: names and exact sources, extended/collapsed state definitions, independent interface/routing questions, three common-axis/endpoint definitions and their declarations, and thirteen raw dimension strings per configuration. An optional, default-off artificial fixed-frame point construction also keeps a named BB point/axis/state definition, its declaration and four independent raw strings per configuration. Turning it off retains hidden editor drafts but excludes those fields from result and review. A collar-to-rail value does not supply a missing BB coordinate.

The whole reviewed TXT includes every active configuration, source/definition, raw field, quantity, scoped reference difference, unknown/withheld reason, contradiction, entered or fictional provenance and UTC preparation date. It excludes local IDs, saved records, rider/contact fields and camera data. Technical free text can identify someone; use part/reference descriptions, not personal or health information. The sheet is not anonymous, a profile, backup, work order, post recommendation, physical measurement, clearance/function or installation approval. It has no bike-database access, persistence, upload, automatic clipboard, sharing or sending. Edits remove results/review; reset, mode change, reload and leaving discard its unsaved memory, not external copies or earlier valid saved-workflow operations already begun. Fixed new-tab references carry no entered values but make ordinary requests; the public mode fragment can remain in browser history/sync. Separate manual TXT download does not confirm storage or delivery. External apps/folders may retain or sync copies that OpenBikeFit cannot recall. Existing rigid-post and one-move workflows remain separate.

The separate fork sheet keeps one technical frame/configuration and exact fork/travel-variant identity, sources, compression axis and extended-reference method, applicable travel and its definition, optional visible-interval datum, 2–6 condition names, load/support/settlement descriptions and methods, classifications, matching-axis declarations, independent fork-length conventions and four raw numerical strings per condition only in page memory. An optional, default-off artificial rigid-rear/equal-support construction also keeps a named initial BB-relative level plane and eight independent geometry strings. Switching that construction off hides its retained editor draft and excludes it from results and review. No missing rear motion or loaded tyre support is inferred.

The complete reviewed TXT includes every active shared reference, condition, raw field, quantity, difference, unknown/withheld reason, entered or fictional provenance and UTC preparation date. It excludes local IDs, saved records, rider/contact fields and camera data. Technical free text can identify someone; use part/reference descriptions, not personal or health information. It is not anonymous, a backup, profile, work order, suspension prescription or verified installation. This workspace has no bike-database access, storage, upload, automatic clipboard, sharing or sending. Edits remove results/review; reset, mode changes, reload and leaving discard its unsaved memory. Fixed new-tab links carry no entered values but make ordinary requests. The fixed public mode fragment can remain in browser history/sync. Separate manual download does not confirm storage or delivery; external apps/folders may retain or sync copies that OpenBikeFit cannot recall. Other geometry and saved-work workflows retain their separate boundaries.

Generic session edits retain their last confirmed wellness-record source in tab memory. The session-only save transaction reads and compares the current saved record before writing. A conflict keeps the latest unsaved working copy in this tab and pauses that copy; it does not merge it or automatically retry. A deliberate read of the exact current saved fit can reopen that version while keeping the rejected copy separately in tab memory. Read failure, a missing identity or an abandoned read does not authorize a replacement. Reopening is not saving the rejected changes. Other independent save, restore and deletion workflows retain their own boundaries; this is not a continuous lock or a repair of older records.

The existing private unsaved-session JSON includes all held session copies, including rejected versions retained after reopening. Several versions may share a fit ID; none is automatically merged or applied. The file may contain personal measurements and recorded session context and is not anonymous. It excludes separate raw-video and pose-landmark files, is readable but non-importable, and is not a complete backup. Downloading does not confirm storage or sending and does not clear the held copies. Reloading or closing the tab can lose those copies; a successful existing local-data clear removes them. No new browser key, upload, automatic clipboard, account sync or recipient transmission is added. Chosen folders or apps may keep or sync outside copies that OpenBikeFit cannot recall.

The separate crank-interface mode keeps 2–4 complete technical configurations: frame/shell/completeBB identity and sources, independently defined widths, exact crank/spindle variant, two journal references, optional shaft-axis/bearing-station declarations, ring family/pattern/chord observation, chainline and whole-system questions, 12 raw numerical strings, three declaration choices and one optional arithmetic reference in page memory. Its reviewed TXT includes every raw declaration, 15 quantities, all differences and unknown/withheld reasons, entered or fictional provenance and UTC preparation time. It excludes local IDs, saved rider/contact/health records and camera data. Technical text can identify someone; use part/source references, not personal or health details. This is not anonymous.

The workspace has no bike-database access, persistence, upload, automatic clipboard, sharing or sending. Edits discard results/review; mode changes, reset, reload and leaving discard unsaved memory, not external copies or an earlier valid saved-workflow operation already begun. Fixed new-tab links carry no entered values but make ordinary requests. The fixed public workspace fragment contains only a mode name, not inputs, and can remain in browser history/sync. Separate manual TXT download does not confirm storage or delivery; apps and folders may retain or sync copies that closing/editing cannot recall. This is a discussion note, not an importable profile, backup, work order, parts choice or compatibility, engagement, spacer/preload, installation, fit, performance or ride approval. Existing crank-length and saved-swap modes remain separate.

The separate mounting sheet keeps 2–4 technical configurations with assembly/source, hub/end/contact-span, retaining-part/diameter-subject/length/thread/head, optional axial-pitch-observation, rotor/brake/bound-source and separate tyre/cassette/clearance references, 13 raw numerical strings, six declaration choices and one optional arithmetic reference only in page memory. Its whole reviewed TXT includes every raw field, quantity, difference, unknown/withheld reason, conflict, entered or fictional provenance and UTC preparation date. It excludes local IDs, saved records, rider/contact/health fields and camera data. Technical free text can identify someone: use part/reference descriptions; the sheet is not anonymous.

This workspace has no bike-database access, persistence, upload, automatic clipboard, sharing or sending. Edits remove old results and review; reset, reload, closing or leaving discard unsaved memory, not outside copies. Fixed disclosed new-tab links carry no entered values but make normal webpage requests. Separate manual TXT download does not confirm storage or delivery; browser, operating-system, apps and folders may retain or sync copies, which closing or editing cannot recall. It is a discussion note, not an importable profile, backup, work order, verified measurement, part choice or compatibility, engagement, installation, braking, handling or fit approval. Existing geometry and tyre workflows remain separate.

The separate headset sheet keeps 2–4 technical names and assembly/source descriptions, upper/lower nominal codes, independent part/source references, ten bearing dimension/contact strings, crown construction and receiving/contact identities, a common-axis/endpoints declaration, condition, interval source, included lower/upper contributions and six axial dimension strings only in page memory. An explicit arithmetic reference defines subtraction, not a preferred assembly. The entire reviewed TXT includes every option, raw field, parsed nominal syntax, complete or withheld span, difference, unresolved question, entered/fictional provenance and UTC preparation time. It excludes local IDs, saved records, rider/contact fields and camera data. Technical text can identify someone: use parts/references, not personal or health information; this is not anonymous.

The sheet adds no bike-database access, persistence, upload, automatic clipboard, sharing or sending; the surrounding existing cockpit reads and optional journal writes remain separate. Edits clear the result/review; reset, mode changes, reload and leaving discard unsaved headset data, not external copies or earlier valid cockpit operations already begun. Fixed new-tab links contain no entered values but make ordinary page requests. Separate deliberate download does not confirm storage or delivery; browser, OS, apps and folders may keep or sync copies. This is a discussion note, not an importable profile, backup, work order, verified measurement, compatibility certificate or installation/cutting/fit verdict.

The separate rear-suspension sheet keeps one technical frame/shock identity, exact source and mount-axis datum, mount family, extended length and usable stroke, an optional named main-frame-fixed coordinate basis, 2–6 condition names, load/support/front-state descriptions and methods, static/marker classifications, matching-reference declarations and four raw observation strings per condition only in page memory. One explicit arithmetic reference defines subtraction, not a preferred load or setting. Its complete reviewed TXT includes every shared reference, condition, raw field, quantity, difference, unknown/withheld reason, entered or fictional provenance and UTC preparation date. It excludes local IDs, saved records, rider/contact fields and camera data. Technical free text can identify someone: use part/reference descriptions, not personal or health details; the sheet is not anonymous.

The sheet adds no bike-database access, persistence, upload, automatic clipboard, sharing or sending; existing cockpit history reads and saved-build actions remain separate. Edits remove results and review. Reset, mode changes, reload and leaving discard unsaved conditions, not external copies or an earlier valid cockpit save already started. Fixed disclosed new-tab links carry no entered values but still request ordinary webpages. A separate manual download does not send to a recipient or confirm storage or delivery; browser, operating-system and folder settings may retain or sync copies. This discussion note is not an importable profile, backup, work order, verified measurement, wheel-path model, sag prescription, compatibility/installation approval or fit verdict.

The separate aero sheet keeps a common BB/frame reference and level/centre-plane method, 2–4 technical configuration names, sources, assembly and support/load/steering descriptions, independent basebar, extension and pad-support references, four pad/grip endpoint definitions and twelve raw coordinate strings, coordinate-basis declarations and separate tube lengths/conventions only in page memory. One explicit arithmetic reference defines subtraction, not a preferred position. The complete reviewed TXT includes every configuration, raw input, derived quantity, difference, unknown/withheld reason, entered or fictional provenance and UTC preparation date. It excludes local IDs, saved records, rider/contact/health fields and camera data. Technical free text can identify a person; use part/reference descriptions and do not treat the sheet as anonymous. The new sheet reads no bike database and adds no persistence, upload, automatic clipboard, sharing or sending. Existing stem comparison and local-journal actions remain separate. Edits remove results and review; leaving this mode, reset, reload or leaving the page discards unsaved aero entries, not external copies or an earlier valid save in another workflow. Fixed disclosed new-tab links contain no entered values but still request ordinary webpages. Manual download does not confirm file storage or delivery; browser, operating-system and folder settings may retain or sync copies. This discussion note is not an importable profile, backup, work order, verified measurement, fit verdict or compatibility/installation approval.

The separate optional A/B sheet keeps two independent technical assembly references, declared dates, support / level / zero descriptions, optional saddle models and open questions, and all 15 fixed quantities per occasion with exact point / side / datum / convention, instrument / method and three raw reading places each, only in page memory. It retains a separate same-protocol declaration. Both whole occasions must be valid before review; missing series and different declarations retain their summaries but can withhold a numerical difference. Matching text and your declaration are not physical matching or accuracy verification.

The complete frozen discussion TXT contains both contexts, all 90 raw places, all 15 quantity statuses, original readings, separate descriptive summaries, any eligible B-minus-A difference and its reason, entered or fictional provenance, questions and limits. Free text can identify someone: use technical references, not rider, contact or health details. The sheet reads no saved-bike database, imports no files and adds no persistence, automatic clipboard, upload, sharing, sending or sensors. Editing either occasion or the declaration removes the entire old review immediately; Close review keeps both drafts. New blank, reload or leaving discards page memory, not external copies or a download already started. Fixed new-tab references contain no entered values but still make ordinary page requests. A failed download retains the exact review for manual retry; started is not a saved file or delivery. Browser, operating system and folder settings can retain or sync copies. This is not a profile, backup, work order, fit verdict, uncertainty estimate, physical-change proof or installation/compatibility approval. The existing single-occasion sheet, single-quantity note and blank paper PDF stay separate.

The optional whole worksheet keeps a technical assembly reference, declared measurement date, support / level / zero conditions, optional saddle model and open questions, plus 15 fixed mechanical quantity slots with exact points, side, datum and conventions, instrument / repeated-placement method and up to three raw readings each, only in page memory. A separate reviewed TXT includes all 15 slots, original entered readings, prepared references, unknowns, descriptive summaries, entered or fictional-example provenance and limits. Free text can identify someone: use technical references, not rider, contact or health details; this is not an anonymous sheet. Blank slots are not zero or targets. The sheet reads no saved-bike database and adds no persistence, upload, automatic clipboard, sharing or sending. Editing any input removes the frozen review. New blank, reload or leaving discard the unsaved sheet, not external copies or a download already started. Fixed disclosed new-tab links contain no entered values and still make ordinary webpage requests. Deliberate download does not confirm a saved file or delivery; browser, operating-system and folder settings can retain or sync copies. This discussion note is not an importable profile, backup, work order, fit verdict, physical verification or installation/compatibility approval. The existing paper PDF and single-quantity A/B note remain separate.

The Tools hub holds your search, workflow, starting-material filter and chosen task preview only in page memory. It does not inspect local bikes, fit recordings or files to infer availability. A task checklist is not confirmation of data or permission. Changing a filter removes the previous preview; reset, reload or leaving clears the launcher choices. Search text may identify you: use parts/tasks, not rider, contact or health information.

Opening a task uses a fixed public page and, for a separate mode, a fixed workspace-name fragment. No entered search, measurements or record IDs are copied into that URL. The fragment is not sent in the HTTP request, but the public mode name may remain in browser history or sync; ordinary page requests still have the hosting metadata described below. This opens the existing workspace, not an automatic calculation, save, import, download, installation or grant of permission. Existing destination processing acknowledgments, camera permissions and local-record controls remain separate.

The separate front geometry workspace keeps 2–4 technical names, source and configuration descriptions, explicit model conditions and length/offset conventions, entered angles, wheel/support radii, fork/steerer/travel dimensions, front/rear centre lengths, independent signed axle Y components and a separately declared wheelbase in page memory. You choose one arithmetic reference, not a preferred bicycle. The complete reviewed TXT includes every option, raw declaration, derived quantity, difference, unknown or contradictory construction, entered or synthetic-example origin and UTC preparation date. It excludes local option/bike/session IDs, saved records, rider/contact fields and camera data. Free text may identify someone; use technical references, not rider, contact or health details, and do not treat the sheet as anonymous. The sheet adds no database access, persistence, upload, automatic clipboard, sharing or sending; the surrounding cockpit studio retains its separate existing local-history reads and saved-build workflow. Edits remove old results and review. Mode changes, reset, reload and leaving discard unsaved fields but cannot recall a valid cockpit save already started or external copies. Fixed disclosed new-tab references carry no entered values and still make normal webpage requests. A separate deliberate download does not confirm storage or delivery; folders and chosen apps may retain or sync copies. This discussion note is not a profile, backup, work order, installation record, fit or handling verdict, compatibility approval or physical verification.

The separate seatpost reference workspace keeps a receiving-system identity and source, shape and nominal bore, insertion limits, and 2–4 option names, sources, post and adapter dimensions, adapter and rail/clamp descriptions, length and one declared insertion in page memory. Its optional rigid model adds named datums, BB-relative receiving coordinates, shaft angle, chosen head-offset convention, a global point vector and an optional separate baseline. A reviewed TXT includes every option, included inputs, arithmetic, unknowns, conflicts, entered or synthetic-example provenance and limitations, but no local IDs, saved records, rider/contact fields or camera data. Technical text may identify someone; use part/reference descriptions, not rider, contact or health details, and do not treat the sheet as anonymous. This workspace adds no bike-database access, persistence, upload or automatic clipboard action; the original one-move assistant retains its separate existing local-record workflow. Edits remove earlier results and review. Mode changes, reset, reload and leaving discard the draft but cannot recall a started valid save in the original workflow or external copies. Fixed disclosed new-tab links carry no entered values but still make ordinary site requests. A separate download does not send to a recipient or confirm storage or delivery; download folders and chosen apps may retain or sync copies. This discussion sheet is not a profile, backup, installation record, work order, compatibility approval or physical verification.

Mateusz Konieczny — Balance IT, ul. Święty Marcin 29 lok. 8, 61-806 Poznań, Poland, NIP 7812090221, REGON 541862820, is the controller for OpenBikeFit product processing and data deliberately sent through the feedback or business-inquiry service. Contact: [email protected].

• Contract and acceptance receipt: notice versions, adult confirmation, locale and timestamps; used to prove and enforce the agreement you requested (GDPR Article 6(1)(b)).
• Local setup records: body and bicycle measurements, setup coordinates, bike profiles, component notes, workflow drafts, journals and preferences; used to calculate and retain the service you requested (Article 6(1)(b)).
• Camera-derived data: reduced MediaPipe landmarks for indices 11–16 and 23–32, timestamps, confidence/quality facts and derived 2D angles. Face and hand landmarks are zeroed immediately; raw video is not retained unless a feature gives you an explicit local-save choice. Purpose and basis: provide the requested local movement comparison (Article 6(1)(b)).
• Feedback: category, message, optional email, page path, submission time and ordinary request/security metadata; used to answer, debug and secure the service (Articles 6(1)(b) and 6(1)(f)).
• Business inquiries: organization, business type, requested work, message, work email, page path, submission time, an allowlisted channel label when the inquiry link contains one, and ordinary request/security metadata; used to assess and answer your request before a possible contract, identify which non-behavioural distribution channel produced the inquiry and protect the endpoint (Articles 6(1)(b) and 6(1)(f)). The channel label is sent only with a submitted inquiry; opening the page creates no page-view event. Sending an inquiry does not create a paid engagement.
• Hosting/security metadata: IP address, requested resource, time, user agent and security signals processed by the host to deliver and protect the site (Article 6(1)(f)).

The product is intentionally not for health concerns and does not request symptoms, diagnoses or injury history. Do not place special-category data, client records, videos or individual fit records in free text, feedback or business inquiries. A one-way local migration removes fields and derived recommendations from the retired symptom-driven workflow.

When you submit feedback or a business inquiry, the open form creates a random attempt identifier. An unchanged manual retry in that same form reuses it; editing the submitted content, closing the form or receiving confirmation ends that attempt. It stays in page memory only, is not sent on page view and is not a visitor-tracking identifier.

The endpoint combines the identifier with the submitted fields to derive a storage key and a reference kept with your message. This helps repeated identical attempts target the same record; it does not guarantee exactly-once delivery. The reference does not grant access to a message. It follows the message retention period of 180 days from its latest stored write; a repeated write after a delayed storage read can restart that period.

The separate bicycle gearing comparator keeps 2–4 technical configurations, every entered tooth inventory, source and component-evidence text, transmission conditions, optional circumference/crank length, independent bounds and one optional reference pair/cadence in page memory. Its reviewed TXT includes every declaration, numerical pairing, unknown, constraint result, provenance and preparation date, but no local IDs, saved-bike/session/camera records or contact fields. Technical text may identify someone; use part/reference descriptions, not rider, contact or health details. This is not an anonymous note, importable profile, backup, work order or verified installation record. The workspace has no bike-database access, automatic copying, save, upload or sending. Edits discard old results/review; reset, reload, closing or leaving discards its unsaved memory. Fixed new-tab links exclude entered values but make normal web requests. A separate download does not confirm file storage or delivery; external apps and folders may retain or sync copies, which Close or editing cannot recall.

The crank shortlist workspace keeps one current crank length, 2–6 option labels and lengths, and optional named saddle-point X/Y coordinates and the declared datum in page memory only. Its separate reviewed TXT includes all those included inputs, both geometry scenarios, entered or synthetic-example provenance and limitations, but no inseam, contact fields, local IDs, saved records, camera data or private notes. Labels can identify someone: use technical part and reference names, not rider, contact or health details; the note is not anonymous. The workspace reads no bike database and does not upload, automatically copy, save or send the note. The surrounding one-pair assistant and saved swap workflow remain separate. Source edits remove earlier results/review; mode changes, reload, closing or leaving discard this workspace. Fixed new-tab reference links carry no entered values but still make ordinary web requests. An explicit download does not confirm file storage or recipient delivery; download folders and external apps may retain or sync copies. Closing or editing cannot recall external copies or a started download. This is a model-only discussion note, not an importable profile, backup, installation record or physical verification.

The control measurement bench keeps two technical assembly descriptions, declared dates and support conditions, eight quantity definitions/methods, every entered independent reading and reviewed A/B copies in page memory. It has no bike-database, upload, download, clipboard or sensor action; the surrounding original controls workflow retains its existing separate local-record actions. Editing one set removes its held copy and comparison but retains the other draft. Reloading, closing or leaving loses the bench. Fixed new-tab guide/worksheet links carry no entered values and keep the original tab's draft; opening a destination is still an ordinary web request. Use technical descriptions, not rider, contact or health details. Matching declarations are not physical verification; this comparison is not an installation record, backup, brake-function test or fit verdict, and it cannot recall external copies you make yourself.

The optional saddle-candidate comparison keeps the current impression readings and posture convention, two or three part names, sizing definitions and references, external widths and named sections, rail declarations, shape descriptions, clamp reference and one explicit inspection choice in page memory only. It does not read a saved bike, create a database record, upload, automatically copy or download a file. Use technical part descriptions rather than rider, contact or health details. Editing removes an earlier comparison or inspection brief; clearing, reloading or leaving removes the draft but cannot recall copies you made yourself. Reference links marked new tab use fixed addresses without entered values; opening one is still an ordinary site request. An inspection brief does not record an installed baseline, compatibility approval, ride outcome or backup.

The frame shortlist bench keeps its declared target/datum, frame names, exact sizes, geometry sources, parts catalog and comparison choices in page memory. Its optional reviewed TXT includes all compared geometry, combinations, model residuals/windows/exclusions, an explicit discussion choice, entered or fictional provenance and preparation date, but no local bike/session/journal IDs or contact form fields. Free-text declarations are included and may identify someone; use technical part names and references, not rider or contact information, and do not treat this note as anonymous. The bench, review and download add no database access, saved record or upload; the surrounding studio retains its existing initial local-history reads and separate explicit saved-build workflow. Source/choice edits, a new blank shortlist, reload or leaving remove the memory-only review, not copies already downloaded or shared. A download does not send to a recipient or confirm delivery; folders and chosen external apps may retain or sync copies outside OpenBikeFit. This model-only discussion note is not an importable profile, backup, work order, physical verification or installation record.

The optional setup-file comparison reads two bike-profile JSON files in this tab without importing, merging or saving profiles. The checked files, selected profiles and review remain in page memory. The separate TXT includes only selected names and disciplines, profile update/export dates, 15 mechanical value rows, named measurement definitions and limitations; it excludes profile IDs, file names, free-text notes, hardware/manual/torque references, other profiles, fits, history, video and recommendations. Names and definitions may identify someone; the note is not anonymous or a restorable backup. Choosing another file or profile removes an earlier result. Reset, reload or leaving clears the in-tab review, not downloaded copies. No automatic clipboard or recipient transmission is performed; browser or download-folder sync may retain external copies.

The optional worksheet reading review keeps the chosen mechanical quantity, point and datum descriptions, instrument/method, conditions, declared dates and entered reading series in page memory. Comparing a second series requires a separate choice and a declaration of the same protocol; the app does not verify physical matching or accuracy. A reviewed TXT contains those included fields, original entered readings, descriptive summaries, the entered or fictional-example label and limitations. Free text may identify someone: do not enter rider, contact or health details, and do not treat the note as anonymous. This tool reads no saved bike and creates no database record. Editing closes an old review; resetting, reloading or leaving clears its draft without recalling downloaded copies. The ordinary explicit download does not send to a recipient, and a download folder may sync outside OpenBikeFit. The note is not an importable profile, backup or verified installation record.

The movement-summary PNG preview stays in memory. Its pixels contain a rounded knee interior angle at maximum extension, knee and analysis confidence bands, the analysis date, a synthetic-demo or camera-derived source label, a reference band and limitations. It excludes contact details, rider inputs, local IDs, free-text notes, raw video, landmarks and adjustment recommendations; it is not an importable backup or a guarantee of anonymity. Preparing and previewing do not upload it. Download and system sharing are separate choices. A chosen app can upload or retain the image, and downloads or app data may sync outside OpenBikeFit. A system hand-off is not confirmation of recipient delivery or publishing. Closing, leaving or changing the analysis removes the preview but cannot recall copies already downloaded or handed off.

The calculator result-link review stays in page memory. Its link contains the current body measurements, preferences and any entered component settings; previous inputs for comparison are included only after a separate choice. Selecting the link does not copy it automatically. A downloaded TXT contains that reviewed measurement link and its boundaries; reviewing or downloading sends nothing to a recipient. Changing the calculation closes the review. The link uses a URL fragment, not query parameters: the fragment is not sent in the HTTP request, but browser history may keep or sync the full link. Closing or leaving cannot remove copied, downloaded or shared links, and download folders may be synced. Opening the link recalculates with the calculator available then, not a frozen report or backup.

The optional business email review keeps the entered business contact fields, message, explicitly attached scope and allowlisted channel in page memory only. It does not submit them or create a reference. Selecting text does not copy it automatically; you use your own copy command. A downloaded TXT contains the reviewed business contact details. Editing the form or attachment closes the review, and leaving the page clears it; copies in your clipboard, download folder or mail app are not cleared by OpenBikeFit. A download folder may have its own sync settings. The mail link contains a fixed recipient and subject, never the draft body or contact fields.

Business-page tool, example, worksheet and contextual privacy links marked “new tab” open separately without adding the entered contact fields, message or email brief to their URLs. The original tab retains its in-memory draft while you keep it open; reloading, closing or leaving that original tab still clears it. These links provide no opener access and omit the referrer, but opening a destination is still an ordinary web request to that site, not a private offline view.

Core records stay in IndexedDB, localStorage or sessionStorage in this browser. The camera and bundled MediaPipe runtime/model execute locally; no runtime or model request is made to jsDelivr or Google. Balance IT does not receive the local database and cannot restore it. URL fragments used for local handoffs are not sent in the HTTP request, although a browser may keep them in local history.

The complete Settings export includes all six IndexedDB stores (sessions, poseSeries, videos, meta, bikeProfiles and bikeJournal), known device keys and workflow drafts. Optional videos are embedded with type and byte size. A separate local recovery copy can include saved database records without raw videos or browser keys and drafts; video playback links are removed from that copy, not from your original records. OpenBikeFit does not upload either file; your chosen download location may have its own sync settings. Delete all data clears and verifies every listed store, known key, draft, OpenBikeFit cache and Service Worker registration.

Cloudflare hosts the public site and optional feedback/business-inquiry endpoint and acts as a processor where it handles data for Balance IT. Its infrastructure may involve international transfers under applicable adequacy decisions or safeguards. The self-hosted MediaPipe code runs in your browser and is not a data recipient. No advertising pixels or behavioural analytics are used. Current vendors and their roles are listed in the governance vendor register.

Local data remains until you delete it, clear site data or a documented workflow expiry removes a temporary draft (normally 30 days). A calculator-to-camera session handoff ends when read or when the tab session ends. The separate calculator-to-bike draft keeps only selected current bike settings and discipline in this tab for up to 30 minutes of usability, even after a reload. It is removed after a successful save, cancellation or starting a different bike form; an expired draft is removed on the next read. Other unsaved bike-form edits are not stored in this draft. The acceptance receipt remains until withdrawal or version invalidation. Optional offline caches remain until you disable offline mode, delete all data or clear site data.

Feedback and business inquiries are scheduled for deletion after 180 days unless needed for a shorter response period or longer to establish, exercise or defend a legal claim. Hosting/security metadata follows the configured processor and security-retention schedule documented in the vendor register; Balance IT operates no separate analytics log.

Choosing the direct email link on the business page opens your own mail app. It does not submit this form to Cloudflare KV or create an OpenBikeFit reference. The 180-day KV period above does not describe copies in email accounts; see Balance IT's privacy policy for business correspondence.

Where applicable, you may request access, rectification, erasure, restriction or portability, and object to processing based on legitimate interests. Email [email protected]; identity verification may be required. For browser-only data, Settings gives you direct access, export and verified deletion because Balance IT cannot identify or retrieve that local copy remotely.

You may complain to the President of the Polish Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl. OpenBikeFit makes no decision with legal or similarly significant effect and does not profile for advertising.

The on-device-processing choice is separate from accepting the terms. You can withdraw the local receipt and delete data in Settings. Withdrawing does not affect processing already carried out. HTTPS, data minimisation, same-origin model assets, restrictive permissions and security headers reduce risk; no internet or local-storage system can promise absolute security.

Material changes receive a new date and, when the acceptance-controlled notice version changes, require a new choice before protected workflows reopen.