ALBA privacy policy
Last updated: August 8, 2026.
ALBA is a local-first file vault, account-isolated browser, web media saver, download manager, and offline player for iPhone, iPad, and Android. The developer does not operate a cloud account service for your vault and does not upload your vault files to third-party servers.
This policy covers the current iOS edition and the Android Launch Edition. Firebase Analytics is disabled and no third-party advertising SDK is used.
1. Local files and download work data
Completed files imported into or saved to the vault are stored in ALBA's app container and protected by ALBA's file-encryption format. The developer cannot view those files or recover your vault passcode.
To support downloading, resume, temporary playback, and finalization, ALBA first stores partial files, HLS segments, playlists, thumbnails, and job metadata in the app's Caches or temporary directory. Job metadata may contain source and referrer URLs, filenames, destination and temporary paths, sizes, status, errors, and poster or thumbnail data.
These work files are not wrapped in ALBA vault encryption before finalization and may remain for retry or recovery until the transfer is finalized, the download record is deleted, a temporary preview expires, or the operating system removes cache data. Browser favorites and download records are kept within the current vault account; active job metadata and media work files are isolated by the operating-system app sandbox but are not yet protected by ALBA vault encryption.
Folders, favorites, recent items, and encrypted file records remain local unless an eligible iOS device backup includes them or you intentionally export content. Android system backup and device-to-device transfer are disabled for ALBA. Video playback position is retained only for the current app session.
2. Web browsing and media requests
When you open a website, probe a page, or download media, your device communicates directly with the website and its delivery services. They may receive your IP address, user agent, cookies, referrer, request URLs, and other standard request information under their own privacy policies. ALBA does not operate a remote media-download proxy.
By default, cookies, cache, local storage, IndexedDB, and other embedded-browser website data persist in a data store isolated to the current local vault account so sign-in state can survive browser-view recreation. This website data is not encrypted by ALBA. You can turn off Keep Website Login Status or clear website data for the current account. In nonpersistent mode, website data is used only for the current browser session. Account isolation does not make you anonymous to websites, network providers, or the operating system.
3. On-device growth and review counters
On iOS, ALBA 1.2 stores first and most recent open dates, active-day dates, coarse onboarding and Web Save stage counts, D1 and D7 markers, review-prompt state, the last review version and date, and the last feedback date. On Android, ALBA stores first-open and last-active times, active days, cold-launch count, review-prompt state, the last requested version and date, and the last feedback date. These values remain in local app settings and are not uploaded as behavioral analytics.
For review eligibility, both platforms keep separate completed-download and played-item lists with at most 200 one-way SHA-256 fingerprints each. iOS derives these from standardized local paths. Android derives them from stable download UUID identities; legacy path hashes are used only while migrating older records. Android also keeps a bounded deduplication and migration ledger of up to 2,000 known UUID fingerprints with creation timestamps. Raw paths are not stored in the active review lists, and these review fingerprints are not uploaded. Deleting local app data removes them; eligible iOS backups remain subject to Apple's backup rules, while Android system backup is disabled.
4. Platform backups
On iOS, Apple may include eligible app data in iCloud Backup according to your settings and Apple's terms. On Android, ALBA disables operating-system backup and device-to-device transfer for app data. Uninstalling the Android app may remove the only local copy, so keep a verified encrypted export of important files.
5. Feedback and support
When you open Feedback and approve network access, ALBA connects to a third-party support service and synchronizes support history; message text is submitted only after you tap Send. Current Android feedback uses Firebase Authentication and Firestore and stores the message, time and status, a per-vault user UUID, and an anonymous Firebase UID. It does not automatically attach vault files, media, browsing URLs, display name, language, region, purchase status, app version, or Android version. The iOS support service may vary by region and app configuration. Do not submit passwords, private files, confidential URLs, account credentials, or sensitive personal information.
6. Purchases and Android Launch Edition
Paid iOS features are offered through Apple StoreKit. ALBA checks Apple-verified current entitlements and caches an unlocked or not-unlocked value on the device; Apple processes purchase and payment information under its own terms. The direct Android Launch Edition is free, includes the complete current feature set, and does not use Google Play Billing or another in-app payment service.
7. Advertising, tracking, and sale of data
ALBA does not use third-party advertising SDKs and does not sell personal information. The current release does not use remote behavioral analytics to build a profile of your browsing, downloads, or vault activity.
8. Your choices
You can delete local files from the app, disable persistent website data or clear the current vault account's website data, manage permissions in system settings, manage eligible iOS backups, and choose whether to submit feedback. Available support-record deletion options depend on the support service; some records or identities may require developer-side handling. Locking or signing out of a local vault does not delete its stored data.
9. This website
The generated ALBA website does not set its own cookies, use local or session storage, or load behavioral analytics. Google Firebase Hosting still processes standard request information such as IP address, user agent, and requested URL to deliver the site. Apple processes subsequent activity after an App Store link is opened; requesting an Android APK also creates a standard hosting request.
10. Children, changes, and contact
ALBA is a general-purpose utility and is not directed to children. This policy may be updated when product behavior or legal requirements change. The effective date at the top will be updated when material changes are published.
For support and hosting processors selected by the developer, the developer requires data protection at least equivalent to this policy to the extent controlled by the applicable service agreement. Websites and services that you independently choose to visit operate under their own terms and privacy practices and are not covered by that commitment.
For privacy questions, use the feedback and support channel inside ALBA. This associates the request with the current support conversation; include the app and operating-system versions manually when they are relevant.