Privacy Policy for Batch Rename Studio

Developer: Aktyva konsaltynh technologies
Privacy contact: mateuszbednarski696@gmail.com

Scope

This policy describes how the current Android application, Batch Rename Studio, handles information when you select files, create naming rules, preview changes, and rename files.

Information the App Accesses

The app uses Android’s document picker to access files or folders you select. It requests read and write access and attempts to retain that permission so access can continue across sessions, where the storage provider permits it.

The app reads file and folder identifiers, document locations, filenames, file sizes, modification dates, and information about whether a provider supports renaming. When you select a folder, it lists its direct files. It also checks entries in that folder to detect conflicting destination names. It does not recursively select files in subfolders.

The inspected implementation uses file metadata and naming instructions rather than reading file contents. Filenames and naming-rule text may contain personal information you choose to include.

Local Storage and Purposes

The app saves the following information in private app storage on your device:

• Draft selections, including file metadata and document locations, naming rules, individual destination edits, and skipped files.
• Settings for naming rules and numbering.
• Named presets containing naming rules and extension preferences.
• Batch history containing timestamps, rule summaries, original and requested filenames, resulting filenames, file metadata, operation outcomes, and undo status.

This information supports restoring drafts, reusing workflows, previewing changes, checking conflicts, showing results, and attempting to restore original names when file access and metadata allow verification. Applying a rename changes the selected file’s name through its storage provider. Clearing app records does not reverse those changes.

Collection, Sharing, and Third Parties

The inspected implementation does not send file information or locally saved records to the developer. It does not implement accounts, app-operated cloud synchronization, advertising, analytics, or remote crash reporting. No advertising, analytics, or remote crash-reporting SDK was identified in the inspected dependencies.

The app communicates with Android’s document system and the storage provider you select to inspect metadata and request renames. If you select a cloud-backed provider, that provider may communicate with its own service and process changes under its own privacy policy. The app does not control that provider’s handling of information.

Android backup is enabled in the application configuration. Depending on your device settings and Android’s backup service, locally stored app records may be backed up or restored by the operating system. This is separate from app-operated cloud synchronization.

Security and Diagnostics

The app uses Android’s permission-based document access and private app storage. It checks file metadata, destination conflicts, and provider capabilities before requesting renames. Private storage is not a guarantee of encryption or absolute security.

Certain provider failures generate local Android diagnostic logs containing error types and technical stack traces. The logging code omits provider exception messages because those messages may contain filenames, document locations, or file contents. The inspected app does not upload these logs.

Although the Android manifest includes internet permission, the inspected active application code does not implement network transmission of user data. Encryption for any communication performed independently by a selected storage provider or operating-system backup service depends on that service; the app does not establish or verify it.

Retention and Deletion

Drafts, settings, presets, and batch history remain in local app storage across sessions. The implementation does not define an automatic expiration period.

You can delete individual presets and use “Clear rename history” to remove batch logs. Clearing history removes the records needed for undo, while leaving your files and presets in place. Draft records may still contain file metadata after history is cleared.

You can remove the app’s local records through Android’s app-storage controls or by uninstalling the app. These actions do not delete the files you selected or restore their original names. Copies held by an operating-system backup service are subject to that service’s settings and retention practices. Persisted document permissions are managed by Android; deleting presets or clearing history does not explicitly revoke them.

For privacy questions or deletion requests, contact mateuszbednarski696@gmail.com. No in-app remote deletion-request feature was identified. The developer cannot directly erase records stored only on your device or information controlled by your storage or backup provider.

Children’s Privacy

Batch Rename Studio is a file-renaming utility. The supplied information does not specify a target age group. The inspected app does not ask for age information or implement accounts or developer-operated collection of children’s information. Questions concerning a child’s use of the app may be directed to the privacy contact below.

Policy Changes

This policy may be updated to reflect changes in the app’s features or information handling. Review the current policy when using an updated version of the app.

Contact

Aktyva konsaltynh technologies
Privacy questions and requests: mateuszbednarski696@gmail.com