Privacy Policy
Version 1.0.0 was reviewed and approved by counsel licensed in the State of Florida and took effect on September 23, 2026. Version 1.0.1 took effect on October 12, 2026 and changes one thing: one sentence that pointed to a section of the Risk Disclosure that no longer exists was removed. It is otherwise identical to 1.0.0. Version 1.0.2 took effect on October 12, 2026 and changes one thing: it describes the new Analyst credit rules. We now keep a record of each credit top-up and of the auto top-up setting you agree to, and the spend cap control is replaced by the auto top-up switch. It is otherwise identical to 1.0.1. Version 1.0.3 took effect on October 12, 2026 and changes these things. The summary and sections 1, 4 and 5 now say that your questions to the Analyst are private to you, and that a finished diligence report is desk research on a market, kept on file and shown to any subscriber who runs diligence on the same market within 24 hours. Section 5 now lists what the Analyst is actually sent: market data, the exchange’s rules, the desk’s own work on that market and your question, and nothing from your account. Section 2 now describes the agreement record as it is kept today, and no longer speaks of a frozen copy of each version or of a condition on checkout. Sections 2 and 13 no longer refer to a control that can place an order, because there is none. Section 4 is one clause shorter. It is otherwise identical to 1.0.2. Version 1.1.0 took effect on October 13, 2026 and changes these things. The desk now sends orders, so the summary and section 1 now say what leaves your browser when you press one: the signed order request, which our relay forwards to the Exchange unchanged, returns the answer to, and does not store. The key itself still never reaches us. Section 1 now says that your trade journal includes the orders you send from the desk and what the Exchange reported back. Sections 10 and 13 now describe the kill switch as the control that stops the desk sending anything further and leaves Cancel working. It is otherwise identical to 1.0.3. Version 1.1.1 took effect on October 15, 2026 and changes nothing in this document. It carries the new number so the three documents stay one set, after the FULL DESK+ monthly allowance in the Subscriber Agreement changed to 3,500 credits. It is otherwise identical to 1.1.0. Version 1.1.2 took effect on October 15, 2026 and changes nothing in this document. It carries the new number so the three documents stay one set, after the consent gate in the Subscriber Agreement became one acknowledgment box. It is otherwise identical to 1.1.1. Version 1.1.3 took effect on October 15, 2026 and changes sections 1, 3 and 13: at sign-up we now ask for a mobile phone number, and we record whether you agreed to receive offers and updates by email and by text or call, with the sentence and the time. That consent is optional and never a condition of purchase, and section 13 says how to stop each. It is otherwise identical to 1.1.2. Version 1.1.4 took effect on October 15, 2026 and changes one thing in section 1: at sign-up we now ask for your first and last name, and the sentence saying we do not ask for your name is gone. It is otherwise identical to 1.1.3. Version 1.1.5 took effect on October 15, 2026 and changes nothing in this document. It carries the new number so the three documents stay one set, after the Subscriber Agreement described cancelation as two clicks. It is otherwise identical to 1.1.4. Version 1.1.6 took effect on October 21, 2026 and changes nothing in this document. It carries the new number so the three documents stay one set, after the Subscriber Agreement made the free trial 3 days. It is otherwise identical to 1.1.5. This is the version you accept at the consent gate, and the version whose fingerprint is written into your acceptance record.
Contents
- We sell nothing about you. No data brokers, no advertising trackers, not now and not later.
- Your card never touches our servers. Stripe handles payment; we see only whether a subscription is active and whether a credit top-up went through.
- Your journal, your positions, and your questions to the Analyst are yours. They are never published, and nothing from them ever goes into the shared signal feed. A finished diligence report is different. It is desk research on a market, and section 1 says how it is shared.
- When you ask the Analyst something, we send our model provider the market’s data, its rules, the desk’s own work on that market, and your question. Nothing from your account goes with it. It never includes a picture of your screen or your payment details.
- Exchange keys never reach our servers. A key you link stays in your own browser, on your own device; requests are signed there and leave as signed requests, which our relay forwards to the exchange unchanged and does not keep. We never see the key, we cannot place orders with it, and unlinking wipes it from your browser.
- We keep one category of record longer than everything else, on purpose: proof of what you agreed to and when. Section 2 says exactly what that is and why deleting it would hurt you as much as us.
- One email gets your data out or gone. Write to support and we export or delete it.
The sections below are the binding version. This summary exists so that none of it arrives as a surprise.
1. What we collect
- Account: your first and last name, your email address (used for magic-link login), the mobile phone number you give when you subscribe, and plan status.
- Marketing choice: whether you agreed, at sign-up, to receive offers and updates from us by email and by text message or call; the sentence you agreed to and when. That consent is optional and is never a condition of buying anything. If you did not tick it, we send no marketing.
- Billing: handled by Stripe. Card numbers never touch our servers; we store only the subscription state Stripe reports and a record of each credit top-up: the amount, the time, and Stripe’s reference for the charge. If you switch on auto top-up, we also record the sentence you agreed to, the monthly limit you chose, the time, your IP address and your browser.
- Exchange API keys (optional): never stored on our servers. If you link a key, it stays in your own browser on your own device; the desk signs its requests there. What leaves your browser is the signed request: for a read, the request for your balance, positions and order status; for an order you press, the order itself (market, side, price, size, type, time in force, and a client order id the desk generates) with the signature headers. Our relay forwards it to the Exchange unchanged, returns the Exchange’s answer, and stores none of it. The key itself never reaches us. Unlink at any time and the key is wiped from your browser.
- Usage: product events (pages, features, Analyst credit usage) and your desk settings (bankroll, Kelly fraction, guard toggles) so the product works and so guard states can be shown on your private order log. A credit record stores which action ran, on which market, when, and how many credits it used. It does not store the text of what you asked, and your questions are never shown to another subscriber.
- Technical and security data: your IP address, browser and device type, and timestamps, captured when you sign in, when you accept an agreement, and when you link or unlink an exchange key. We collect it to secure accounts, to detect abuse, and to make the records in section 2 mean something.
- Your research: your trade journal (including the orders you send from the desk and what the Exchange reported back) and conviction inputs are stored for you and shown only to you. Your questions to the Analyst and its answers are private to you. A finished diligence report is different. It is desk research on a market, and it holds market research only: never your account data, your questions, or who asked for it. We keep it on file, and any subscriber who runs diligence on the same market within 24 hours is shown that same report, unless the market has moved enough to call for a new one. It stays on file after you leave, because it holds nothing about you.
- Support: what you write to us, so we can answer it.
We do not ask for, and do not want, your address, date of birth, government identifiers, or bank details. Your exchange holds those; we do not need them.
2. Agreement records — the one thing we keep longer
When you accept an agreement, we record what you accepted — not merely that you clicked.
The record holds: the version identifier, the documents it named, and a cryptographic hash (a fingerprint of the exact text) of each of those documents, taken by our server from the published file at the moment you accepted; the exact wording of each box you ticked together with a hash of that wording; the time; your email address; your IP address, and the address a network proxy reported if there was one; your browser; and which gate it was, such as subscribing. The hash of a box’s wording and the hash of a whole document are separate things, and the record carries both rather than letting either stand in for the other.
The record does not hold a copy of each document. It holds the fingerprint. Each published version of these documents is kept in the version history of this site, and the fingerprint shows whether a given copy is the exact text you accepted.
These records are deliberately excluded from the deletion schedule in section 11 and are kept for the period in section 11 even after you cancel. A deleted consent record is an unenforceable agreement — which cuts both ways: without it, neither of us could later prove what was or was not agreed, including the protections the agreement gives you. If you ask us to delete your data, these records are what remains, and we will tell you so.
A record is kept from the first acceptance onward. Joining the seat queue runs through the same consent gate as subscribing, and the server writes the same record for it. If you have joined that queue, one of these records describes you, and this policy governs it.
They are used for one purpose only: establishing what was agreed. They are never used for marketing, never sold, and never shared except as section 7 describes.
3. What we do with it
Run the service, bill you, secure accounts, keep proof of what was agreed, improve the product in aggregate, and meet legal obligations. If you agreed to it at sign-up, send you offers and updates by email and by text or call, which you can stop at any time. That’s it. We do not use your data to train models on your identity, we do not profile you for advertising, and we make no automated decision about you that produces a legal or similarly significant effect.
4. What we never do
- We never sell your personal data, and we never share it for cross-context behavioral advertising.
- We never publish your positions, your journal, or your questions to the Analyst.
- Your journal, your conviction inputs and your questions never feed the shared signal feed.
- We never share or sell your order flow, and never take payment for it.
- We never take a screenshot of your screen or read anything outside this product.
5. What the Analyst sends out, exactly
When you press Ask or Run Diligence, we send our AI model provider structured text about the market it is pointed at. That is the market’s title and status, its current quotes and book depth, its exchange-published settlement rules, its fee type, the exchange’s settled history for that series, and the desk’s own model work on that market where there is any. For Ask, it also carries your question. That is all it carries. It never includes your position, your balance, your fills, your desk settings, your payment details or your email address. It is never a screenshot of your screen.
Queries are processed to produce your answer and are not used to train models on your identity. The market data and rules text inside a request are public exchange information. The answer to a question comes back to you alone. A finished diligence report is desk research on that market, and section 1 says how it is kept and shared.
6. Third parties
Stripe (payments), our hosting provider (infrastructure), our email provider (login links and receipts), and our AI model provider (Analyst queries are processed to generate answers; they are not used to train models on your identity). Each receives only what its function requires, under a written agreement limiting what it may do with it. We do not sell data to any of them and they are not permitted to sell it either.
7. When we disclose data for legal reasons
We may disclose data where we are legally required to — a valid subpoena, court order, or lawful demand — or where it is necessary to establish or defend a legal claim, to enforce the Subscriber Agreement, or to protect the rights or safety of a person. If a business transfer occurs (a merger, acquisition, or sale of assets), data may move with it under this policy.
Where the law allows us to tell you about a demand for your data before we respond to it, we will.
8. Where data is held
The Service is operated from the United States and data is stored and processed there. If you use it from elsewhere, you are sending your data to the United States, whose privacy laws differ from your own. The Service is offered to United States subscribers; see section 6 of the Subscriber Agreement for who may subscribe.
9. Cookies
Essential cookies for login and preferences, and nothing else. No third-party advertising trackers, no cross-site tracking pixels, and no consent banner — because there is nothing to consent to beyond what makes login work.
10. Security
Encryption in transit and at rest, exchange keys that never leave your browser, a per-account kill switch that stops the desk sending orders, access logging, and least-privilege access internally. No system is perfectly secure, and we do not claim otherwise. If a breach affects your data we will notify you as the law requires and as honesty demands, with what we know, when we know it.
11. Retention and deletion
- Account, usage, and research data — kept while your account is active and for 90 days after cancelation, so you can come back or export your journal, then deleted on request or on schedule.
- Exchange API keys — deleted immediately when you delete them, and on account closure.
- Billing records — kept as long as tax and accounting law requires.
- Agreement records under section 2 — kept for seven years after the subscription ends, which must be at least the period in which a claim could still be brought. These survive a deletion request, and we will tell you exactly what was kept.
- Backups — deleted data persists in encrypted backups until they rotate out.
Email support@evdesk.ai to access, export, correct, or delete your data.
12. Children
The Service is not for anyone under 18 and we do not knowingly collect data from anyone under 18. If we learn we have, we delete it. See section 6 of the Subscriber Agreement.
13. Your controls, and where each one lives
- Auto top-up: the desk’s credits panel. Off by default. If you switch it on, it adds 2,000 credits for $20 when your balance runs low and stops at the monthly limit you set, and it is yours to change or switch off.
- Exchange API key: the desk’s link control. Unlink in one action; the key is wiped from your browser and the mirror stops.
- Kill switch: per account. Stops the desk sending anything further, leaves Cancel working, and deletes nothing. It reaches nothing already at the Exchange.
- Anything that re-runs on its own, such as Watch, is a toggle you switched on and can switch off in the same place you found it.
- Export, correction, or deletion: email support@evdesk.ai and we act on the request.
- Marketing email: one-click unsubscribe in every marketing email.
- Marketing texts and calls: reply STOP to any text, or email support@evdesk.ai, and they stop. Account, billing, security, and agreement-change notices are not marketing and continue for as long as you have an account.
14. State privacy rights
Depending on where you live, you may have the right to know what personal data we hold about you, to get a copy of it, to correct it, to delete it, and to not be discriminated against for exercising any of those rights. We extend these rights to every subscriber regardless of state, because operating two standards is worse than operating the better one.
To exercise any of them, email support@evdesk.ai from the address on your account. We respond within 30 days. If we decline a request we tell you why, and you may appeal by replying to that answer; an appeal gets a written decision. Section 11 explains the one category we keep regardless.
We do not sell personal data and we do not share it for targeted advertising, so there is no opt-out to operate for either — there is nothing to opt out of.
15. Changes to this policy
Every version carries a version number and a date, shown at the top of this page. Corrections and clarifications take effect on publication. If a change materially affects what we collect, what we do with it, or who receives it, we email you before it takes effect and ask you to accept the new version in the product — and if you would rather not, you can cancel before it applies and we refund the unused part of any period you paid for. Section 30 of the Subscriber Agreement governs.
16. Contact
Questions, requests, and complaints: support@evdesk.ai, or by mail to EVDESK LLC, Attn: Privacy, 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110. The data controller is EVDESK LLC, a New Mexico limited liability company — the same entity named in section 1 of the Subscriber Agreement. Its notice address is the one above.