Last changed 2026-10-10. Written in English and translated for convenience; where a translation and the English differ, the English applies.
We keep what a booking needs and nothing for its own sake. No cookies, no advertising, no selling, and no script from anyone but Stripe, on the page where you pay. The pages are served and the data is stored on Cloudflare’s network, in a database called D1. Below is everything it holds, and why.
What we never touch
Your documents. There is no place in InterpDirect to upload them, so we hold none. The only images we keep are photographs of a building’s entrance that you choose to post for the next interpreter, and a screenshot you send with a suggestion.
Your bank and card details. Card payments run through Stripe, which holds the account and card numbers. What we keep is a Stripe account reference and three yes/no flags: whether the account can take payments, pay out, and has finished its forms.
Your clients. A booking stores the requester’s name, email and organisation, because the request has to reach you and the requester has to be told your answer. Those details exist for that booking and for your own records on your page. We do not sell them, share them, or contact your requesters for any purpose but that booking.
In one database on Cloudflare D1, under an account held in the United States. Cloudflare chooses the data centre the database sits in; we do not pick the country. The photographs and screenshots are in the same database. Nothing of this is on any other host.
Cloudflare keeps short-lived logs of errors so we can fix them, and, like any host, its own network logs include the address of each connection. We do not use those logs to identify anyone.
Name, city, state or province, country, languages, specialties, certifications, and the address of the public roster they came from. Why: so you can be found, and so the source can be shown. An email or telephone number taken from a roster is used once, to tell you that you are listed, and is never shown to anyone. An opt-out is kept so you are never written to again.
Your email and telephone, to send you requests and your sign-in code. Your rates by mode and setting, languages, specialties, service area, a short bio, a website, your page name and any earlier one so old links keep working, and your plan. Your pay-direct details exactly as you typed them, shown only to a requester whose booking you accepted. A Stripe account reference and three yes/no flags, if you connected one. Who referred you, and the fee credits that earned. Notes and photographs you add about a building, which the next interpreter sent there sees. A suggestion you send us, with its screenshot.
Teams and conferences. When a job needs a team, or you run or join a conference, we keep the team, who was invited and each person’s answer, the languages, the days and sessions, the lead’s quote in the lead’s own words, and which interpreters vouched for which. Why: so each person sees their part and the requester sees one quote.
Name, email, credential and organisation as you gave them, your verdict on each sentence, and whether you agreed to be credited. Why: the credit line on the pages you reviewed, and so we can ask you again.
If you suggest a correction: the page, the words you flagged, your wording, and the email and qualification if you gave them. Why: a proofreader checks it before anything on the site changes.
Your name, email, organisation, the appointment time, the address or the video or telephone choice, the suite and who to ask for, your notes, who pays, and how long the session was expected to last. Why: the interpreter needs all of it to turn up in the right place, and you need to be told their answer. Your email is also how you open your own bookings page; the code we send for that is stored hashed and expires.
If you mark an interpreter to skip, or leave a note about one, we keep that choice with your email so that it applies the next time you book.
People who learn. Someone who signs up to learn gets a private page. We keep their name, email, languages, country and the language of the page, and a sign-in code stored hashed.
The interpreter’s quote, our fee, the processing cost, what was charged and paid out, the currency, the status, and Stripe’s references. Card numbers and bank accounts never reach us. Payment records are kept for as long as accounting law requires.
The room link, its provider, and when it opens and closes. The provider receives the room’s time window and nothing about who is in it. We do not record sessions, and we do not keep what was said.
For each interpreter and month we count the minutes people were in a room and how many rooms were opened, to apply the plan’s allowance. Counts only: no names, no recording.
When a page was opened or a form sent, which kind of page, one word for where the visitor came from, the interpreter and request it concerns, the state and the language of the page. No address, no browser details, no name. Searches are kept as the language and the region asked for, and how many results there were.
To stop one connection from scraping the directory or using the booking form as a mail relay, we keep a hash of the connection’s address and the day, with a count per hour. It cannot be turned back into the address, and it is deleted after a day. Sign-in codes are stored hashed, with the same hash of where they were asked from.
Every email we send is logged with its recipient, whether it left, and when a request link was first opened. No tracking pixel, and no link tracking. When you write to us, your message is in our mailbox like any other email.
Nobody else. We do not sell, rent or trade any of it, we do not advertise, and we do not hand it to an analytics company.
Humans interpret. InterpDirect uses software, including AI tools, to help interpreters with the work around interpreting, and will keep doing so as the technology develops. It is never used to do the interpreting.
When what we store or who sees it changes, this page changes first and every interpreter with a claimed page is told by email. The date at the top is the date of the last change.
Anything about these pages: hello@interpdirect.org. Anything about your data: privacy@interpdirect.org.
Stuck? Write to us and a person will answer.
Send an email