Transparency report · pre-launch · last updated 2026-05-30
Numbers we publish, because we should.
QiFlux has not launched yet, so this page reports our commitments and what they will be measured against. The moment the app is live, we will replace these with real, dated figures — the same numbers we look at internally, and the same numbers you should be able to look at.
0
Marketing popups (hard cap)
Our cap is 0, enforced in code. The day this becomes nonzero, this page goes amber.
0
Data egress by default
For users who never opt in to cloud AI / Sentry / sync. Verified by static analysis on every build.
≤5
Third-party SDK cap
Counted toward the cap: RevenueCat, Sentry (opt-in), Health (HealthKit/Health Connect). Apple & Google Sign-in are OS-level APIs, not counted. Enforced in CI.
—
Live since
Not yet on any store. Launch and usage figures will appear here once the app ships.
Status
Nothing has shipped yet.
QiFlux is in development and has not been released on the App Store or Google Play. As of 2026-05-30 there is no version history to report, no shipped features, and no usage to measure.
Once the app is live, this section will become a dated changelog of what we shipped and what we deliberately held back — including any time one of our promises was at risk, what happened, and how we fixed it. We would rather show the misses than hide them.
What is already true today is in the code, not in a metric: local-first storage, anonymous by default, no analytics SDKs, and end-to-end encrypted cloud backup that our server cannot decrypt. Those are the commitments this report will hold us to.
Things we don't measure (and why)
DAU. Streak length. Time-in-app.
Standard SaaS dashboards make products that demand attention. We are trying to make a quiet one. So our internal dashboard tracks a different question: did the app close in under 30 seconds? If yes, that's a good day. If users stayed for 4 minutes, we ask why.
We do not have, and will not build, an "engagement loop." We do not run growth experiments on cycle data. We do not A/B-test the AI answers. We do not measure how many people read this page.
If that means we grow slower, that is the correct outcome.