Privacy, in plain words.
The app doesn’t need an account. This website’s optional forms are a separate matter.
1. The Hirasa app
The Hirasa app collects no personal data, has no user accounts, and has no ads or analytics. You do not provide an email address to use the app.
Your photos, videos, files, file names, and thumbnails are encrypted on your phone before they are stored. The app keeps no record of how many vaults exist.
2. Limited network use
App network use is limited to:
- App-store purchases.
- Purchase verification.
- Encrypted backup to your own Google Drive, only if you choose to turn it on.
- Direct encrypted-package transfers to a phone on your local Wi-Fi or hotspot, only when you start nearby sharing.
The app stores and Google handle information under their own policies when you use their services. Those services are separate from Hirasa’s lack of app accounts or analytics. When you buy or restore Pro, the app sends the store's purchase identifier (an Apple transaction ID or a Google Play purchase token) and the product ID to our verification service, hosted on Netlify. The service checks the purchase with Apple or Google and returns a signed confirmation to the app. It receives no name, email, device identifier or vault content, and it stores nothing.
Nearby sharing does not send files through a Hirasa server. A temporary QR contains a local IP address, port, upload capability and public receiving invitation. These are used for the local session. The connection carries encrypted packages; network observers can see its timing, size and temporary capability. No Google Nearby or analytics SDK is used. Temporary incoming package copies are removed after use or by lock/launch cleanup, without a forensic-erasure guarantee. If you instead use another app to carry a package, that app has its own privacy practices.
3. Your vaults and backups
A pattern or passphrase opens a separate vault. A 32-character recovery key can reopen a vault if its pattern is forgotten. It is shown when the vault is created and can be viewed again from that vault’s settings while the vault is open. If both the pattern or passphrase and the recovery key are lost, access to the vault is gone for good.
Pro lets you export a vault as one encrypted file or back it up automatically to your own Google Drive. Restoring is always free.
Opening an ordinary decoy vault destroys nothing. Opening a designated Pro duress vault silently destroys every other vault on that phone. It cannot reach backup files saved elsewhere. You must manage those copies separately.
4. This website and its forms
This website does not use analytics, advertising trackers, third-party fonts, or tracking cookies. It is hosted by Netlify. Hosting and form processing may involve technical request information, such as an IP address and submission time.
The optional launch waitlist collects the email address you submit and your consent to receive Hirasa launch updates. This does not create an app account.
The support form collects your email address, selected topic, message, and your name if you choose to provide it. The information is used to address your request.
Both forms send submissions to Netlify Forms, where they are stored for the site operator to review. These website submissions are separate from the encrypted vaults and are not encrypted by the Hirasa app.
Do not submit patterns, passphrases, recovery keys, or private vault contents. To request removal from the waitlist or deletion of a website submission, use the support form and select “Website privacy request.”
5. Security and its limits
Hirasa has not yet had an independent security audit. It cannot protect a phone that is already unlocked and compromised, recover a vault after both access methods are lost, or wipe backups saved elsewhere.
See the security page for a plain explanation of these limits.
6. Before this policy is final
Hirasa is published by 10X Companies, a trade name of Vejzovic Holdings and Capital, LLC. Contact: 10xcompanies@gmail.com .
Legal review must confirm applicable privacy rights and jurisdictions, website-form retention and deletion periods, service-provider details, and any age-related requirements.
No final effective date is stated in this draft. Questions about this website can be sent through Support .
Device sync and iCloud backup
Optional Google Drive sync uploads encrypted file blobs and encrypted manifests to your own account. Manifests merge additions and retain deletion records so an offline device does not restore deleted items. Cloud blobs may remain after deletion; turning sync off or duress wiping does not erase remote copies. Sync requires configured Google sign-in and is in beta.
Native iCloud Drive backup requires an iCloud-enabled signed iPhone build. Only encrypted .hirasa backups are written. Apple controls upload scheduling. Restore through Files with the vault’s recovery key. iCloud setup and real-device verification remain pending.
Managed shared vaults are not available. Current transfers create recipient-owned copies and do not offer post-delivery revocation or open limits.