Privacy Policy

Last updated: October 9, 2026

1. Introduction

Miki Matoba, the operator of AgentDoor (“we”), treats the protection of personal data as a core responsibility and complies with Japan's Act on the Protection of Personal Information (APPI) and other applicable laws, including the GDPR where relevant. This policy describes how the site handles personal data. The service provides vendor "doors" (AI agents), buyer requests with interview reports, accounts, and paid plans.

2. What we collect

Your email address, only when you submit it to the waitlist form.
A source tag recording which page and language the sign-up came from (e.g. home-en, compare-ramp-vs-expensify-en).
A timestamp of when you signed up.
The country you signed up from (a two-letter country code inferred from your IP address, e.g. JP, US) and the page language. We do not store the IP address itself or your city.
An optional "vendor or buyer" choice on the waitlist form, only if you pick one. We use it to tailor the launch announcement.
How you first arrived (utm parameters in the URL, the referring site's URL, the first page path you saw, and when). Recorded together with a waitlist sign-up, door creation, or buyer request. It identifies no individual.
Account details: email address and password (stored as a hash; we never see the plaintext). If you sign in with Google, the email address and display name Google provides.
Vendor registration (door creation): your company website URL, the content imported from its public pages, any documents you add from the manage screen (Markdown / plain text), an optional contact email, and an optional notification URL you configure (a CRM / Slack webhook).
Buyer requests: the need you describe. Only if you tick the consent box, your name, company, and email address. A request without consent stores no contact at all.
Meeting proposals: the name, company (optional), email address and message (optional) you enter in the proposal form, the candidate times you send and the one you fix, and when the vendor accepted. None of it is disclosed to a vendor that has not accepted the proposal; if you pass before it accepts, the vendor receives only a fixed text.
For abuse prevention, a daily-salted hash of your IP address. The IP address itself is not stored.
When you subscribe to a paid plan, or register a card on the Free plan before accepting a meeting: your Stripe customer id (and, on a paid plan, the subscription status). When a Free-plan success fee is billed: the Stripe invoice id and payment state (the invoice line carries only the door name and the date the meeting was fixed, never the buyer's name, company or email). Card numbers are handled by Stripe and never reach our servers.
Team invitations (a discontinued feature): the record of addresses invited before it closed. We accept no new invitations and send no invitation email.
Compliance document vault: the files a vendor uploads (PDF / Excel / Word) and a hash of their contents. For access requests to a gated document, only if you tick the consent box, your name, company and email, plus a record of when the document was downloaded. A request without consent stores nothing.
We do not buy, enrich, or append data from other sources, and we collect no phone number.

3. How we use it

To contact you when AgentDoor opens for early access.
To understand which content is useful, by aggregating the source tag, first-touch source and country.
To provide the door feature and buyer requests. For AI answer generation, imported public-page content, documents the vendor added, the buyer's request text, and the question/answer text are sent to Anthropic; under Anthropic's commercial terms, it is not used to train its models.
To disclose a consenting buyer's contact to the vendors (paid plans) that appeared in that request's shortlist.
To show paid-plan vendors, as demand trends, the first 200 characters of the request text from up to 10 recent requests that evaluated their door (shown whether or not the buyer agreed to share contact details; no name or contact is attached, but whatever is written in the text is shown as is).
To disclose the name, company, email address and message of a buyer who proposed a meeting to that vendor, only after the vendor accepts the proposal (on the manage screen and in the candidate-times, date-fixed and decline emails), on any plan. Before it accepts, the vendor is shown nothing that identifies the buyer.
To email a buyer who proposed a meeting, once, at the address entered in the proposal form, that the vendor accepted and how to fix the date (the email carries neither the vendor's contact details nor any price).
To email a consenting buyer when that request's results are updated (a vendor answer or a correction).
To send the contact email given when a door was created notices about that door: a note on a day it answers, questions it could not answer, compliance-document access requests, and buyers' replies about meetings. A reply about a meeting names the buyer and carries their contact only after the vendor has accepted it.
To send, to a notification URL the vendor configured on the manage screen (a CRM / Slack webhook), the questions asked of their door and whether they were answered, meeting proposals and acceptances, how buyer requests evaluated the door, and the questions the door could not answer that we are holding for the vendor. What is sent is the question text (with its id for a held question), the verdict, the company name of a meeting the vendor accepted (a proposal carries not even that), and the requirement labels with their verdicts; never a buyer's name, email address or request text. The destination is a URL the vendor chose, not a subprocessor of ours.
To pass a compliance-document access request to the vendor that provides the document and, once approved, to email a time-limited download link. The documents themselves are never sent to an AI model.
To bill and invoice paid plans and the Free plan's success fees.
To prevent abuse and keep the service running safely.
We send no newsletters or marketing sequences, and we do not sell or share the list.
Legal basis (where GDPR applies): your consent, given by submitting a form, and performance of a contract; consent is withdrawable at any time (section 6).

4. Subprocessors

We entrust personal data to the processors below only to the extent necessary to run the site. We do not otherwise disclose personal data to third parties except with your consent, where required by law, or to protect life, body, or property.

Processor	Purpose	Location
Supabase, Inc.	Database storage for the waitlist, accounts, doors and buyer requests, private file storage for compliance documents, and authentication (email/password, Google sign-in)	United States (data stored in the Tokyo region, ap-northeast-1)
Resend (Plus Five Five, Inc.)	Email delivery (waitlist confirmation and operator notification, door-owner answer notifications and unanswered questions, result-update notices to consenting buyers, buyers' meeting replies, compliance-document access requests and approval links)	United States
Vercel, Inc.	Website hosting / analytics (Vercel Web Analytics, cookieless)	United States
Stripe, Inc.	Payment processing for paid plans, and monthly billing of the Free plan's success fees (charged to the card on file, or invoiced by email when there is none; the line carries only the door name and the date the meeting was fixed). Card details are held by Stripe and never reach us	United States
Anthropic, PBC	AI response generation for the door feature. What is sent is imported public-page content, documents the vendor added, the buyer's request text and the question/answer text; Anthropic's commercial terms do not allow it to use this content for training its models	United States
Google LLC	Traffic analytics (Google Analytics 4). Loaded only after cookie consent	United States
Microsoft Corporation	Behavioural analytics for site improvement (Microsoft Clarity: session recordings and heatmaps). Loaded only after cookie consent	United States

5. International transfer and retention

As shown above, personal data may be transferred to Supabase, Resend, Vercel, Stripe, Anthropic, Google, Microsoft (all US entities) and is handled under their data-processing terms. Waitlist data is kept until AgentDoor launches and we have contacted you, or until you ask us to delete it — whichever is first. If the product does not launch, the list is deleted. Account, door, and buyer-request data is kept until you ask us to delete it. Billing records are kept for the period the law requires.

6. Your rights

You may ask us to disclose, correct, or delete your data, to stop using it, and to withdraw your consent. Under the APPI and, where applicable, the GDPR, you may also lodge a complaint with a supervisory authority. A request from your account email (or, for waitlist-only entries, from the address you registered) is sufficient to identify you; we will action deletion requests promptly.

7. Cookies and analytics

Vercel Web Analytics measures aggregate traffic. It is cookieless and builds no per-visitor profile.
One functional cookie, NEXT_LOCALE, remembers your English/Japanese choice. It holds no personal data.
Your browser's local storage (not a cookie) keeps how you first arrived (utm parameters in the URL, the referring site's URL, the first page path you saw, and when). It is stored whatever you choose on the cookie banner, and reaches us only when you submit a waitlist sign-up, door creation, or buyer request. Local storage also holds flags that make some actions count only once (the value is just "1", with no identifier, and is never sent).
When you sign in, we set cookies that keep you signed in (Supabase Auth; their names start with "sb-" and they last up to 400 days). If you never sign in, none are set.
Only if you open a pre-launch preview link, we set a door_preview cookie (7 days) that enables the preview.
The tags for traffic analytics (Google Analytics 4) and behavioural analytics (Microsoft Clarity: session recordings and heatmaps) load only if you choose "Accept" on the cookie banner shown on your first visit. If you do not accept, these tags are never loaded and set no cookies. You can withdraw consent at any time via "Cookie settings" in the footer.
We set no advertising cookies.

Email we send

Joining the waitlist triggers one confirmation email (transactional).
At launch we send one announcement email (marketing). We send no other promotional email.
Every list email carries an unsubscribe link. Opt-out requests are authenticated by a signed link, so nobody can unsubscribe an address that is not theirs.
After you opt out we keep the record of the opt-out and exclude you from all future sends. The row is retained as evidence of consent and its withdrawal; ask us if you want it deleted outright.
If you create a door, we email you when it answers a question or an interview (transactional; at most one email per door per day, and never the question text).
When you request access to a compliance document, we email the vendor about your request and, once approved, email you a download link valid for 24 hours (both transactional).
When your door could not answer a question, we email you the question text only (at most one email per door per day; never the buyer's request text or contact details).
When a buyer sends proposed meeting times or declines a meeting, we email the vendor what they sent (transactional).
If you propose a meeting, we send one email to the address you entered in the proposal form when the vendor accepts, saying so with a link to your results page (transactional; at most one per proposal, with neither the vendor's contact details nor any price; only for proposals made while the form showed this note under the email field).
If, when making a request, you agreed to be emailed about updates to its results, we email you when a vendor's answer or a correction updates them (transactional; the email carries only a link to the results page. Without that consent we send nothing — the results page shows the update).
Email delivery is handled by Resend on our behalf.

8. Changes to this policy

If what we collect or how we handle it changes, we update this policy and the date above. The revised policy takes effect when posted.

Contact: contact@agent-door.com