🐾 ForagePlan a trip

Your data

Forage knows things most apps don't — who you travel with, who's single, what you're into, when you'll be away. That deserves plain words, not a wall of legal text.

What Forage keeps

Who can see it

Reading chats to improve Forage

Forage is young, and the fastest way to improve it is to see where a real conversation went wrong. That means reading actual chats — different from counting them — so it's your call.

Taking it and deleting it

Where it lives

On a server the steward runs in Europe — not a third-party analytics platform. Conversations are processed by Anthropic's API to write the replies. Event data comes from the Bearings commons; nothing about you goes back to it.

What we count

How busy each page is, by day. That's a number per page per day and nothing else — no visitor identity, no IP address, no browser, no order of pages, so the count can't be turned back into one person's visit. It tells us which parts of Forage are worth building on. Your own account keeps a separate list of sign-ins and keys, which only you can see. One exception, only at the very start: when you first join, Forage records the order of your first dozen steps — purely so the steward can see where new members get stuck setting up. It's tied to your account, visible to the steward alone, and stops after those first steps.

Somewhere risky

In countries where being gay is criminalised, Forage never records or shows an event's location more precisely than the country, and never attaches anyone's identity to it. If that's your situation and you'd rather Forage held less, say so — the desks will work with whatever you're comfortable sharing.

Not built yet

Honest roadmap: your data lives on Forage's server because that's the only option built. Keeping your data somewhere you choose is wanted, not done. This page will change when that does.

Questions, or want something removed by hand? How Forage is funded and run.