Taxefy (at.taxefy.app): Privacy & Security Findings

report - rfi-irfos
Skip to content

Permanent Disclosure Ledger

The discipline, demonstrated

On behalf of our research partners, we investigate publicly distributed Android and iOS apps: we decompile them, follow their code and data flows, and trace every connection to the servers it reaches. Hundreds of agents work through each app and join the technical evidence into one picture, which our specialists then review and verify.

387+
Android/iOS apps audited
Every app is decompiled at source-code level, not just scanned from outside.
1.04M+
Smali classes read
The full shipped code we have actually read, not an estimate.
262+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
970+
Weak points found
Third-party tracking we have provably found inside the binary.
567+
Endpoints investigated
Real servers and countries where data actually flows.
132+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for Taxefy.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Taxefy
Private
2026-06-21
90d ago
Escalated
Critical
Taxefy lets you log into an app handling your income and tax details using Facebook, hardcodes a live database key directly in the app, and sets its advertising-data sharing to the widest possible setting so other apps on your device can read it, on top of recording an identity-verification video. Rather than fixing any of this, the CEO responded to the disclosure by demanding the analysis be destroyed under threat of copyright law and dismissing the report as AI-generated, without disputing a single technical point in it.
Facebook Login on Austrian tax app. Hardcoded production Firebase key. Privacy Sandbox allowAllToAccess="true" - broadest possible advertising data sharing on an app processing income and tax data. Veriff Art.9 video. The CEO's response named this pattern for the disclosure series: the Decompile-Destruction Pivot - instead of addressing the hardcoded key or the ad-sharing config, he demanded destruction of our analysis under threat of copyright/UrhG action, dismissed the report as "offenbar KI-generiert," and questioned whether the research was genuine or a sales funnel, all without disputing a single technical finding. RFI-IRFOS declined the destruction demand (a public interest research exception applies to static analysis of a legally distributed binary), the archive stays intact for the duration of the open GDPR matter, and the Austrian DSB remains visible in cc throughout.
click to expand
GDPR Art. 32(1)GDPR Art. 5(1)(c)GDPR Art. 9(1)+1
Yes
Closed
Disclosure
90d 00h 00m 00s
Published
PDF

This ledger is updated in real time as companies respond. Silence is public. Severity is scored primarily by CVSS v4.0, we reserve the right to deviate based on blast radius.