Privacy Policy

1. Who is responsible and what this policy covers

This policy explains how Veyora Technologies, Inc., a Delaware corporation ("Veyora", "we", "us"), handles personal data when you use Veyora at veyora.ai and the pages, emails and interfaces that belong to it. Veyora Technologies, Inc. is the controller of that data, which means we decide why and how it is processed. We are based in the United States.

Veyora is a research and analysis product for prediction markets. It reads public market data from Kalshi, an exchange we are not affiliated with. We are not an exchange, broker, dealer or investment adviser, we hold no funds and we place no orders, so this policy has nothing to say about trading accounts: we have none of yours. The link "Open on Kalshi" inside the product takes you to Kalshi's own site, where Kalshi's policies apply.

This policy sits beside our Terms of Service and our Refund Policy. Where those documents describe how a feature works, this one describes what data that feature touches. The version number and effective date at the top of this page tell you which edition you are reading.

2. What we collect

We collect only what the product needs to run. The table lists every category, what it holds and where it comes from. We buy nothing about you from data brokers and add nothing from a source the table does not name.

Your email address is required to sign in. To activate the product, you must also declare your US country and state or district of residence or business operation. If you purchase, a complete supported billing address is required. What you sync, what you ask the assistant and whether you buy a plan remain your choice.

3. What we do not collect

Some things people expect a financial product to collect, we do not. Being clear about them matters as much as listing what we do collect.

• No trading positions or balances. We have no broker connection to Kalshi or any other exchange. We cannot see what you hold, what you have traded or what you have deposited anywhere.
• No card numbers or financial account numbers. Payment details go straight to Stripe and never pass through our servers.
• No government identifiers. We do not ask for a passport, driver's license, social security or tax number.
• No precise location. We do not read GPS or device location. Your IP address reaches our hosting provider with every request and sits in its request logs for the short time it keeps them, and your browser sends it to the image servers named under Cookies and browser storage. Our own records keep only a hashed, coarsened form of it (your address with its final part removed) for abuse prevention, which is pseudonymous and can be recomputed for abuse checks; it is not anonymous.
• No contacts, calendars or files from your device. A file you add to a notebook stays in your browser and is never uploaded.
• No data from children. The product is not for people under 18 and we do not knowingly collect their data.
• No behavioral profile. We do not build advertising profiles, buy data about you from brokers, or track you on other sites.

4. How we use it, and on what legal basis

We use personal data for the purposes below and no others. We do not use it for advertising, we do not sell it, and we do not profile you for advertising. Automated checks enforce eligibility, payment state and usage limits. You can contact support to request review of an eligibility or billing restriction.

5. The assistant and other AI processing

Veyora's assistant is an AI model reached through OpenAI's API. This section says exactly what leaves our servers for it, with what settings, and what never does.

What is sent when you message the assistant. Your message and the recent history of that conversation, together with a dossier we assemble about the market you are looking at: its price and price history, order book and recent trades, rules, stored news coverage, known catalysts, and the quotes of related contracts in the same event and category. Every section carries the time its data was last read, and if any was delayed the answer's list of sources says so. All of the dossier is public market data or text we generated from it. The request also carries your chosen response depth. We add nothing that identifies you: no email, no account id, no name, and no identifier the provider could use to link your conversations to you. Your own words are the exception. Whatever you type into a message, including anything personal about you or about someone else, goes to OpenAI as you wrote it, so treat the composer as you would any message sent to a company you do not know.

With what settings. Every request is sent with OpenAI's storage turned off (the request carries "store: false"). OpenAI therefore does not keep the conversation to serve a later request, and we never rely on a stored conversation on its side. We do not use your content to train any model, ours or anyone else's. OpenAI's own API terms govern what it retains for abuse monitoring. At the time of writing, its API data policy states that API content is not used for training by default and may be kept for up to 30 days for abuse and misuse monitoring. See OpenAI's API data policies for the current statement.

What is never sent. Your workspace is not part of the dossier. Your notes, your models and forecasts, your saved screens, your notebooks and the files you add to them never go to OpenAI. Nothing the assistant does reads the workspace stored in your account. There are three deliberate exceptions, and each begins with a button you press. Pressing "Discuss this result" on an analysis card, or "Discuss this output in chat" on a notebook cell, sends that one result or output into the conversation. And when the assistant offers to run one of the product's own analyses and you press "Run it" on that offer, the result is sent back to the assistant when the run finishes, so it can interpret it. In every case what crosses is bounded text built from the result's own figures and warnings, never a chart, a file or a file name. A result that read your own local inputs (your saved model or journal, a file you added, or an input pre-filled from your saved estimate) is refused rather than sent. The copy that crosses belongs to that one turn only: it is never stored in the thread and never replayed later.

Usage returned to us. For each answer OpenAI reports how many tokens it processed. We use that count, and only that count, to meter your credits (one credit is 10,000 billable tokens of model work).

News research. When news coverage is gathered for a market, the market's question, its rule text, its current price and how long until it resolves are sent to Perplexity, which returns cited articles. No personal data is included in that request: not who asked, not what you hold, not anything from your workspace.

The contract explainer. The plain-language reading of a market's rules is generated from the market's question and rule text and nothing else. The request carries no price, no news, no history and no personal data, and the result is stored per market, not per person.

What the assistant is. It reasons about markets and may hold analytical views, and it can be wrong. It is not a licensed adviser and it never issues a personalized instruction to trade. Decisions you make after reading it are yours; the Terms of Service say more.

6. Cookies and browser storage

We use cookies only to keep you signed in. There are no analytics cookies, no advertising cookies and no third-party trackers of any kind on any page, and there is no consent banner because nothing on the site needs one.

Do Not Track and Global Privacy Control. We do not track you across other sites, we do not let anyone else do so from our pages, and we do not sell or share personal data, so there is nothing for a Do Not Track or Global Privacy Control signal to switch off. We treat every visitor as if the signal were set.

Browser storage. The product keeps your workspace and preferences in your browser's local storage under keys prefixed "veyora.". Some of those keys are mirrored to your account when you are signed in (see the workspace mirror above); the rest stay on the device. Session storage holds the Explore screen you are currently looking at, for the life of the tab. The notebook's Python runtime is downloaded once from our own site and kept in the browser's HTTP cache so it does not download again. You can inspect, export, import and clear every one of these from Settings, Local data.

Email. The emails we send carry no tracking pixel of ours and we do not enable our email provider's open or click tracking, so we do not know whether you opened a message or followed a link in it.

Images from other sites. Two kinds of image are loaded by your browser from servers we do not run: market thumbnails from Kalshi's image server and, if you signed in with Google, your profile picture from Google's. Those servers see your IP address and browser details in the ordinary way, as any image host does. No script, font, style or analytics file is loaded from any third party; everything else on the site, including the notebook's Python runtime, is served from our own domain.

7. Who we share it with

We do not sell personal data and we do not share it for advertising. We use a small number of providers. Vercel, Neon, Resend, OpenAI and Perplexity process data only on our instructions under a contract that says so. Stripe and Google act on their own account for the data you give them directly (your payment details, your Google sign-in) under their own policies, and we receive only what each row below says. Kalshi and GitHub receive no personal data from us. They are:

Beyond those providers, we disclose personal data only:

• At your direction, for example when you export your data and send it somewhere yourself.
• To comply with the law, a court order, a subpoena or another lawful request, after checking that the request is valid.
• To protect rights and safety, where disclosure is needed to investigate fraud, abuse or a security incident, or to protect the rights, property or safety of you, other people who use Veyora, ourselves or others.
• In a merger, acquisition or sale of assets, in which case the data may pass to the successor, and we will tell you before it does.

8. Where your data is stored and processed

Veyora is operated from the United States and its data is stored there. Every provider named under Who we share it with also processes data in the United States. If you use the product from somewhere else, your data is transferred to and processed in the United States, where privacy law differs from the law where you live.

If you are in the EEA, the UK or Switzerland, each provider named in the table above processes data for us under its own published data-processing terms, which include the standard contractual clauses approved by the European Commission, with the UK addendum where UK law applies, for the transfers that require them. Those terms are linked from each provider's name in that table, and they apply together with the measures described under How we protect it. We do not rely on your consent for these transfers.

9. How long we keep it

We keep personal data for as long as the purpose it serves lasts, and no longer. The table gives the period for each category.

10. Your rights and controls

Most of what privacy law gives you a right to ask for, you can do yourself in Settings without asking. These controls work for everyone, wherever you live.

• Download an export. Settings, Account gives you a file holding your profile fields, your workspace with its revisions, your billing record (plan, period, grants and ledger), your briefs record and your record of which of these documents you accepted. It never contains tokens, secrets, hashes, counters or any provider identifier.
• Export, import or clear local data. Settings, Local data lists every key the product keeps in your browser, including data from retired features, and lets you export, import or delete it.
• Clear the cloud workspace. Removes the workspace mirror, the copy of your workspace held in your account. Your browser's copy stays, and a signed-in browser mirrors it back on its next visit unless you clear that too. This needs a sign-in within the last 15 minutes.
• List and revoke sessions. Settings, Account shows every signed-in session with its device label and dates. You can revoke any one of them, or choose Sign out everywhere to revoke all of them.
• Delete the account. Delete account removes, in one operation, the account itself, every signed-in session, the account's workspace mirror (tracked markets, models, chat threads, notebooks and analysis runs stored with it), the live billing record (subject to the minimal financial and consent archives described under Retention), the Google link if there was one, and any unused sign-in links. It needs a sign-in within the last 15 minutes. If a subscription is live, we cancel it at Stripe first, and if that cancellation cannot be confirmed the deletion is refused so that nothing keeps billing an account that no longer exists. Where email delivery is configured, a confirmation is sent to the address that was on the account.
• Manage briefs. Turn market briefs on or off and choose daily or weekly in Settings, App preferences. Every brief carries an unsubscribe link that works without signing in.
• Choose which copy wins. The first time you sign in on a browser that already holds a different workspace, the product asks whether the account's copy or the device's copy should win. It lets you export both first, and it keeps the losing copy on the device in a recovery store.
• Disconnect Google. There is no separate control for this yet. If you connected Google, the link stays until you delete the account.

If you are in the EEA or the UK, you also have the rights that the GDPR and the UK GDPR give you. You can ask to access the personal data we hold about you, to have it corrected, to have it erased, and to restrict or object to its processing. You can ask to receive it in a portable form. Where consent is the basis, you can withdraw it at any time; withdrawing does not affect processing that already happened. You also have the right to complain to a supervisory authority. In the UK that is the Information Commissioner's Office. In the EEA it is the data protection authority of the country where you live, listed by the European Data Protection Board.

If you are in California, and to the extent the California Consumer Privacy Act applies to us, and in any case as a matter of our own practice, you have the right to know what personal information we collect, use and disclose. You also have the right to delete it, the right to correct it, the right to opt out of its sale or sharing, and the right not to be treated differently for exercising any of these. In the twelve months before the effective date of this policy we have not sold personal information and have not shared it for cross-context behavioral advertising, and we do not do so now, so there is nothing to opt out of. In the categories the Act uses, we collect identifiers (your email address, the name and profile image Google reports if you sign in with Google, and session and customer identifiers), the US state or district of residence or business location you declare, commercial information (your plan, purchases and credit ledger), and internet or other electronic network activity (request logs at our host, the workspace you sync, your messages to the assistant). The sources and the providers that receive each are the ones named under What we collect and Who we share it with. We collect no sensitive personal information as the Act defines it and make no inferences about you. You may make a request yourself or through an authorized agent; we will ask the agent for your signed permission and will verify the request with you at the account's email address. The California Attorney General's office explains these rights.

If you are in another US state with a privacy law, such as Virginia, Colorado, Connecticut, Utah, Texas or Oregon, you have comparable rights to access, correct, delete and port your data and to opt out of targeted advertising, sale and profiling with legal effects. We do none of those three, and you can exercise the other rights exactly as described below. If we refuse a request in whole or in part, we tell you why, and you may appeal by replying to our answer with "Appeal" in the subject line. We answer an appeal in writing within 45 days, and if we still refuse we tell you how to contact the attorney general of your state. We do not disclose personal information to third parties for their own direct marketing, so there is nothing to report under California's Shine the Light law.

How to exercise a right. Use the controls in Settings where one exists; that is the fastest route and needs no request. For anything else, email hello@veyora.ai from the email address on your account, or use the matching door on the contact page. We verify a request by confirming it came from the account's own email address; we may send a sign-in link to that address to be sure. We confirm that we received a request within 10 business days and answer within 30 days. If a request is complex or there are several, we may take longer where the law allows it (up to two further months under the GDPR, up to 45 further days under California law); if so we tell you within the first period why and how long we need. We do not charge for a request unless it is plainly excessive, and we will say so before doing anything.

11. How we protect it

We build the product so that the data it holds is hard to reach and easy for you to take away. The measures that matter most:

• Every connection uses HTTPS, with HSTS and a set of security headers that stop the site being framed or loaded from places it should not be.
• Sessions live in the database, not in the cookie alone, so any session can be revoked on the server and stops working on its next request.
• There are no passwords to steal. Sign-in links are single use, stored as a hash, expire after 15 minutes and are carried in the URL fragment, which browsers do not send to servers, so a link never lands in a server log.
• Sign-in and usage counters are stored under a keyed hash (HMAC) of the identifier, so neither an email address nor a network address is stored in them but the service can recompute the pseudonymous keys; they are not anonymous.
• Secrets live only in the deployment environment. Nothing in the code repository holds a key.
• Destructive actions (clearing the cloud workspace, deleting the account) need a sign-in within the last 15 minutes, so a session left open on a shared machine cannot be used to destroy your data.
• Account deletion runs as one atomic operation: either every part of it completes, the restricted archive it writes included, or none of it does.
• We hold no card data. Payment details go to Stripe and never touch our servers.

No method of storage or transmission is perfect, and we do not promise that a breach can never happen. If one does affect you, we tell you without undue delay and as the law requires. If you believe you have found a security problem, please write to hello@veyora.ai with "Security" in the subject line and we will respond.

12. Children may not use Veyora

Veyora is not directed to anyone under 18, and prediction-market trading is not open to them. We do not knowingly collect personal data from a person under 18. If we learn that an account belongs to someone under 18, we delete it. If you believe a child has created an account, email hello@veyora.ai and we will act on it.

13. Changes to this policy

The version number and effective date at the top of this page identify the edition you are reading. When we make a change that affects you, such as a new provider, a new use of data or a new right, we raise the version. We tell you at least 14 days before it takes effect, by email to the address on your account, in the product, or both, the same period the Terms of Service state, except for a change the law requires, which applies when the law does. That notice comes before the change applies so you have time to export or delete your data first. Wording fixes that change nothing about what we do are not announced. Each version carries a one-line note of what changed, shown with the document.

14. Contact

Questions about this policy, requests about your data and anything else go to one inbox. Email hello@veyora.ai from the email address on your account, or use the matching door on the contact page. Put "Privacy" in the subject line and it reaches the right person; the contact page's Privacy door does that for you. Our contact details, including a postal address where one is published, appear below.