SECURITY

Privacy starts with architecture.

KARAKOLA is designed around a simple idea: private content should remain private even when the device, files or transport applications around it are not fully trusted.

01

Encrypted local vault

Files added to KARAKOLA are stored inside an encrypted vault on your device. Vault content is not stored as ordinary photos or documents that other gallery or file-management apps can simply browse.

02

Authenticated encryption

KARAKOLA uses AES-256-GCM authenticated encryption. This protects both confidentiality and integrity: encrypted content cannot simply be modified without detection.

03

Keys are separated from the interface

The cryptographic keys that protect the vault are handled in a dedicated native security layer and are not exposed to the application interface.

Sensitive vault keys remain isolated from higher-level application code.

04

Android hardware-backed protection

KARAKOLA uses Android Keystore to protect key material and uses hardware-backed protection where supported by the device. Biometric authentication is performed by Android rather than by KARAKOLA collecting fingerprint or facial biometric data.

05

Automatic locking

KARAKOLA locks the vault whenever the app leaves the foreground or the lifecycle otherwise requires it, such as when the app is backgrounded. Reopening a locked vault requires your password or enrolled biometric credential again.

06

Screen-capture protection

Private surfaces inside KARAKOLA use Android's screen-capture protection, which can block screenshots and hide those surfaces from the system's Recents preview where the platform supports it.

This reduces accidental exposure, not every possible capture method, and it offers no protection on a rooted or otherwise compromised device.

07

Encrypted Backup & Restore

KARAKOLA backups are encrypted before leaving the vault. You decide where the backup file is stored and you remain responsible for keeping both the backup and its recovery credentials safe.

KARAKOLA cannot recover a backup if the information required to unlock it has been lost.

08

Deliberate sharing

Private content only leaves the vault when the user explicitly chooses an export or sharing action. Temporary access granted to another Android application is scoped to the content being shared rather than exposing the vault itself.

09

Hostile documents are treated as hostile

PDF rendering is isolated from the main application process. This reduces the amount of access available to document rendering code when processing potentially malicious files.

10

No security theatre

KARAKOLA does not claim to make a compromised phone magically safe. A sufficiently compromised operating system, unlocked device or user-authorised export can defeat protections that no application can independently control.

Our goal is to make KARAKOLA's security model understandable, to minimise unnecessary exposure and to state limitations clearly rather than hide them behind vague claims.

TRANSPARENCY

Security documentation will evolve with the product.

As KARAKOLA develops, this page will be updated to reflect material changes to its security architecture. We intend to document the system clearly enough to be useful without relying on obscurity as a security mechanism.

Report a security issue →