Privacy Policy
Last updated: November 19, 2026
1. Who We Are
This Privacy Policy explains how Kavrn LLC, 30 N Gould St, STE R, Sheridan, WY 82801, USA ("Qotify", "we", "us", "our") collects, uses, shares, and protects personal data when you visit our website, create an account, or use the Qotify service: a web app for building rule-based trading bots that trade in a simulated account and, if you choose, place real orders through your own connected broker or exchange account (collectively, the "Service"). You must be at least 18 years old to use the Service.
For the purposes of the EU General Data Protection Regulation ("GDPR") and the UK GDPR, Kavrn LLC, 30 N Gould St, STE R, Sheridan, WY 82801, USA is the "controller" of personal data described in this Policy. You can reach us at the email address given in section 15 (Contact).
2. Data We Collect
2.1 Account data
- Email address, provided when you sign up with email and password, or fetched from your Google account when you sign in with Google.
- Display name and profile image, only if returned by Google sign-in.
- Password hash, for email/password accounts. We never store the plain password; it is hashed by the Better Auth library before storage.
- Google sign-in tokens, access and refresh tokens issued by Google, used only to verify your identity at sign-in.
- Account state, language, the country used for pricing, the referral or partner code that brought you (if any), timestamps for terms acceptance, account creation and updates, and the last in-app notification you saw.
2.2 Bots and their activity
- Bots, the name, look, rules, watched symbols, risk settings and status of each bot you create, and the bots you copied from the ranking.
- Decisions and simulated trades, each scheduled check, the market prices it used, the decision and its reason, and the simulated orders, positions and balance of each bot.
- Backtests and scheduled tasks, the backtests you run and the tasks you schedule for your bots.
- Bot reviews, whether you turned on email reviews, their frequency, your time zone and preferred hour, and a record of each review sent.
2.3 Chat messages and usage
- Messages, what you write in the setup chat and in each bot's chat, the AI's replies, and the changes it proposed and whether you applied them. This includes any strategy or paper you paste into a chat, and the text read from a PDF you add. The PDF is read on your device and the file itself is not uploaded.
- Usage metering, the amount of AI processing (tokens) each message used, so we can show your usage as a percentage, and when you last bought a usage reset.
- Questions on our website, if you use the question box on our marketing site, the question you type and the answer.
- Feature requests, if you ask the setup chat to send a request to our team, the summary of what is missing, your own words if you add any, your account, email address, name and language, and where you asked. We store the request and email it to our team.
2.4 Connected trading accounts and real orders (optional)
If you connect a trading account on the Integrations page, we store the platform, whether it is a practice or real account, the account identifier the platform reports (or a fingerprint of your key), any name you give it, the connection status, any error type and the dates, and the API key or token you enter. The key is encrypted with AES-256-GCM before it is stored, is never sent back to your browser, and is only decrypted to make a request to that platform for you. With that key we read the account's balance, positions and working orders when you test the connection and while a live bot runs.
If you switch a bot to live, we also record the limits you set, when you confirmed the risks, and a journal of each real order: the bot, symbol, side, amount and quantity, the reason, the order we sent, the platform's order number, status, fills and response, and any failure with its reason. The platform you connect receives your key and orders and handles your account under its own privacy policy.
When you disconnect a trading account, we erase the stored key and mark the connection as revoked. The connection record and the order journal stay, because they are the record of what was sent. Disconnecting does not cancel the key at the platform: delete it there too.
A "Create an account" link on the Integrations page can be a referral link, and Qotify may earn a commission. The platform receives your visit under its own privacy policy.
Separately, Settings may offer a read-only link to an Alpaca paper account. You sign in on Alpaca's own page and authorize Qotify there. We never receive your Alpaca password, and no bot can place orders through this link. We read your account record when you open Settings, to check that the link still works, and we do not store what we read. We store your Alpaca account identifier, the connection dates and the access token Alpaca issues to us, encrypted with AES-256-GCM. Disconnecting in Settings deletes the token and record. It does not by itself withdraw the authorization at Alpaca: you can also revoke Qotify's access there, and you can ask us to delete any remaining data (section 9).
2.5 Subscription and billing data
Payment is processed by our payment provider, Whop. We never see or store your full card number, CVV, or banking details. From Whop we receive the membership and payment identifiers, the plan or product bought, the subscription status, and the current period end date: enough to grant and revoke access and to record purchases such as usage resets. Whop runs the checkout form and may ask for other details, such as a phone number; we do not store that number. On the first payment of a bot plan we read the billing country from Whop, compare it with the country the price was set for, and send that comparison to PostHog with the membership identifier and no person profile. This measures our pricing and changes no price.
2.6 Screenshots in chats
If you add a screenshot in a chat, we upload it to our file storage and an AI vision model reads it. A chart, order ticket or exchange screen becomes a written reading and proposed rules, which are kept as chat messages. The uploaded image is held in temporary storage and swept after about a day.
A screenshot of a prediction market or a bet is no longer analysed. The market analysis that used to read them is retired: the conversations and screenshots it collected are deleted under the 30-day retention described in section 8. A record of each analysis (the market, its prices and the call made, without images or messages) is kept to measure accuracy; it contains no contact details and is unlinked from your account if you delete it.
2.7 Technical and session data
- Session tokens, IP address, and user agent, created and stored when you sign in, to authenticate later requests and detect abuse.
- Pricing signals, to set your price: the country our hosting provider derives from your IP address, your browser's language setting, which can raise a price but never lower it, and a check for VPN, proxy or hosting networks. For that check we send your IP address to proxycheck.io, and we store the address and the result in our database, reusing the result for 30 days.
- Server logs, short-lived logs of requests, kept for operational and security purposes.
2.8 Cookies, analytics and your privacy choices
- Session cookie, set by Better Auth to keep you signed in. Strictly necessary.
- Privacy choice, a cookie shared by www.qotify.io and app.qotify.io, plus a copy in your browser's local storage, that remembers your choice in our consent banner for 1 year.
qotify_locale, remembers your language.qotify_country, remembers the country used for pricing (30 days).qotify_ref, records the referral link that brought you, so the referral can be credited (30 days). It grants nothing.qotify_creator_code, carries a partner join code through sign-up.qotify_alpaca_oauth, a 10-minute cookie that protects the Alpaca connection step.- Product analytics, cookies set by PostHog to measure how the Service is used: events, page views and heatmaps.
- Session recordings (see below): PostHog session recordings, which mask all text inputs (including email and password) and exclude the payment form.
- Whop pixel (see below), a script from our payment provider, Whop, that records page views in the app and a browser identifier so that Whop can link a checkout to the visit that led to it (attribution). Whop receives your IP address, browser information and the pages you view in the app.
What runs without consent. Basic product analytics in PostHog (events, page views, heatmaps), Umami (cookieless traffic measurement) and Sentry error reporting run without asking, to understand how the Service is used and to fix problems.
Session recordings and the Whop pixel. In the European Economic Area, the United Kingdom and Switzerland, they run only after you click Accept in our consent banner. If you decline, they stay off. Elsewhere, they are on by default, and you can turn them off at any time from Privacy choices, linked in the footer.
Global Privacy Control. If your browser sends a Global Privacy Control (GPC) signal, wherever you are, we treat it as a decline and as a request to opt out of the sale or sharing of your personal information for that browser. Session recordings and the Whop pixel then stay off, and they cannot be turned on from that browser.
Changing your choice. Your choice is kept for 1 year. You can change it at any time from Privacy choices, available on every page. To limit basic analytics as well, you can block cookies and scripts in your browser, or write to us at the email address given in section 15 (Contact) and we will delete the analytics data linked to your account.
We do not use advertising or cross-site tracking cookies, we do not run advertising networks on the Service, and we do not sell your personal data or share it for advertising.
3. How We Use Your Data
We process the data described above for the following purposes:
- Provide the Service, authenticate your account, run your bots on schedule, fetch market data, record simulated trades, run backtests and scheduled tasks, generate chat replies, show the ranking, and, if you connect a trading account, maintain that connection and send the real orders of the bots you switch to live.
- Process payments and manage subscriptions, verify your subscription status, react to renewal, cancellation and past-due events from Whop, and apply usage resets.
- Meter usage, measure AI usage against your allowance.
- Operate, secure, and improve the Service, investigate bugs, prevent fraud and abuse, and improve product quality.
- Improve default strategies: we analyse bots' settings and their simulated results, combined across many users and without identifying anyone, to improve the default bots, presets and suggested settings we offer. We never publish or sell individual results, and we never use your data to trade for ourselves.
- Communicate with you, send password-reset emails, bot reviews if you turned them on, and messages about your account or payments.
- Comply with legal obligations, keep records as required by applicable law, respond to lawful requests, and enforce our Terms.
4. Legal Bases (GDPR)
If you are in the EU, EEA, or UK, we rely on the following legal bases under Article 6 GDPR:
- Performance of a contract (Art. 6(1)(b)), to deliver the Service you signed up for, including your account, bots, chat, the trading accounts you connect, the real orders your live bots send, subscription management, and customer support.
- Legitimate interests (Art. 6(1)(f)), to secure the Service, prevent abuse, set local prices and check for VPN, proxy or hosting networks, debug issues, measure usage and pricing, and improve product quality. We balance these interests against your rights and freedoms.
- Legal obligation (Art. 6(1)(c)), to comply with applicable law (e.g., tax, accounting, lawful requests).
- Consent (Art. 6(1)(a)), for optional features that require it, such as bot review emails, session recordings and the Whop pixel (section 2.8). You may withdraw consent at any time.
5. AI Model Processing
When you add a screenshot in a chat, we send the image to AI providers through OpenRouter to read it. This processing uses models from Google and OpenAI. Do not upload images containing personal or confidential information you do not want shared with these providers.
To answer you in the setup chat and in a bot's chat, we send your message, including any strategy you paste or the text of a PDF you add, the recent conversation, and the facts the reply needs (the bot's rules, its saved notes, recent decisions and market data) to third-party AI providers through OpenRouter, our gateway. Questions typed on our marketing site are sent the same way. The models currently used come from DeepSeek and Google. Models from OpenAI are used as a fallback for the setup chat and for questions on our website when the main model is unavailable. These providers therefore receive the content of those chats. We may change providers or models to improve quality and will update this list when we do.
The AI provider processes this data to return a reply to us. We do not authorise the use of your messages to train models. OpenRouter and each provider also apply their own data policies, under which a provider may keep data for a limited time, for example to detect abuse. Please do not put information in a chat that you do not want sent to these providers.
To label news for the news filter, we send headlines from Alpaca News to a Google model through OpenRouter. Headlines are third-party text and carry nothing about you.
AI outputs are generated automatically and may be incorrect, incomplete, or biased. They explain your bot's decisions but do not make them. See our Terms of Service and Risk Disclosure for the full disclaimer.
6. Sharing of Personal Data, Sub-Processors
We do not sell personal data. We share data only with the following recipients, each acting as a processor on our behalf unless stated otherwise:
- Cloudflare, application hosting (Workers), database (D1), file storage (R2) and email sending.
- Vercel and Neon, our hosting and database providers until October 2026. The Service no longer runs on them, but they may still hold data from that time until we delete it.
- OpenRouter and the underlying AI providers (currently DeepSeek, Google and OpenAI), AI replies and screenshot analyses. They receive the data needed for the processing described in section 5.
- Alpaca, market data and news for every bot, and, if you connect your account, the connection itself. Alpaca is your broker and handles your brokerage account data under its own privacy policy. We request market data and news by symbol, with nothing about you.
- cTrader and your broker, only when you connect a cTrader account. We process the account identifiers, broker name, demo or live status, available symbols and prices needed for your bots. Authorization tokens are encrypted on our servers. Access is read-only. We do not request order or withdrawal permissions through this connection. cTrader and your broker process data under their own policies.
- Twelve Data, forex and spot gold and silver prices, when forex is available on your account. We request prices by symbol, from our servers, with nothing about you.
- The trading platforms you connect (Alpaca, Tradier, OANDA, Binance, Coinbase Advanced, Kraken, Bybit, OKX, KuCoin, Bitget or Gate.io), only if you connect one. They receive your key and your bots' orders and act as independent controllers under their own policies.
- proxycheck.io, the VPN, proxy and hosting network check, which receives your IP address.
- SEC EDGAR, the US public filings database, which is not our processor. We request public filings by company, with nothing about you.
- Whop, checkout, subscription management, payment processing, billing communications to you, and the Whop pixel described in section 2.8.
- Google, only if you choose to sign in with Google.
- PostHog (EU region), product analytics, the billing-country comparison in section 2.5 and masked session recordings (section 2.8).
- Umami, cookieless website-traffic analytics.
- Sentry, error monitoring and performance.
Other Qotify users see each bot in the ranking with its name, look, method, number of watched symbols and simulated results, never your name or email. A user who copies a ranked bot receives a copy of its rules.
We may also disclose personal data: (a) to comply with a legal obligation, court order, or lawful request; (b) to protect the rights, property, or safety of Qotify, our users, or others; or (c) in connection with a merger, acquisition, or sale of assets, in which case we will require the acquirer to honour this Policy.
7. International Data Transfers
The processors listed above are based in or operate from the United States and other countries outside the EU/EEA/UK. When we transfer personal data outside the EU/EEA/UK, we rely on appropriate safeguards permitted under applicable law, such as the European Commission's Standard Contractual Clauses, the UK's International Data Transfer Addendum, or equivalent mechanisms. You may request a copy of the relevant safeguards by contacting us.
8. Data Retention
- Chat messages with your bots are automatically deleted 30 days after they are written. Conversations and screenshots from the retired screenshot analysis tool are deleted 30 days after they were created, including the files on Cloudflare R2.
- Bots, decisions, simulated trades and settings are kept while your account exists.
- Your connected-account keys and Alpaca access token are kept until you disconnect or delete your account. Records of real orders and connections are kept while your account exists, including after you disconnect an account or delete a bot, and longer where the law requires.
- IP checks (an IP address and its VPN result) are deleted by a daily cleanup once they are more than 30 days old.
- Feature requests are kept until we delete them or you ask us to.
- Uploaded chart screenshots in temporary storage are swept after about a day.
- Account data (email, name, password hash, subscription state) is kept while your account exists. If you ask us to delete your account, we delete or anonymise account data without undue delay, except where retention is required by law (e.g., accounting records).
- Server logs and security telemetry are kept for a short period (typically a few days to a few weeks) and then deleted or aggregated.
- Payment and billing records are kept by Whop and by us for as long as tax, accounting, and consumer-protection law requires (typically up to 10 years in the EU).
9. Your Rights
Subject to applicable law, you have the following rights regarding your personal data:
- Access, request a copy of the personal data we hold about you.
- Rectification, correct inaccurate or incomplete data.
- Erasure ("right to be forgotten"), ask us to delete your account and data, subject to legal retention obligations.
- Restriction, ask us to limit how we use your data while a request is being resolved.
- Portability, receive your data in a structured, commonly used, machine-readable format.
- Objection, object to processing based on legitimate interests.
- Withdraw consent, at any time, for processing based on consent.
- Complain, lodge a complaint with your local data-protection authority (in France, the CNIL,
cnil.fr).
To exercise any of these rights, including deleting your account or receiving a copy of your data, write to us at the email address given in section 15 (Contact), from the address associated with your account. You can disconnect a trading account yourself on the Integrations page once no live bot holds a position there, disconnect Alpaca in Settings, and change your tracking choices at any time from Privacy choices (section 2.8). We will respond within the timeframes required by applicable law (one month under the GDPR, extendable by two further months for complex requests).
10. California and Other US State Privacy Rights
California residents have specific rights under the California Consumer Privacy Act (CCPA), as amended by the CPRA, including the right to know what personal information we collect, to delete personal information, to correct inaccurate information, to opt out of the sale or sharing of personal information, and not to be discriminated against for exercising those rights. Residents of other US states may have similar rights under their state's law.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law. We treat a Global Privacy Control signal as a request to opt out of sale and sharing for the browser that sends it (section 2.8). You can also opt out at any time from Privacy choices or by writing to contact@qotify.io with the subject "Privacy opt-out".
To exercise your rights, contact us at the email address given in section 15 (Contact). We will verify your request using the email address on your account. You may use an authorized agent where the law allows it.
11. Security
We use administrative and technical safeguards designed to protect your personal data, including encrypted transport (HTTPS/TLS), hashed passwords, encryption of brokerage access tokens and connected-account keys (AES-256-GCM) before storage, scoped access keys, and restricted access to production systems. No method of transmission or storage over the internet is 100% secure; we cannot guarantee absolute security. If we become aware of a personal data breach affecting your data, we will notify you and the competent authorities as required by applicable law.
12. Children
The Service is not directed to children. You must be at least 18 years old (and of the age of majority where you live, if higher) to use Qotify, in line with our Terms. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us so we can delete it.
13. Automated Decision-Making
Your bots make automated decisions about simulated trades by following the rules you set or approve. If you switch a bot to live, it sends orders to your connected account automatically, at your direction and within your limits. These are decisions you instruct, not decisions about you. We do not use your data for automated profiling that produces legal or similarly significant effects on you within the meaning of Article 22 GDPR.
14. Changes to This Policy
We may update this Policy from time to time. The "Last updated" date at the top reflects the most recent revision. For material changes, we will take reasonable steps to inform you (for example, by email or an in-app notice) before the change takes effect. Continued use of the Service after the effective date constitutes acceptance of the updated Policy.
15. Contact
Qotify is operated by Kavrn LLC, 30 N Gould St, STE R, Sheridan, WY 82801, USA, the controller of your personal data.
For any privacy question, request, or complaint, email contact@qotify.io. Please include the email address associated with your Qotify account so we can locate your records.