1. Scope and developer
TR Tech Invents develops Muddi Video & Audio Enhancer (“Muddi”). This policy explains how the Android app handles information when you use its video, photo, audio, document and status-saving tools. It is separate from the TR Tech Media website privacy policy, which applies when you visit this site.
Muddi processes selected media locally. It does not upload your selected photos, video, audio, cutout masks or scanned pages to TR Tech Invents or Firebase for editing, compression or conversion. The app does connect to Google services for usage measurement, reliability and notifications.
2. Files you choose and permissions
Muddi reads files selected through Android’s photo picker or document picker. Supported read access may be retained for a user-started export, retry or editing session. If you choose a cloud-backed file, its provider may download it first under that provider’s terms.
Document Scanner can launch your installed camera app and supply a temporary destination for the captured page. The camera app handles capture under its own permissions and privacy practices. Muddi does not require direct camera access or microphone recording for these workflows.
Status Saver accesses only status folders you connect through Android’s system folder picker. It does not read your WhatsApp conversations. Disconnecting a folder releases its stored access without deleting its files.
Foreground-service and wake-lock permissions support user-started processing. Notification permission supports processing updates and app messages. Internet and network permissions support Google services. The app does not request all-files storage access, contacts or location permission for its tools.
3. Analytics, diagnostics and notifications
Muddi includes the following Google services:
- Firebase Analytics: app-use events, screen interactions, app and device information, and app-instance identifiers used to understand usage and improve the app.
- Firebase Crashlytics: crash traces, diagnostic information and installation identifiers used to investigate failures.
- Firebase Cloud Messaging: installation registration tokens and message-delivery information used for app notifications.
Google services may process network information, such as an IP address, when the app connects. Analytics can also collect a resettable advertising identifier where available and permitted by device settings. The app’s integrated dependencies declare advertising-ID-related permissions; the absence of displayed ads does not mean no identifiers are processed.
For provider details, see Firebase privacy information, Analytics data controls and Google’s Privacy Policy.
4. Local records, camera drafts and outputs
Muddi stores appearance preferences, export settings, output history, queue and recovery records, connected-folder locations and editing state in private local storage. Records can include filenames, content URIs, sizes, dates, formats and chosen presets. Scanner drafts include page locations and edit settings; captured page images are temporarily held in private cache.
Each export creates a new file instead of overwriting the source. Video and audio outputs use Movies/MuddiEnhancer and Music/MuddiEnhancer. Images use Pictures/MuddiEnhancer; PDFs use Downloads/MuddiEnhancer. Status copies use the Pictures or Movies MuddiEnhancer/Statuses subfolder.
Status copies preserve existing metadata, which can contain personal information, including location. Do not assume that saving or sharing any media strips all metadata.
5. Retention and cleanup
Private settings and records remain until removed by the app, cleared in Android settings or removed through uninstalling. App backup and device-transfer rules exclude Muddi’s private app data. Originals and exported shared-storage files can remain after the app is uninstalled.
Failed or cancelled pending outputs are cleaned up by the saving and recovery workflows. Completed temporary video/audio results held for a save failure or size review expire after 24 hours and are removed during reconciliation, rather than at a guaranteed background deletion time.
Scanner captures are removed when their page is removed, the draft is discarded or export succeeds. Abandoned captures not referenced by the restored draft become eligible for cleanup after 24 hours when scanner cleanup runs. Already-completed outputs from a partially cancelled multi-file export can remain saved.
Google-service data has separate retention and deletion rules governed by the relevant service settings and policies. Clearing Muddi’s local data does not itself erase information already processed by Google.
6. Sharing and support
Open and Share use Android’s chooser and grant the selected destination temporary read access to the output. The receiving app handles it under its own policy. Camera, cloud-storage and sharing providers may process information independently.
If you email support, we receive your email address and whatever information you choose to send. Send only information needed for the request; avoid attaching private media unnecessarily. Support correspondence is kept as needed to address the request and related obligations.
7. Accounts, ads and data use
The current app has no account or sign-in system and no ad-serving SDK. TR Tech Invents does not sell your selected media. Technical information processed by the integrated Google services is described above. This policy will be updated if accounts, advertising or materially different processing are introduced.
8. Your controls and privacy requests
- Remove history entries without deleting the underlying media.
- Delete saved outputs through Android’s Files, Gallery or audio apps.
- Disconnect status folders and manage available file-access controls in Android settings.
- Disable notifications, clear app data or uninstall through Android settings.
- Manage advertising-ID controls where available in your Android version. Notification settings do not disable Analytics or Crashlytics.
The current app does not provide an in-app Analytics or Crashlytics opt-out switch. Contact us about access, deletion or other privacy requests, including rights available under applicable law. Some requests depend on whether we can identify the relevant records; we may need information to verify and process your request.
9. Security and policy updates
Muddi uses Android’s app-private storage and scoped file-sharing mechanisms for its private records and temporary files. No system can guarantee absolute security. Take care when sharing outputs or using third-party camera, storage and messaging apps.
We may revise this policy as the app changes. The latest version and its updated date will be published on this page.
10. Contact
For Muddi support or privacy questions, contact TR Tech Invents at tariqahmed7@proton.me. Please mention “Muddi privacy” in the subject.