Last updated: 27 July 2026
Responsible body in the sense of the data protection laws, in particular the EU General Data Protection Regulation (GDPR), for the Android app “Awesome Markdown” (in the following “offer”) is:
Sascha Kühne
Bahnhofstraße 13
76764 Rheinzabern
Germany
Email: info@kuehne-informatik.de
The developer name in the Google Play Store is SuddenH4X. This policy covers “Awesome Markdown” only; the general privacy policy for mobile apps applies to the other SuddenH4X apps.
Overview
Awesome Markdown is a Markdown editor that works on your documents entirely on your device. There is no user account, no server run by me and no advertising. Your files and their contents are never uploaded.
The app reaches the network in three places, and you can switch off each of them individually inside the app: images a document embeds by web address, crash reports, and pseudonymous usage statistics. None of them contain file names, file paths or document content.
Your files and their contents
The app opens and saves files through Android’s Storage Access Framework (SAF). You pick every file or folder yourself in the system picker; the app has no blanket access to your storage and requests no storage permission.
File contents are read, edited and written back locally on your device only. They are transmitted neither to me nor to any third party.
Data stored locally
The app stores the following in its private app storage:
- Settings: theme (light/dark/system), font size, auto-save, restoring the scroll position, and the three privacy switches for loading images, for crash reports and for usage statistics.
- Recently opened files: display name, the file reference issued by the system, and the time you last opened it.
- Unsaved drafts: if you have unsaved changes, the app keeps the edited text so it can offer it back to you the next time you open the document. It is deleted as soon as you save or discard.
- The position you last read up to within a document.
None of this leaves your device. Automatic cloud backup is disabled, so it is not copied into a Google account either. You can remove all of it at any time by clearing the app’s data in the Android settings or uninstalling the app.
Submitting data
Images in your documents
Markdown documents can embed images by web address. To show such a document the way it was written, the app fetches that image from the third-party server hosting it. This is what the app’s INTERNET permission is for.
As a technical consequence, the operator of that server learns your IP address and the time of the request. This is not processing by me but by that third party, whose own privacy policy applies. Note that an image like this can deliberately be used as a tracking pixel to record that a document was opened. The app cannot tell whether an image address was embedded for that purpose.
You can switch this off — in the app under Settings → Legal & privacy → Load images from documents. The switch is on by default so documents render as expected. When it is off, images are never requested in the first place.
Crash reports and usage statistics (Firebase)
So that faults get noticed and fixed, and so it is visible which features are used at all, the app uses two Google services: Firebase Crashlytics for crash reports and Firebase Analytics for pseudonymous usage statistics. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. “Pseudonymous” here means the data is tied to a random identifier of the app installation, not to your name or an account.
What is transmitted:
- Crash reports: time and type of the crash or error, the affected place in the program code (stack trace), app and Android version, device model and rough device state (such as free memory), plus the app’s own last log lines before it — for example “file could not be saved”.
- Usage events: counters and categories only — such as which screen was shown (home, editor, settings, legal), that a file was opened, created or saved, that edit mode, search or the table of contents was used, that an unsaved draft was recovered or discarded, or which setting was changed, for example theme or font size. Which events these are in detail may change with new app versions; the kind of data stays the same — counters and fixed categories, never free text.
- Automatic collection by Firebase: in addition to the app’s own events, the Firebase library collects session information on its own (first app start, session start, engagement time, app or system update) as well as standard technical attributes with every event, such as app and Android version, device model, language setting and country. The app does not trigger these itself; they stop once you switch usage statistics off.
- Technical identifiers: Firebase assigns a random identifier per installation and derives a rough location from the IP address (usually the country). The identifier belongs to the installation, not to you, and is reissued when the app’s data is cleared or the app is reinstalled. For Firebase Analytics, Google additionally uses your device’s advertising ID.
Explicitly not transmitted are file names, file paths, file references and the content of your documents — not even in crash reports. No user ID is set either: there is no sign-in and therefore nothing an account could be attached to.
You can limit the use of the advertising ID device-wide, or reset the identifier, on your Android device under Settings → Google → Ads. The app itself shows no advertising and contains no ad library.
Both services can be switched off independently — in the app under Settings → Legal & privacy via the switches Send crash reports and Send usage statistics. Both are on by default. Your choice is remembered. For usage statistics, switching off takes effect immediately; for crash reports Firebase only applies it fully from the next app start, so a crash in the same session can still be reported. Data already transmitted is unaffected and is deleted according to the retention periods stated below.
The legal basis is the legitimate interest in a stable and usable app (Art. 6 (1) (f) GDPR). You exercise your right to object under Art. 21 GDPR directly through those two switches — no correspondence is needed.
Google processes the data on my behalf; for certain purposes Google additionally acts as a controller in its own right. A transfer to the USA is possible, based on the standard contractual clauses or the EU-US Data Privacy Framework. The Firebase privacy information applies in addition. Crash reports are retained by Crashlytics for 90 days by default; Analytics data according to the retention period configured in the Firebase console (up to 14 months by default).
Distribution via Google Play
The app is distributed through Google Play. In that context Google processes data on its own behalf (for example about installs and, if you have enabled sending usage and diagnostics data in your Android settings, system-level crash reports). I have no influence over this; Google’s privacy policy applies.
What the app does not do
- No user account, no sign-up, no login.
- No server run by me — there is no backend your documents could be sent to.
- No advertising in the app and no ad library.
- I set no user ID and keep no profile across installations or devices.
- No access to location services, contacts, camera or microphone.
- I do not sell data and do not share any for advertising purposes.
Permissions
The app itself requests a single system permission: INTERNET, for the image loading described above and for sending crash reports and usage statistics. File access goes through the Storage Access Framework; the app requests no storage permission.
The Google libraries it includes bring further technical permissions that appear in the finished app package: among others access to the network state and a wake lock, so reports are sent reliably across changing connections, access to the advertising ID mentioned above, and permissions for Google Play’s advertising and install attribution; the app does not use the latter actively, they ship with the Analytics library. On top of that come app-private signature permissions for communication inside the app itself; they grant no access to your data. The app never accesses location, contacts, camera or microphone.
Your data subject rights
Your documents and everything listed under “Data stored locally” above reside solely on your device and under your control; they are not transmitted to me. The only processing that goes beyond your device is the crash reports and the usage statistics.
Under the GDPR you have the rights of access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR), as well as the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). The authority responsible for you depends on your place of residence, your workplace or the place of the alleged infringement; a list of the supervisory authorities with addresses is available at bfdi.bund.de.
In practice: the data sent to Firebase is tied to a random identifier of the app installation that the app never displays; without further information from you I cannot attribute it to you (Art. 11 GDPR). Access or erasure relating to you personally is therefore possible only to a limited extent. Your objection, by contrast, you exercise yourself and with immediate effect through the switches in the app; if you additionally clear the app’s data, Firebase issues a new identifier and the data already transmitted no longer belongs to any active installation. Locally stored data is likewise deleted by clearing the app’s data or uninstalling the app.
Contacting me
If you write to me, I process what you provide — your email address and the content of your message — solely to answer your enquiry and to clarify any follow-up questions. The legal basis is your voluntary consent (Art. 6 (1) (a) GDPR), which you can withdraw at any time with effect for the future by email to info@kuehne-informatik.de.
Change of this privacy policy
If the app changes — for instance through a new feature that processes data — this policy will be updated accordingly. The version published here, carrying the date shown above, is the one that applies.
Questions about privacy in this app
If you have any questions about privacy, please write me an email: info@kuehne-informatik.de.