Privacy policy
Effective October 27, 2026.
Who we are
This policy covers E3D Pilot at pilot.e3d.ai, run by FutCo LLC, a California limited liability company. Contact for all privacy questions and requests: support@pilot.e3d.ai. This policy was adopted by the owner of FutCo LLC.
What we collect
Account: your email address, and a password hash and sign-in or verification codes held by our account service. Sessions and abuse limits: a hashed session identifier, and short-lived counters keyed by digests of your network address and email, which we treat as personal data. Your content: the questions you submit, and the answers, per-model positions and summaries, in stored debates and, if you save them, decisions. Usage and billing: counts, credits, model names, outcomes and timing for each request, without question or answer text, and the payment id, pack, amount, currency and status of each purchase. If you have a plan: its tier, billing interval, status, start, renewal and end dates, the amounts of its payments, and the Stripe ids of your customer record, subscription and invoices. We never receive your card number. Keys and connections: a hash of each API key (never the secret) and hashed connector tokens. Terms acceptance: which version you accepted and when, with a keyed digest of your network address and a coarse browser or other class; when you subscribe to a plan, which version of the plan terms you agreed to, for which plan and price, and when. Logs: operational logs that are designed not to hold question or answer text, passwords, codes or key secrets.
Cookies
The site uses only cookies that are strictly necessary: a session cookie that keeps you signed in and a CSRF cookie that protects changes you make. Where the try page is available, it sets one more strictly necessary cookie: a random identifier that limits how many tries a browser can run, kept for one day. We set no advertising or analytics cookies, and the site, the try page included, loads no analytics or other third-party scripts.
Emails to support and early-access requests
If you email support@pilot.e3d.ai or use the early-access form, including to ask for early access, we keep what you send. An early-access request can include your name, company, use case, the AI vendors you use and the AI app you connect from. A request sent with the form holds your email address and, if you give them, your company, which AI tools you use and a short note on how you would use E3D Pilot; it also records the page you sent it from, that you agreed to be emailed about early access and which version of this policy you saw, and, if you ran a try first, a reference to that try and whether the models agreed (never the text). Only we read these requests, and we do not send them to the AI model companies. We use them only to reply to you, to issue invite codes and to understand how people use the preview. We keep them for 24 months.
Trying E3D Pilot without an account
Where the try page is available, you can run a short debate without an account. The text you enter is sent to the AI model companies named on that page to answer it, as described in "AI model companies"; web search is off for tries. Do not paste passwords, secret keys, personal information or confidential code or text: treat what you paste as shared with those companies. We store the text you enter and the answers for 24 hours after the try, then delete them. To limit how many tries can be run, we use the cookie described above and counters keyed by keyed digests of that cookie's identifier and of your network address; the counters are deleted within 60 days. We keep a record that a try happened, without the text, your network address or the cookie identifier, for 30 days. Copies of the text and answers can remain in our database backups for up to 14 days, and with the AI model companies under their own terms. A try creates no account, and we do not link it to your email unless you send an early-access request that names it.
Invite codes
When we issue an invite code we store it only as a hash, not the code itself. We also store the note attached to it, which can be your company and contact name, so that we know who the code was issued to.
How we use it
To run the Service, sign you in, bill for credits and plans, prevent abuse, protect the Service, give support, and keep the records we need for accounting and disputes. We do not sell your personal information, and we do not use your content for advertising. We do not train AI models on your content.
AI model companies
To answer your question we send its text to the AI model companies on your panel: Anthropic, OpenAI, Google and xAI. In later rounds each company also receives the other companies' answers, which can repeat parts of your question, and the company that writes the summary receives all of them. Each company's own terms and privacy practices govern what it does with what it receives, including how long it keeps it, whether it reviews it for abuse, and where it processes it. We do not control those practices and do not promise them.
Web search
When web search is on, a model company may send your question text, rewritten as search queries, to its own search tool and to the search provider behind that tool, and may open pages it finds. We do not see those queries or pages. The answers we store can quote what was found and list the sources, and we also keep search counts and cited domains. Web search is on by default for every model company on your panel, Google included. Each company's own terms govern what its search tool and search provider receive and keep, and we do not control or promise those practices. You can turn web search off for any debate, on the Ask page or per request from a connected AI app.
Other companies that receive data
Stripe processes payments, and receives your payment details and the pack or plan and amount. For a plan, Stripe also keeps your subscription and its invoices; we keep the plan, its status, dates, amounts and Stripe ids. Amazon Web Services hosts our server in the US East (Ohio) region, us-east-2. An email delivery provider sends sign-in, verification and account emails, and receives your email address and the message. We have one server, and our database, backups and usage records are on it. Share links: if you create one, anyone who has the link can read that one decision until it expires or you turn it off. We may disclose information if the law requires it, and it may transfer to a successor if our business is sold or merged.
Saved decisions and share links
Where Decisions is available, a decision you save keeps its own copy of a debate's question and answer with your title, status and optional private note, for 365 days after your last change, or until you delete it or close your account. Only you can see it. A share link shows one decision, without your title, note or account details, to anyone who has the link until it expires (at most 30 days) or you turn it off. We store only a hash of the link. Apps that preview links may keep a copy.
How long we keep it
Stored debates: 90 days after they finish, or until you delete them. Saved decisions: 365 days after your last change, or until you delete them or close your account. Share links: at most 30 days. Sessions: up to 7 days, and 12 hours when idle. Rate-limit and sign-in counters: minutes to hours. Usage records, credit ledger, plan and payment records: kept for accounting and disputes under a pseudonymous account id, and not deleted when you close your account; we have not set a deletion date for them. Terms acceptance records: kept after you close your account, under the pseudonymous id and without your email, for as long as we need to show what was agreed. Support emails and early-access requests: 24 months. Text entered on the try page and its answers: 24 hours; the record that a try happened: 30 days. Invite codes (stored hashed) and the note attached to each: kept with the invite record; we have not set a deletion date for them.
Backups
We make daily backups of our database. They are kept on the same server as the database; there is no off-site copy today, and we may add a rolling snapshot later. The backups contain debate and decision content, so content you delete, or that expires, remains in backups until older backups are replaced; our deployment keeps backups for 14 days. We do not describe our backups as encrypted.
Closing your account
Closing your account revokes your keys, ends your sessions, and deletes your stored debates, saved decisions and account record from our live systems. Copies in backups remain until they are replaced, copies held by the AI companies follow their own terms, and the financial and acceptance records described above stay under the pseudonymous id.
Your choices and requests
You can delete debates and decisions, turn web search off for a debate, and close your account in the dashboard. To ask for a copy of your personal data, a correction, a deletion or to object to a use, email support@pilot.e3d.ai from your account email. We will check that the request comes from you, and answer within the time the law sets where one applies. There is no self-service export today.
Security and incidents
We take reasonable steps to protect your data, described on our Security page, but no system is free of risk. If we learn of a security breach that affects your personal data, we will notify you as the law requires.
Where data is processed
Our server is in the United States (AWS us-east-2). The AI companies, Stripe and our email provider process data in their own locations, which may be in other countries.
Children
The Service is not for anyone under 18, and we do not knowingly collect data from them.
Changes to this policy
We will post any new version here with its date and ask you to accept it where our Terms require it.
Website chat
While the chat is switched on, the public pages of this site (not the account, billing or sign-in pages) load a chat widget from chat.pilot.e3d.ai, a chat server (the open-source Chatwoot) that we run ourselves on our own infrastructure, so the page loads a script from that address and the widget sets its own cookie or browser storage to remember your conversation. What you type in the chat, and your email address if you type one, is stored on that server, read by us, and deleted 30 days after the last message; backup copies are removed within a further 7 days. An AI model from Anthropic reads each message you send in the chat to answer questions about Pilot, and a person on our team can step in. If the chat hands you to a person, we send a text message to the owner that contains a link to the conversation and none of your words. Do not put secrets, passwords or card numbers in the chat. This section replaces the sentence above that the site loads no third-party scripts, for the pages where the chat is shown.