Short answer
PelvicEx saves profile choices and progress in this browser. You can use it without creating an account, export your local record, clear session history, or delete the local profile and progress record.
Local-only does not mean anonymous, encrypted, medically secure, or impossible for another person using the same device to access. Browser data can also disappear when site data is cleared.
What this page describes
This page explains how PelvicEx stores and handles data when you use the site, including local progress, web requests, and your export and deletion controls.
Data the current application may store
The local PelvicEx record can contain information you enter or create while using the interactive planning experience, including:
- selected goals and optional goal details;
- relevant treatment or personal context answers;
- safety-routing and technique self-check answers;
- your chosen Gentle or Balanced starting preference;
- time-zone and schedule information used to decide when a session is due;
- programme, module, tutorial, and progression state;
- prepared session identifiers and trainer outcomes;
- post-session feedback, including difficulty, release quality, unwanted responses, and selected symptom trends;
- review and maintenance choices;
- technical schema and content-version numbers needed to validate or migrate the record.
Some of these fields concern pelvic, urinary, bowel, sexual, pregnancy, postpartum, surgery, cancer-treatment, or neurological context. Treat them as sensitive even when they do not contain a name or email address.
The current profile does not ask for your legal name, email address, postal address, telephone number, date of birth, payment card, government identifier, or clinical record number.
Where the data is stored
The application uses the browser’s localStorage under a PelvicEx-specific key. The record is versioned and validated before the application uses it. If storage is unavailable, the application can switch to temporary in-memory mode and should display that changes are not being saved.
The current static application does not send the local profile or progress record to a PelvicEx application server. It also does not include code that signs you into an account or synchronizes progress across devices.
When you visit PelvicEx, the hosting or network infrastructure may receive ordinary request information such as an IP address, requested page, time, and browser headers. Keeping your progress in the browser does not prevent these web requests or hosting-layer logs.
Following a link to an external source also takes you to another organization’s website. That site applies its own privacy policy and may receive ordinary request information.
What PelvicEx must not do with sensitive answers
PelvicEx keeps goals, symptoms, treatment context, calibration values, and workout history out of:
- page URLs or query strings;
- server-rendered HTML;
- advertising requests or audience segments;
- analytics events;
- third-party tracking payloads;
- public logs or social-sharing metadata.
The application’s planning logic receives local structured data, but that does not authorize reuse for marketing or health-based ad targeting.
Optional usage counts
If you allow optional usage counts, PelvicEx sends only an event type, the site language and a broad page category. The events are page views, trainer starts, session completions, return visits and guide-to-trainer clicks. Page categories are home, guide, library, trainer or other. The payload contains no page URL, referrer, cookies, visitor identifier, profile, goals, symptoms or workout history. A completion count contains no exercise details or feedback.
The collector stores daily totals for up to 90 days, rather than individual event records. Your choice is remembered in this browser for up to 365 days. A locally saved UTC visit day helps count a return within 90 days; it is not a visitor identifier.
You can change your choice in the usage-count controls at the bottom of the page. Declining keeps optional counts off and clears the local visit-day marker. This choice is separate from advertising consent. Deleting local progress does not remove previously aggregated counts: those totals contain no identifier that lets us link them back to your record.
Deleting the local profile and progress record does not reset this usage-count choice; use the footer controls to change it.
Export, clear, and delete controls
The current application provides three different actions:
Export
Export downloads a JSON copy of the current local PelvicEx record to your device. That file may contain sensitive answers. You become responsible for where it is saved, copied, emailed, backed up, or shared.
An export is not automatically sent to a clinician, and PelvicEx does not monitor or interpret exported files.
Clear history
Clear history removes applied detailed session history and month-level summaries while preserving unresolved feedback by default. It is intended to remove workout history without necessarily resetting the entire profile and current plan.
Delete all local data
Delete all removes the PelvicEx application record from this browser and resets the local experience. If storage itself is unavailable, the application can only clear its temporary in-memory copy and should say so.
Browser backups, device backups, manually exported files, screenshots, or copies created outside PelvicEx are not deleted by the website’s local delete action.
Retention and compaction
The current code keeps a bounded set of the newest detailed applied-session records. Its default cap is 365 records, a privacy and product choice—not a clinical threshold. Older eligible records can be compacted into month-level counts and outcome-trend summaries. Pending responses and records with unusable timestamps are retained rather than placed into an invented month.
Compaction reduces detail but does not make the summary anonymous. It remains part of the local PelvicEx record until you clear or delete it.
Limits of browser storage
Browser storage is convenient, but it has practical security and reliability limits:
- another person using the same unlocked device and browser profile may open PelvicEx;
- browser extensions or malicious code with inappropriate access could create risk;
- clearing cookies and site data may also remove local progress;
- private-browsing sessions may discard storage;
- browser or device failure can cause loss;
- storage quotas, corruption, or an incompatible future record can interrupt persistence;
localStorageis not a medical-record system and PelvicEx does not claim end-to-end encryption.
Use device authentication, a separate browser profile, and other operating-system controls when sharing a device. Do not enter information you are not comfortable storing in that browser.
Advertising and local data
Your goals, symptoms, context answers, calibration, and workout history are not used for ad targeting.
Read the PelvicEx advertising policy for the editorial and placement rules.
Privacy is separate from medical suitability
Keeping data on a device does not make a programme clinically appropriate. A local algorithm still cannot examine the pelvic floor, diagnose symptoms, or replace a clinician. Conversely, seeking clinical care may require sharing relevant information directly with a qualified professional.
Use the medical disclaimer and product limitations to understand that boundary.
Source
- Bø K, Berghmans B, Mørkved S, Van Kampen M, editors. Evidence-Based Physical Therapy for the Pelvic Floor. 3rd edition. Elsevier; 2023. Chapter 17 discusses pelvic-floor apps, access, adherence, and limitations. Official publisher record.