Can I trust Revolut Business?

Trust checks

• Secure by Design

  ● Strong

  Strong security foundation

  Why this result

  This check looks for security issues at high severity or above in the code of this build, and none were recorded. Its scope covers stored credentials, how the app protects data on the device, and how it protects data in transit.

  Revolut Business implements a layered security architecture with no critical or high-severity vulnerabilities. All connections to Revolut servers use certificate pinning, preventing interception even when a device trusts a rogue certificate authority. Unencrypted network connections are globally prohibited with no exceptions. Browser component SSL errors are correctly rejected rather than bypassed. Authentication credentials are stored in the Android operating system's protected credential vault, encrypted with hardware-backed keys tied to biometric enrollment. The local database is encrypted at the application layer with a passphrase derived from the hardware secure enclave. Commercial code protection prevents reverse engineering and detects tampered installations at startup. A layered stack of root detection, emulator detection, and hook-framework detection blocks the app from running in compromised environments. The weaknesses identified, including brute-force lockout counters stored without encryption and a remotely-disableable screen capture setting, require physical device access combined with root-level compromise to exploit. No remotely exploitable vulnerability was identi…

• Data Minimization

  ◐ One criterion not met

  Tracking lacks clear disclosure

  Why this result

  This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.

• Manifest Mismatch

  ◐ One criterion not met

  Disclosure incomplete or contradicted

  Why this result

  The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.

• User Control

  ● Strong

  No lock-in

  Why this result

  The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.

  No artificial barriers to leaving the service were found in the app. The app does not use proprietary data formats that would trap transaction records or account data, and no mechanisms designed to prevent account closure or data retrieval were identified. As a regulated European financial institution subject to GDPR and banking regulations, customers have legal entitlement to portability of their financial data.

What the app contains

• 21 services

  Third-party services the scan names in the build:

  • AppsFlyer
  • Firebase Analytics
  • Firebase Crashlytics
  • Firebase Performance
  • Firebase Messaging
  • Firebase App Check
  • Firebase Remote Config
  • SEON
  • hCaptcha
  • Google Ad Manager
  • Google Play Integrity
  • Onfido
  • Google ML Kit
  • Branch.io
  • MeshConnect Link
  • SQLCipher
  • DexProtector
  • Google Pay / Tap and Pay
  • RootBeer
  • youTransactor uCube
  • jMRTD

Method and limits

Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.

Build SHA-256

08e0e84369c062111fd35935a9cb9e362d1892c10c4fe8464047de2add1219e7

Rule pack

citt-ruleset-2026-08-v1

Files decompiled

92,591

Scan date

13 August 2026

Corrections

No correction is published for this app.