Privacy policy
Last updated 7 August 2026
This policy covers Footwork, run by Tomer Davies, and says what the product stores, who it is sent to, and what you can ask us to do with it.
Footwork is one person's product rather than a company — "we" below means Tomer Davies, and nobody else has access to any of this.
Footwork writes cold emails and sends them from your own mailbox. That means it holds two unusually personal things: the half-written emails, and access to the mailbox they go out from. Most of this page is about those two.
What we store
Your account: the email address you signed up with, and your name if you gave one. Passwords are handled by Supabase Auth and we never see them.
Your profile: school, course, year, graduation year, portfolio link, skills, what you are looking for, and how you describe your own writing. Plus the projects you list. All of it is optional, and all of it is read into the prompt that writes your emails — that is what it is for.
Your list: the companies you add and the contacts at them, including names, job titles, email addresses and any notes you write. Some of this you type; the rest is read off the company's own public website, or from public sources like git commit history and npm package metadata.
Your email: every draft Footwork writes, every email you send through it, and the replies that come back on those threads.
Your mailbox connection: which provider, which address, the permissions granted, and the access tokens needed to act on your behalf. Refresh tokens are encrypted before they are written to the database, so a database dump on its own is not access to anyone's email.
Support requests: what you type into the help form, plus your plan, your mailbox status, the page you were on and your browser, so the message can be answered without a round trip asking what was on screen.
Billing: whether you are on the free or paid plan, and the Whop membership id that decided it. No card details ever reach Footwork — Whop hosts the checkout and we never see a card number.
Product analytics: which pages and features are used, and whether things succeeded or failed. This is optional and can be switched off for a deployment entirely.
Your mailbox, specifically
Connecting a mailbox grants Footwork two permissions: permission to send, and permission to read.
The send permission is used when you press send, and at no other time. Footwork does not send email on a schedule you did not set, and it does not send anything you have not seen.
The read permission is deliberately used far more narrowly than it is granted. Footwork only ever fetches messages on threads it sent into itself. The filtering happens on thread identifiers before any message body is requested, so a message on a thread we do not own is never fetched, never stored and never read. The rest of your inbox is not touched, not indexed, and not visible to this product.
You can disconnect at any time from Settings, which deletes the stored tokens, and you can revoke access from your Google or Microsoft account settings independently of us.
Google user data
Footwork's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain terms, what that commits us to:
- We request gmail.send and gmail.readonly. Send is used when you press send. Readonly is used only to read replies on threads Footwork itself sent into, as described above.
- We do not use Gmail data for advertising, and we do not sell it or transfer it to data brokers, ever.
- We do not use Gmail data to develop, improve, or train generalized artificial intelligence or machine learning models. It is not training data and it never will be.
- Nobody reads your mail — there is one person behind this product and reading it is not something they do — with three narrow exceptions: with your explicit permission (for example, when you send us a support request about a specific message), where it is necessary for security purposes such as investigating abuse, or where we are required to by law.
The same commitments apply to mail read through Microsoft accounts. There is no reason for those to be weaker; they are stated under Google's heading because Google is the one that requires the wording.
What the AI sees
Footwork writes email by sending a brief to Anthropic's API and getting text back. That brief contains your profile and projects, the contact and company being written to, and your notes about them.
Two features send message content: drafting an answer to a reply sends that conversation, and sorting a reply into "wants to talk", "asked something", "passed" or "referred" sends the text of that one reply.
Anthropic processes this to return a result and does not use API inputs or outputs to train its models. We do not use your email, your contacts or your drafts to train any model of our own, and we do not have one.
The output is a suggestion. Everything Footwork writes is shown to you before anything is sent, and nothing leaves your mailbox without you pressing send.
Where contact information comes from
Footwork does not buy contact data and does not scrape LinkedIn. Contacts come from what a company publishes about itself: its own team or about page, its public git commit history, and public package metadata. Email addresses are either published outright, found in public commit metadata, or built from the address pattern a company's own site reveals — and when they are built rather than found, the app marks them as assumed rather than presenting a guess as a fact.
If you are on that list and would rather not be, write to us and we will remove you and refuse the domain. You do not need an account here to ask.
Who else processes it
Footwork is a small product built on other people's infrastructure. These are everyone who touches your data, and why:
| Who | What they get | What for |
|---|---|---|
| Supabase | Everything stored, and your login | The database and authentication |
| Vercel | Requests as they pass through | Hosting the site and the API |
| Anthropic | Prompts: your profile, contacts, drafts, and reply text | Writing and sorting |
| Google / Microsoft | Nothing new — it is your own mailbox | Sending and reading replies |
| Whop | Your email address and an account identifier | Checkout and subscriptions |
| PostHog | Product usage events, optionally session recordings | Knowing what works |
| Hunter.io | A company domain. Never a person | The email pattern for that domain |
| GitHub / npm | A company domain or organisation name | Reading public commit and package data |
We do not sell your data. There is no advertising in this product and no data broker in this list.
Session recording
If session recording is switched on for this deployment, PostHog may record how pages are used. Every text input is masked, and so is every surface that renders mail — a recording does not contain your drafts, your replies or anything you typed.
It is a switch rather than a fact of the product, and it is one word in the deployment configuration. For a product that holds people's half-written emails, the honest default is that this paragraph exists.
How long we keep it
While your account exists, your rows exist — a sent email is a record of something that happened and the product would be lying if it quietly dropped them.
Delete your account and everything keyed to it goes with it: profile, projects, companies, contacts, drafts, sent mail, replies, mailbox tokens. Disconnecting a mailbox deletes its tokens immediately, without touching anything else.
Support requests are kept as a record of what was said, so a conversation can be picked up later.
Backups may hold copies for a short period after deletion before they roll over.
What you can ask for
A copy of everything we hold about you. A correction. Deletion. A stop to any particular use. If you are in the UK, EU, California or anywhere else with a law giving you those rights by name, this is us saying we will honour them wherever you are, because keeping two standards would be more work than keeping the higher one.
Ask at support@usefootwork.com. We answer within 30 days, usually the same week.
Security
Every table is protected by row-level security in the database itself, which means "not yours" is enforced by Postgres rather than by application code remembering to check. Mailbox refresh tokens are encrypted with a key held outside the database. Mailbox credentials sit in a table with no read policy at all — no login, anywhere, can reach them.
No system is perfect and we will not pretend otherwise. If you find a hole, write to us and we will fix it and thank you.
Age
Footwork is for university and college students. You must be at least 16 to use it. We do not knowingly collect anything from anyone under 13, and will delete it if we learn we have.
Where it lives
The services above are US-based, so data is processed in the United States. If you are outside it, using Footwork means your data crosses a border to get here.
Changes
If this policy changes in a way that matters, the date at the top changes and we say so by email before it takes effect. Fixing a typo does not earn an email.
Contact
Footwork is operated by Tomer Davies.
Questions, requests, or anything about this page: support@usefootwork.com. It is read by a person, and it is the fastest way to reach one.