Privacy Policy
Last updated: 2026-08-08 · Controller: David Reid, trading as Knockstack (a sole trader, not a registered company) · Contact: david@davidre.id
1. What this covers
Knockstack helps you find local businesses, write a tailored cover letter for each, and print them as a stack to hand-deliver on foot. This policy explains what we do with your data, who else sees it, and how to get it back or get rid of it.
We have tried to write it in plain language. Where we have had to be vague, it is because the answer is genuinely uncertain, and we say so rather than papering over it.
2. Who the data is about
Two groups, and they are treated differently.
You, the applicant. You sign in, upload a résumé and build campaigns. Most of this policy is about you.
The businesses you write to. Their names and addresses come from Google Places and end up on your letters. For a limited company that is not personal data. For a sole trader — a great many small hotels, cafés and shops — a business name and address can be personal data about a real person. We do not contact them, profile them, or build a mailing list from them. They appear in your campaign because you selected them, and they are deleted when you delete your campaign or your account.
3. What we collect
3.1 Account
From Google when you sign in: name, email address, profile image, and OAuth tokens that let us keep you signed in. We do not receive or store your Google password.
3.2 Your résumé — read once, then discarded
When you upload a résumé, its contents are sent to Anthropic (see §5) to extract a structured profile. The file itself is never stored. It is held in memory for the duration of the request and discarded.
What we keep is the extracted profile you then confirm on screen: name, email, phone, city, a one-line headline, key facts about your experience, availability, languages, and any standing notes you add.
A caution about résumés. A CV can contain things that European law treats as sensitive — health, religion, trade union membership, ethnic origin, sexual orientation. We do not ask for any of it and do not use it for anything, but we cannot detect it either. Anything in your résumé is sent to Anthropic for parsing and stored in the profile that parsing produces. If your CV contains something you would rather not send to a third-party AI service, remove it before uploading.
3.3 Your campaigns
The businesses you selected (Google place ID, name, address), the letter template you approved, each generated letter, the researched fact about each business, your walking order, and your printing preferences. Stored as a single record per user.
3.4 Usage counters
Monthly counts of searches, AI calls, place lookups and route orderings, per account. Used to enforce fair-use limits and detect abuse. No content, just numbers.
3.5 What we do not collect
No device location. No tracking cookies, no advertising identifiers, no third-party analytics. No payment data — Knockstack does not currently take payments at all (§6). We do not sell or share personal data for advertising, ever.
3.6 Your notes on a business
While you are out delivering, you can mark a business as delivered and write yourself a note about it — “closed Sundays”, “ask for Anna”, “handed it to the manager”. A note is kept against the business itself, not against a campaign, so it is still there after that campaign is finished or deleted, and still there if you come back to the same hotel a year later. We keep it until you delete it or delete your account (§8), and nothing in the app reads it back to you or anyone else (§5).
4. Why we are allowed to process it
| What | Basis (UK/EU GDPR Art. 6) |
|---|---|
| Account, résumé parsing, letter generation, campaigns | Contract — this is the service you asked for |
| Usage counters, abuse prevention | Legitimate interests — keeping the service affordable and available |
| Any sensitive data incidentally in your résumé | Explicit consent (Art. 9(2)(a)), given by choosing to upload that file after the warning in §3.2 |
5. Who else sees your data
We use these processors. We do not sell data to anyone.
| Who | What they get | What for |
|---|---|---|
| Anthropic (US) | Your résumé contents; business names and addresses; your letter text | Parsing your résumé, writing your template, researching each business |
| Google (US) | Your search terms and map viewport; the place IDs in your campaign | Finding businesses, showing the map, fetching coordinates and walking distances |
| Neon (EU region) | Everything in §3 except the résumé file | Database hosting |
| Vercel (EU region — see §7) | Everything, in transit and in memory during processing | Application hosting |
| Google (OAuth) | Your sign-in | Authentication |
A note goes to no one but you. A note you write against a business (§3.6) is not sent to Anthropic, not sent to Google, and never printed on a letter — it plays no part in producing anything. Neither of the US processors in the table above is anywhere in its path. It is stored by Neon in the EU, travels through Vercel's EU servers to reach you, and is read back only into your own browser.
Your résumé content goes to Anthropic. That is the single most sensitive flow in the product and we would rather state it plainly here than bury it.
Anthropic's terms forbid them training models on it. Section B of their Commercial Terms of Service (effective 17 June 2025) says: “Anthropic may not train models on Customer Content from Services”, where Customer Content means what we send them and what comes back. We link the source rather than paraphrase it, because this is their commitment and not ours to give — you can read it and check that it still says this.
6. Payments
Knockstack does not currently process payments. There is no card data, no Stripe account, no billing records. If and when paid plans launch, this section will be replaced and you will be told before it takes effect. Payment card details would then be handled by the payment processor directly — we would never see or store a card number.
7. Where your data is processed
Our database and our application servers are both in the EU. The database is hosted in an EU region and the application runs in Frankfurt. Both were deliberate choices.
Some of your data still leaves the EEA. Anthropic and Google are US-based processors, so your résumé contents (to Anthropic) and your search terms and place IDs (to Google) may be processed in the United States regardless of where our own servers run.
What we can tell you about the safeguards, and what we cannot. Because we are in the EEA, our contract for the Anthropic API is with Anthropic Ireland, Limited, and their Commercial Terms (section C) put all data we submit under their Data Processing Addendum. Google, Neon and Vercel each publish their own data processing terms covering EEA transfers.
We have deliberately not written a sentence here claiming those agreements contain Standard Contractual Clauses. An earlier version of this policy did, and nobody had read the documents — the addenda are not all published openly, so we could not check. We would rather tell you exactly what we know than repeat a reassuring phrase we cannot stand behind. If you need the transfer safeguards for a specific processor before using Knockstack, email us at david@davidre.id and we will get you the current document or tell you we could not.
8. How long we keep things
| Data | Kept for |
|---|---|
| Your résumé file | Not kept. Discarded after parsing |
| Account and campaign data | Until you delete your account |
| Google place IDs | Indefinitely — permitted, and the only Google Places field we retain long-term |
| Business names and addresses on your letters | With your campaign, until deleted. We ask you to re-check them after 30 days, because businesses move |
| Cached Google search results | 24 hours, then deleted automatically |
| Usage counters | With your account, until deletion |
| Your notes on a business | Until you delete them, or until you delete your account |
9. Your rights
Under UK/EU GDPR you can ask for access, correction, deletion, restriction, objection, portability, and to withdraw consent. You can also complain to a supervisory authority — in Germany, your state Datenschutzbehörde.
In practice:
- See your data — everything in your campaign is on screen, and your account menu shows what we hold.
- Correct it — the profile and every address are editable in the app.
- Delete it — “Delete account” in the account menu. It is a hard delete: your account, profile, campaigns, letters and usage counters are removed from the database immediately and the copy cached in your browser is cleared. It is not a soft flag and there is no recovery.
- Ask us anything else — email david@davidre.id. We will respond within one month.
10. Storage in your browser
Knockstack keeps a copy of your current campaign, and of your notes, in your browser's local storage so the app stays fast and survives a dropped connection — a note is written on the street, often with no signal, and is uploaded when there is one. Both are held under your own account and both are cleared when you sign out or delete your account. It is not a cookie and is not used for tracking.
A session cookie keeps you signed in. That is the only cookie, it is strictly necessary, and it is why you do not see a cookie banner.
11. Security
Encrypted in transit. Access limited to what the application needs. Sign-in is delegated to Google, so we never handle your password. No security is perfect and we will not pretend otherwise; if a breach affects your data we will notify you and the relevant authority as required.
12. Changes
We will update the date at the top and, for anything material — a new processor, a new purpose, a change to retention — tell you before it takes effect.