What we keep, why we keep it, and the control you have.

This policy explains what personal data Travise collects, why, who we share it with, how long we keep it, and the rights you have over it. Travise is operated as an individual business based in Hong Kong and is the data controller for the account you create with us. Questions or requests go to info@travise.ai .

Advertising, in short

We run ads on Meta and Google, and both of them measure whether those ads work. Here is exactly what that means for you, in one place, because it is the part people most want to know and least want to hunt for.

• If you accept cookies: Meta and Google both learn that you visited Travise and, if you sign up, that you signed up. We also send Google a scrambled one-way version of your email address so it can tell that the person who signed up is the person who clicked its ad. Google cannot turn that code back into your email, and we never send the address itself.
• If you decline: we send Google nothing that can identify you. No cookie is set for advertising, and the scrambled email code is never sent. Google's tag does still load and tells Google that a visit happened and that you declined, which is how it stops guessing about people it cannot see. Meta's pixel does not load at all.
• Either way: what you write in your journal is never used for advertising. Not your trades, not your notes, not how you felt.

You can change your mind whenever you like through Cookie preferences in the footer. The rest of this policy sets out the full detail.

1. The data we collect

We collect the following categories of personal data:

• Account and identity: your email address, a password (stored hashed by our authentication provider), your account id, and, if you upgrade to a paid plan, your Whop user and membership ids.
• Trade content you write: ticker, entry and exit, size, fees, and P&L, plus the free-text fields you fill in: your thesis, notes, self-assessment, expected outcome, and how you felt during the trade.
• Chart screenshots you attach: the image itself, plus the entry and exit points you mark on it. Attaching one sends the image to our model provider so the read can look at the same chart you did.
• Prop-firm account settings: if you trade a funded account, the account size and the firm's rules you enter so the read can grade against them.
• Support messages: what you write to us in the in-app support thread, and our replies. You can also message us before you have an account: in that case we store the email address you give us, so we can reply, and the messages themselves. We do not check whether that address already belongs to an account.
• Data we derive: the Travise read for each trade, the cross-trade behavioral profile we compute from your history, your coaching history, daily reads, chat history, and Mentor Letters.
• Connected broker data: if you link a broker, the encrypted key we use to read from it and the trade and position data we import on your instruction. For brokers connected through SnapTrade that key is a SnapTrade user secret; your broker password is entered on SnapTrade's page or your broker's, and never reaches us. For Interactive Brokers connected directly it is the Flex Web Service token you paste in. We also record when you confirmed the broker-connection notice in our Terms and which version of it you confirmed.
• Technical and usage data: a first-party analytics identifier, session identifier, pages visited, referrer, device viewport, and error diagnostics. We do not store your IP address or your browser's user-agent string alongside these events; your IP is used in the moment to rate-limit abusive traffic and is not written to our analytics records.
• Email engagement: for the emails we send you, whether the message arrived, bounced, or was reported as spam, whether it was opened (measured through a small tracking image your mail app loads, which some mail apps load automatically whether or not you open the message), and whether you used the button in it. We use this to know the letters are landing and to improve them.
• Marketing and campaign data: when you accept non-essential cookies, the Meta Pixel and Google Ads identifiers described in our Cookie Policy, plus the advertising click identifier carried by the link you arrived on (Meta, Google, TikTok and Microsoft each add one), the campaign parameters, the referring site, and the page you landed on. If you go on to create an account, we copy that click identifier and campaign onto your account so we can tell which campaign brought you. If you decline, none of this is collected and no advertising cookie is set. The one thing that still happens is that Google's tag reports the visit with no cookie and nothing that identifies you, as described above.
• A one-way code made from your email, sent to Google: if you accept non-essential cookies and then create an account, we turn your email address into a one-way code (a SHA-256 hash) in your browser and send that code to Google Ads. It lets Google match your signup to the ad you clicked without us handing over your address. The code cannot be turned back into your email. We never send the address itself, we send nothing at all if you decline cookies, and we do not do this for any other company. That rule is stricter than the one for the tag above: Google's own settings would suppress the code for someone who declined, and we do not rely on that. Our own check stops it leaving your browser.
• Account deletion survey: if you delete your account and choose to tell us why, the reason you pick and anything you type in the comment box. Answering is optional and skipping it does not slow the deletion down.
• Waitlist data: if you joined our pre-launch waitlist, your name, email, how you found us, your browser's user-agent string, and a one-way hash of your IP address that we used only to spot spam signups. The unsubscribe link in the confirmation email deletes the entry.

Some of what you write (how you felt during a trade) and what we infer (behavioral patterns) is personal, so we treat it with extra care and never use it for advertising. The notes about how you felt are trading-discipline reflections (for example calm, rushed, or revenge), not health data, so they are not a special category under GDPR Article 9, and we do not collect special-category data. Please do not enter health, biometric, or other special-category information into the free-text fields.

2. How we use it, and our lawful basis

We process your data for these purposes:

For analytics and the Meta Pixel, what happens depends on where you are. In the EEA, the UK, and Switzerland (and anywhere we cannot determine your region), neither one loads until you accept in the consent banner. Elsewhere, including the United States, we show a notice and they run unless you opt out; rejecting in the banner or the footer's Cookie preferences stops them. We honor the Global Privacy Control signal as an opt-out everywhere, and an explicit choice you make in the banner always wins over the regional default. Nothing in this area runs on our legitimate interests: if you decline, our analytics and the Meta Pixel both stay off, and the only first-party work that continues is the security, abuse prevention and error monitoring that never needed those cookies.

The Google Ads tag is the one exception, and we would rather say so than bury it. It loads wherever you are, with every advertising permission switched off until you accept. Declining keeps it switched off: no advertising cookie, no scrambled email code, and nothing that identifies you. What Google still receives is that a visit happened and that permission was refused, which is how it estimates the results of its ads without tracking the people who said no. Accepting turns the permissions on. This is the setup Google calls consent mode, and we chose it on 17 August 2026 so that declining costs you your privacy and not our ability to count.

Email works stream by stream, and the table above splits it that way on purpose. The weekly Mentor Letter is the thing you signed up for rather than a marketing message, so it goes out on our contract with you and stops the moment you switch it off. The daily read, the comeback read, the monthly ledger, the reminder to log your first trade, and product news each need the consent you give at signup, and each has its own switch in Settings on every plan, including the trial. One email is different from both: if you cancel a paid plan, we send a single note about what you built and how to return. That one rides our legitimate interest in winning back a former subscriber, which the law allows for someone who has bought from us before, and it carries an unsubscribe link like everything else. Every message we send has one.

We also produce aggregate, de-identified statistics from what happens across the platform, and our Terms let us keep and publish those. They describe patterns across many traders, never you. We commit publicly that we will not try to re-identify anyone from them, and anyone we give them to is barred from trying. We do not sell your personal data, and this does not change that.

3. Who we share it with

We do not sell your personal data. We share it with the service providers that run Travise (our sub-processors): our hosting, database and authentication provider, our email provider, our error monitoring provider, our broker-data aggregator (SnapTrade) and, for Interactive Brokers, its Flex Web Service, the messaging service that alerts our team to events we need to respond to, and the third-party model provider (Anthropic) that generates the read from your trade notes. The full list, with what each receives and where it is located, is on our sub-processors page. Each processes this data only on our instruction. Most are covered by a data-processing agreement that forms part of the provider's standard terms; where a provider asks us to accept or sign one separately, we are working through those, and we will not keep sending your data to a provider that refuses one.

4. International transfers

Travise is operated from Hong Kong and almost all of our providers are based in the United States, so your data is processed outside the UK and EEA. For those providers the transfer relies on the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum), and on the EU–US Data Privacy Framework where the provider is certified.

One provider is not in the United States, and we would rather name it than round it off. Our team alerts run through Telegram, operated from the United Arab Emirates, which is not a country the European Commission has found to offer adequate protection. Those alerts carry your email address, the ticker, direction and result of a trade you log, your plan, the campaign you signed up from, and, if you write to support, a short excerpt of your message. That transfer rests on Standard Contractual Clauses and on our own assessment of the risk, and it is the transfer we are working hardest to shrink: our intent is to cut these alerts back to an account reference and a link, so that nothing identifying you leaves for that destination at all. Until that lands, this is what happens, and you can ask us to keep your data out of those alerts by writing to info@travise.ai .

Across every destination we apply the same supplementary measures: encryption in transit, encryption at rest for your broker credentials, redaction of error diagnostics, and minimizing what each provider receives. Our market-data provider gets only tickers and dates and never your identity, and the model provider that writes your read receives your trade text and figures with your account id and email stripped out before the request leaves us.

5. How long we keep it

We keep your trades, reads, profile, and the rest of your account data for as long as your account is active. Those are the service, so they run on your account rather than on a timer. Everything else has a fixed life:

• Raw analytics events: about 13 months. Aggregate, non-identifying statistics are kept longer.
• Records of our own model usage (which feature ran, token counts, and cost, tied to your account id): about 13 months.
• Billing webhook logs: 30 days.
• Email delivery webhook logs (the raw delivered, opened, bounced, and spam-report events from our email provider): 30 days. The per-letter stamps derived from them live with your account and go when it goes.
• Security records (failed sign-in attempts, and any time a member of our team views your account): failed sign-ins for 90 days, the rest for about 13 months. Identifiers in them are one-way hashed rather than stored in the clear. That hashing stops a casual reader of the table from learning who a row is about; it is not a guarantee that the value could never be worked back to, so we treat the table as sensitive rather than as anonymous.
• The campaign and click identifier we copy onto your account: kept for the life of the account, because it is what tells us which campaign brought you. It goes when the account goes.
• Support conversations from people without an account: about 13 months after the last message. If you later sign up with the same address, those messages become part of your account's history and are deleted with the account instead.
• Error diagnostics: our monitoring provider's retention.
• Waitlist entries from before launch: kept until you use the unsubscribe link in the confirmation email, which deletes the entry. The waitlist is closed and takes no new entries, and these rows have no automatic expiry today. Ask us at info@travise.ai and we will remove yours.
• The team alerts described in section 4: those messages stay in our team's message history at Telegram. We cannot put a deletion timer on that history, which is the second reason we want to stop sending anything identifying to it.

Two things deliberately outlive your account, and both are one-way hashes rather than anything readable. We keep a hashed record that an account with your email address once existed, how many free reads it used and whether it ever started a free trial, so that deleting and re-registering cannot hand out a fresh set of free reads or a second free trial; and if you answered the deletion survey we keep the reason you picked, with anything you typed erased. Neither can be read back to your email address by looking at it. Beyond those, after you delete your account, residual copies may remain in our providers' encrypted backups until those roll off on their normal schedule.

6. Your rights

You can access, correct, export, delete, restrict, or object to our processing of your data, and withdraw consent at any time. You also have the right to complain to a supervisory authority. If you are in Hong Kong, that authority is the Office of the Privacy Commissioner for Personal Data (PCPD); in the EEA or the UK, you can complain to your local data protection authority (the Information Commissioner's Office in the UK).

• Access and portability: download your data from Settings → Download my data. The file covers your account, trades, reads, profile, coaching history, chat, support messages, letters and broker links, in a machine-readable format. Two things are not in it: chart screenshots export as their details rather than the image files, and the security records described in section 5 are held back because a single row can involve someone other than you. Email info@travise.ai and we will send you either one, including the record of any time our team viewed your account.
• Erasure: Settings → Delete my account starts a 30-day wind-down. We cancel your subscription straight away and lock the account, so it can no longer be used, and we email you the date your data is erased. During those 30 days you can restore the account yourself and pick up where you left off, and you can still export your data. On day 31 it is erased for good. If you would rather not wait, say so at info@travise.ai and we will erase it immediately, with no waiting period. Either way, the survey we ask on the way out is optional and skipping it changes nothing. Section 5 describes the two hashed records that survive.
• Correction: edit your trades, name, and email in the app.
• Withdraw consent: use Cookie preferences in the footer for cookies, and the unsubscribe link or Settings → Subscription for email (the Mentor Letter, daily read, and product news each have their own switch, on every plan including the trial).
• Restriction and objection: to restrict processing, object to it, or correct something you cannot edit in the app, email info@travise.ai and we will handle it directly.

We respond to rights requests within one month, as the law allows.

7. Automated analysis and profiling

Travise reads your trades automatically and builds a behavioral profile of your patterns. This is decision support for you, the trader. It is not financial advice, and it does not make decisions that produce legal or similarly significant effects about you. You stay in control of every trading decision. Because every trading decision stays with you and the read has no legal or similarly significant effect on its own, this is not the solely automated decision-making that GDPR Article 22 restricts. You can ask how a read is produced, and you can stop using it at any time.

Reads, letters, the daily read, the first-five-trades diagnostic, and chat answers are AI-generated. Each of those surfaces, and every email that carries one, is labeled “AI-generated” in the product, as EU AI Act Article 50 requires.

8. Children

Travise is not for anyone under 18. We do not knowingly collect data from children.

9. Cookies

Essential cookies run Travise and are always on. Everything else, which means our own analytics and the Meta advertising cookies alike, sits behind a single choice: accepting in the banner turns all of them on and rejecting turns all of them off. We do not split them into separate switches today, so declining costs you nothing you would have wanted. See the Cookie Policy for the full list and use Cookie preferences in the footer to change your choice.

10. California privacy rights

If you are a California resident, you have the right to know, access, correct, and delete your personal information, and to opt out of the "sale" or "sharing" of it. We do not sell personal information. We do treat the Meta Pixel as "sharing" for cross-context behavioral advertising, because Meta uses what it receives for its own advertising rather than only on our instruction. Reject in the consent banner, or use Cookie preferences in the footer, and that sharing stops. We do not need a separate "Do Not Sell or Share" link because we honor the Global Privacy Control signal as an opt-out, which the law accepts in its place.

We honor the Global Privacy Control browser signal as an opt-out from cookie-based analytics and sharing. We do not respond to legacy "Do Not Track" browser signals, which never became a standard; Global Privacy Control is the signal we act on.

11. Changes

We will update this policy as Travise changes and post the new effective date here. We will tell you about material changes by email or an in-app notice.

12. Contact

Reach us at info@travise.ai . Travise is based in Hong Kong. If you are in the EEA or the UK, you can contact us directly at that address about your data; where the law requires us to designate a local representative, we will name them here.