Beta notice

Privacy — Beta

Updated October 7, 2026

This notice describes how the current Rugby Cleat Finder beta handles data. It applies only to this beta.

What this beta does not ask for

  • No account or login is required.
  • No email address is required.
  • The finder does not request precise location or location permission.
  • No health, injury, or medical information is requested.

Random identifiers and browser storage

  • The finder uses a randomly generated anonymous session UUID, stored in your browser's session storage for the current visit. It is not linked to your name, email, or device.
  • A separate random anonymous browser identifier is stored in your browser's local storage so we can estimate repeat versus unique browser visits across sessions. It is not tied to a name, email, login, precise location, IP-based identity, or device fingerprint. Clearing browser storage, using another browser or device, or private/incognito mode creates a new identifier. Session IDs remain separate and temporary.
  • These random browser and session IDs are pseudonymous identifiers: they let us recognize repeat browser interactions without identifying a person by name. They are not a promise that all service data is fully anonymous.
  • When you tap "See my matches", your finder answers are sent to our server to calculate your recommendations. They are processed in memory and are not stored in the app's validation event table.
  • Recent anonymous product-finder events and feedback may also be kept in your browser's local storage for beta testing.
  • The app's validation events use browser storage rather than analytics cookies; the app does not perform device fingerprinting.

App validation events

The beta sends pseudonymous validation events to our first-party project database so we can measure, in aggregate, whether the finder and guides are useful. Each event record is limited to:

  • the random session and browser UUIDs and the event name (for example, "finder started" or "result viewed");
  • a product ID when the event concerns a specific product, or a guide name when it concerns a guide;
  • minimal interaction or funnel details, such as a step number, result count, outcome type, rank, or whether you marked results helpful.

Event records do not include your exact finder answers, email, name, precise location, health information, or free-text feedback, and we do not store IP addresses in our validation event table. The app does not send these validation events to a separate third-party analytics vendor.

Campaign and referral parameters, such as UTM tags in the link you arrived from and the referring site's domain name, may be recorded with these pseudonymous interaction events so we can understand which acquisition channels work. They are kept for your session in browser session storage alongside the anonymous session UUID; no cookies are used for this.

Hosting analytics and service logs

The app's validation events are separate from hosting and platform analytics. Lovable hosting reports pageviews, referral sources, device categories, and country-level traffic information. Hosting and infrastructure providers also process network requests and service logs to operate the site. This service processing may involve data such as IP addresses; the absence of IP addresses in our validation event table does not mean no provider processes them.

Retailer and manufacturer sites you visit through this app have their own privacy practices. This notice does not cover them — review their policies before you buy.

If this beta changes

This beta may evolve. If new data collection is added — anything beyond what is described above — this notice will be updated before that collection begins.

Contact

For privacy or business questions, email fifty22partnerships@gmail.com. Please do not send medical, health, or injury information.