WeSearch
Hub / Terms
TERMS · OF · USE

Terms of use.

Plain English. The whole agreement fits on one page. We don't want a 60-page document either.

This is the agreement between WeSearch and you, the reader. We've kept it short because long terms documents nobody reads aren't actually agreements; they're cover. If anything here is unclear, send an email to /support and we'll explain.

What WeSearch is

WeSearch is a community news aggregator at wesearch.press. We pull headlines from public RSS and Atom feeds, host a stable summary page per story, and run an anonymous threaded comment layer. We don't republish full articles — we link to the publisher.

Your account (or lack of one)

You don't need an account. The first time you react or comment, your browser generates a random API key and a stable display handle locally. More on the anonymity model. If you optionally enable email recovery, the email is hashed before storage. We never see your real name, address, or phone number.

Your content

What you agree not to do

Comments that cross these lines get hidden. Repeat violations result in time-bound or permanent key bans. Full moderation policy.

What WeSearch agrees not to do

Service availability

WeSearch is provided "as is." We can't guarantee uptime, that the feed is current, or that every comment thread loads. Hosting is one droplet; outages happen. If we go down, we'll work to restore service.

Termination

Either side can end this relationship anytime:

Liability

We're a small project. We try to be careful. If something goes wrong (bug, breach, content dispute), our liability is capped at what you've donated, which is often $0. WeSearch isn't responsible for the content of articles we link to — that's the publisher's responsibility. We aren't responsible for comments other readers post — those are theirs. We are responsible for our own moderation decisions and the platform's behavior.

Disputes

If you have a complaint, email /support first. We try to resolve issues directly. If that doesn't work, the governing law is the jurisdiction where WeSearch's operator resides, currently the United States.

Changes

If we change these terms, we post a dated changelog at the bottom of this page. Continued use after a change means you accept the new terms. If a change is meaningful (anything beyond typo fixes or clarifying language), we surface a banner on the homepage for at least 30 days.

Contact

Email /support. One human reads it. Replies usually within a working day.

Why this is one page instead of forty

Most major platforms publish 40-100 page terms documents covering every conceivable scenario. Those documents serve a different purpose than this one — they're written by lawyers for lawyers, designed to give the platform maximum flexibility in litigation, and the operative assumption is that no user will read them. The result is that "I have read and agree to the terms" becomes a legal fiction that protects only the platform.

This page is the opposite. It's short enough to read in five minutes. The commitments are concrete and few. If you actually disagree with anything here, you can decide not to use WeSearch — there's no per-feature unlock that makes more terms apply. The trade-off: this page can't anticipate every weird edge case, and we'll have to handle some by writing back when something specific comes up. We accept that trade.

What's not here that you might expect

Bottom line

Frequently asked

Are these terms legally binding?

Yes — they're a real agreement. The brevity is a stylistic choice, not a legal weakness. If a court had to interpret them, "the parties' actual practice" would matter as much as the wording.

What happens to my comments if I leave?

If you reset your key, future activity is unlinked from past. If you request full deletion, comments are removed within 7 days.

Is there a refund policy for donations?

Donations are gifts, not purchases — there's no product to refund. If you feel a donation was made in error, email support and we'll work it out case by case.

What if WeSearch shuts down?

We'd post a 30-day notice and give readers time to export their bookmarks (the bookmark API supports JSON export).