Reader Privacy Policy

Last updated

2026-05-15

Apps covered

This policy applies to the Reader app family published by ADZ Dev Coding, including:

• Reader: com.adzdevbox.mdredv2android
• Reader Dev: com.adzdevbox.mdredv2android.dev

Contact

For privacy questions or data requests, contact privacy@adz-dev-coding.pl.

Summary

Reader is designed for local document workflows on Android. You can create, open, edit, import, and export documents on your device. Reader does not require a Reader-specific account for local document use.

Reader may store documents, document names, recent document entries, versions, selected file or folder references, connector settings, and diagnostics locally on your device.

If you choose optional connector features, Reader sends the data needed to perform the action to the selected third-party service. For example, Google Drive features communicate with Google services, and GitHub features communicate with GitHub.

Information you provide or create in Reader

Reader may handle the following information when you use the app:

• documents you create, open, import, edit, save, or export;
• document names, file names, folder names, and file paths or references selected by you;
• local document history, versions, recent document entries, and editing state;
• files, folders, or workspace references selected through Android document and folder pickers;
• diagnostics or support information that you choose to copy, export, or send.

Documents opened, imported, edited, or exported by you are treated as user-controlled content.

Local storage on your device

Reader stores app data locally so that document workflows can function. This may include app-local document copies, document content and versions, recent document entries, selected Android document or workspace references, local settings, connector account summaries, session information, local diagnostics, and validation reports.

Reader uses Android document and folder selection flows where applicable. Files exported by you remain in the location you choose. Files stored in third-party services such as Google Drive or GitHub remain subject to those services and your settings there.

Reader account

Reader does not require a Reader-specific account for local document use.

Optional third-party connector features may require you to connect an account with the third-party service, such as Google Drive or GitHub. Those accounts are not Reader accounts and are managed by the corresponding service.

Optional Google Drive connector

If you choose to use Google Drive features, Reader may use Google Sign-In and Google Drive APIs to perform actions you request, such as opening, saving, or updating files.

When you use Google Drive features, Reader may process or store locally your connected Google account summary, Google Drive file identifiers, file metadata, file names, and file content needed to perform the selected action.

Reader uses Google Drive only when you choose to connect or use Google Drive features. Data handled by Google is subject to Google’s own terms and privacy practices.

Optional GitHub connector

If you choose to use GitHub features, Reader may communicate with GitHub APIs to perform actions you request, such as validating a token, reading repository contents, syncing files, pushing changes, or creating pull requests.

When you use GitHub features, Reader may process or store locally a GitHub token or session information, GitHub account or repository metadata, repository names, branch names, file paths, commit or pull request metadata, and file content needed to perform the selected GitHub action.

Reader uses GitHub only when you choose to connect or use GitHub features. Data handled by GitHub is subject to GitHub’s own terms and privacy practices.

AI-related features

Reader may include AI Actions or AI-related user interface features for current-file workflows.

The current Reader release does not provide an external AI provider runtime by default. If a future Reader version sends document text, prompts, excerpts, or metadata to an external AI provider, this Privacy Policy will be updated before that feature is released, and the app’s Google Play Data Safety declarations should be updated accordingly.

Do not enter or send sensitive documents to any AI or provider feature unless you understand where the data will be processed.

Diagnostics and support

Reader may include local diagnostics or self-check information to help understand app behavior. These diagnostics are intended to be local or user-controlled unless you choose to copy, export, or send them.

If you contact ADZ Dev Coding by email, we may receive your email address, message content, screenshots, logs, attachments, or other information you choose to include.

Please do not include tokens, private documents, provider payloads, or sensitive workspace names in support emails unless specifically requested for a narrow private diagnosis.

Support and privacy emails may be kept for as long as reasonably necessary to respond to the request, maintain records of the request, and comply with applicable legal obligations.

Analytics, advertising, and payments

Reader is not designed to show advertising in its local document workflow.

Reader is not designed to process in-app payments or subscriptions in its local document workflow.

Reader does not operate a developer-owned analytics backend for ordinary local document editing. Google Play and Android platform services may process app distribution, update, security, and platform-level diagnostic information according to Google’s own terms and privacy practices.

Permissions

Reader uses the Android Internet permission for optional network-based features such as Google Drive or GitHub connector actions.

Reader uses Android document and folder selection flows where applicable, so access to user files is based on files or folders selected by the user.

Sharing and disclosure

Reader does not send your documents to ADZ Dev Coding by default as part of the ordinary local document workflow.

Reader may transmit data to third-party services when you choose optional connector features. Google Drive actions may send file content, file names, account information, and file metadata to Google services as needed to perform the selected action. GitHub actions may send tokens, repository metadata, file paths, file content, commit data, and pull request data to GitHub as needed to perform the selected action.

Reader may also rely on Google Play and Android platform services for app distribution, updates, security, and platform-level diagnostics.

Data retention and deletion

Reader keeps local app data for as long as it is needed for app functionality or until you remove it.

You can remove local data by deleting documents or entries inside Reader where supported, disconnecting optional connectors where supported, clearing Reader app data or cache in Android settings, or uninstalling Reader.

Deleting a document from Reader may remove the app’s local copy or reference, but it may not delete exported files, original files selected through Android, Google Drive files, GitHub repository content, or other copies outside Reader’s local app storage.

Files stored in Google Drive or GitHub must be managed through those services unless Reader explicitly provides and you use an action to update or delete them.

Support and privacy emails may be retained as described in the Diagnostics and support section.

Security

Reader is designed to keep ordinary local document workflows on the device by default.

Where optional connector credentials or session data are stored locally, Reader should use Android-backed secure storage where available.

No method of storage or transmission is perfectly secure. Use care when opening, editing, exporting, or syncing sensitive documents.

Children

Reader is not intended to be directed to children.

Changes to this Privacy Policy

We may update this Privacy Policy when Reader changes, when optional connector or provider behavior changes, or when legal or platform requirements change.

The updated version will be posted at https://adz-dev-coding.pl/reader/privacy/.