ModernMarkdown privacy policy

What this policy covers

ModernMarkdown is a login-free Markdown editor. This policy explains what the current mobile app stores on your device, what leaves your device when you choose sharing, embedded AI, advertising, or an optional Google Play purchase, and what the published ModernMarkdown API may process.

Information stored on your device

Your documents are stored as JSON files in the app's private app-data directory, under FileSystem.AppDataDirectory/documents. The app remembers the last-opened document and provider preferences in platform preferences. Theme and accent preferences are stored in the embedded WebView's local storage.

A provider API key is optional. If you enter one for embedded AI, it is stored in platform secure storage such as Keychain, Keystore, or DPAPI. The key is used to authenticate requests to the provider you select.

Files, import, export, and deletion

When you choose a .md, .markdown, or .txt file in the platform file picker, ModernMarkdown reads the selected content and copies it into its private app storage. The source path is not retained. Export creates a separate Markdown copy at the path you choose.

Settings can remove app-managed documents, the saved AI provider and key, and appearance preferences from this device. Exported copies and original imported files are controlled separately by you and are not deleted by that reset.

Embedded AI and provider requests

Embedded Improve, Summarize, Grammar, and Chat are optional and require a key that you provide. When you choose an action, the app may send your document or selected text, your instructions, and conversation context directly from your device to the selected OpenAI, Anthropic, Gemini, Groq, or DeepSeek service. ModernMarkdown does not proxy those requests or receive the provider response on your behalf.

The selected provider handles the request under its own terms, privacy policy, security practices, and retention or training settings. Review those terms before sending sensitive content. ModernMarkdown cannot control how a provider processes content that you send to it.

External AI sharing and clipboard

Open in AI… uses your operating-system share sheet to pass the selected text or document to another app. If sharing fails, ModernMarkdown uses a clipboard fallback. The receiving app, share target, and operating system may handle content according to their own policies. Content that you share or copy is separate from the app-managed local data reset.

The published API and purchases

The current mobile app does not call the ModernMarkdown API for editing, document storage, or AI requests. For Google Play billing, the app may send a purchase token to the API to verify the exact package com.appsolutelyfabulous.modernmarkdown and product modernmarkdown.pro_lifetime. The purchase verification endpoint is anonymous and stateless: the purchase token exists only transiently in the request and in outbound Google Publisher verification/acknowledgement calls. The API does not persist or log the purchase token, token hash, or request body. There is no ModernMarkdown account involved.

Only a verified Google Play PURCHASED result grants the permanent ModernMarkdown Pro — lifetime ad-removal entitlement. Pending, cancelled, refunded, revoked, invalid, duplicate, or failed verification does not grant ad removal. The on-device secure entitlement cache contains only a schema version, product ID, and verification time, never the purchase token.

Third parties and hosting

Depending on your choices, content or settings may be handled by your device operating system, its file picker, its share or clipboard services, an AI provider listed above, Google Play, Google Mobile Ads, the User Messaging Platform, or Azure hosting the published API. Those parties operate independently and their own terms and policies apply.

On Android, the current mobile app uses Google Mobile Ads for anchored adaptive banner ads only. A banner may appear in Library or phone rendered Preview after the editor loses focus and the software keyboard is dismissed. Settings provides purchase, restore, and privacy controls but is not an ad placement. Banners are not requested in Write, while the IME is visible, in tablet or wide split editor layouts, or in AI chat. When an eligible banner is considered, the User Messaging Platform (UMP) refreshes consent before Mobile Ads initialization/request and shows a certified consent or privacy-options form when Google requires it. Ads are initialized or requested only after UMP reports CanRequestAds; a consent failure remains fail-closed. Candidate Google Mobile Ads data categories are IP address, user product interactions, diagnostics, and device/account identifiers; candidate purposes are advertising, analytics, and fraud prevention. These are candidate declarations pending final SDK/AAB/Play Console owner review. This policy page uses no cookies, external scripts, or external assets.

Security and operational processing

Provider keys use the platform secure-storage facility, and the published API runs on Azure. The API may perform ordinary operational and security processing. Standard ASP.NET logging and in-process OpenTelemetry diagnostics are wired into the service. A production OTLP, Application Insights, or Log Analytics destination is not currently configured; that does not mean requests, errors, or platform activity can never produce server-side or provider-side logs.

Retention and your choices

Local documents and preferences remain on your device until you delete them, reset them in Settings, or remove the app according to your platform's behavior. Exported, imported, shared, copied, provider-held, and future API records are controlled separately. No fixed retention period is promised here for third-party or future API records; retention can depend on the feature, the third party, security needs, legal requirements, and the circumstances of use.

For records held by a provider, platform, Google, or another share recipient, use that party's available privacy and deletion controls. For a question about ModernMarkdown's handling, use the developer contact details on the Google Play listing.

Changes to this policy

This page may be updated when the app or its data flows change. The date at the top identifies the current version.