Privacy

Plain disclosures for a simple site

What we collect

The site processes operational request logs and a separate first-party counter for reviewed public pages. That counter removes query strings and fragments, keeps only the referring origin, and does not read forms, cookies or case content. Optional Google analytics is controlled separately by your choice below every page.

Google analytics tags

Configured Google Analytics and Tag Manager load only after you choose Accept analytics, on reviewed public reading pages without query strings or private fragments. A document carrying an external or private inbound referrer is excluded too, so configured tags cannot read that URL. They stay off on forms, sponsor/payment pages, admin and unknown routes, and when Do Not Track is enabled. Accept and Reject are equally available. Your accepted or rejected preference is saved in this browser’s local storage; if storage is unavailable, analytics stays off. Use Withdraw analytics below any page to stop Google tags and remove accessible first-party Google analytics cookies; the page reloads to discard code already loaded. Withdrawing cannot erase data already sent to Google or cookies on Google’s own domains. Opening a private route after accepting also starts a new document without Google tags. Google receives the public page origin and path; configured tags must respect this limited analytics purpose.

Submissions

When you submit a website, we store the site details you provide and the optional submitter email. Submissions are reviewed before approval.

Contact requests

When you use the contact form, we store the topic, your name, your email, an optional website URL, and the message so the team can review and respond to the request.

Admin accounts

Admin sign-in uses Supabase Auth. Admin access is limited to emails on the allowlist.

Sponsor payments

Sponsor review requests are stored in our contact inbox. Public sponsor checkout is unavailable. Stripe may retain historical payment details, billing information, receipts, fraud checks, and related payment records. The Useful Web does not store card numbers.

Advertising conventions

Sponsors and ads are intended to be clearly labeled. If display ads or ad networks are enabled later, those partners may use cookies, web beacons, or similar technologies for measurement, fraud prevention, and ad delivery.

Third-party links

The randomizer sends visitors to external websites. Those sites have their own privacy practices, terms, and tracking systems.

Directory records

The Useful Web may store listing titles, URLs, categories, descriptions, sponsor status, review notes, screenshots, and editorial decisions needed to operate the directory.

Retention

Submission, sponsor, analytics, and support records should be retained only as long as needed for directory operations, accounting, fraud prevention, dispute review, legal compliance, and security.

No sale of personal data

The site should not sell submitter or visitor personal data. If ad networks, remarketing, or additional analytics tools are enabled later, this page should be updated before launch.

Questions: partnerships@theusefulweb.app

Optional analytics

Allow Google Analytics and Tag Manager on public reading pages? They stay off until you accept. Forms, payments and private pages are excluded. Do Not Track keeps them off.

Read our privacy notice

Google analytics is off until your preference is checked.