Aksaty: Property Installments
Last updated: May 14, 2026
Your asset names, payment amounts, locations, photos, and notes are encrypted on your iPhone before they ever leave it. The encryption key lives only on your device (and in your private iCloud Keychain, which is itself end-to-end encrypted by Apple). The developer of Aksaty, Firebase/Google, and anyone who gains access to our servers — including via a subpoena — can only see opaque ciphertext. They cannot read your data. Even we cannot read your data.
The detailed explanation is in the "End-to-End Encryption" section below.
Aksaty collects only the information you provide directly:
We do not collect payment card numbers, national ID numbers, or any sensitive financial credentials.
Your information is used solely to:
We never sell your personal data to third parties.
Aksaty cannot read your asset names, payment amounts, locations, photos, or notes. Starting with version 1.1.0, every piece of personal content you enter is encrypted with AES-256-GCM on your device using a key that only your device holds. Firebase, the developer, and anyone served a subpoena receive only opaque encrypted bytes — not the underlying data. There is no back door and no master key on our side.
How the encryption key is managed: the first time you open Aksaty 1.1.0 a fresh 256-bit master key is generated on your device. The key is stored in the iOS Keychain (Apple's hardware-backed secure storage), and synced to your iCloud Keychain so it follows you to your other Apple devices automatically. iCloud Keychain is itself end-to-end encrypted by Apple — Apple cannot read it either. The key is never transmitted to our servers, never logged, and never stored outside of your Apple ecosystem.
What this means in practice:
What is still visible to Firebase / the developer: only your account UID, document timestamps, the number of assets you own, and storage size. The actual content of every asset, payment, location, photo, and note is opaque ciphertext — completely unreadable without your device-local key.
When you sign in, your asset and payment data is stored in your personal cloud account powered by Firebase (Google Cloud). The content is end-to-end encrypted on your device before being sent — Firebase only receives ciphertext. Transport itself uses HTTPS, and Firebase additionally encrypts data at rest, but those layers are secondary to the client-side E2EE described above.
OCR contract scanning: when you use the contract scan feature, the photo is sent to our processing server only at the moment of the scan and deleted immediately after the payment schedule is extracted. The extracted schedule is encrypted on your device before it's saved.
AI market-price estimates: the asset name and location you enter are sent to our pricing service for the duration of a single request and are not retained server-side. The result is encrypted on your device before it's saved.
Crash reporting: crash and performance data is collected via Sentry. We do not include user content in crash reports — only stack traces and device diagnostics.
We do not share your personal data with third parties except:
We do not share your asset or financial data with real-estate companies, banks, or advertisers.
You have several rights regarding your personal data:
We retain your account data for as long as your account is active. If you delete your account, all personal data is permanently deleted within 30 days.
We implement multiple layers of security, with end-to-end encryption as the strongest:
No method of electronic storage is 100% secure. The strongest protection in our stack is the client-side encryption — we cannot decrypt your content even when compelled by court order, because the key never leaves your device.
Aksaty is not directed to children under 13 years of age. We do not knowingly collect personal information from children under 13.
We may update this Privacy Policy from time to time. We will notify you of significant changes through the app or by email.
Questions? Contact us at aksatysupport@gmail.com