Privacy
Plainly, what happens to your data on Ticker Council.
Who's responsible
Ticker Council is based in Ontario, Canada. It is responsible for your personal information and is who to contact about privacy, including under Quebec's privacy law. To reach Ticker Council, email ethan@tickercouncil.com or use the Feedback form once you're signed in. By post: 168 Gosling Cres, Ottawa, ON K2W 0K7, Canada.
Your runs are private
Other users can't see your runs, your History or your settings, unless you share a run in the Community chat (below). The site's owner runs the service and can see everything, including your runs, through the admin page.
To keep the site working, run diagnostics (errors, timings, costs, which seats could read their data, and messages sent with the Feedback button) are reviewed regularly, with the help of automated tools. That review never includes your name, email or API keys.
Whose AI your runs use
- Free: runs use the AI keys you add, and your AI provider charges you for them.
- Pro and Elite: runs use Ticker Council's own AI (Google's Gemini, with OpenAI as a backup when Gemini is busy), paid for by the site. If you've added your own key you can also run on that.
Your API keys
- Your keys are stored encrypted and are only ever used for your own runs.
- They're never shown back to anyone, including you: Settings only shows their last four characters.
Scores are pooled anonymously
When a run's time is up it's scored against what the price actually did. Those scores, from everyone's runs, are pooled to decide how much each seat counts. The pooled numbers never show whose run was whose. Before they're used, the owner reviews them.
What's stored about you
- Your name and email, and a scrambled (hashed) password if you set one. The actual password is never stored.
- If you sign in with Google: your Google account ID, name and email. Nothing else from Google.
- Your runs, settings, keys and watchlist, and when you last signed in.
- Anything you send with the Feedback button or in a survey.
It's used to run your account and the site, and nothing else. It's never sold or used for ads.
Stock pages
When public stock pages are on, each stock's page shows the Council's combined lean from everyone's recent runs of it: totals only, and only once at least two different people have run it. Never a single person's run, name, email or account.
Shared links
If you share a result, anyone with its link can see that one run: the call, the summary and how each seat leaned. Never your name, email or other runs. You can stop sharing at any time and the link stops working.
The Community chat
- In the chat you appear only by your username and avatar, with a Pro or Elite badge if you're on one of those plans (whether you pay for it or it was given to you). Your real name and email are never shown to other members. Tapping your name shows when you joined and how many runs you've done, never what they were.
- Messages you post can be read by every signed-in member. You can delete your own messages at any time.
- When you share a run there, any signed-in member can open that whole run, read-only: every seat, the debate and the Business check. Never your name, email, keys, other runs or what it cost. Unsharing (or deleting the message) closes it again.
- The owner (and any moderators they choose) can read every message, including reported ones and ones the spam filter holds, and can delete messages or mute or ban someone from the chat. The chat is backed up nightly like everything else.
Visitor counts
The site counts how many people open the landing page, the sign-up form and shared results, and which sites sent them, so the owner can see if anyone's finding it. When you sign up, your account notes where you came from (the site that linked here, or the tag on the link, like "reddit"), so the owner can see which posts work; it's deleted with your account. Counting visits uses no cookies and no outside tracking services. The only cookies the site sets are the one that keeps you signed in and, if you open a friend's invite link, one that remembers the invite for 30 days so you both get your bonus runs. If you join with someone's link, the site keeps who invited you; they only see how many friends joined, never who. Your IP address isn't stored: visits are counted with a code that changes every day, so nobody can be followed from one day to the next.
Backups
The databases are backed up nightly so nothing is lost if the server fails. Backups never include the key that unlocks saved API keys.
Emails
- Emails about your account: approval and password resets.
- Emails about your own runs: when a call of yours is scored and (Pro and Elite) the Monday email about your watchlist, each with a "Stop these emails" link; and when a run you asked to save for later is done or couldn't go ahead.
- Now and then, a personal note from the owner about your account or something you sent.
- Product news (new plans and features), only if you said yes: on the sign-up form, when the app asks, or in Settings. Every one has an unsubscribe link, and you can turn it off in Settings. We keep when and where you said yes or no, and the words you were shown, as a record of your choice.
Who else handles your data
A few services do part of the work, each under its own terms and only for that job:
- Oracle Cloud hosts the server and its backups.
- Resend sends the emails (your name and email address, and the email itself).
- Google, if you sign in with Google.
- Stripe, if you subscribe (see Payments).
- The AI providers (Google, OpenAI, and any others whose keys you add) get the stock data and prompts for each run, never your name or email. On Google's free tier, Google may use what's sent to improve its products.
Some of these services are outside Canada, mostly in the US, so your data may be stored or handled there, under those countries' laws. If you're in the EU or the UK, data that leaves it is covered by the safeguards those services offer for it, like the standard contractual clauses approved by the European Commission and the UK's addendum to them.
If you're in the EU or the UK
We use your data because it's needed to run the account and the plan you asked for (your account, runs and payments), because we have a legitimate interest in keeping the site working and safe (diagnostics, backups, preventing abuse), and, for product news, because you said yes, which you can take back at any time. You have the rights described below, plus the right to object to the legitimate-interest uses and to complain to your data protection authority (in the UK, the Information Commissioner's Office).
Payments
If you subscribe to Pro or Elite, Stripe takes your card and processes the payment under its own privacy policy. Ticker Council never sees or stores your card number. It keeps your plan, whether you pay monthly or yearly, your Stripe customer and subscription IDs and when your plan renews, so it knows which plan to give you.
How long things are kept
Your account and what's in it, for as long as you have the account. Server error logs, two weeks. The nightly backups kept on the server roll over after two weeks. Feedback messages and the pooled scores are kept, with your name and email taken off when your account goes.
Your rights
You can ask to see the personal information held about you, to correct it, to get a copy, or to have it deleted, and you can withdraw your consent (by deleting your account or turning emails off). Ask using the contact details above and you'll get an answer within 30 days. If you're not happy with the answer, you can complain to the Office of the Privacy Commissioner of Canada, to Quebec's Commission d'accès à l'information, or to the data protection authority where you live.
Deleting your account
Ask the owner (contact details above) and your account, keys, settings and chat messages are deleted, and any subscription is cancelled. Stripe keeps its payment records as the law requires. Scored runs stay in the pooled record, which can't be edited, but no one can open them any more except the owner.
Changes
If this page changes in a way that matters, you'll hear about it by email or in the app before it applies.