Projected Payments Privacy Policy

Last updated: 10 October 2026

This policy applies to the native Android version of Projected Payments distributed through Google Play. It assumes a one-time paid app download through Google Play, with no in-app purchases, subscriptions, developer-support payments, user accounts, advertising, analytics, cloud sync, or app-operated server.

Who provides the app

Projected Payments is provided by Joseph Moseley, an independent developer in the United Kingdom.

For privacy questions or requests about information I hold, email olalopapps@gmail.com.

Information stored by the app

The app stores information you enter so it can calculate and display your wage projections. This can include:

• shift dates and times, unpaid breaks, hourly rates, notes, and estimated pay;
• past-period totals and notes, including which shifts are already included in a total;
• planned weekly rota entries;
• subscription names, amounts, billing frequency, renewal dates, last-payment dates, and end information;
• work-period and payday settings, tax estimate settings, colour choices, and other app preferences.

This information is stored on your Android device in the app’s private storage. The current Android build encrypts saved records using AES-GCM with a key held by Android Keystore. Android cloud backup and system device migration are disabled. The app requests no Internet permission and does not send your shift, wage, subscription, note, rota, or settings data to me or to an app-operated server.

The optional app lock asks Android to confirm the screen lock already set on your device. Projected Payments does not receive or store your device PIN, pattern, or password.

Encrypted backups and tablet transfer

You can make a password-protected `.ppay` backup. The app encrypts the backup before opening Android’s share sheet. The receiving device decrypts it after you enter the same passphrase. I do not receive the backup or its passphrase.

If you choose to save or send the backup with another app or service, that provider may store or process the encrypted file under its own terms. Copies saved, sent, or received outside Projected Payments remain there until you or the recipient delete them. Keep the passphrase separate from the backup file; I cannot recover it if it is lost.

Google Play purchases and purchase records

Google Play handles the checkout and payment method for a Play Store download. I do not receive or store your full payment-card number, bank login, or Google Account password.

As the developer, I can use Play Console to review order and earnings information for app sales and to respond to purchase issues or refund requests. Depending on the report and transaction, this can include an order reference, purchase date, app or product, amount and currency, tax and Google fees, payment or refund status, and limited region or device information. Play Console can locate an order using its order reference or a buyer email address. I do not create a separate customer list or routinely copy buyer email addresses into my own records.

I use the minimum purchase information needed to reconcile sales and payouts, keep required accounting records, answer a purchase-support request, and handle a refund, chargeback, or dispute. If you contact me about a purchase, I may use the order reference and the contact details you provide to locate the transaction. Please do not email me your wage records, payslip, National Insurance number, payment-card details, or Google password.

For the limited purchase and support information I handle, I use it as needed to deal with your app purchase or support request, to meet legal accounting and tax obligations, and for my legitimate interests in responding to questions and resolving refunds, chargebacks, and disputes.

Google independently processes Google Account, checkout, and payment information under Google’s Privacy Policy. For UK purchases through Google Play Billing, Google says it handles the customer VAT for the transaction. I receive Google’s developer reports and payout information, not your full payment credentials.

Support messages

If you email me, I receive the email address and any information you choose to include, such as your message, Android version, app version, or order reference. I use it to reply and resolve the issue. I normally delete or anonymise support messages 12 months after the issue is closed, unless I need the relevant information for an open complaint, refund, legal claim, or other legal requirement.

How purchase records are stored and how long they are kept

I do not store purchase records inside the app. I keep only the Play earnings, payout, fee, tax, and refund evidence needed for bookkeeping and legal obligations. Downloaded business records are kept in access-restricted, encrypted storage, and access to the Google account used for Play Console is protected with multi-factor authentication.

Where Self Assessment business-record rules apply, HMRC says records must be kept for at least five years after the 31 January filing deadline for the relevant tax year. I may need to keep relevant records longer if an HMRC enquiry or legal dispute is still open. I do not keep buyer contact details for that whole period unless they are necessary for a continuing matter. See HMRC’s record-keeping guidance.

The app keeps your local records until you delete them, clear the app’s storage, or uninstall the app. Exported backup files remain wherever you chose to save or send them until those copies are deleted.

Sharing

I do not sell your information or use it for advertising. Projected Payments has no analytics or advertising SDKs and no app-operated cloud service. Information may be handled by:

• Google Play and Google Payments for app distribution, checkout, order management, and payouts;
• the email provider used for support correspondence;
• an app or storage provider you choose when exporting or sharing an encrypted backup;
• HMRC or another authority if I am legally required to provide relevant business records.

The providers above may process information under their own privacy terms. Google may process purchase or support information in other countries under its applicable safeguards and privacy terms.

Your choices and privacy rights

You can edit or delete individual shifts, past totals, subscriptions, and rota entries in the app. To remove all app data from a device, use Android Settings to clear Projected Payments’ storage or uninstall the app. Separately delete any exported backup files from the places where you saved or sent them.

I cannot view, change, or remotely delete records that remain only in the app’s local storage. For purchase-support emails or other personal information I hold, you can contact me at olalopapps@gmail.com to ask for access, correction, deletion, restriction of use, or portability, or to object where I rely on legitimate interests. These rights depend on the circumstances, and I may retain information where the law requires it or where it is still needed to handle a dispute or legal claim. For information held by Google, use Google’s privacy tools and policies.

You can also complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint.

Estimates and automated decisions

The app calculates estimates from the information you enter, including a UK tax and National Insurance estimate. It does not send that information to me, use it to make decisions about you, or create an account or profile about you. Its estimates are not a payslip or a guarantee of what an employer will pay.

Changes to this policy

If the app’s data handling changes, I will update this policy and the Google Play Data safety information before distributing the changed app. The latest version of this policy will be available through the privacy-policy link on the Google Play listing and from within the app.