Privacy Policy
Last updated: July 28, 2026
Summary
Live Video Feedback (“LVF”) uses your phone as a camera and your computer as a large live monitor. Recordings, filenames, exercise names, and the local library stay on your computer. LVF does not upload that content to LVF cloud storage.
Online services are still used for the initial phone connection, access verification, app updates, optional analytics and diagnostics, and this website. This policy explains those boundaries.
Founding-pilot requests
When you request pilot access, we collect the information you submit: name, email address, participant or physiotherapist role, optional practitioner or clinic, optional referral code, device eligibility confirmations, pilot-commitment confirmation, and permission to contact you.
Do not submit diagnoses, injury details, medical history, exercise names, or other health information. We do not need that information to review a request.
We use request data only to acknowledge receipt, assess pilot fit, manage approval and access, provide support, and evaluate the pilot. An accepted request triggers one transactional receipt email. If access is later approved and provisioned, a separate operator-authorized email delivers the private macOS installer and Access Key. Duplicate requests receive the same generic browser confirmation, are not added again, and do not trigger another receipt email.
What stays on your computer
- Recordings and original video files
- Exercise names and local app settings
- Trimmed and exported clips
- The local recording library
You control any files you export or upload to a practitioner’s existing sharing channel. That sharing channel has its own privacy practices.
Phone camera and connection signaling
After you scan the QR code shown by the Mac app, the phone page asks for camera permission. The browser sends the camera stream to the desktop app over an encrypted WebRTC connection. LVF’s server coordinates the initial signaling messages but does not store the video stream.
Network services involved in establishing the connection can see technical connection data such as IP addresses, browser details, connection codes, and timestamps. Signaling codes are short-lived and must not be treated as permanent secrets.
Access verification
Founding-pilot and existing paid access are verified through Polar. Activation sends the access key and a device label to Polar. LVF stores only the provider record identifiers needed to reconcile an approved pilot request; it never stores an access key in the pilot-request database.
People who purchased LVF before the founding pilot keep their existing paid-license rights. Polar may retain the customer and transaction records required for those purchases.
Optional analytics and diagnostics
LVF uses PostHog to understand whether the website and app workflows function reliably. Website analytics require your consent. If you decline, the website sends no analytics events. Desktop telemetry is off by default and can be changed in Settings.
Allowed telemetry describes product steps, broad platform information, timings, and sanitized technical failures. It must not include recordings, filenames, file paths, exercise names, diagnoses, health details, access keys, signaling codes, raw entitlement credentials, or unnecessary personal information.
Session replay is disabled. Autocapture is disabled on the website; named events are used instead. We do not use analytics for advertising or create marketing profiles.
Operator notifications and support
When enabled, a new-request notification is sent to the LVF operator through Pushover. It contains only an opaque request reference and the selected role, not your name or email. If you contact support or are admitted to the pilot, we retain the correspondence needed to respond and support access.
Service providers
| Service | Purpose | Data involved |
|---|---|---|
| PostHog | Consent-based analytics and diagnostics | Named product events and sanitized errors |
| Polar | Access verification and legacy payments | Access key, device label, customer and entitlement records |
| Cloudflare | Website security and delivery | IP address and request metadata |
| LVF signaling / Reverb | Phone-to-computer connection setup | Short-lived codes, IP addresses, signaling messages |
| Google STUN | WebRTC network traversal | Device IP addresses; no video content |
| Pushover | Operator notification when enabled | Opaque request reference and role |
| Resend | Transactional request, access, support, and legacy purchase email | Email address, approved transactional message content, and delivery metadata |
Cookies and local storage
The website stores your analytics choice in your browser. If you accept analytics, PostHog may use first-party storage to maintain an anonymous identifier. If you decline, analytics remain off. Essential session and security storage may still be used to submit forms and protect the service.
Retention
- Local app data: remains on your device until you delete it.
- Pilot requests and status history: retained while the request or pilot is active, then scheduled for deletion within 180 days after decline, withdrawal, or pilot completion unless needed to resolve an access or legal issue.
- Analytics: retained for the configured PostHog retention period and deleted or aggregated when no longer needed for pilot decisions.
- Signaling sessions: expire after approximately 15 minutes and are automatically deleted.
- Legacy purchase records: retained by Polar and LVF as required to honor licenses and meet legal obligations.
Your choices and rights
You may decline website analytics, keep desktop telemetry off, revoke camera access in your phone browser, delete local files, withdraw a pending pilot request, or ask what personal information LVF holds about you. You may also request correction or deletion where applicable, subject to records needed to honor an existing license or meet legal obligations.
Adults in the founding pilot
The founding pilot is for adults aged 18 or older. LVF does not knowingly admit children or collect children’s information through the pilot-request form.
Changes and contact
Material changes will be reflected on this page with a new date. For privacy questions or requests, email [email protected].