Last updated 15 September 2026
iPayment is a personal payment tracker for iPhone. This policy explains exactly what the app accesses, what it stores, where it stores it, and what it never does. It covers the iPayment iOS app only.
The short version. Your payments live on your iPhone. If you choose to connect Google Drive, they are also backed up to a private folder inside your own Drive that only this app can see. There is no iPayment account, no server operated by us, no analytics, no advertising, and nothing is sold or shared with third parties.
iPayment records only what you enter:
This is held in the app’s local database on your device. We do not receive it and cannot see it.
Connecting Google Drive is entirely optional; the app works fully without it. If you sign in, Google provides iPayment with your email address and basic profile information. Your email address is shown in the app’s Settings screen so you can tell which account is connected. It is not transmitted anywhere else and is not stored off your device.
iPayment never receives or handles your Google password. Sign-in happens through Google’s own interface.
iPayment requests one Google Drive permission:
| Scope | What it allows | Why iPayment asks |
|---|---|---|
drive.appdata |
Access only to the hidden application-data folder that Drive reserves for this app. It grants no access to any other file in your Drive. | To back up your payment records so you can restore them on a new device. |
Inside that folder the app maintains a single file, ipayment-sync.json, containing
your payment records, your monthly credit amounts, and your exchange rate. Nothing else is
written, and no other file in your Drive is read, modified, or listed.
The application-data folder is hidden by design: other apps cannot see it, and it does not appear when you browse Drive normally. The file is stored under your own Google account and remains your data.
iPayment’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Data obtained through Google APIs is used solely to provide and improve the backup and restore feature described above. It is never used for advertising, never sold, never transferred to third parties, and never read by humans.
The microphone is used only while you are actively dictating a payment — after you tap the microphone button, and until the entry is added or dismissed. It is never accessed in the background.
Speech is converted to text using Apple’s speech recognition. Depending on your device, language, and settings, Apple may process the audio on its servers; that processing is governed by Apple’s privacy policy. iPayment does not record, store, or transmit audio itself, and the resulting text is used only to fill in the payment you are creating.
Because we hold no copy of your data, there is nothing for us to delete on your behalf. If you have a question about any of this, contact us using the address below.
iPayment is not directed at children under 13 and does not knowingly collect information from them.
If this policy changes, the revised version will be posted on this page with a new date above. Material changes affecting how Google user data is handled will be reflected here before they take effect.
Questions about this policy or about your data: ikhaled.dev@icloud.com.