PayCycle
Sub & Bill Tracker
Privacy Policy Version 1.1 Your records stay on your device

Effective 29 October 2026

Privacy Policy

PayCycle: Sub & Bill Tracker keeps your records on your device. There is no sign-up, no server of ours to talk to, and no analytics running behind the screens. Everything you type into PayCycle is written to the app's private storage on your device, and none of it reaches BAPU Apps.

Applies to PayCycle 1.1 on Android and iOS Published by BAPU Apps Last updated 29 October 2026

The ledger, in short

Your records never leave
Records sent to BAPU Apps 0 Still true. The app has no server of ours to send anything to. It does ask the network for ads, but those requests carry no part of your records.
Records shared with third parties Google only Google AdMob serves the ads. It sees your device's advertising identifier and the rough shape of the ad request — never what you have entered in PayCycle.
Accounts you need to create 0 No email address, no password, no social sign-in. The app opens and works straight away.
Records kept on your device All of them Every subscription, bill, category, price change and setting you enter, plus the reminders scheduled on the phone.

Why it works that way: PayCycle shows you what you told it to show you. With no bank connection and no sync, the app has nothing of yours to transmit and nothing to reconcile, which is also why it runs on a plane with the SIM card out. The ads are the one thing that leaves, and they leave without taking any of it with them.

01 — Who we are

The publisher of PayCycle

PayCycle: Sub & Bill Tracker ("the app", "PayCycle") is developed and published by BAPU Apps ("we", "us", "our"). We are the business behind the app and the only party involved in operating it.

We reach you at hevcode.com and at contact@hevcode.com. If a question in this policy is unclear, that is the address to ask it at.

02 — Information we collect

Your records, and one advertising identifier

We do not collect, receive, transmit or buy any personal information through PayCycle. There is no server-side copy of anything you enter, because there is no server of ours in the app's path. Every figure the app shows is calculated on your device from records you typed in yourself.

The app does contain an advertising SDK, because it shows ads. That SDK is provided by Google, and it is the one part of the app that talks to the network. It sees the advertising identifier your device already carries, and it may store a cookie or a similar identifier on your device. It does not receive your subscriptions, bills, categories or notes — the app never sends them.

The following is never requested, accessed, or stored by the app:

  • Your name, email address, phone number, postal address or any other contact details
  • Payment card numbers, bank details, bank logins or transaction history — PayCycle does not connect to a bank, so it never holds what you pay with
  • Your photos, contacts, calendar entries, files, location, microphone or camera
  • Your subscription and bill records — the names, amounts and notes you enter stay in the app's private storage
  • Usage analytics, session logs, crash reports or telemetry
  • Anything belonging to another app on your device

One thing to be aware of. PayCycle's reports and reminders describe money you owe, and the amounts and names you enter are private, but they are not secrets from anyone who can open your phone. Use a device lock. We never see any of it, and that cuts both ways: we also cannot recover it for you.

03 — Information stored on your device

What the app keeps, and where

The app writes to its own private storage on your device. Android and iOS both keep that storage inside the app's sandbox, so other apps cannot read it and it is removed when you uninstall PayCycle. This is the full inventory:

Everything PayCycle stores, and where it lives
Records What it holds Where
Subscriptions and bills Name, price, billing cycle, start date, category, notes, payment method label, free-trial flag and end date, reminder lead time, last-used date, "no longer using" flag, and the dates the record was created and last edited The app's private database on this device
Categories The names, icons and colours of the categories you add, plus the default set that ships with the app The app's private database on this device
Price history The previous and new price of an item and the date of the change, written automatically when you edit an amount The app's private database on this device
Settings Your default reminder lead time, your theme choice, and whether you have seen the intro The app's private database on this device
Reminders The time each reminder should fire, and the item's name, amount and renewal date as shown in the notification The operating system's notification scheduler on this device
Export files A JSON copy of the records above, in a file you chose Whichever app or folder you saved it to — see section 05
Advertising and consent state Your consent choice, and the advertising identifiers Google's SDK keeps on this device Google's own storage on this device — see section 07

The app also lets you fill it with example records so you can look around before entering your own. Those examples are ordinary rows in the same database, and you can edit or delete them like anything else.

04 — Permissions PayCycle asks for

Four for reminders, and the network for ads

PayCycle asks for the following. The first four relate to a renewal reminder, and declining any of them leaves the rest of the app working. The last two are what Android needs before an app may reach the network at all.

Permissions requested by the app
Permission Why If you decline
Notifications Android 13+ / iOS To show the reminder before a renewal No reminders. Everything else works.
Exact alarms Android 12+ So a reminder arrives at the time you picked rather than "sometime later" Reminders are still delivered, a few minutes late
Reboot Android To re-arm scheduled reminders after the phone restarts Reminders scheduled before a restart may be lost
Files Only when you open a document, to read an import file or write an export file Import and export are unavailable
Internet Android To fetch the ads from Google's servers No ads. Everything else works.
Network state Android To tell whether the device is online before spending a request on an ad No ads. Everything else works.

PayCycle does not request access to your camera, microphone, contacts, photo library, location or background location. It does not request the "exact alarm" permission that Google Play reserves for alarm and calendar apps, and it does not run in the background or watch other apps.

On iOS the system may also ask whether you allow apps to track you across other apps. That prompt comes from iOS, not from us. If you decline it, the ads are still shown but they are not personalised, and the app works exactly as before.

05 — Export and import files

Your records leave only when you send them

PayCycle lets you export your records as a JSON file and send it through the system's own share sheet, and lets you import such a file through the system file picker. Those files are written and read directly on your device. The app has no upload step, and the service you send a file to receives it from your device, not from us.

An export file is readable. It is plain JSON, not encrypted, and it contains the names, amounts and notes of your subscriptions and bills. Treat it like a bank statement: keep it somewhere private, and delete it once you no longer need it. Files you send to a third-party service, such as an email or messaging app, leave our control at that point and are handled under that service's own privacy policy.

06 — How information is used

Your records are used on your device, and nowhere else

The app uses the records you enter to do one job: calculate and display your spending, renewal dates, free trials, projected savings and reminders. All of that arithmetic happens locally, on your device, using the data stored in its private database.

None of it is used for advertising, profiling, model training or market research, and no one else is given access to it. The advertising identifier the ad SDK works with is Google's own business, and it is not connected to anything you have entered in PayCycle.

07 — Advertising

Ads, and what they can see

This version of PayCycle shows ads, served by Google AdMob. The app carries Google's advertising SDK, and the ads it shows are banner, native, interstitial, and app open ads.

The SDK does not receive anything you have entered in PayCycle. It does not receive your subscriptions, bills, categories, notes or amounts, and it never sees your export files. What it does receive is your device's advertising identifier, the app's version, and the approximate region and language. It may also set a cookie or a similar identifier on your device, to remember which ads it has already shown you.

In the EEA, the United Kingdom and Switzerland we ask for your consent through Google's consent form before showing personalised ads. If you decline, or if you are somewhere the form is not offered, the ads are non-personalised: the same ads for everyone, chosen at random rather than chosen for you.

You can withdraw or change your consent at any time from Settings → Privacy options in the app, and you can limit ad tracking from your device's own settings. Withdrawing your consent does not change anything else about the app.

An ad is still an ad. PayCycle asks for no financial permissions and holds no banking credentials, which makes it a poor target for anything that wants your money. But an advert is a stranger's marketing, and it can be a convincing one. Read the advertiser before you act on one, and treat any request for money that comes from an ad with the suspicion it deserves.

08 — Sharing and third parties

One third party, and it is an ad server

We do not sell, rent, trade or otherwise disclose personal information. We do not share it with data brokers, analytics providers, cloud storage providers, or any other third party, and we have no partners who receive it.

The exception is the advertising SDK. Google AdMob receives the advertising identifier described in section 07 in order to serve and to measure ads. We do not receive the data Google collects, we cannot see it, and we cannot join it to anything you have entered in PayCycle. Google's handling of it is governed by its own privacy policy, which you can read at policies.google.com/privacy.

We will never disclose your information in response to a request from a third party, because no third party holds any of your records.

09 — Security

Local storage, kept local

Your records are stored inside the app's private storage, which the operating system isolates from other apps and encrypts at rest where the device is set up to do so. The app has no server-side copy of anything, so there is no database of yours for anyone to breach.

The advertising SDK does talk to the network, over an encrypted connection, to fetch ads. Nothing in that connection is a record you entered.

You are responsible for the security of your device, and for the export files you create. Anyone who unlocks your phone, or who receives an export file, can read what is in it.

10 — Retention and deletion

Your records stay until you remove them

Nothing expires on a schedule. Data lives as long as the app is installed, and you control its removal:

  • Delete one record: open it in PayCycle and use the delete button. Its price history goes with it.
  • Delete everything: uninstall PayCycle. This removes the app's private storage, including every subscription, bill, category, price change and setting.
  • Delete an export file: delete it wherever you saved it. Removing the app does not remove files you already exported.
  • Withdraw a permission: revoke notification access in your device settings, which cancels the reminders the app has scheduled.
  • Withdraw your permission for ads: use Settings → Privacy options, or limit ad tracking in your device's settings. The ads stop being personalised; nothing else about the app changes.

Since we hold no copy of your information, deleting it from your device is a complete deletion. We have no backup to purge, because we made none.

11 — Your rights

Rights that are easy to satisfy here

Under data protection law — including the GDPR and the UK GDPR, the CCPA and CPRA, and India's Digital Personal Data Protection Act — you have rights over your personal data: the right to access it, correct it, delete it, restrict or object to its use, export it, and withdraw consent.

Because PayCycle operates no server and holds no copy of your records, there is no separate copy of your data for us to hand over, correct or delete. Those rights are exercised directly in the app: the records you can see are the records we hold, so viewing, editing, deleting and exporting them in PayCycle is access, correction, deletion and portability all at once.

The one thing you can opt out of is personalised advertising, from Settings → Privacy options or from your device's own ad settings. We do not sell personal information, and we do not share it for anyone else's benefit.

If you want a copy of your data outside the app, use the export feature described in section 05. If you want a right exercised in any other way, write to us at contact@hevcode.com and we will help.

12 — Children's privacy

Not aimed at children

PayCycle is a general-audience utility app and is not directed at children under 13, or under 16 where that is the applicable threshold in your country. We do not knowingly collect personal information from children, and we do not collect your records from anyone.

If you believe a child has put personal information into the app on a device you manage, uninstall the app to remove it.

13 — International transfers

Your records do not travel

We do not transfer your information across borders, or anywhere else, because your records do not leave your device.

The advertising identifier the ad SDK handles is processed by Google, which may process it outside your country under its own safeguards. It never contains a record you entered.

14 — Changes to this policy

When the page changes, the date changes

We may revise this policy when the app changes. The "Last updated" date at the top always reflects the current version, and the store listing for the app will point at this page. If a revision changes what the app does with your information, we will say so clearly here.

This version records the change made for PayCycle 1.1, which added advertising. Sections 02, 04, 06, 07, 08, 09, 10, 11 and 13 were rewritten to describe the ad SDK and the consent it requires. Nothing else about the app's handling of your records changed.

15 — Contact us

Questions, requests and complaints

If you have a question about this policy, want to exercise a right, or want to raise a concern, contact BAPU Apps. We read every message.

BAPU Apps

The publisher of PayCycle: Sub & Bill Tracker. Write to us about this policy, or about anything in the app, at the address below.