Privacy policy

Last changed November 7, 2026.

Who runs TicketForge

TicketForge is run by one person, not a company, and is not affiliated with CN or CPKC.

What the website stores for your account

• Your name, email address, city, province, railway and home station.
• Your password, kept only as a one-way hash that cannot be turned back into the password.
• Your timeslips, whether you added them or the extension pulled them, any screenshots an older copy of the extension sent with them, and the trips, meals and pay TicketForge works out from them.
• The work and assignment history you pull, as the text of its screens, which keep the names and user IDs CATS prints on them, for your own crews and, on a pool pull, for every crew in the pool.
• Your employee number, as read from your own timeslips.
• Files you upload, such as a photo of a paper ticket or a VIA Rail PDF.
• Your settings, and a log of what happens on your account, such as sign-ins, pulls and downloads, sometimes with the internet address it came from. The log is used to fix problems.

What the extension sends to your account

• Your timeslips, and the work and assignment history you pull, as the text of the screens. Those history screens keep the names and user IDs CATS prints on them, for your own crews and, on a pool pull, for every crew in the pool.
• With the Share CATS and CMA screens switch on, copies of the screens a pull reads and the terminal screens you browse go to a separate research store, with every person's name, employee numbers, user IDs and anything typed into a field removed before they are stored.
• Notes about what the extension itself did, used to fix problems.
• A check for a newer version, which carries nothing about you.

Nothing from your terminal is sent until the extension is signed in to your account, from the panel on CATS or because you are already signed in to TicketForge in this browser. Before that, it only checks for a newer version and whether you are signed in.

A copy installed from a folder also reports whether its update worked. The report carries nothing about you, though the site notes the internet address and browser it came from.

What the extension keeps only on your computer

The CATS ID and PIN you save in the extension stay on your computer, and the extension never sends those saved copies to TicketForge. It only types them into the CATS sign-in screen: when you press its sign-in button there, to sign in again when CATS has timed out during a pull, and to sign back in when a pull finds CATS signed out.

The Share CATS and CMA screens switch

The screens in the second line of that list help fix the extension when CATS or CMA changes. Sharing them is on unless you turn it off. The Share CATS and CMA screens switch is on your Settings page and on the extension's welcome page. With it off, the extension stops sending those screens, and TicketForge refuses any that still arrive.

Who can see your data

You. The developers of TicketForge can see what you send, to run the site and to find and fix faults, and the tools they use for that work see it with them. TicketForge never shows your timeslips, meals or pay to another member. Anything you post on the Issues & Feedback page is shown to other members, because that page is shared.

Some features send part of your data to an outside service to produce their answer. The help chat and the Library's AI search send your question to Grok, an AI service from xAI, and the help chat sends your trips, meal totals and settings for that year with it. The account health check, and the check that works out your home station from your trips, send Grok a summary built from your trips (station codes, dates and counts) with no name, employee number or pay in it. You can turn the health check off in Settings. A message sent with Contact Developer goes only to the developers. A photo taken with the ticket scanner is sent to Google's text recognition service to read the ticket.

Every page of the site loads its fonts from Google Fonts and some of its scripts and styles from jsDelivr and code.jquery.com, and the trip entry page also loads from cdn.datatables.net, so those services see your internet address when a page opens.

How TicketForge uses your data

TicketForge uses the data the extension sends to show you your own timeslips, meals and pay, and to find and fix faults. It is never sold and never used for advertising. A person reads it only to run the site and to find and fix faults, which you agree to by using the extension with your account, or with your consent for anything else.

The use of information received through Chrome's extension APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

How long it is kept, and how to delete it

Your data is kept until you ask for it to be deleted; write to admin@ticketforge.ca and it is removed.

Contact

For anything about your data or this policy, write to admin@ticketforge.ca.