Privacy Policy for Placeholder
- App:
- Placeholder
- Package:
- com.batranelu.placeholder
- Effective:
- 15 November 2026
- Last updated:
- 15 November 2026
Placeholder is a budgeting app published under the trading name Batranelu.dev ("we", "us") by an independent developer based in the Netherlands. Batranelu.dev is not a registered company. You can reach us at [email protected].
This policy explains what the app does with your information. It covers the Android app com.batranelu.placeholder distributed through Google Play, and nothing else.
If you want the short version: your financial data never leaves your device unless you choose to send it somewhere, and we hold no data about you at all. Your budgets, expenses, income, bills and subscriptions, loans and trips stay in the app's own storage, and none of it is ever in anything the app sends. Three things can leave your device. If you switch on Crash reports & usage data, the app sends crash reports and a few counts of how it is used to Google Firebase, with amounts, quoted text and file names removed on your device first, and carrying no identifier we chose, so we never receive anything that identifies you; this is off until you switch it on. If you switch on Back up to Google, Android copies the app's data to your own Google account backup; that is off until you turn it on too. And because the app is free and paid for by advertising, Google receives your Advertising ID and IP address in order to select and show ads. That part is not optional, it starts when an ad first loads, and section 2.3 sets it out in full.
1.What stays on your device
Placeholder stores the following in the app's own private storage, which other apps cannot read:
- Your budgets. For each envelope: its name, monthly amount, group, icon and, where you made one for a trip, the trip it belongs to. When you move money from one envelope to another, the month, the two envelopes and the amount moved.
- Your transactions. For each expense or income entry: the amount, the date, the description you typed, the envelope or income source it belongs to, any subcategory, the trip it belongs to, whether it was logged from a bill's payment, and, for an amount in another currency, the original amount, the currency and the exchange rate used. An expense spread over several months also records which months it covers.
- Your bills and loans. Bills are your subscriptions, such as streaming or software, and your household bills, such as rent, utilities or insurance. For each bill: its name, category, amount and whether that amount varies, how often it is due (every month or every two, three, six or twelve months) and, for a longer cycle, whether it is spread across the months or counted when paid, its due date, the envelope it is paid from, its icon and any notes you add. For each loan: its name, monthly payment or single repayment, interest rate, remaining balance, due date, the envelope it is paid from, icon and any notes you add, and whether it is money you borrowed or money you lent.
- Your trips. Their names, currency, length, budget and whether they have ended.
- Your settings. Your home currency, which features you track (income, bills and subscriptions, loans) and, if you track income, the date you started, the income sources you named, any exchange rates you set yourself, any custom currencies you added, whether you finished first-run setup, and your answers to Back up to Google and Crash reports & usage data. Whether Reminders are on is stored too. Reminders are made on your device: once a day the app looks at the bills, subscriptions and loans you entered and, if a payment is due or a recap is ready, shows a notification. Nothing is sent anywhere to do this, and on a locked screen the notification says only "Payment reminder", without names or amounts.
- When the weekly and monthly recaps were last shown, and which reminders were already sent, so each appears once rather than every time you open the app or every day.
- Your chosen language, on Android versions that do not keep that choice for the app themselves.
- Your answer to the advertising consent form, where one applies to you. Google's consent SDK writes it to the app's own preferences in the standard format the advertising industry uses, so that the ad network can read the answer you gave. It records your choice, not you.
Exchange rates are either built into the app or typed in by you. The app does not fetch them from anywhere.
We have no server, no account system and no sync. We cannot see any of this, and there is nothing for us to log into.
2.What leaves your device
Crash reports and usage data leave only if you switch them on. The last step of first-run setup asks whether the app may send them, and the switch is off unless you turn it on. Until you do, both Google services below are switched off in the app and transmit nothing at all. You can change your answer at any time in Settings → Data → Crash reports & usage data.
Advertising is not opt-in, because the app is free and advertising is what pays for it. Where the law requires your consent first you are asked, through the form described in section 2.3, and no ad is requested until you have answered.
Your financial data is never in any of it. No amount, description, envelope, bill, subscription, loan or trip name, income source or exchange rate is sent by any of the services in this section.
2.1Crash reports (Google Firebase Crashlytics)
If you consent, when the app crashes or hits an error it handles, it sends:
- the stack trace and the type of error;
- the error message, with numbers, quoted text, file paths and document names removed on your device before sending;
- a short trail of the app's own actions leading up to it, in fixed phrases such as "Export as CSV failed";
- your device model, Android version and app version;
- the exact source revision the build came from, and whether it was built from modified source (these describe our code, not you);
- a random identifier Crashlytics generates for the installation, and the time of the crash.
Why: to find and fix what breaks. Without a report, "the app closed when I exported" cannot be investigated.
What is never in a crash report: any amount or figure you entered, any name or description you typed, and the name of any file you exported or imported. Error messages in a budgeting app can quote what was being processed, which is why the app removes every number and every piece of quoted text from them, not only file names.
What Google receives that we do not. Sending a report means your device contacting Google's servers, so Google sees your IP address in the process, the same way any server sees the address of a device that connects to it. It is not part of the report and never reaches us. Google calls this service data and handles it under its own privacy policy rather than on our instructions. For the report itself Google acts on our behalf; for this it does not.
2.2Usage data (Google Analytics for Firebase)
If you consent, Google Analytics for Firebase collects, while you use the app:
- a randomly generated app-instance identifier;
- your IP address, which Google uses to derive an approximate location, typically country or region;
- automatic events such as first open, app updates, session starts and session length;
- one event the app sends deliberately: that an imported file was rejected, with the type of error, so that a broken import can be told apart from a damaged file. It never includes the file or anything in it.
Unlike crash reports, this is sent during ordinary use, not only when something goes wrong.
Three things we have deliberately switched off:
- Your Advertising ID is not collected as usage data. Analytics is configured not to collect it, in every version of the app. The app does hold the
AD_IDpermission, because AdMob needs it to serve the ads described in section 2.3; that is a separate system, with its own separate consent, and we have not linked Analytics to AdMob or Google Ads. Nothing in the usage data described in this section carries a cross-app advertising identifier. - Install attribution is not collected. The app does not request permission to ask the Play Store how it was installed, so we do not learn which link or campaign brought you here.
- Automatic screen-view reporting is off, so Google does not receive a record of which screens you visit, such as when you look at your loans or a trip.
Why: to understand how many people use the app, on which devices and Android versions, and whether an update made things worse.
2.3Advertising (Google AdMob)
Placeholder is free and supported by advertising served by Google AdMob.
To show ads, Google receives your Advertising ID, your IP address, general device information, and information about the ads shown to you and whether you interacted with them. It does not receive your budgets, transactions or anything else listed in section 1.
On Android versions that provide them, the ads SDK can also use Android's own Privacy Sandbox interfaces, and the app asks for the permissions they require. These are operating system features rather than something we run: Android derives coarse interest topics from the apps on your device and can pass them to advertisers, and it can measure whether seeing an ad led to an install without handing anyone a profile of you. They exist to reduce what cross-app identifiers are used for. We receive nothing from them, and you can review Android's own controls for them in your device settings under Privacy.
Where the law requires your consent before any of that, you are asked for it first, through a form provided by Google's certified consent platform. Fetching that form means your device contacting Google, so Google sees your IP address in the process; nothing about ads is requested until you have answered. In the European Economic Area, the United Kingdom and Switzerland that form appears before any ad loads, and it asks whether Google and its advertising partners may use your data for personalised advertising. Where a form applies to you, you can reopen it at any time from Settings → Ad privacy settings. If you decline, you will still see ads, but they will not be personalised. Non-personalised ads still use your Advertising ID and IP address for frequency capping, aggregate reporting and fraud prevention.
Which form you see, and whether you see one at all, is decided by Google's platform from where you are, not by the app. The app asks it each time it starts and shows whatever it returns; it never decides for itself that your region does not need asking. That is deliberate, so that a form becoming applicable to more people reaches you without the app having to be updated. Where no form applies to you, Ad privacy settings does not appear in Settings, because there is nothing for it to open. Your device's own advertising controls work either way.
You can reset or delete your Advertising ID at any time in Settings → Privacy → Ads on your Android device.
Your answer to Crash reports & usage data and your answer to the advertising form are recorded separately. Neither one answers for the other.
Placeholder shows two kinds of ad. One is a small native ad, marked "Ad", inside the lists on its Home, Budgets, Bills (subscriptions and household bills), Loans and Trips screens, after the third row, or at the end of a shorter list. The other is a banner along the bottom of the Stats, Recaps and Settings screens. Both come from AdMob and are governed by everything above. There is no ad in the detail screens or during first-run setup, and there are no full-screen ads.
Removing ads. You can pay once, through Google Play, to remove every ad for good, the ads in the lists and the banners alike. Google Play takes the payment and keeps the record of it; Placeholder never sees your payment details, your name or your Google account. The app asks Google Play only whether the account on your device has bought it, and keeps nothing but a marker on your device saying so, which is never part of a backup. Once the app knows you have bought it, no ad loads and no ad consent form is shown, and Ad privacy settings disappears from Settings because there is nothing left for it to control. Your answer to Crash reports & usage data is unaffected.
2.4Back up to Google (only if you turn it on)
Android can back up an app's data to your Google account. For Placeholder that is your choice, and it is off until you turn it on: the option is offered as the last step of first-run setup and at any time in Settings → Data → Back up to Google.
When it is on, Android copies everything listed in section 1 to your personal Google account backup, stored in Google Drive. That is all of it, not a selection: your budgets, transactions, bills and subscriptions, loans, trips and settings. It is also nothing more: the files the advertising and Firebase software keep for themselves, including the identifiers described in section 2, are left out, apart from your answer to the advertising consent form listed in section 1, so on a new device they start afresh rather than following you there. Android makes the backup, not the app, and only if backup is also switched on in your device's own settings. That backup belongs to you and is encrypted by Google; we have no access to it.
When you set up a new device with the same Google account, or install the app again, Android can put that data back.
When it is off, nothing from section 1 is copied to your Google account. The backup Android keeps for the app then holds a single setting, the fact that backup is off, so that a backup made while the option was on is replaced by that one rather than left in your account. If you want a copy of your data that you keep yourself, use Settings → Data → Export as JSON.
2.5Moving to a new device directly
On Android 12 and later, a new device can copy apps and their data straight from your old one during setup, by cable or over Wi-Fi. That transfer goes from one of your devices to the other without passing through the cloud, and it always includes Placeholder's data, whether or not Back up to Google is on. It copies the same things as the backup in section 2.4 and nothing more. Your data does not reach us in either case.
3.What Placeholder never collects
The app does not request or receive your name, email address, phone number, contacts, photos, location, bank account details, card numbers or login credentials, messages, or the contents of any other app. It does not connect to your bank and cannot read your bank's statements, notifications or text messages. Every figure in it is one you typed in or imported yourself. It has no account and no login.
When you export your data (Export as JSON, Export as CSV) or import it (Import from JSON), the file goes to or comes from the location you choose in your device's file picker. That file is yours; it does not pass through us. An exported file contains your financial data in readable form, so keep it somewhere you trust.
Placeholder does not need a network connection to do its job. Budgeting, entering expenses and income, bills and subscriptions, loans, trips, statistics, recaps, export and import all work with the device offline. The network is used for two things only: loading the ads described in section 2.3, and sending the crash reports and usage data in sections 2.1 and 2.2 if you have switched those on. Buying the removal of ads, and checking that you have, goes through the Google Play Store app on your device, which talks to Google itself. The Google backup in section 2.4 is carried out by Android, not by the app.
4.Who else is involved
| Service | Provided by | What for | Their policy |
|---|---|---|---|
| Firebase Crashlytics | Google Ireland Limited / Google LLC | Crash and error reports | firebase.google.com/support/privacy |
| Google Analytics for Firebase | Google Ireland Limited / Google LLC | Usage measurement | firebase.google.com/support/privacy |
| Google AdMob, including its consent form | Google Ireland Limited / Google LLC | Serving ads, and asking for consent where the law requires it | policies.google.com/technologies/partner-sites |
| Android Backup | Your own Google account backup, only if you turn it on | policies.google.com/privacy | |
| Google Play Billing | Google Ireland Limited / Google LLC | The one-time purchase that removes ads | policies.google.com/privacy |
For crash reports and usage data, Google acts as our processor under the Firebase Data Processing and Security Terms. For advertising, Google acts as an independent controller of the data it collects, and its own privacy policy governs what it does with it. For the backup, Google stores your data on your behalf under your Google account's terms; we are not involved and cannot reach it.
These services are operated by Google and data may be transferred to and stored in the United States and other countries. Google relies on the European Commission's Standard Contractual Clauses and its certification under the EU-US Data Privacy Framework for those transfers.
We do not sell your personal information, and the only parties who ever receive it are the services listed above, all of them Google. ("Share" has a narrower, specific meaning under California law, which section 7.2 addresses directly rather than leaning on the ordinary sense of the word.)
This policy covers the app and nothing else. When Placeholder opens something outside itself, what happens there is governed by whoever runs it, not by this page. That includes the link to this policy, the file picker you export through, and the app you open an exported file with. We do not receive anything back from any of them.
An ad is a link out too. Tapping one hands you to Google's ad network and then to an advertiser's own page or store listing, or to a Google Play install sheet shown over the app. What that advertiser collects is theirs and is covered by their policy, not this one. We do not choose which ads you see and we receive nothing about what you do after you tap.
5.Legal basis (EEA, UK and Switzerland)
Everything the app stores stays on your device, under your control. We process crash reports and usage data only with your consent, under Article 6(1)(a) UK/EU GDPR. There is no other basis, and no legitimate-interest processing of your data by us.
Where the law requires it, personalised advertising also happens only with your consent, asked for through the form described in section 2.3. Google, as an independent controller, sets out its own legal bases for the rest of its ad processing, such as frequency capping and fraud prevention, in its policy linked in section 4.
The Google backup in section 2.4 happens only because you turned it on, and you can turn it off again at any time.
You can withdraw consent at any time, with no effect on the lawfulness of what was processed beforehand:
- Crash reports and usage data: Settings → Data → turn off "Crash reports & usage data".
- Advertising: Settings → Ad privacy settings, where a form applies to you.
- Back up to Google: Settings → Data → Back up to Google.
Withdrawing crash-reporting consent stops further collection immediately. It also deletes any report still waiting on your device to be sent, and clears the analytics identifiers held on your device.
The app works identically whether you consent or not. No feature is withheld.
6.How long it is kept
- On your device: your data stays until you delete it, use Settings → Data → Reset data, or uninstall the app.
- Your Google backup, if you turned it on: Android keeps it in your Google account and replaces it with each new backup. Turning Back up to Google off replaces it at the next backup with one that holds only that setting. How long Google keeps an app's backup after you stop using the device is set by Google, not by us.
- Crash reports: Google retains Crashlytics crash data for 90 days.
- Usage data: user-level analytics data is retained for 2 months, counted from your last activity in the app rather than from when it was collected. Each time you use Placeholder, the two months start again, so it is deleted two months after you stop using the app. Aggregated reports that cannot identify a device may be kept longer.
- Advertising data: retained by Google under its own policy, linked in section 4.
7.Your rights
7.1EEA, UK and Switzerland
If you are in the EEA, the UK or Switzerland, you have the right to access, correct, erase, restrict or object to the processing of your personal data, to data portability, and to withdraw consent.
We cannot action a request to delete or produce "your" data, and we do not operate a service that tries to. This is not a policy choice dressed up as a limitation. It follows from the app's design, and the law provides for it directly.
Your financial data never reaches us: it is on your device. What we can receive, crash reports and usage data, and only if you agreed, is pseudonymous. We receive no name, no email address, no account, no device identifier that belongs to you rather than to an app installation. The identifiers attached to a crash report or a usage event are randomly generated by Google's SDKs and mean nothing outside them. Given a person, we have no way to find their data; given a record, we have no way to find the person. We hold nothing that bridges the two, and we have deliberately not built anything that would.
Article 11(2) UK/EU GDPR covers exactly this position: where a controller can demonstrate it is not in a position to identify the data subject, the rights of access, rectification, erasure, restriction and portability (Articles 15 to 20) do not apply. Article 11(1) adds that we are not obliged to acquire or keep extra information about you purely so that we could comply. Collecting more about you in order to be able to delete you would make your privacy worse, not better, and we will not do it.
Those rights revive, under the one exception Article 11(2) itself provides: if you can supply information that identifies your data to us. In practice that would mean the Firebase app-instance identifier or the Crashlytics installation identifier for your install. The app does not display either, so this is a real exception rather than a practical route. If you do obtain one and send it to us, we will act on it.
What this does not mean. It does not mean the data is kept forever, and it does not leave you without control. Deletion happens by time and by your own switches rather than by asking us: crash reports are deleted by Google after 90 days and usage data two months after your last activity (section 6); withdrawing consent stops collection, deletes queued reports and resets the identifiers on your device, so old records stop being about your install at all; and uninstalling removes everything held on the device.
The rights still work, through the controls that actually hold your data:
- Your financial data: it is on your device. Edit or delete it in the app, use Settings → Data → Reset data, export a copy with Export as JSON (which also covers portability), or uninstall the app.
- Your Google backup: turn off Back up to Google, and manage or delete backups in your Google account.
- Crash reports and usage data: withdraw consent in Settings → Data, as above.
- Advertising: reopen the consent form at Settings → Ad privacy settings, where one applies to you.
- Your Advertising ID: reset or delete it in your device's Android settings.
- Data held by Google: contact Google directly using the links in section 4.
You also have the right to lodge a complaint with a data protection authority. Ours is the Dutch Autoriteit Persoonsgegevens (https://autoriteitpersoonsgegevens.nl). You may also complain to the authority where you live or work, wherever that is in the EEA. You do not have to come to ours.
7.2United States
This section applies wherever you are in the United States. Several states now give residents similar rights, and rather than guess which of them we are large enough to be caught by, we give everyone the same answers and the same controls.
Categories of personal information collected in connection with the app. Using the categories California's law defines:
| Category | What, specifically | Where it comes from |
|---|---|---|
| Identifiers | A random app-instance identifier and a random Crashlytics installation identifier, if you switched on crash reports and usage data; your Advertising ID; and your IP address, which Google receives whenever the app contacts its servers, and which we never see | The random identifiers are generated on your device; your Advertising ID is held by Android; your IP address is observed by Google |
| Internet or network activity | If you switched them on: app opens, sessions, updates, which of the app's own actions preceded an error, and the import event in section 2.2. Always: which ads were shown and whether you interacted with them | Your use of the app |
| Geolocation (approximate only) | A country or region derived from your IP address. We do not collect precise location | Your IP address, by Google |
| Financial information | None. Your budgets and transactions stay on your device | n/a |
| Inferences | None by us. We build no profile of you | n/a |
| Sensitive personal information | None. | n/a |
These are collected for the purposes in sections 2.1, 2.2 and 2.3, from no source other than your own device, and go only to Google as described in section 4.
Selling and sharing. We do not sell your personal information for money, and never have.
However, California's law defines "sharing" specifically to include disclosing personal information for cross-context behavioural advertising, which means personalised ads. Placeholder serves ads, and where you have not declined personalisation your Advertising ID and IP address go to Google for that purpose, which is "sharing" as the statute uses the word. Other states describe the same activity as "targeted advertising".
How to opt out of that.
- On your device, at Settings → Privacy → Ads, you can turn on "Opt out of Ads Personalization" or delete your Advertising ID outright. This applies to every app, not just this one, and Google honours it.
- In the app, at Settings → Ad privacy settings, where Google's platform offers a form for your state.
- Declining crash reports and usage data in Settings → Data stops everything described in sections 2.1 and 2.2, independently of advertising.
Your rights. To know what is collected, to a copy of it, to have it corrected or deleted, to opt out of sale or sharing, and to limit the use of sensitive personal information. The last of these has no basis here, because none is collected.
Non-discrimination. We will not charge you a different price, give you a lower level of service, or withhold any feature because you exercised any of these rights. The app behaves identically whichever way you answer.
We do not operate a data deletion or access service. A request to know or delete has to be verifiable: we have to be able to establish that the data is yours before acting on it. We cannot, for anyone. Your financial data never reaches us, and what does, only with your consent, is pseudonymous: no name, no email address, no account, and identifiers randomly generated per app installation that mean nothing outside Google's SDKs. California's section 1798.145 provides that a business is not required to reidentify or otherwise link information that it does not, in the ordinary course of business, maintain in a form that would be considered personal information, nor to collect, retain or obtain any data or technology in order to become capable of linking a request to a person. Every state law modelled on it takes the same approach.
What still deletes your data, without asking us: 90 days for crash reports and two months from your last activity for usage data (section 6); withdrawing consent, which stops collection, clears queued reports and resets the identifiers on your device; and uninstalling, which removes everything held locally, your financial data included.
You can still write to us at [email protected], and we will respond within 45 days, including to tell you, where that is the answer, that we could not identify any data as yours. An authorised agent may contact us on your behalf. If you can supply the Firebase app-instance identifier or Crashlytics installation identifier for your install, that changes things and we will act on it.
Do Not Track. Placeholder is a mobile app, not a web browser, and receives no Do Not Track or Global Privacy Control signal from your device. We therefore do not respond to one. The device-level advertising controls above are the equivalent mechanism on Android, and those we do honour.
Children. We do not knowingly collect personal information from anyone under 18. That is well above the age of 13 set by the federal Children's Online Privacy Protection Act, and deliberately so. See section 8.
8.Children
Placeholder is not directed to children and is not designed for them. It is listed on Google Play for an audience of 18 and over.
Crash reports and usage data rest on consent, and so does advertising where the law requires it, and the age at which a person can give that consent for themselves differs by country. Rather than apply a different age in each place, we apply the highest one everywhere: we do not knowingly collect personal data from anyone under 18, wherever you are.
That is higher than any of them requires. The Netherlands, where we are established, sets 16, and that is what the EEA and the UK would ask of us; the United States sets 13 under the Children's Online Privacy Protection Act, and other countries fall between. Eighteen is the age this app is listed for, so it is the age we hold ourselves to as well.
If you are a parent or guardian and believe a child has used Placeholder, tell us at [email protected]. We receive nothing that identifies anyone, so we cannot locate one child's records among pseudonymous data. The remedy that works is on the device and takes effect immediately: turn off Crash reports & usage data in Settings → Data, which stops collection and clears the identifiers held on the device, delete the app's data with Reset data or uninstall the app, and reset the device's Advertising ID in its Android settings. What has already been sent then ages out on the schedule in section 6.
9.Security
Your data is stored in the app's private storage, which the Android operating system isolates from other apps. Everything sent to the services in section 4 travels over encrypted connections. We hold no database of our own, which is the strongest security property this app has: there is nothing of yours for us to lose.
No method of transmission or storage is completely secure, and we will not claim otherwise. What we can say is narrower and more useful: the part of this that is normally the risk, a server holding users' financial records, does not exist here. The copies that can exist outside the app, an exported file and your Google backup, are under your control, so protect them as you would any financial document.
If there is ever a breach. Where a breach affects personal data and the law requires it, we will notify the Dutch Autoriteit Persoonsgegevens within 72 hours of becoming aware of it. We cannot notify you individually, because we hold no email address, no account and nothing else we could reach you with. So we would also publish a notice at this address, and keep it here rather than replacing the page silently. A breach at Google affecting crash, usage, advertising or backup data is Google's to disclose, under the policies linked in section 4.
10.Legal requests, and what happens if the app changes hands
Requests from authorities. We have never received a request from a law enforcement agency or a court for user data, and we hold nothing that would answer one. There is no database, no account and no server. If we ever do receive a lawful request we will comply with it to the extent the law requires, which for the data described in this policy means telling the requester that we hold nothing responsive. Crash, usage, advertising and backup data sit with Google, and a request for those has to go to Google, which handles it under its own policies rather than on our instructions.
If the app is sold or transferred. Placeholder is published by an independent developer, and an app can change hands. If that happens, there is no user database to transfer, because none exists. What would transfer is the app itself and the Google service accounts behind it. A new owner would take on this policy as it stands, and any change to what the app collects would go through section 11 like any other change: published here first, and asked again in the app if it is material.
11.Changes to this policy
If we change what the app collects, we will update this policy and change the date at the top. A change is published at this address before it takes effect, not after. If a change means collecting something materially new, we will ask for your consent again in the app rather than relying on this page having changed.