Effective date: 2026-09-11 Last updated: 2026-09-11
Resume Builder makes a CV on your phone and exports it as a PDF. Everything you type stays on your phone.
There is no account, no sign-up, no cloud and no server of ours anywhere. We never see your name, your employment history, your address or the jobs you are applying for.
This matters more here than in most apps, and it is worth saying why. A CV is the most identifying document most people own. It carries your full name, your email address, your phone number, where you live, every employer you have had and when you worked for them. Handing that to a service is a decision, and this app is built so that you never have to make it: there is nothing to send it to.
The only data that leaves your device is what Google AdMob needs to show ads, and none of it is anything you typed.
com.dashfusion.listresume)Everything is written to this app’s private storage, which no other app on your phone can read:
That is the whole list. There is no photograph anywhere in it, no location fix and no contact imported from your phone, because the app never asks for any of them.
We hold no copy of any of it. There is no analytics SDK in this app, no crash reporter of our own, and no telemetry.
The app also opts out of Android’s cloud backup and device-to-device transfer, so your CV is never copied into Google’s backup service. That is a deliberate trade and you should know which way it cuts: nothing about your career is stored off your phone, and uninstalling the app, or losing the phone, loses it. Use Settings → Save a copy before you switch phones — it is the intended way to move your data, and it is never behind an ad.
When you export, the app writes the PDF to the place you choose, through Android’s own document picker. From that moment the file is an ordinary document on your phone and this policy no longer governs it — you can send it wherever you like, and the app has no idea where that is.
The app never uploads it. There is no share link, no hosted copy and no shortened URL. The Share action hands the file to whichever app you pick using Android’s own sheet, and what happens next is between you and that app.
The PDF contains what you typed and nothing else: no tracking pixel, no hidden metadata about you, no watermark and no advertisement for this app.
Worth stating plainly, because apps in this category commonly do these things:
You can save a copy of every resume to a file you choose, and restore one back. A saved file leaves the app’s protection: it is written where you point it, in a readable JSON form other apps can open, and it contains everything in the app — which for this app means your full contact details and your whole employment history. Keep it somewhere you would keep the CV itself.
Restoring replaces what is in the app — it does not merge — and the confirmation says so before anything is overwritten.
Both the file you save and the file you restore are chosen through Android’s own document picker, which hands the app that one file and grants it nothing else.
The app is supported by ads served by Google AdMob. Ads are the only reason the app needs an internet connection at all; writing a CV, reordering it, exporting the PDF and saving a copy all work fully offline.
The app shows no banner ads, no native ads and no ads on launch. The only moment an occasional full-screen ad can appear is after a PDF has finished exporting — never while you are writing, never on the way into anything, and never between you and an email you are sending. There is also an optional rewarded video you can choose to watch to switch ads off for 24 hours. Nothing in this app is locked behind it, and that includes exporting your PDF and saving a copy of your data.
To serve ads, Google receives data from your device, which may include your
device’s advertising identifier (AD_ID), coarse location inferred from your IP
address, device and app information, and ad-interaction data. It does not
receive your name, your contact details, your employment history, any bullet
point you wrote or any PDF you exported. Google’s processing is done as an
independent controller under its own policies:
Where required by law, the app shows Google’s User Messaging Platform consent form before ads are initialised, and records your choice. In the EEA and the UK you are asked about personalised advertising; in covered US states you are offered the opt-out required there. You can change your decision at any time from Settings → Ad privacy options, and if you decline, every feature of the app continues to work exactly as before.
None. We operate no servers, no accounts and no analytics. We have no database with your name in it and no way to identify you or your device. We do not sell or share personal information, because we do not have any.
A role here has a start and, if it has finished, an end. The app sorts your roles by those dates, works out how long each one lasted, and tells you when an end date falls before its start. That is arithmetic on figures you typed.
It is not a check of anything: the app does not know whether an employer exists, whether the dates are right, or whether anybody will agree with them.
That is both of them, and there is no third. The app requests no location, no notifications, no camera, no contacts, no photo or media access, no storage permission, no calendar and no exact-alarm permission. Exporting a PDF and saving a copy both work through Android’s document picker, which needs no permission at all.
Seven more permissions are merged into the final app package by the libraries
the app is built on, so the list Google Play shows you is longer than the two
above: the advertising ID (AD_ID), the three Android Ad Services permissions,
and wake-lock, foreground-service and job-service, all of which come from the
Google Mobile Ads SDK and its scheduling library. None of them is a permission
Android stops to ask you about, and none is used by any code we wrote.
This app is not directed at children under 13 and is not designed for use under the COPPA framework. We do not knowingly collect personal information from children — as described above, we hold no personal data at all.
If we change this policy we will update the Last updated date above and publish the new version at this URL. Material changes will also be noted in the app’s release notes on Google Play. This policy is versioned publicly in the Dash Fusion privacy repository, so any change is visible in its history.
Questions about this policy or about the app: dash.fusion@outlook.com