Cookie policy and privacy choices

How we use cookies

Cookies are small values stored by your browser. FencerLens uses essential cookies to protect sign-in, prevent forged requests, support time-limited private previews, and remember your privacy choice.

Cookies used by FencerLens

Optional product analytics

Product analytics is off by default. If you allow it, Google Analytics receives public-page views, selected navigation clicks, a successful-trial-submission event, other engagement information, browser and device information, and cookie identifiers. The browser connects to Google, which processes network information to provide the service. We send canonical page URLs without query strings or fragments and only the origin of referring websites. We do not send account identities, form contents, private reports or videos. Analytics is not loaded in signed-in workspaces, sign-in or invitation pages, or community posts. Advertising features are disabled. Withdrawing permission stops collection and removes our Google Analytics cookies from this browser; it does not erase data already processed by Google.

Sign-in and account-access security records

We also record rate-limited observations when a valid signed-in session successfully opens a private athlete, administrator or account-security page. These are visits, not new sign-ins or proof that the account owner is online. The same account, network and reported device is sampled at most once every 15 minutes, with at most 20 samples per account in that period. We do not store page URLs, query strings, referrers or browsing trails, or record public browsing, background APIs, video chunks or prefetch requests in this feature. Existing sessions do not need to sign out first; only new observations are recorded.

For account protection and abuse investigation, FencerLens records the account involved (where recognized), sign-in time, result, network IP address when available, approximate country and first-level region supplied by Cloudflare for that IP, and a coarse device, operating-system and browser summary. IP location can be inaccurate or changed by a VPN; it is not nationality, a home address or the country entered on a trial application. We do not collect city, street, postal code or coordinates in this log. Failed attempts do not establish who made them. We do not store the submitted email for unrecognized accounts. Device information is browser-reported and may be incomplete or inaccurate.

These records are stored privately in Cloudflare D1, our infrastructure provider. Administrators see masked IPs by default; revealing a full IP requires administrator authorization and creates a separate access-audit event. Signed-in users can see only their own recent successful sign-ins and visits with masked IPs. We do not send these addresses to external IP-lookup services, use them for advertising, or collect passwords, session tokens, precise GPS or additional device fingerprints in this log.

IP, approximate location and device records for both sign-ins and visits are available for 30 days. Expired records are excluded from all history and IP-reveal requests, and an hourly cleanup removes them from the application database and deletes expired sessions. The separate operational audit retains account/time/action records without copying full IPs or location. Cloudflare infrastructure logs and recovery copies have their own retention; application deletion does not imply instant removal from those copies. Contact info@fencerlens.ai with access or privacy questions. Necessary security logging is separate from optional analytics preferences.

AI-assisted video analysis

Uploaded bout videos and analysis reports are linked to the athlete account. Other athletes cannot access them through their accounts. Authorized FencerLens administrators can access this material for processing and review. Uploading does not publish videos or reports to the public website or community; reviewed reports are delivered to the athlete account. For privacy or access questions, contact info@fencerlens.ai.

With your AI-processing permission, FencerLens may send selected evidence frames and bout context to OpenAI to generate an analysis draft. This involves third-party processing. Drafts require human review before publication to your account. The upload form provides a separate choice for this permission.

Trial request forms

Trial requests are stored in the private FencerLens administration database. The FencerLens Cloudflare Worker may also send a server-side notification through Cloudflare Email Service to the designated administrator inbox.

Account invitation emails

When an administrator approves account access, FencerLens uses Resend as a server-side transactional email provider to deliver the one-time setup link from info@fencerlens.ai. Resend processes the recipient email, display name, language, and invitation message for delivery. This is used only for necessary account access, not marketing or browser tracking.

After an athlete completes a video upload, Resend also sends an operational notification to the designated administrator mailbox. It includes the athlete label, filename, upload time, review target time and a task link that requires administrator sign-in. It does not include the video, analysis questions, sign-in credentials or a public media link. The notification is used to arrange analysis, not for marketing.

Community posts and images

Community posts, replies, moderation status, and reports are stored in the FencerLens administration database. Optional listing images are stored in private FencerLens object storage and are served publicly only while an approved post is published or closed. Members should not include phone numbers, home addresses, payment details, or other sensitive personal information in public content.

Change your choice

Open Cookie settings at any time from the footer. You can also clear site data in your browser; FencerLens will ask for your choice again on the next visit.

Contact

Questions about these choices can be sent to info@fencerlens.ai.