NoteBud is a plain-text editor. This page explains, in plain text of its own, exactly what that does and does not mean for your data.
The short version: the files you write in NoteBud never leave your device. NoteBud has no account, no cloud sync, and no server of its own — the only data it sends anywhere is small, anonymous diagnostic data described in §2, used solely to keep the app working.
01 What happens to your files
NoteBud opens, edits, and saves files exclusively through Android’s Storage Access Framework — the same system dialog you’d use in any file manager. NoteBud does not bundle a third-party file-storage or cloud-sync library, by design.
Practically, that means: the text you type is written straight to the location you chose (your device storage, an SD card, or a storage provider you’ve connected at the OS level, such as Drive) and nowhere else. NoteBud’s own servers do not exist, so there is no upload step for file contents to go through.
The one exception is a local crash-recovery draft: if the app is killed before you save, NoteBud keeps a snapshot in its private app storage (invisible to other apps) so you don’t lose work. That snapshot never leaves your device either, and is cleared once you save or discard it.
02 Diagnostic & usage data
NoteBud uses Firebase Analytics and Firebase Crashlytics (both operated by Google) to understand crashes and coarse feature usage. This is the only data that leaves your device, and it never includes your file contents or file names. It can include:
- Device model, OS version, and app version
- Coarse feature usage (e.g. that Find & Replace was opened — not what was searched for)
- Crash stack traces and the app state immediately before a crash
- An anonymous, resettable installation identifier
Crash reporting is disabled in development builds and only active in the version you install from Google Play.
03 How this data is used
Solely to find and fix bugs, and to understand which editor features are actually used, so effort goes where it matters. It is not used for advertising, it is not sold, and it is not combined with any identity you provide elsewhere (NoteBud never asks for your name, email, or an account).
04 Third-party processors
Firebase (Google LLC) is the only third-party processor NoteBud uses. Data collected through it is handled under Google’s Privacy Policy. If you use a cloud storage provider (like Drive) as your save location, that provider’s own privacy policy governs the files you choose to store there — that relationship is between you and them, outside NoteBud entirely.
05 Storage & retention
Your notes are retained exactly as long as you keep the file, wherever you saved it — NoteBud has no independent copy. Diagnostic data in Firebase is retained per Google’s standard Analytics/Crashlytics retention windows, currently up to 14 months for Analytics data.
06 Your choices
You can clear NoteBud’s local app storage (including the crash-recovery draft) at any time from Android’s App info → Storage screen. Uninstalling the app removes all app-local data immediately. Because analytics identifiers are tied to the install, uninstalling also ends that identifier’s history.
07 Children’s privacy
NoteBud is a general-purpose text editor, not directed at children, and does not knowingly collect data from children under 13.
08 Changes to this policy
If this policy changes, the effective date at the top of this page will change with it. Meaningful changes — anything that expands what’s collected — will also be noted in the app’s release notes.
09 Contact
Questions about this policy or your data can be sent to nikbit.dev@nikbit.com.