TickFlowTickFlowField
PricingFAQ
Sign In
Book a demo
Skip to content
  • Overview
  • How it works
  • Security
  • Platforms
  • Integrations
  • Solutions
  • Developers
  • Trust
  • Pricing

Trust centre

What we hold, where it goes, and how you can check.

For security teams, privacy officers and assessors: where data goes, who else touches it, the questions we are asked most and how to report a problem. The detailed controls are in our technical briefing.

On this page

  1. 01Data flows
  2. 02Subprocessors
  3. 03Security FAQ
  4. 04Technical briefing
  5. 05Responsible disclosure

Data flows

Follow a report through the system.

The merchant’s networkTickFlow Field · Canadian regionreport · signed · outboundencrypted reportapprovalsredacted factssigned commands (pulled by the device)Terminalredacts on the deviceFieldCanada · checks again · encryptsStorageencrypted · 30 daysApproval servicekept apart from commandsAI providerno training · limited retentionYour approversportal · SSO
Every connection is opened by the device. Card data never crosses the first arrow.
  1. On the device Recent evidence is kept encrypted on the device. Nothing leaves until someone reports or an authorised person asks for a capture.
  2. On the way The device opens every connection, outbound only, and every message is encrypted and signed.
  3. In Field Checked again for card data, stored encrypted, turned into a diagnosis, then deleted on schedule.
  4. Back to the device Only named, signed fixes, and only when your policy and your approvers say so.

Subprocessors

Who else touches the data.

Every company that processes customer data on our behalf, what it sees and where. Customers are told before we add or change one; the signed list goes with the DPA.

Subprocessors
PurposeProviderWhat it seesLocationSafeguardsStatus
Hosting: API, workers, database, queueAmazon Web Services (AWS)All customer data the service holdsCanada (Central) region, mostlyEncrypted disks; access limited to the service and named staffconfirmed
Object storage: bundles, attachments, backupsAmazon S3 (AWS)Bundles and attachments, each encrypted with its own data key before uploadCanada (Central) regionEnvelope encryption by us; the provider never sees a keyconfirmed
E-mail deliveryAmazon SES (AWS)Recipient address; ticket number, title, status and a link; single-use sign-in links. Never device contentCanada (Central) regionMessage contents limited by designconfirmed
AI model provider (triage, the Coder)A third-party AI model provider; customers can switch AI offRedacted facts about a report, never card dataMay be outside CanadaNo training on customer data; zero or limited retention; you can switch AI offconfirmed
Your code host (only if you turn on the Coder)Your own GitHub organisationRead access to one repository per job; draft pull requestsWhere your code host keeps itAccess to one repository at a time, revoked when the job endsconfirmed
Service deskTickFlow Web (Orthoplex); or your own ServiceNow or Zendesk account, if you connect oneA summary of each report you choose to send, its likely cause, status and a link back; replies and status changes come back. Never card data, raw logs or screenshotsTickFlow Web: our hosting above. Your own service desk: where it keeps itConnected, scoped and revoked by your administrators; every change in your audit logconfirmed
  • The reverse proxy and web application firewall run on our own hosting; they are not a separate company.
  • This website loads its fonts from Google Fonts, which sees visitors' IP addresses. No customer data reaches it.

Security FAQ

The questionnaire, answered.

The questions procurement and security teams ask us first. Send us your questionnaire and we will answer it in full, in writing, for your file.

  • Card data
  • Encryption
  • Residency
  • Retention
  • Access
  • Device safety
  • AI
  • Testing
Card dataDoes the service bring our terminals into PCI DSS scope?

It is designed not to. Card data is removed on the terminal before anything is sent, the server checks every report again, and Field never touches the payment kernel or PIN entry. We document the scoping argument for your QSA; the assessment stays with your QSA, and the product holds no PCI certification.

EncryptionIs our data encrypted?

Yes, in transit and at rest, and every message between a device and Field is also signed, so it cannot be forged or altered on the way. Diagnostic reports are deleted after processing and kept only for the retention period you agree.

ResidencyWhere is our data stored?

In Canada by default. Enterprise customers can ask for a dedicated region or an on-premises deployment. AI triage may use a provider outside Canada; it never receives card data, and you can switch AI off.

RetentionHow long is data kept?

Diagnostic reports 30 days, the redacted search index 13 months and the record of remote actions 7 years, by default. Your agreement can set shorter periods.

AccessWho can see our data?

Your people, through your sign-in or single sign-on, limited to your organisation and, where you set it, to specific stores. Orthoplex staff have separate, audited access. Nobody can approve their own request, and destructive actions need two people.

Device safetyCould a compromised server make our terminals do something harmful?

Field is built so that it cannot on its own: terminals run only named, signed fixes, and anything disruptive or destructive also needs a separate approval the command service cannot produce. Limits and automatic pauses cap what a bad fix can do, and you can switch remote actions off per device or fleet.

AICan the AI act on its own?

No. The AI can only propose a cause and a fix. Your policy and your approvers decide what runs, and anything that looks like an instruction hidden in a log goes to a person.

TestingHas the product been penetration tested? Which certifications do you hold?

An independent penetration test is planned before the first bank goes live; we share the summary under NDA. The product is not certified against PCI DSS, SOC 2 or ISO 27001; its controls map onto Orthoplex's security programme and your assessor's questions.

Detailed technical briefing available on request

The how behind this page — our controls, the full questionnaire answers, how the ledger is chained and what is still to do — is in our technical briefing for customers, security teams and assessors. Ask us for access, then sign in.

Sign in to the briefing →

Responsible disclosure

Found something? Tell us first.

How to report

Write to security@tickflow.co with what you found, the steps to reproduce it, and what an attacker could do with it. Please include the request and response or a short video if you have them, and tell us how you would like to be credited. Encrypt it if you prefer: ask and we will send a key.

In scope

  • The TickFlow Field pages on tickflow.co and the Field app
  • The API and its device, customer, staff and public endpoints
  • The device agents (Android, Windows, macOS, Linux, the browser extension) on a test device you own
  • Device enrolment, signing and redaction

Out of scope

  • Any real payment terminal, merchant or customer organisation that is not yours
  • Denial of service, load or volume testing, spam, social engineering, physical attacks
  • Findings that need a rooted device, or a missing header with no demonstrated impact
  • Third-party services (the font host, the code host, the e-mail provider): report to them

Rules of engagement

  • Test only against your own account, your own test device or a demo environment we set up for you. Ask, and we will.
  • Never touch a real payment terminal or a real merchant’s data. If you reach someone else’s data by accident, stop, don’t keep it, and tell us.
  • Don’t degrade the service for others, and don’t use what you find beyond what is needed to show it.
  • Give us reasonable time to fix before you publish; we agree a date with you, normally within 90 days.

Safe harbour

If you follow this policy in good faith, we will not take legal action against you or report you to the authorities for your research, and we will say so to anyone who asks.

  1. 2 business daysWe confirm we have your report, with a person's name.
  2. 5 business daysWe tell you whether we can reproduce it and how severe we think it is.
  3. Every 2 weeksAn update until it is fixed, whether or not there is news.
  4. Target fix timesCritical 7 days · high 30 days · medium 90 days, from confirmation (targets, not guarantees).
security.txt (draft, published once the contact is confirmed)
Contact: mailto:security@tickflow.co
Expires: 2027-11-09T00:00:00.000Z
Preferred-Languages: en, fr
Canonical: https://tickflow.co/.well-known/security.txt
Policy: https://tickflow.co/field/trust#disclosure

More detail: Security & PCI · Privacy policy

Send us your questionnaire.

We answer security questionnaires and walk your assessor through redaction, approvals and the ledger on a live terminal.

Book a demoEstimate your savings

Or write to hello@tickflow.co

Report a problem.
TickFlow Field

On-demand diagnosis and remote repair for payment terminals and field devices. Part of the TickFlow family, built by Orthoplex Solutions in Canada.

hello@tickflow.co

Product

  • How it works
  • Security & PCI
  • Platforms
  • Integrations
  • Product tour
  • Playbook catalog
  • Compare
  • Pricing

Solutions

  • Savings calculator
  • Banks & acquirers
  • ISOs & resellers
  • Retail & QSR
  • Kiosk operators

Developers

  • Developers
  • Trust centre
  • Changelog

Field

  • Book a demo
  • Open Field
  • Privacy policy
  • Terms of service
  • Report a vulnerability
© 2026 Orthoplex Solutions. TickFlow and TickFlow Field are products of Orthoplex Solutions.Pilot targets and figures marked illustrative are not results.ServiceNow, Zendesk and ClickUp are trademarks of their respective owners (ClickUp™ of Mango Technologies, Inc.), named to show compatibility; no partnership is implied, and TickFlow is not affiliated with, endorsed by or sponsored by them.