Textly - TXT Editor

Privacy Policy

Introduction

Last Updated: October 21, 2026

VenzApps ("we", "us", or "our") provides the Textly - TXT Editor Android application ("Textly" or the "App"). This policy explains how the App and the third-party services it uses handle information.

Textly is primarily an offline text editor. Its main document-editing features work locally on your device, and you do not need to create an account to use them.

We do not collect sensitive information from your documents. Your document text, filenames, file paths, searches, and clipboard contents are not collected for our custom analytics or advertising tracking. We do not upload your text files to VenzApps servers. Google services used for analytics, crash reporting, and ads may process technical device and app information, as explained below.

1. Your Documents and Offline Editing

You can create, open, edit, save, organize, and search text files on your device. Textly does not provide its own cloud storage or cloud synchronization for your documents.

We do not collect or transmit document contents, filenames, file paths, document links, selected text, clipboard contents, or search and replacement terms through our custom analytics or advertising events. We also take steps to exclude this information from manually reported crash diagnostics.

If you choose to share a file, print it, save it through an Android document provider, or compose a feedback email, the information you choose may be passed to the Android service or other app you select. Those services handle the information under their own privacy practices.

2. App Analytics, Crash Reports, and Advertising

We do not ask for your name, phone number, passwords, or other sensitive personal details to use Textly's main editing features. To maintain and improve the App, we use Google services that may automatically process technical information, such as device identifiers, app activity, and diagnostics. Some of this technical information may be considered personal data under applicable laws.

2.1 App Analytics - Google Analytics for Firebase

We use Google Analytics for Firebase to understand how features are used and identify areas to improve.

Examples of app events include opening the app, visiting screens, creating or saving a document, using search or Find & Replace, changing settings, using print preview, and interacting with the Rate Us or ad-free features.

Custom event details use predefined categories, such as the type of editor action, search area (Files or Content), success or failure, and broad document-size ranges. We do not intentionally include the actual text of documents, filenames, search queries, or feedback messages in these custom events.

Google Analytics may also process app instance identifiers, device and app details, event timestamps, and approximate location derived from network information to support measurement and reporting.

2.2 Crash Reports - Firebase Crashlytics

We use Firebase Crashlytics to diagnose crashes and important app failures. Crash reports may contain error information, stack traces, technical app state, device model, Android version, app version, and installation-related identifiers.

We take steps to keep document contents, filenames, paths, and user-entered text out of custom non-fatal reports and diagnostic metadata. Because automatic crash reports can include system-generated exception details, we cannot guarantee that every technical report will be free of incidental sensitive information.

2.3 Advertising - Google AdMob

Textly displays ads using Google AdMob (Google Mobile Ads), including native, interstitial, and optional rewarded ads. Rewarded ads can provide temporary ad-free access when you choose to watch them.

Google Mobile Ads may collect or process IP addresses, advertising or app identifiers (where available), app and ad interactions, and diagnostic information. Google uses this information for advertising, measurement, security, and fraud prevention. The exact data processed may vary with your device, region, consent choices, and SDK settings.

3. Sensitive Information We Do Not Collect

We do not collect sensitive information from the content you create or edit in Textly through our own analytics and advertising tracking. In particular, our custom analytics and manually reported diagnostic events do not include:

These statements describe our app's custom tracking and intentional data collection. Google SDKs may independently process device identifiers, app events, and technical diagnostics. Automatic crash reports may occasionally contain incidental information in system-generated error details. We cannot guarantee that third-party services collect no information considered sensitive under every applicable law. See Section 2 for details.

4. Third-Party Services

Textly uses these Google services:

To learn more about their privacy practices, see:

5. How Information Is Used and Shared

App usage and diagnostic information helps us understand whether features work, identify errors, and improve Textly. Advertising-related information is used to display and measure ads and support advertising safety.

We do not collect or sell the text you write in your documents, and we do not upload it to VenzApps servers for advertising or analytics. We do not sell your text documents or their contents.

Technical information may be transmitted to and processed by Google through the integrated SDKs. Google may process and share data according to the relevant services, settings, and applicable policies. Data you deliberately send using another app (for example, sharing a file or opening an email composer) is handled by the chosen destination.

6. Your Privacy Choices

Where required, Textly requests advertising consent using Google's User Messaging Platform. When available or required, the App's Privacy screen offers a Change Privacy Choices option so you can review advertising preferences.

You can also manage your Android advertising ID and related ad preferences through your device and Google settings. Available controls depend on your device, location, and applicable laws.

Advertising privacy choices do not necessarily disable every form of technical data collection by Firebase Analytics, Crashlytics, or Google Mobile Ads. Those services may process some information for permitted functions, security, or diagnostics.

For privacy questions or applicable data-rights requests, contact us using the details in Section 12.

7. File Access and Permissions

Textly accesses files or storage locations as needed when you choose to create, open, save, rename, share, print, or delete documents. Android file pickers and document providers may allow you to choose which files and locations the App can access.

We do not collect document contents for advertising or use the text you write to customize advertisements. File-access behavior and permissions can differ across Android versions.

8. Local Storage, Retention, and Deletion

To provide its features, Textly may save app settings, recent or pinned file information, editing preferences, and draft-recovery information locally on your device.

You can delete or move documents in their storage location. Clearing Textly's app data or uninstalling the App may remove locally stored preferences and drafts. Files stored outside the App's private storage may remain after uninstalling and may need to be deleted separately.

Google Analytics, Firebase Crashlytics, and AdMob data is retained according to the relevant provider policies, service settings, and applicable requirements. Clearing local app data does not necessarily delete information previously processed by those services.

If you have a privacy or deletion request, email us using the contact details below. We will review requests as required by applicable law; some data is managed by Google rather than directly by VenzApps.

9. Data Security

Textly's core text editing takes place locally on your device. Google states that data collected by the Firebase and Google Mobile Ads SDKs is encrypted while being transmitted.

We aim to limit custom event parameters and manually reported errors to information relevant to app improvements. However, no method of storage or transmission can be guaranteed to be completely secure.

10. Children's Privacy

Textly is not specifically directed to children under 13. We do not knowingly request personal information directly from children through the App's core editing features.

If you have concerns about a child's information, please contact us. Third-party SDKs may process technical data as explained in this policy and according to applicable settings and requirements.

11. Changes to This Policy

We may update this policy when Textly's features, third-party services, data practices, or legal requirements change. When we do, we will update the Last Updated date at the top of this page.

12. Contact Us

If you have questions about this policy, data handling, or applicable privacy rights, contact:

Developer: VenzApps
Application: Textly - TXT Editor
Email: venzapps.support@gmail.com