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.
- Trail runnerSize 9 · Blue$129.00
- Running socks3 pack$18.00
TF-8F42-QKDoneWhat 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.
14:31:52 [LOG] Navigated to Checkout 14:31:53 [LOG] GET https://api.shop.example/cart?session=[redacted] 14:31:58 [LOG] Receipt e-mail set to [email] 14:32:01 [LOG] POST /checkout Authorization: Bearer [redacted] 14:32:02 [WARN] Payment request failed, status 502 14:32:02 [ERROR] TypeError: Cannot read property 'id' of undefined
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.
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.
Or write to hello@tickflow.co