Legal
Privacy policy
What the TickFlow Field pages on tickflow.co and the Field service collect, why, where it is kept and for how long, and what you can ask of us.
In plain words
- This website
- Sets no cookies and runs no analytics or ads. The demo form keeps what you type, to reply; your IP address is kept only as a keyed hash.
- Your devices' data
- Card data and personal data are redacted on the device before anything leaves it. Evidence leaves only when someone reports a problem or asks for a capture.
- Where it lives
- Canada by default is the design intent for customer data. AI triage may run with a provider outside Canada, on redacted facts only, and you can switch it off.
- How long
- Diagnostic bundles 30 days, the redacted search index 13 months, the action ledger 7 years, unless your agreement says otherwise.
01Who we are and what this covers
TickFlow Field is built and operated by Orthoplex Solutions (“Orthoplex”, “we”), a Canadian company at 80 Atlantic Avenue, 4th Floor, Toronto, Ontario M6K 1X9, Canada.
This policy covers two different situations, and we are careful to keep them apart:
- This website (tickflow.co). Here we decide what is collected and why, and we are accountable for it.
- The TickFlow Field service, used by our business customers (banks, acquirers, ISOs, retailers, kiosk operators) on their own devices. There, the customer is the organisation accountable for the personal information on its devices and in its account, and we process it on the customer’s behalf and on its instructions, under the customer agreement and a data processing agreement (DPA). Where this policy and your agreement differ, the agreement wins.
We follow Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) and, for people in Quebec, the Act respecting the protection of personal information in the private sector as amended by Law 25. Where a customer operates elsewhere, its agreement sets out any additional rules.
02This website
No cookies, no tracking. This site sets no cookies and uses no browser storage (no localStorage, sessionStorage or IndexedDB). It loads no analytics, advertising, session-recording or social-media scripts. The interactive demos (the signing demo, the ledger, the redaction playground) run entirely in your browser; nothing you type into them is sent anywhere.
Fonts. The site’s typefaces are served by Google Fonts. When a page loads, your browser asks Google’s servers for the font files, which gives Google your IP address and browser details; no cookie is set by those requests.
Server logs. The web server that serves these pages keeps no access log. The reverse proxy and web application firewall in front of it record technical details of requests (IP address, time, address requested, browser) to protect the site from attacks, kept for 12 months and deleted within 2 years at most.
The Book a demo form. If you send it, we receive what you typed (name, work e-mail, and optionally organisation, role, fleet size and a message), the page you sent it from, your browser’s user-agent string and a keyed hash of your IP address. We keep the hash, never the address itself, so we can limit abuse from one source. We use these details only to reply to you and arrange a demo; we do not add you to a mailing list or share them with anyone outside Orthoplex. An e-mail with your request goes to our team’s inbox.
E-mail. If you write to us, we keep the correspondence as long as needed to answer and follow up, then as set out in retention.
03What the service processes
What follows is how TickFlow Field is designed and built. Your agreement may narrow it further.
Device information
For each enrolled device: its platform, model, operating-system and agent versions, a hash of its serial number (not the serial itself), its public key, and the health facts in its periodic check-in (battery, storage, network signal, clock skew, last seen). The agent is dormant: it sends this small signed check-in about every 15 minutes and nothing else until there is a report.
Diagnostic bundles
When someone taps Report a problem, or an authorised person in the customer’s organisation asks for a capture, the agent packages a bundle: a screenshot, the last 30 minutes of logs from the apps it is set up to watch, the device’s state, recent crash events and an optional short note from the person at the device. The screenshot can show whatever was on screen; screens the operating system marks as secure (such as PIN entry) come out blank. A bundle can contain personal information about the person using the device (for example a cashier’s name shown on screen) and, despite redaction, could contain information about customers of the merchant.
People who use the portal
For people our customers invite: name, work e-mail, organisation and role, sign-in method (magic link or single sign-on), and for each session the IP address, browser and times, with only a cryptographic hash of the session token. Their actions in the service are written to an audit log and, for remote actions and approvals, to the ledger.
Tickets
Ticket titles, descriptions, comments and attachments written by the customer’s people and by our support staff, with who wrote them and when.
What we never want
Card numbers, track data, PINs and card verification codes. The service is designed so this data never leaves the terminal: see redaction.
04Redaction on the device
Before a bundle leaves the device, every text file in it is passed through the same redaction rules, compiled into each agent (Android, Windows, macOS, Linux and the browser extension) and tested against one shared corpus so they produce identical output. The rules replace with tokens:
- card numbers (including separated forms), track data, card data read from the chip, card verification codes and PIN-related values;
- secrets: bearer tokens, JWTs, API keys and passwords in configuration or query strings;
- personal information patterns: e-mail addresses, phone numbers and Canadian social insurance numbers.
The redaction record in each bundle keeps counts of rule hits, never the values. When a bundle arrives, the server scans it again with the same rules. A hit means the device-side redaction missed something: the bundle is quarantined, kept out of tickets, search and AI, and treated as a defect we must fix. Raw logs never appear on tickets.
Redaction reduces risk; it cannot recognise every piece of personal information, such as names in free text or faces in a screenshot. That is one reason bundles are short-lived, encrypted and visible only to authorised people.
05Why we use it, and consent
We use the information described above only to:
- diagnose and fix the problem that was reported, and verify the fix;
- recognise the same fault across the customer’s own fleet (known issues and clusters);
- run the remote actions the customer’s policy and approvers allow, and keep the record of them;
- operate, secure and support the service, including investigating abuse and incidents;
- meet legal obligations.
We do not sell personal information, use it for advertising, or use one customer’s data to serve another. We do not use customer data to train AI models, and we choose AI providers whose terms forbid them from doing so.
The customer decides which devices run the agent and is responsible for telling the people who use those devices (its staff, and where relevant the public) that problems they report are captured with a screenshot and recent logs, and for any consent its law requires. We provide wording customers can adapt for that notice, on request.
06AI triage and the Coder
When AI triage is on, a language model helps find the cause of a report. The model receives identifiers and facts our own code has already extracted and validated; it can read device text only through tools, inside clearly marked boundaries, and only after redaction. It can propose a cause and a fix; it cannot run anything. Your policy and your people decide.
We use AI only through providers and settings where your data is not used for training and is retained for zero or a limited time. The model provider we use is listed in our subprocessor list and may process requests outside Canada. A customer can switch AI off for its organisation; triage then uses our rules only.
The Coder, when a customer turns it on for its own application, reads the customer’s code at the exact version a device runs and opens a draft pull request in the customer’s own code host. It receives the same redacted, validated facts, never screenshots, keys or other customers’ data.
07Where data is stored
Our design intent is that customer data is stored in Canada by default: the database, encrypted bundles, backups and e-mail delivery in Canadian regions. Enterprise customers can ask for a dedicated region or an on-premises deployment. The service runs on Amazon Web Services, mostly in its Canada (Central) region; the subprocessor list names each provider and where it processes data.
Some processing can happen outside Canada, notably AI triage (see above) and support tools. When personal information is processed outside Canada it remains protected by contract, and it may be accessible to courts and authorities in that country under its laws. For people in Quebec, we assess the protection a transfer outside Quebec gives (a privacy impact assessment) before we make it.
08How we protect it
- Every connection is opened by the device, outbound only, and every request and answer is signed; a device pins our key when it enrols.
- Each diagnostic report and each ticket attachment is encrypted at rest; plaintext is deleted after processing.
- Access is limited by organisation and account; nobody can approve their own request; risky remote actions need a signature from a separate approval key.
- Sign-in sessions are random 256-bit tokens of which we store only a hash; single sign-on works only for domains a customer has proved by DNS.
- Every user action is written to an audit log, and every remote action to a hash-chained ledger that rejects edits and deletions.
The detail, and demos you can test yourself, are in the trust centre.
10How long we keep it
Defaults below; a customer’s agreement can shorten most of them.
| What | Kept for | Then |
|---|---|---|
| Evidence buffer on the device | 30 minutes, rolling (5–120 configurable) | Encrypted on the device; overwritten continuously; never leaves unless a report or authorised capture is made |
| Diagnostic bundle (screenshot, logs, state) | 30 days | Deleted by a scheduled sweep; plaintext is deleted as soon as processing ends |
| Redacted search index (error signatures, codes) | 13 months | Used to recognise known issues and clusters across your fleet |
| Action ledger (who asked, who approved, what ran) | 7 years | Append-only and hash-chained; kept as audit evidence |
| Tickets, comments and attachments | For the life of your agreement | Exported to you and deleted at the end of the agreement |
| Sign-in sessions | 12 hours idle, 7 days at most | Only a hash of the session token is stored |
| Magic sign-in links / invitations | 15 minutes / 7 days | Single use |
| Bundles an agent could not upload | 7 days on the device | Then dropped by the agent |
| Demo requests sent from the Field pages | 2 years after our last contact | Then deleted |
When an agreement ends, we give the customer an export and then delete its data within 30 days, except the ledger and records we must keep by law, which stay protected until their period ends. Backups age out on their own, within 90 days at most.
11Your rights
You can ask us for access to the personal information we hold about you, ask us to correct it, and withdraw consent where we rely on it. In Quebec you can also ask for it in a structured, commonly used technological format, ask us to stop disseminating it, and ask how an automated decision about you was made. We answer within 30 days.
If your information is in the service because your employer or a business you dealt with uses TickFlow Field, that organisation controls it: write to them first. If you write to us, we pass your request to them and help them answer.
If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d’accès à l’information.
12If something goes wrong
We keep a register of every confidentiality incident. If one involves a customer’s data, we tell the customer without undue delay, with what we know and what we are doing, so it can meet its own obligations. Where an incident creates a real risk of significant harm (PIPEDA) or a risk of serious injury (Quebec), we report it to the Privacy Commissioner of Canada or the Commission d’accès à l’information and notify the people affected, as the law requires, and we keep records of breaches for at least 24 months.
13Children
The Field pages and the service are for businesses. They are not directed at children, and we do not knowingly collect information about them.
14Changes to this policy
We date every version. If we make a material change, we say so on this page and tell customers before it takes effect.
15Our privacy officer
The person responsible for the protection of personal information at Orthoplex Solutions is our Privacy Officer. Write to hello@tickflow.co with “Privacy” in the subject, or by post to the Privacy Officer, Orthoplex Solutions, 80 Atlantic Avenue, 4th Floor, Toronto, Ontario M6K 1X9, Canada.
Security issues are not privacy requests: report them through our responsible-disclosure policy.