What FilterFound collects
FilterFound does not currently offer user accounts or on-site checkout. When analytics is enabled, the site loads Cloudflare Web Analytics to understand aggregate site usage.
Searches and merchant clicks
A search is processed to resolve the identifier you enter. If you open a merchant option, FilterFound records a server-side outbound event containing a random event ID, timestamp, the search context, canonical filter part number, offer ID, merchant, offer type, and the verified result state.
FilterFound's outbound event object intentionally does not add request headers, IP addresses, or user-agent strings. Hosting, analytics, and destination merchants may independently process standard request or device information under their own services and policies.
Landing-to-resolver measurement
When you use the “Open the fit resolver” control on a controlled filter page, FilterFound records a bounded server-side transition event containing a random event ID, timestamp, the controlled landing path, the canonical filter part number, and the resolver destination path.
This landing-to-resolver event does not add IP addresses, user-agent strings, referrers, cookies, free-text input, or user identifiers to the stored event.
Suspected compatibility errors
If you use the report-error control on a technical result, FilterFound stores a random report ID, timestamp, the search context, the canonical entity ID when one exists, the current result state/reason, and the error category you selected.
The report form does not ask for or store an email address, account identifier, free-text message, IP address, or user-agent string. A report is review input only and cannot automatically create, change, or invalidate compatibility truth.
Affiliate links
FilterFound may earn a commission from qualifying purchases when an affiliate merchant link is active. Amazon Associates links, when enabled, go directly to Amazon and include the assigned FilterFound tracking tag. When you click one, FilterFound may send a bounded same-site outbound event in parallel; the link itself is not redirected through FilterFound. FilterFound does not receive Amazon checkout, payment, or customer-account data.
Affiliate status never changes compatibility results, evidence, merchant ordering, or whether a filter page is eligible for publication.
Third-party merchants
Merchant links leave FilterFound. A merchant controls its own checkout, cookies, account data, shipping, payment processing, and privacy practices. Review the destination merchant's policies before providing information there.
How data is used
Analytics, landing-to-resolver events, outbound events, and suspected-error reports are used to measure product usage, diagnose failures, review possible technical errors, and understand whether merchant options are useful. When resolver-outcome measurement is enabled, FilterFound may also record bounded result state, input class, clarification state, canonical identity when already resolved, and offer count. Resolver-outcome telemetry does not store the free-form lookup text, user/session identifiers, IP address, user-agent, referer, or cookies. These measurements cannot create, strengthen, or weaken a compatibility result.
Changes to this policy
This page will be updated when FilterFound materially changes the information it collects or the services it uses.