Privacy
We store only what a match needs, and delete it on a schedule. There are no accounts, no analytics, no trackers, no ads, and no third-party fonts or scripts.
What we store, and for how long
| What | Why | Deleted |
|---|---|---|
| The work you name (title, author or creator; for hand-entered works, an optional link) | It is the basis of a match | When no request or meeting uses it any more |
| Your request: the work, the city you picked (or "online only"), the meeting format, how far you will travel, the hour it was posted | To find matches | When you close it, or 90 days after posting |
| A hash of your private link | To recognize the link when you return. We cannot turn the hash back into the link. | With the request or meeting |
| Your email address, if you give one | To tell you a match exists. Encrypted. Never shown to anyone. Our emails never include the work's title or anything anyone typed. | When you remove it, close the request, or the request expires |
| Meetings: work, city, date, time zone, format, venue, video link, organizer note | To run the meeting | 30 days after the meeting date |
| Your display name in a meeting | So the people in that meeting can recognize each other | When you leave, or 30 days after the meeting |
| Reports: the meeting, a reason, and optional text. Nothing about who sent it. | To handle abuse | When dismissed, or with the meeting |
| Backups of the database | To recover from failure | Within 12 days (daily backups kept 7 days, inside disk snapshots kept 5 days) |
Times are stored rounded to the hour, and records have random ids, so their order reveals nothing. There are no accounts, so nothing ties your requests to each other, or a display name in one meeting to any other. The database does not record which request a meeting was started from or who joined from which request. But a meeting is stored with the organizer's city and work, so where only one person has asked for a work in a city, someone holding the database could guess that they started it.
What we don't store
- Your name, unless you type it as a display name.
- Your IP address. To limit spam we keep short counters in memory, keyed by a scrambled form of the address (for IPv6, of its network prefix). The scrambling key changes every day and is never written to disk; counters expire within 24 hours. To be exact about the limits of this: while the server is running, its memory holds that key, so someone who seized the running machine could work out which addresses recently posted or joined. The counters are kept separate per work and per meeting so they don't link one person's actions together.
- Logs of the pages you visit.
- Your birth date or any ID.
Who sees what
- Everyone: the open board (works with nobody within 50 km or on video yet, with region and country only, updated about hourly), and the meeting listing (work, city, date, format).
- You, with your private link: your request, how far you said you will travel, and how many people match it. Nobody else sees your travel distance.
- People who join a meeting: its venue, video link, note, and the display names of others who joined.
- The site admin: requests and meetings (never emails), reports, and the audit log of admin actions.
Cookies
One cookie that protects forms from cross-site forgery. It holds a random value and nothing about you. The admin has a second cookie when signed in.
Other services
- When you search for a book, our server asks Open Library. Your browser does not contact them, so they don't see your address.
- Email notices are currently switched off.
- Video links go to whatever service the organizer chose. Their privacy terms apply there.
- City data comes from GeoNames (CC BY 4.0) and is stored on our server.
Requests for data
If anyone, including a government, asks for records, this page describes everything that exists. Most of it is gone within weeks.
Your choices
Close a request, remove your email, or leave a meeting from your private link at any time. That deletes the data right away (and from backups within 12 days).