Privacy

Fastenerhub operates this website. Contact us at [email protected] about privacy or data corrections.

Aggregate usage

On the public site, we collect page-view counts, broad referral categories, searches and supplier-link clicks to understand which reference information is useful. Search analytics retain recognized part identifiers and a limited set of general fastener terms; other search text is grouped as “other query.” Full search text is processed to provide results but is not stored by our analytics.

Our analytics do not use tracking cookies or persistent visitor IDs, and do not store raw IP addresses, full referring URLs or user-agent strings. Random event IDs prevent duplicate counting; they are not visitor identifiers. We honor browser Do Not Track and Global Privacy Control signals for this collection. Analytics are disabled during the private launch rehearsal.

Duplicate-event records are deleted after two days and daily aggregates after 365 days. Backup copies expire on a separate retention schedule of up to eight weeks. Counts measure events, not unique people, orders or sales. Aggregated demand and supplier-specific referral summaries may be shared with suppliers.

Operating the service

Railway hosts the application and data. Better Stack monitors availability and scheduled jobs. These providers process operational information under their own policies. Requests necessarily include network information such as IP addresses; our rate limits keep temporary counters in memory. Hosting and security logs may contain network and request information. We do not intentionally log search request bodies or analytics payloads.

Emailing us shares your address and the content of your message with our support inbox at Gmail. We use that information to respond. Supplier websites have their own privacy practices; following a link leaves Fastenerhub.

Operational access is restricted to the site operator. We do not sell individual visitor profiles or run advertising trackers. Because aggregate analytics do not identify visitors, we generally cannot associate those counts with an individual request.