All Cloak documents

Cloak: Secret Calculator Vault ("Cloak" or "the App"), for Android and iPhone, is published by Aquison Technologies ("we", "us"). It is a local-first, privacy-focused app. This policy explains exactly what information the App stores on your device, what limited, anonymous diagnostic information leaves your device, and why. Where Android and iPhone differ, it says so.

1. Summary

  • Your vault stays on your device unless you back it up. Photos, videos, files and notes leave it only inside an encrypted backup file that you create and save to a place you choose (for example your phone's storage, an SD card, a USB drive or a cloud folder such as iCloud Drive), or that the App makes on its own in a folder you chose when you turn on automatic backup. Your PIN and recovery answers are never uploaded anywhere and are not part of backups. The vault is left out of your phone's own backups (a Google backup on Android; iCloud and computer backups on iPhone).
  • We do not run our own servers and we have no way to see your vault contents or your backups. If you save a backup to a cloud service, that service stores the encrypted file under its own terms and cannot read what is inside.
  • We collect anonymous usage statistics and crash reports through Google Firebase to keep the App stable and improve it. See section 3 for exactly what that includes.
  • If you buy Cloak Pro, Google Play (on Android) or the App Store (on iPhone) handles the payment, and our purchase processor RevenueCat records the purchase against an anonymous ID, so the App knows you have Pro. See section 4.
  • No advertising, no data brokers, no sale of data.

2. Data stored on your device

The following data is stored only inside the App's private, sandboxed storage on your device. Other apps cannot read it unless the phone is rooted or jailbroken:

  • PIN credentials — a salted one-way hash of your PIN (and decoy PIN, if set); the actual PIN is never stored.
  • Security recovery answers — hashed and stored locally to verify your identity if you forget your PIN.
  • Vault contents — photos, videos, audio, files and secure notes you import or create within the App, including photos and videos you take with the App's private camera.
  • Intruder photos — if you enable the optional Intruder Selfie feature, photos taken by the front camera after repeated wrong PIN attempts are stored locally so only you can review them.
  • App preferences — theme, language, sorting, auto-lock and stealth settings.
  • Plan records — whether you have Pro (the plan, and when it renews or ends, as Google Play or the App Store and RevenueCat last reported it), the free plan's rules as last received, how many free uses of limited tools you have had, when the App last showed a Pro notice, and the id of a discount campaign you applied with a code (never the code itself). Clear vault does not remove Pro.
  • Backup records — for each vault, when its last backup finished, whether the last attempt failed, and a SHA-256 fingerprint of what the vault held then, made from its records without decrypting anything, so an automatic backup can tell when nothing has changed. The location of a backup you make by hand is kept only while it is being written, so an unfinished file can be removed.
  • Automatic backup — if you turn it on for a vault: the folder you picked (its address and name), how often to back up, how many backups to keep, whether to wait for the charger (Android) or for the vault to be opened, when it last ran and why it last failed, and the addresses of the backup files it made in that folder, so it deletes only its own older files. Also a key derived from your backup password (never the password itself), encrypted with that vault's key.
  • Away report guard (Android only) — the time you started the guard, the time you first opened the vault after it, and whether you have opened its report since, kept until you stop the guard or start a new one. The report itself (unlocks, screen-ons and apps opened) is read from Android each time you open it, or when Home shows what happened while you were away, and is never stored.
  • Locked files you make — Locked send writes the encrypted file into the App's private cache, where it waits for you to share or save it, and deletes it at your next share or when the vault locks. Its password is never stored. Items you open from a locked file are kept in the vault like any other, encrypted.
  • Evidence locker — the cases you open and what you add to them: photos, videos and files exactly as they were (picture details included), copies of vault items, and notes you type, each with its SHA-256 and MD5 fingerprints, its size, when it was added and, where the phone reports it, when it was taken. Each case keeps a history of every change (when each item was added or withdrawn, and when a report or export was made), chained by fingerprints so that a change made outside the App shows. Everything in the locker is encrypted with your vault's key; titles, file names and note text are encrypted too, while the history holds only times, fingerprints and sizes. Each vault (real and decoy) has its own locker. Withdrawing an item deletes its file (or a note's text) and keeps its fingerprint and when it was withdrawn in the history. A report or a locked export is written to the App's private cache, where it waits for you to share or save it, and is deleted at your next share or when the vault locks. Cases are included in your vault backups and deleted by Clear vault; Export everything leaves them out. Voice recordings you make in a case are kept the same way: the sound is encrypted as it is recorded and saved into the case in parts (every 10 minutes and when you stop), each with its fingerprint and length.
  • Phone check marks (Android) — the apps you mark as known in Phone check (each app's package name and the kinds of access it had when you marked it), encrypted with your vault's key. What a check finds is read from Android each time you run it and is never stored.
  • iPhone check mark (iPhone) — if you tap That's only me in iPhone check, the App keeps the value iOS gives for the current Face ID or Touch ID enrolment, so a later check can tell you if it changed. The App never sees your face or fingerprint. What a check finds is read from iOS each time you run it and is never stored.
  • Safe show (iPhone) — the photos and videos you pick from your library are read into a temporary folder in the App's private storage for the show, and deleted when the show ends, when the vault locks or at the next start.
  • Safe share copies you keep — if you choose Keep in vault, the copy is stored and encrypted like any other vault photo. Nothing else from Safe share is stored: the photo you pick or scan, what it finds and your watermark are held only in memory while you edit. On Android, the document scanner hands its page to the App as a temporary file in the App's private cache, which is read into memory and deleted at once (and swept at the next start if the App was closed in between); on iPhone, the scanned page is held in memory only. A copy you share is written briefly to the App's private cache for the receiving app to read, and deleted at your next share or when the vault locks; a copy you save to your phone goes to its Pictures folder on Android or its photo library on iPhone, outside the App.

3. Analytics and crash reporting

The App includes Google Firebase Analytics and Firebase Crashlytics. Apart from purchases (section 4), the store's own update and rating screens, and the performance metrics Google ML Kit sends when you use Safe share on Android (section 7), these are the only services that send data off your device. They are always active in the published App.

What is sent

  • Usage events — which screens are opened and which features are used (for example "vault unlocked with biometrics", "12 photos imported", "theme changed to dark"). Item counts are grouped into ranges, never exact.
  • Crash reports — stack traces, the screen that was open, device model, operating system version (Android or iOS) and App version when a crash or serious error occurs.
  • Device and app information — device model, operating system version, App version, language, country derived from IP address, and a pseudonymous app-instance identifier generated by Firebase. On Android, Firebase may also collect the Android Advertising ID where available; we do not use it for advertising. On iPhone, the App does not collect the advertising identifier (IDFA) and never asks to track you, and Firebase's collection of the identifier for vendor (IDFV) is turned off.

What is never sent

  • Your PIN, decoy PIN, recovery answers or stealth codes.
  • Any photo, video, file, note or intruder image, and no file names, thumbnails or storage paths.
  • Whether you entered a decoy PIN. A decoy unlock is deliberately not tracked.
  • Which apps you use, when your phone was unlocked, or anything else the Away report shows.
  • Which apps on your phone have special access, which settings are on, or anything else Phone check or iPhone check finds, and whether you marked a Face ID or Touch ID enrolment as yours. Only whether a check ran is counted.
  • A locked file's password, its name or anything in it. Only how many items a locked file holds is counted, in ranges.
  • Anything in the evidence locker: case titles, what you add, notes, recordings, fingerprints, reports or exports. Only how many items were added or how many parts a recording saved, and whether a check, report, export or recording finished, are counted, in ranges; never how long a recording is.
  • Anything Safe share reads or finds: the photo, its location, time or camera details, the ID numbers, codes or faces on it, or your watermark. Only how many items were covered is counted, in ranges.
  • Your name, email address, phone number, contacts or precise location.

Why we collect it — to find and fix crashes, to understand which features are used so we can improve them, and to measure the effect of updates. We do not use this data for advertising, profiling or to identify you.

Who processes it — Google LLC, under the Firebase Terms of Service and the Google Privacy Policy. Data is encrypted in transit. Firebase Analytics event data is retained for 2 months and Crashlytics data for 90 days by default, after which it is deleted or aggregated by Google.

Legal basis — our legitimate interest in keeping the App reliable and secure. You may stop all collection at any time by uninstalling the App; because the data is pseudonymous, we cannot link it back to you to honour individual deletion requests.

4. Purchases (Cloak Pro)

Pro is optional. If you never buy anything, RevenueCat holds no purchase record for you: only the anonymous ID and the technical details below.

  • Google Play (on Android) processes the payment in its own purchase screen, under the Google Play Terms of Service and the Google Privacy Policy.

  • The App Store (on iPhone) processes the payment in Apple's own purchase screen, under Apple's Media Services Terms and Conditions and the Apple Privacy Policy.

  • We never see your card or payment details, your name or your e-mail address.

  • RevenueCat, Inc. is our purchase processor. When you open the vault, the App asks RevenueCat whether you have Pro and which plans and prices to show. When you buy or restore, the App sends RevenueCat the store's proof of the purchase (Google Play's purchase token, or the App Store's signed transaction), which RevenueCat checks with Google or Apple. RevenueCat then holds:

    • the purchase record: the product, price, currency, store country, and purchase, renewal and expiry dates;
    • an anonymous ID made by RevenueCat's library on your phone. The App shows it as your Support ID. It is not linked to your name, e-mail or phone number;
    • technical details such as the versions of the App and of Android or iOS and the phone's language, and the IP address of each request, which RevenueCat uses to tell the country and to keep its service secure;
    • if you apply a discount code, the campaign's id (never the code).

    RevenueCat receives nothing from your vault. The App does not send it device identifiers such as the Advertising ID, and turns off its diagnostics. On iPhone, RevenueCat's library sends the identifier for vendor (IDFV) with each request: an ID iOS gives the App on that iPhone, which is not the advertising identifier. See the RevenueCat Privacy Policy.

  • Google Block Store (Android): RevenueCat's library keeps the anonymous ID in Google Block Store, a feature of Google Play services. After you reinstall the App, or move to a new phone restored from your Google backup, the App can then find your Pro without an account. On iPhone, Restore purchases asks the App Store for the purchases of your Apple Account, so Pro comes back after a reinstall or on a new iPhone, also without an account.

  • Why: to provide Pro and the plan you bought, to restore it, and to see how many people buy which plan. The legal basis is the contract you enter when you buy, and our legitimate interest in understanding sales.

  • Retention and deletion: the purchase record is kept while you have Pro and afterwards for as long as tax and accounting law requires. To have it deleted sooner, write to support@aquisontechnologies.com with your Support ID. Deleting it removes Pro from the App, and Google Play or Apple keeps its own order history.

5. Security measures

  • Encryption at rest: every photo, video, file, note and intruder photo in the vault is encrypted with AES-256-GCM. The encryption key is generated on your device and protected by the Android Keystore (hardware-backed where the device supports it) on Android, or by a key in the iPhone's Secure Enclave on iPhone; a second copy is protected by your vault PIN so your content survives a reset of that protection. Neither the key nor your content ever leaves the device.
  • Your PIN, decoy PIN and recovery answer are stored only as salted PBKDF2-HMAC-SHA256 hashes, inside EncryptedSharedPreferences on Android and in the iPhone's Keychain, kept on that device only, on iPhone.
  • Vault files live in the App's private internal storage, which is inaccessible to other apps on an unrooted device, and are hidden from gallery and file-manager apps.
  • On Android, the App blocks screenshots and screen recording of vault screens (via FLAG_SECURE). iOS does not let any app block screenshots; on iPhone, the App hides every photo and video while the screen is recorded or mirrored, and the App Switcher shows only the calculator.
  • Repeated wrong PIN attempts trigger increasing lockout periods to slow down guessing. In Safe show, only your PIN ends a show, and three wrong PINs end it and lock the vault.
  • Locked send: a locked file is a ZIP whose every item is encrypted with AES-256 (the WinZip AE-2 format, which common unzip apps open with the password). The format derives the key from the password with only 1,000 rounds of PBKDF2-SHA1, so the App suggests a generated 20-character password and accepts your own only if it passes the same rules as a backup password. The ZIP format leaves each item's name, size and date readable without the password, so the App names items with plain numbers and gives them all the time the file was made. Nothing is written unencrypted while the file is made: each item is decrypted and encrypted again in memory.
  • Evidence locker: files in a case are encrypted with AES-256-GCM under your vault's key as they are read, while their SHA-256 and MD5 fingerprints are computed; nothing is written unencrypted. Each line of a case's history carries the SHA-256 of the line before it and of its own details, and the case keeps its last line, so a line changed, removed, moved or cut off shows when you check the case. Check also reads every file again against its fingerprint. The times come from your phone's clock. A report (PDF) and an export to a folder are not encrypted, because they are made to be given to someone; an export as a locked file uses the same format and password rules as Locked send. A report records evidence you kept; the App does not promise that police or a court will accept it. Voice recordings are encoded (AAC) in memory and written straight into the encrypted file; no unencrypted sound is ever written. If the phone stops the App while it records, only the part in progress is lost, and its unfinished encrypted file is deleted at the next start.
  • Backups: a backup file is encrypted with AES-256-GCM under a random key, which is sealed with a key derived from your backup password (PBKDF2-HMAC-SHA256, tuned to about a second of work on your phone). Without the password nothing in the file can be read, not even how many items it holds. Making a backup requires your PIN, and the password is never stored or sent anywhere, so it cannot be recovered.
  • Automatic backup: when you set it up, your backup password is turned into a key once (the same PBKDF2 as above, with a salt kept for every automatic backup), and that key is stored on your phone encrypted with AES-256-GCM under the vault's own key; the password itself is never stored. Each automatic backup has its own random key sealed with it, so your password opens every one of them. To back up while the vault is locked, the App opens the vault's key through the Android Keystore on Android, as it already does to seal intruder photos, or the Secure Enclave on iPhone; this means the protection of those backups' key on the phone rests on that hardware-backed key, as the vault's own normal unlock does. If you prefer, choose to back up only after you open the vault: that key is then not used for it, and a backup in progress stops when the vault locks. Every new file is read back and checked before it counts, and an unfinished one is deleted.

6. Device permissions

The App requests only the permissions it needs.

On Android

  • Internet and network state — used solely for the anonymous analytics and crash reports described above, for checking and buying Pro (section 4), and for Google Play in-app update and review prompts. Your vault contents are never transmitted.
  • Google Play billing (com.android.vending.BILLING) — lets you buy Pro in Google Play's own purchase screen.
  • Camera — used by the Private camera tool while you have it open, and by the optional Intruder Selfie feature after you enable it in Settings. The App never accesses the camera otherwise. Photos from the private camera are encrypted in memory and written only to the vault; a video is recorded to a temporary file in the App's private storage, then encrypted into the vault and deleted as soon as the recording ends. Nothing is added to your gallery, Google Photos or any other app.
  • Microphone — used only while you record: sound for a video with the private camera (without it, videos are recorded without sound), and the evidence locker's voice recorder, which can't start without it. While the recorder runs, Android shows its microphone dot and the App's notification; the recording goes on with the screen off and after the vault locks, until you stop it in the App or with Stop in the notification. The App can't record phone calls; Android doesn't allow it.
  • Notifications (Android 13 and later), foreground service and wake lock — only for the voice recorder. Its notification says "Recording" with the time and a Stop button, and nothing about what or where. If you don't allow notifications, the recorder still works and you stop it in the App. A foreground service and a partial wake lock keep the recording going while the screen is off; both end when the recording does.
  • Photos you pick to show — Safe show uses Android's photo picker, which needs no permission and gives the App access only to the photos and videos you pick. They are displayed while the show runs and are never copied or stored. Screen pinning, if you turn it on, is Android's own feature and asks you to confirm it.
  • Usage access — used only by the Away report, and only after you turn it on in Android's settings (you can turn it off there at any time). While the report is open, and when Home shows what happened during a guard, the App reads Android's own record of when the screen turned on, when the phone was unlocked and which apps were opened, for the time you chose (for Home, from the guard's start until you came back). Nothing from it is stored, backed up or sent. To show those apps by name and icon, the App can see the apps on your phone that open from the home screen, not every installed package.
  • Apps with special access (Phone check) — no permission is needed. To find apps that could be used to watch you, the App can see the apps on your phone that offer an accessibility service, read notifications, act as a device admin, provide a keyboard or provide a VPN, besides the apps that open from the home screen; it cannot see every installed package. It reads which of those powers are switched on and where each app was installed from, and a few phone settings: whether USB or wireless debugging and developer options are on, whether a screen lock is set, the security update level and whether a VPN is on. All of this is read only while you run a check and is never stored, backed up or sent. The App never removes or turns off anything; its buttons open Android's own settings. Its help links open in your browser.
  • Photos you pick or scan to share safely — Safe share also uses Android's photo picker (no permission), takes a photo from your vault, or scans a page with Google's document scanner. The scanner is a Google Play services screen that uses Play services' own camera permission; the App doesn't need the camera for it and receives only the page you keep. The App reads the photo you pick to make a new copy; the original is never changed. The copy is a fresh picture that carries none of the original's metadata (location, time, camera, embedded preview or editing details).
  • Files you open or save (Locked send) — opening a locked file and saving one to your phone go through Android's file picker, which needs no permission and gives the App access only to the file you pick.
  • Evidence you add, and where you export it (Evidence locker) — photos and videos come through Android's photo picker and other files through Android's file picker; neither needs a permission, and the App reads only what you pick, without changing or deleting the original. Exporting to a folder goes through Android's folder picker, which gives the App access only to the folder you choose; a report or locked file you save goes to the place you pick. Help numbers in a report are only text: the App calls nothing.
  • Storage (Android 12 and below) — used to export items from the vault back to your gallery or Downloads. On Android 9 and below the App asks for it the first time you export an item or save a Safe share copy to your phone. On newer Android versions the App uses the system picker and needs no storage permission.
  • Run after a restart (RECEIVE_BOOT_COMPLETED) — added by Android's WorkManager library so that a scheduled automatic backup is still scheduled after the phone restarts. Nothing runs at startup unless you turned automatic backup on, and it runs without a notification.
  • A folder you pick (automatic backup) — chosen through Android's folder picker, which needs no permission and gives the App access only to that folder. The App makes its backup files there and deletes only older backup files it made itself; it never reads or changes anything else in the folder. You can take the access back in Android's settings or by turning automatic backup off.

On Android, the App does not request location or contacts permissions, and asks for notifications only for the voice recorder.

On iPhone

  • Internet — iOS needs no permission for it. Used solely for the anonymous analytics and crash reports described above, for checking and buying Pro (section 4), and for the App Store page that Check for updates opens inside the App. Your vault contents are never transmitted.
  • In-app purchases — Pro is bought in Apple's own purchase screen; no permission is needed.
  • Camera — used by the Private camera tool while you have it open, by the optional Intruder selfie after you turn it on in Settings, and by Safe share's document scanner (Apple's document camera, on the device). The App never accesses the camera otherwise, and iOS shows its camera indicator while it is on. Photos from the private camera are encrypted in memory and written only to the vault; a video is recorded to a temporary file in the App's private storage, left out of backups, then encrypted into the vault and deleted as soon as the recording ends. Nothing is added to your photo library.
  • Microphone — used only while you record: voice recordings in the vault, the evidence locker's voice recorder, and sound for a video with the private camera. While a recording runs, iOS shows its microphone indicator, and the App shows a Live Activity on the Lock Screen (and in the Dynamic Island, where the iPhone has one) that says "Recording" with the time and a Stop button, and nothing about what or where. The recording goes on with the screen off and after the vault locks, using iOS's background audio, until you stop it in the App or with Stop. iOS ends a Live Activity after 8 hours; Stop is then in the App. The App can't record phone calls; iOS doesn't allow it.
  • Face ID or Touch ID — only if you turn it on: to open the vault when you forget your PIN, and to confirm it's you inside the vault. iOS checks your face or fingerprint; the App never sees it and learns only whether it matched.
  • Photos — adding photos and videos, Safe show and Safe share use Apple's photo picker, which needs no permission and gives the App only the photos and videos you pick. Saving to your photo library asks for add-only access, which lets the App add photos without seeing your library. Full access to your library is asked for only if you choose to move items into the vault, so the App can delete the originals from your library once they are safely in the vault; iOS keeps them in its Recently Deleted album for a while.
  • Files — adding files, opening a locked file, and saving a backup, a locked file, a report or an export go through Apple's Files picker, which needs no permission and gives the App access only to what you pick. For automatic backup, the App remembers the folder you picked, and only that folder: it makes its backup files there and deletes only older backup files it made itself; it never reads or changes anything else in the folder.
  • Background tasks — iOS lets the App run in the background, at a time iOS chooses, to make a scheduled automatic backup and to remove items from Recently deleted after 30 days. No automatic backup runs unless you turned it on.

On iPhone, the App does not ask for location, contacts or notifications, and never asks to track you.

7. Third-party services

  • Google Firebase (Analytics, Crashlytics) — see section 3.
  • Google Play Billing and Google Block Store (Android), the App Store (iPhone) and RevenueCat — for Cloak Pro; see section 4.
  • Google Play services (Android) — the in-app update and in-app review features are provided by Google Play. When you interact with them, Google Play's own privacy policy applies.
  • Apple's App Store (iPhone) — Check for updates opens the App's App Store page inside the App, and the App may ask iOS to show its rating prompt. These are Apple's own screens, and the Apple Privacy Policy applies.
  • Google ML Kit (Android, through Google Play services) — on Android, Safe share uses ML Kit's text recognition, face detection and barcode scanning to find ID numbers, faces and QR codes on the photo you pick, and ML Kit's document scanner when you scan a page. The photo is processed on your device and is never sent to Google or to us. Google Play services downloads the detection models and their updates, and ML Kit sends Google metrics about how the feature performs and how much it is used (not the photo or what was found), as described in the ML Kit terms.
  • Apple's Vision and VisionKit (iPhone) — on iPhone, Safe share finds ID numbers, faces and QR codes with Apple's Vision framework, and scans pages with Apple's document camera. The photo is processed on your device and is never sent to Apple or to us.

Other libraries in the App (Android Jetpack, including WorkManager for automatic backup, Room, Media3, Coil, CameraX, and zip4j for opening locked files) run entirely on your device and do not send data anywhere. On iPhone, the App is built on Apple's own frameworks, which likewise run on the device.

8. Children's privacy

The App is for people aged 13 and over. It is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has used the App, uninstalling it deletes all locally stored data.

9. Data deletion and your control

  • In the App: delete individual items, clear the intruder log, or use Clear vault in Settings to remove everything stored by the App.
  • Uninstalling the App (on iPhone, Delete App), or clearing its storage in Android Settings, permanently destroys all locally stored files, notes and credentials. This cannot be undone and we cannot recover it, unless you restore it from a backup you made. On iPhone, Offload App keeps the App's data on the phone.
  • Backup files you created stay where you saved them. Uninstalling the App does not delete them; delete them there when you no longer need them.
  • Automatic backup: turning it off (or turning the decoy off, or resetting the vault) deletes the stored key and stops it; the backups already in the folder stay there until you delete them. While it is on, it deletes only older backup files it made itself in that folder, and never anything else. An empty vault is not backed up, so clearing the vault never replaces your older backups.
  • Analytics data already sent to Firebase is pseudonymous and expires automatically as described in section 3.
  • Purchase records at RevenueCat can be deleted on request; see section 4. Deleting the App does not cancel a subscription: cancel it in Google Play or the App Store.

10. Changes to this policy

We may update this policy when the App changes. The current version is always published at this address and linked from the App's Settings. Material changes are reflected in the effective date and version at the top of this page and, where appropriate, highlighted in the App's release notes.

Contact us

Questions about this page, or about Cloak? We usually reply within a day.

Developer
Aquison Technologies