Privacy.

The website

This site sets no cookies and runs no analytics. It is served through Cloudflare, which processes your IP address and request headers to deliver the pages and to block abuse, under Cloudflare's own terms.

The contact form

When you send the contact form we receive what you typed — name, email, level, the offer you are considering, markets, and your message — plus the time it arrived. It is stored in a log on our server and forwarded to our inbox so a person can reply. We use it to answer you and for nothing else. Ask and it is deleted.

The launch list

When you join the coming-soon list we store your email and, if you gave them, your phone, the level you search at, and which offer interests you, with the time you joined, in a Cloudflare key-value store. It is used to send you one message when the offer opens. Ask and it is deleted.

Employer visibility

Being visible to employers is off unless you turn it on. If you tick the box, employers who use ExecRecon may be shown that you are open to a move and, once the employer offer is running, the evidence in your fact bank read against their role. You can see whether it is on, turn it off, or leave the list at any time, and turning it off removes you from any list not yet sent. Nobody outside ExecRecon sees your name without this being on.

The employer list

When an employer joins the list we store the work email, company, hiring level, and typical volume they gave, for the same single message. When the employer offer runs, a job description we receive is used only to build that employer's requirement profile and list. Where the engine finds a person on a public job board who has said they are open to work, we contact that person first and pass their details to an employer only once they have agreed. We do not build or sell lists of people who have not agreed.

Checkout

Payment is handled by Stripe. Stripe collects your card details and billing information directly; we never see the card number. We receive your email, the offer you bought, and for the Recon Kit the GitHub username you gave, which we use solely to send the repository invitation and to remove it when the subscription ends. Stripe's privacy policy governs what Stripe holds.

The kit, running on your machine

The Recon Kit runs on your own computer inside your own Claude Code or Cowork account. Everything it produces — your fact bank, workbook, and documents — stays on your machine. ExecRecon receives none of it. Your AI provider's terms govern what your provider processes.

Full-Service engagements

To run a search for you we hold what you tell us in intake and what the engine produces: your work history, target roles, compensation floor, and the documents built from them. It lives in one engagement folder on ExecRecon's systems, is seen only by the Scout assigned to you and any Recon Partner you are told about, and is never used for another client. At the end of the engagement you receive a full copy and we delete ours after the retention period stated in your order.

What we do not do

• Sell, rent, or share your information with anyone for marketing.
• Apply for jobs, or contact employers, on your behalf, or show an employer your name unless you turned employer visibility on.
• Train any model on your data.
• Send you email you did not ask for. Order receipts and engagement correspondence are the only messages you will get.

Where data lives

Our server runs on Railway and its intake log on a Railway volume; DNS, the site, and the launch list are on Cloudflare; the repository is on GitHub; payments are on Stripe. Each is a processor under its own terms. Data may be stored in the United States.

Your rights

Ask us what we hold about you, ask for a copy, ask for it corrected, or ask for it deleted. Use the contact page; we answer from the address you write from, so use the one you used with us.

Draft. Reviewed by counsel before the site is indexed; the effective date and the operating entity are filled in then.