TickFlowTickFlowSDK
PricingFAQ
Sign In
Talk to us
Skip to content
  • Overview
  • How it works
  • Privacy & security
  • Developers
  • Pricing

Privacy & security

Nothing is collected invisibly. The reporter sees it first.

A TickFlow SDK report is small, redacted on the phone and sent only when someone sends it. Here is what it holds, what it never does, and the switches you and your testers have.

14:32
‹ CartCheckout
  • Trail runnerSize 9 · Blue$129.00
  • Running socks3 pack$18.00
Saved card ···· 4242
Total$147.00
Payment failed. Please try again.
Pay $147.00
Report a problemSends a ticket to the team behind this app
ScreenshotInclude screenshot
Title *
What went wrong?Checkout fails after Pay
Attach diagnostics (logs.zip)212 log lines · 1 error · 34 network calls · iPhone 16, iOS 19.1
[LOG] POST /checkout Authorization: Bearer [redacted][WARN] Payment request failed, status 502[ERROR] TypeError: Cannot read property 'id' of undefined
Send report
Thanks, your report was sentQuote this reference if you follow up:TF-8F42-QKDone

What a report contains

What leaves the phone, and what never does.

The report card shows a one-line summary of the diagnostics, can expand to the last log lines, and lets the reporter leave the screenshot or the diagnostics out.

Sent with a report

  • A screenshot of the screen the person was on (they can switch it off)
  • The last console lines and JavaScript errors, with stack traces
  • Network calls: method, address, status and timing
  • Breadcrumbs and context you add, and the user id you set
  • Device model, OS, app id, version and build

Never sent

  • Request or response bodies and headers
  • Anything collected in the background: nothing leaves the phone until someone sends a report
  • Values your redaction rules remove

Redaction on the phone

Secrets are gone before they are stored.

Redaction runs on the phone as each value is captured, not when a report is sent. Tokens, keys and passwords in addresses, bearer tokens and e-mail addresses are replaced on the spot, so they never sit in what the SDK keeps and cannot reach a report by another path. Scroll the log to watch it happen.

The same rules run in TickFlow Web’s website feedback widget, so a report reads the same whichever surface filed it.

console · as the SDK keeps it3 secrets → tokens
14:31:52 [LOG] Navigated to Checkout
14:31:53 [LOG] GET https://api.shop.example/cart?session=8f2a91c4e7d0[redacted]
14:31:58 [LOG] Receipt e-mail set to dana.k@example.com[email]
14:32:01 [LOG] POST /checkout  Authorization: Bearer 0f9e8d7c6b5a4f3e[redacted]
14:32:02 [WARN] Payment request failed, status 502
14:32:02 [ERROR] TypeError: Cannot read property 'id' of undefined
redacted as it is capturedkept on the phoneleaves only when someone sends a report

Who controls it

Your switches, your admins’ list, your testers’ choice.

Only the builds you choose
One switch keeps the SDK to internal, QA or beta builds. Switched off, it does nothing at all: nothing is captured and nothing can be sent.
Only the apps you allow
An admin lists each app’s bundle id or package name under Collect Feedback for the client account. Reports from apps not on the list are refused.
Keys your admins control
A key built into an app can be read out of it, as with any client-side key. Your admins can regenerate the embed key, which retires the old one, or switch the embed off.
Your own rules on top
Add your own redaction for anything sensitive in your app, such as an account or loyalty number. It runs on every captured value, after the built-in rules.
Only your app’s screen
The screenshot is of your app, taken just before the report card opens, and the reporter can switch it off.
Network calls, not their contents
A call is recorded as its method, address, status and timing. Request and response bodies and headers are never sent.

Detailed technical briefing available on request

The how behind this page — how the SDK hooks into your app, what it keeps on the phone and the exact redaction rules — is in our technical briefing for customers, security teams and assessors. Ask us for access, then sign in.

Sign in to the briefing →

Questions from your security team?

Talk to us. We will walk them through what a report holds, where it goes and the switches you control.

Talk to usSee SDK pricing

Or write to hello@tickflow.co

Shake to report.
TickFlow SDK

In-app bug reporting and testing for mobile apps. Reports land as TickFlow Web tickets, built by Orthoplex Solutions in Canada.

hello@tickflow.co

TickFlow SDK

  • Overview
  • How it works
  • Privacy & security
  • Developers
  • Pricing

TickFlow

  • TickFlow Web
  • TickFlow Field
  • All pricing
  • FAQ
  • Privacy policy
  • Terms of service

Get started

  • Talk to us
  • SDK pricing
  • Technical briefing
© 2026 Orthoplex Solutions. TickFlow and TickFlow SDK are products of Orthoplex Solutions.The app, device and report shown on these pages are illustrative.TickFlow is an independent product and is not affiliated with, endorsed by, or sponsored by ClickUp. ClickUp™ is a trademark of Mango Technologies, Inc.