Privacy Policy

The rest of this policy explains exactly what that means in practice — what we hold, who touches it, how long we keep it, and how to exercise your rights.

Chronvel is a sole proprietorship established in Quebec, Canada, and is not incorporated. We are the party responsible for your personal information — the “controller” in European terms, and the “person carrying on an enterprise” under Quebec law.

This policy covers:

• the marketing site at chronvel.com;
• the Chronvel application at app.chronvel.com; and
• the transactional emails we send you about your account.

It does not cover third-party sites we link to. Our Terms of Service govern your use of the Service.

Privacy questions, requests, and complaints: privacy@chronvel.com. See section 11 for our Privacy Officer.

Account information

• Your email address.
• Your password. Sign-in is email and password only — there is no sign-in with Google or Apple, and no magic-link sign-in, so no third-party identity provider learns that you use Chronvel. Passwords are stored in hashed form by our authentication provider; we never see or store your password in readable form.
• Account creation date, plan, trial status, and subscription state.
• Plan selection. If you reached the signup form from a pricing link, the plan you selected is stored with your account so we can preselect it later. It records a preference only, and does not affect your price, your plan, or what you have access to.

We do not ask for your name, address, phone number, or date of birth to open an account.

The journal data you create

This is the substance of the product, and all of it is entered by you or derived from what you entered:

• Trades — instrument, direction, session, entry method, R multiple, profit and loss, timestamps, your execution rating, and the mistake tags you apply.
• Notes — anything you write in trade notes, day notes, and the day modal.
• Backtests and playbooks — paper trades, strategy names, and the results and reports generated from them.
• Habits and readiness — the sleep, mind, body, and market-context inputs you log, the readiness score calculated from them, and your streaks.
• Rituals — the rituals you define and your completion records.
• Calendar and dashboard entries — daily records and the analytics derived from them.
• Screenshots — images you attach to live trades and to backtest trades. These are held in private Supabase Storage buckets, not public ones, and are served only through time-limited signed URLs. They are never sent to our AI provider.

Some habit inputs — sleep in particular — describe your physical and mental state. You enter these by hand, and every one of those fields is optional. There is no wearable integration. We do not connect to Whoop, Oura, Apple Health, Garmin, or any other device or health service, and we receive no health data from any third party.

AI Coach conversations

If you use the AI Coach, we store your messages and the responses in your account so the conversation persists. See section 6 for exactly what is sent to our AI provider.

Technical and usage information

• Server and hosting logs generated automatically when you use the Service: IP address, browser and device type, pages or endpoints requested, and timestamps. These come with operating any web service and we use them for security, abuse prevention, and debugging.
• No product analytics. We have no Google Analytics, no Vercel Analytics, no PostHog, no Plausible, and no advertising or social pixels. Nothing counts your pageviews, measures your sessions, or scores your engagement. If we add anything of that kind, we will update this policy first.
• Error tracking, through Sentry. This is the only telemetry we run, and it reports solely when something breaks. The next subsection sets out every field it sends.

Error tracking (Sentry)

Each error report contains:

• The error type and message, with anything email-shaped redacted before it is sent.
• The stack trace — file paths, line and column numbers, function names, and the original source lines of our own code.
• The route the error happened on, path only; query strings are stripped. Record IDs can appear in a path, so a report may contain something like /backtesting/<id>.
• The HTTP method, for errors that happen on our server.
• The user-agent header, from which your browser, operating system, and device model are derived — a report may name the handset you were using, for instance.
• An approximate location: your city and country. Sentry derives this from the IP address your device connects with, and stores the result alongside the error. It is city-level — a place name and a country, never a street address, coordinates, or anything from your device’s location services.
• Your account ID — a UUID — if you were signed in. Never your email or your name.
• The environment and release identifier, so we know which build failed.
• Up to 20 breadcrumbs leading up to the error: page navigations, path only, and network requests by method, status code, and path. Never request bodies. Because a request path names the resource being queried, a breadcrumb can reveal which kind of record was involved — a path such as /rest/v1/user_subscriptions names the table. It carries no row data and no query parameters, and sensitive paths are filtered out before sending.
• For server-side errors only: the Node version and the server’s operating system.

Sentry never receives:

• No session replay, performance tracing, or profiling. None of those features are enabled.
• No console output, and no capture of your clicks or keystrokes.
• No request or response bodies, no cookies, no authorization headers, and not your session token.
• Not your email address, your name, or a username.
• Nothing from your browser’s local storage.
• No trade, habit, ritual, note, or journal content of any kind.

Error reports travel to our own domain first and are forwarded to Sentry from our server, rather than going straight there from your browser — the data and the recipient are identical either way, but it means a content blocker cannot silently discard a crash report before we ever see it.

Billing information

Billing is not live yet, and no payment details are being collected today. When it goes live, payments will be processed by Stripe. Stripe will receive your payment card details directly; we will never receive or store your full card number. We will hold only what we need for accounting: your subscription status, invoices, transaction amounts and dates, billing country, and the card brand and last four digits.

Correspondence

If you email us, we keep the correspondence so we can deal with your request and keep a record of it. Mail sent to our addresses is routed by Cloudflare and held in a Google-hosted mailbox, so both companies process whatever you put in an email to us — including the contents of an access or deletion request. Both are listed in section 6.

What we deliberately do not collect

• No demographic data — we never ask your age, gender, income, occupation, ethnicity, or household details.
• No broker or exchange credentials. Chronvel never connects to your brokerage account.
• No advertising identifiers, cross-site tracking, or data purchased from third parties.
• No precise geolocation. We never ask for or receive your device’s location, GPS coordinates, or anything from its location services, and the product has no feature that uses your position. The one exception is coarse and indirect: a crash report carries an approximate city and country worked out from your IP address, as described above.
• No audio recordings and no voice notes. The app plays audio as part of rituals; it has no recording capability and captures nothing from your microphone.
• No biometric identifiers.

Where we rely on legitimate interests, we have considered the effect on you and use the least information that achieves the purpose. Where we rely on consent, you can withdraw it at any time — for the wellness fields, by leaving them blank or clearing them; for the AI Coach, by not using the feature. Withdrawing consent does not affect processing that already took place.

• We do not sell or rent your personal information, and we do not share it for advertising, cross-context behavioural advertising, or any commercial purpose of a third party.
• We do not use your journal data to train, fine-tune, or evaluate AI models — ours or anyone else’s. Our AI provider does not use it to train its models either, under the commercial API terms we are on.
• We do not build advertising or marketing profiles about you.
• We do not disclose your journal data to brokers, prop firms, exchanges, employers, or anyone else.
• We make no decisions about you by automated means alone that produce legal effects or otherwise significantly affect you. The analytics and AI Coach produce observations and suggestions for you to read; every decision remains yours.

We are a small operation and rely on outside service providers to run the product. Below is the complete list of those that process personal information on our behalf. Each acts on our instructions under a written agreement, receives only what its function requires, and may not use your data for its own purposes.

About the AI Coach specifically

When you send a message to the AI Coach, it is processed by Anthropic PBC. Requests are made from our server — your browser never contacts Anthropic directly. This is the exact payload:

Sent to Anthropic

• Your new message and the last 20 messages of the conversation.
• Trade data: trade dates and times, R values, and execution ratings.
• Daily journal entries: lifestyle score, hours of sleep, whether you flagged the day as rushed, stress, pre-session anxiety, emotional baseline, and your non-negotiables note.
• Ritual session data: completion times, psychological focus, focus grade, and audio completion.
• Analytics card state.

Not sent to Anthropic

• Your email address, your user ID, and your name.
• Your entry, stop, and exit prices.
• The symbols or instruments you trade.
• Your position sizes and your profit and loss in currency terms.
• Your broker or account names.
• Any screenshot or attachment.

In other words, the Coach sees the shape of your performance and your state, not what you traded, at what price, for how much, or with whom.

If you would rather none of this reached an AI provider, do not use the AI Coach. Every other part of Chronvel works without it, and nothing is sent to Anthropic unless you use the feature.

Other disclosures

Beyond those providers, we disclose personal information only where:

• the law requires it — a valid court order, subpoena, warrant, or lawful demand from a competent authority. We disclose the minimum required, and we will tell you unless we are legally barred from doing so;
• it is necessary to establish, exercise, or defend legal rights, or to prevent fraud or a serious threat to someone’s safety; or
• the business is reorganised, incorporated, or sold, in which case any successor is bound by commitments no weaker than those in this policy, and we will notify you before your data is transferred.

Your journal is stored in the United States. Our database and file storage are hosted in Supabase’s US East 2 region, in Ohio, and our other providers are established mainly in the United States too. So your personal information is stored and processed outside Quebec, and outside the European Economic Area and the United Kingdom.

Quebec. Before communicating personal information outside Quebec, Law 25 requires us to assess whether it would receive adequate protection, taking into account the sensitivity of the information, the purpose, the protections in place, and the legal framework of the destination. We carry out that assessment, and the transfer proceeds only under a written agreement.

EEA and UK. Transfers rely on the European Commission’s Standard Contractual Clauses, together with the UK International Data Transfer Addendum for UK transfers. Where a provider is also certified under the EU–US Data Privacy Framework or its UK extension, we rely on that certification in addition. We do not rely on the EU–US Privacy Shield, which was invalidated in 2020 and has no legal effect.

You can ask us for details of the safeguards applying to a particular transfer by emailing privacy@chronvel.com.

Chronvel sets no cookies — not on this site, and not in the application. Our hosting providers may set their own infrastructure cookies where one is needed to route, serve, or protect a request; those are operational, not analytical, and we neither read them nor use them to identify you.

chronvel.com — this marketing site

This site writes nothing to local or session storage, runs no analytics, carries no error tracking, and loads no tracking pixels or third-party scripts. Our fonts are served from our own domain rather than fetched from Google, so simply reading these pages does not contact a third party. The error tracking described in section 3 runs in the application only, not here.

app.chronvel.com — the application

The application uses your browser’s local storage rather than cookies. Here is the complete list of what it writes there.

• chronvel_tags_v2 — trade tags you have created.
• chronvel_date_filter — the date range you last set on the Trades page.
• chronvel_trades_page_size and chronvel_backtest_page_size — how many rows you want per page.
• chronvel_context_tags_custom — custom context tags in the daily lifestyle block.
• chronvel_settings_enable_macros — whether macro tracking is switched on.
• chronvel_analytics_preview_mode — whether analytics is showing sample data.
• chronvel_sidebar_collapsed — whether your sidebar is collapsed.
• chronvel_info_banner_<name> — whether a given info banner is expanded.
• chronvel:coach-conv-start:<userId> — the timestamp your current Coach conversation began.
• chronvel_backtests_migrated_for_user:<userId> — a one-time flag recording that your backtests have been uploaded.
• chronvel_plan_intent — records which plan you selected on our website before creating an account, so the correct plan is preselected when you subscribe. Set only if you arrive from a pricing link. Unlike the preferences above, this one is short-lived: it is removed automatically once used, and you can clear it with your browser data at any time.

Every one of those is a preference or a piece of local state. None of it identifies you to anyone, and none of it is tracking.

Legacy keys from earlier versions

The app reads but never writes three keys left by earlier versions: chronvel_instruments_v2, chronvel_backtests_v1, and chronvel_backtest_trades_v1. Four more are dormant, from a much older local-only version that stored your journal on your own device: chronvel_accounts_v2, chronvel_strategies_v2, chronvel_trades_v2, and chronvel_initialized_v2.

Local storage has no expiry, so anything in the two lists above stays on your device until you sign out or clear your browser data. You can clear it yourself at any time; the app will rebuild the preferences as you use it.

Session storage

One key: chronvel:coach-seed, which carries a single analytics pattern from the Analytics page to the Coach. It is written when you click through, deleted the moment it is read, and does not survive closing the tab.

The one item we do not set ourselves

sb-<projectref>-auth-token holds your Supabase Auth session — this is what keeps you signed in. It is written by the Supabase client library rather than by our code, and it lives in local storage like the rest.

Clearing your browser data

No consent banner, and why

We run no advertising, analytics, or profiling technology — no cookies, no pixels, no fingerprinting, on either domain. Our error tracking is not analytics and is not consent-based tracking: it transmits only when the app throws an error, and it is itemised in section 3. What we do store is either necessary to sign you in or a preference you set yourself, so there is nothing to ask you to consent to, and nothing to dismiss. If we ever introduce anything non-essential, we will ask for your consent first and update this policy before it is set.

Wherever you live, you can ask us to:

• Access — tell you what personal information we hold about you and give you a copy.
• Correct — fix information that is inaccurate or incomplete.
• Delete — erase your account and journal data, subject to the billing records we are legally required to keep.
• Export (portability) — provide your data in a structured, commonly used technical format.
• Withdraw consent — where we relied on your consent.
• Object or restrict — object to processing based on legitimate interests, or ask us to pause processing while a dispute is resolved.
• Complain — to us, and to a regulator. See section 11 and section 12.

How this works in practice today

• Export. The application has one export today: CSV of your backtest data — the trade fields plus the confluence columns. It is generated in your browser, so exporting transmits nothing to us or to anyone else. There is no live-trades export yet. For a complete copy of everything we hold — live trades, habits, rituals, notes, screenshots — email us and we will produce it.
• Deletion. There is no self-serve delete button. Email privacy@chronvel.com from your account address and we will action it by hand, on the schedule in section 9.
• Everything else. Email privacy@chronvel.com.

We respond within 30 days — one month for requests under the GDPR or UK GDPR, which we may extend by two further months for genuinely complex requests, telling you why. Requests are free. We may ask you to confirm your identity before acting, so that nobody else can obtain or delete your journal. If we refuse a request, we will explain why and tell you how to challenge it.

We are established in Quebec, so we are subject to the Act respecting the protection of personal information in the private sector as amended by Law 25, and to the federal Personal Information Protection and Electronic Documents Act (PIPEDA).

Privacy Officer

Responsibility for the protection of personal information at Chronvel rests with our Privacy Officer, who can be reached at:

• Privacy Officer, Chronvel — privacy@chronvel.com

We do not publish a postal address; the Privacy Officer is reachable by email, which is monitored.

Consent

We tell you at the point of collection what we are collecting and why, in plain language. We do not bundle unrelated consents together, and we do not make consent to optional processing a condition of using the product. For sensitive information — the wellness fields described in section 3 — we rely on your express consent, given by choosing to fill those fields in. You may withdraw consent at any time.

Privacy by default

Your journal is private to your account by default. We publish nothing, share nothing with other users, and there is no social or public feed to opt out of.

Confidentiality incidents

We keep a register of confidentiality incidents, as Law 25 requires. If an incident involving your personal information presents a risk of serious injury, we will notify you and the Commission d’accès à l’information du Québec (CAI) with diligence, and take reasonable measures to reduce the risk of harm and prevent a recurrence.

Automated decisions and profiling

We do not use your personal information to render a decision about you based exclusively on automated processing. We use no profiling technology, and nothing that follows you between sites or across sessions.

Two things to be straight about, both from our error tracking. A crash report attaches your account ID, so we can tell whether a bug hit one person or many. It also carries an approximate city and country, which Sentry works out from the IP address your device connected with.

That is identification and coarse location, for debugging. We do not use either to follow you, to build a profile, or to reach any conclusion about you, and neither feeds a decision of any kind. Both are set out field by field in section 3.

Transfers outside Quebec

Assessed in advance and governed by written agreements, as described in section 7.

Complaints

Raise it with our Privacy Officer first and we will look into it. If you are not satisfied, you can complain to the Commission d’accès à l’information du Québec or, where PIPEDA applies, to the Office of the Privacy Commissioner of Canada.

We accept users in the European Economic Area, the United Kingdom, and Switzerland. Where the GDPR, the UK GDPR, or the Swiss FADP applies to you, we act as the controller of your personal information, and the following apply in addition to everything above.

• Legal bases. Set out purpose by purpose in section 4.
• Your rights. Access, rectification, erasure, restriction, portability, objection — including objection to processing based on legitimate interests — and the right to withdraw consent. Exercise them as described in section 10.
• Special category data. Where the wellness fields you fill in amount to data concerning health, we process them on the basis of your explicit consent under Article 9(2)(a). They are optional, and you can leave them empty and still use the product.
• International transfers. Standard Contractual Clauses, the UK Addendum, and the EU–US Data Privacy Framework where the provider is certified — see section 7.
• Automated decision-making. We carry out no solely automated decision-making with legal or similarly significant effects within the meaning of Article 22.
• No statutory obligation to provide data. You are not required to give us anything, but we cannot run an account without an email address, and the journal has nothing to analyse if you do not log trades.
• Complaints. You can lodge a complaint with the supervisory authority in your country of residence, work, or where the alleged infringement occurred — in the UK, the Information Commissioner’s Office. We would appreciate the chance to address it first.

• Traffic between your browser and the Service is encrypted in transit using TLS.
• Data is encrypted at rest by our database provider, and backups are encrypted.
• Passwords are stored only as salted hashes, never in readable form.
• Access to production data is limited to the operator of Chronvel, on a need-to-know basis, and is not granted to anyone else.
• Row-level security is enabled on all user tables, with additional restrictive policies for read-only accounts. Each account can reach only its own rows, so one user’s journal is not accessible from another’s session.
• Uploaded screenshots sit in private storage buckets and are served only through time-limited signed URLs. There is no public link to your images.

Multi-factor authentication is not currently available. Sign-in is email and password only, so your password is the single thing standing between someone and your journal — use a strong one, unique to Chronvel, and a password manager if you can. We will say so here when MFA ships.

No service can promise perfect security, and we will not pretend otherwise. Tell us at privacy@chronvel.com if you suspect a problem with your account.

Chronvel is for adults. You must be at least 18 to hold an account, and we do not knowingly collect personal information from anyone under 18. If you believe a minor has given us personal information, email privacy@chronvel.com and we will delete it and close the account.

If we change how we handle your personal information, we will update this page and change the “last updated” date at the top.

For material changes — a new purpose, a new category of data, a new provider receiving your journal data, or a change in the basis on which we process it — we will email you at your account address at least 30 days before the change takes effect, and we will ask for your consent again where the law requires it. We will not apply a new purpose to data we already hold without telling you.

• Privacy, access requests, export and deletion: privacy@chronvel.com
• Legal and subscription matters: legal@chronvel.com
• Privacy Officer: Privacy Officer, Chronvel
• Operator: Chronvel, a sole proprietorship established in Quebec, Canada

We handle privacy contact by email. There is no postal address to write to.