Privacy Policy for Video Converter & Compressor

Last updated: 11 July 2026

This Privacy Policy applies to the Android app “Video Converter & Compressor”, which may be offered under translated names in other languages and is uniquely identified by the package name com.androho.simplevideoconverter, in its current version and, where technically applicable, to older versions that remain installed.

Individual features, services, permissions or privacy options may vary depending on the app version, Android version, device configuration, region and user choices. We recommend keeping the app up to date so that the latest features, security improvements and privacy options are used.

1. Controller

The controller responsible for data processing is:

Androho Software – Matthias Höpfler

Ziegelweg 1

84164 Moosthenning

Germany

Email: info@androho.com

Website: www.androho.com

2. General Data Processing in the App

The app can generally be used without creating a user account. No account is created with Androho Software. We do not operate our own cloud storage or our own personal user database for this app.

The app’s main functions, including selecting, previewing, trimming, compressing, converting, muting, extracting audio tracks and saving media files, are performed locally on the device.

Videos selected by users and the resulting video or audio files are not transferred to Androho Software for server-side conversion. The actual media processing is performed on the device using FFmpeg or an FFmpegKit-based component.

Many types of data are processed or stored exclusively locally on the device, for example:

selected input videos
temporary video or audio files
converted output files
video duration, resolution and available audio channels
selected quality, format, audio and trimming settings
settings for the standard or advanced conversion mode
progress and technical status of an ongoing conversion
local app settings
the locally stored status of an ad-free purchase

Data is transferred to external services only in the cases described below, particularly in connection with advertising, analytics, error diagnostics, consent management and optional in-app purchases.

3. Services and Components Used

The app may use the following services and components:

Google Firebase Analytics
Google Firebase Crashlytics
Google AdMob
Google User Messaging Platform / Consent SDK
Google Play Billing for the optional “Remove ads” purchase
Meta Audience Network as a possible AdMob mediation partner
Pangle as a possible AdMob mediation partner
FFmpeg, libx264 and an FFmpegKit-based open-source component for local media processing

Depending on the region, consent status, app version, AdMob configuration and availability, individual services may be disabled, restricted or used with reduced data processing.

4. App Permissions

Depending on the Android version and the feature being used, the app may use the following permissions:

Internet

The INTERNET permission is required for advertising, consent management, analytics, error analysis, in-app purchases and technical communication with the services used for these purposes. Selected videos are not uploaded to a server merely because this permission is present.

Advertising ID

The com.google.android.gms.permission.AD_ID permission allows access to the Android Advertising ID where it is available on the device and where its processing is permitted under the applicable settings and legal requirements.

The Advertising ID may be used in particular for ad delivery, ad measurement, reach measurement, fraud prevention and, where appropriate consent has been provided, personalised advertising. Users can reset or delete the Advertising ID through the Android or Google settings on their device.

Foreground Service

The permissions FOREGROUND_SERVICE, FOREGROUND_SERVICE_DATA_SYNC and, on supported newer Android versions, FOREGROUND_SERVICE_MEDIA_PROCESSING are used so that a conversion initiated by the user can continue when the user temporarily switches to another app.

The foreground service processes the conversion progress, technical status values and, where applicable, the name of the output file locally on the device. The use of the foreground service does not cause media files to be automatically transferred to Androho Software or other servers.

Notifications

The POST_NOTIFICATIONS permission may be requested on Android 13 and newer versions in order to display a progress or completion notification for an ongoing or completed conversion.

The notification may locally display information such as conversion progress, processing speed, estimated remaining time, file size or the name of the output file. This permission is not used to transfer this information to external servers.

Selecting Videos

In the current version of the app, videos are selected through a media or file selection interface provided by the Android system. This gives the app access to the file specifically selected by the user.

The current version of the app does not request general read access to all images or videos in the device’s media collection. The permissions READ_EXTERNAL_STORAGE, READ_MEDIA_IMAGES, READ_MEDIA_VIDEO and READ_MEDIA_VISUAL_USER_SELECTED are removed from the current app manifest.

Older versions that remain installed may have used different storage permissions depending on the technical implementation and Android version applicable at the time.

Write Access on Older Android Versions

The WRITE_EXTERNAL_STORAGE permission is used exclusively on Android 9, API level 28, and older supported Android versions. It allows an output file created by the user to be saved in the local device storage or gallery.

Files are saved only as a result of a conversion initiated by the user or a locally enabled automatic saving feature. The stored files are not transferred to external services merely because this storage permission is present.

5. Local Processing of Video and Audio Files

After a video file has been selected, the app may open and analyse it locally in order to provide the requested functions. The following information may be processed locally:

file path, content URI or temporary access address
file name and file format
video duration
video width and height
video and audio codecs
number of available audio channels
file size
start and end positions selected by the user
selected resolution, quality, bitrate, frame rate and audio settings
technical conversion progress

This information is used for previewing, validating, estimating output size, converting, compressing, extracting audio and saving the result.

The actual video and audio content is not deliberately transferred to Androho Software, Firebase Analytics, Google AdMob or advertising partners.

In the event of a technical error, however, certain technical information may be processed as part of a Crashlytics error report. Further information can be found in the section concerning Firebase Crashlytics.

6. Temporary Files, Cache and Saved Results

For processing purposes, the app may temporarily create copies or output files in its local cache directory.

Temporary conversion files may be deleted in particular when:

a conversion is cancelled
a result is discarded
a conversion fails
the app cleans its temporary conversion cache
the app data is deleted through the Android settings
the app is uninstalled

Results saved in the gallery or in a storage location selected by the user generally remain there until they are deleted by the user through the app, gallery, file manager or another system function.

If users open or share a file through the Android sharing interface or another app, the subsequent processing is performed by the external app selected by the user. The provider of that external app is responsible for its data processing.

7. Android System Backups

Depending on the Android version, device settings and the backup rules configured in the app, certain local app settings may be backed up by the Android system and restored following a reinstallation or transfer to another device.

This may include settings, local feature states or a locally stored purchase status. Temporary conversion files and videos stored in the gallery are not necessarily included in such an app backup.

The creation and storage of system backups is controlled by Android or the backup service used by the user and not by an independent cloud service operated by Androho Software.

8. Firebase Analytics

The app may use Google Firebase Analytics. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Firebase Analytics may process pseudonymous usage and technical data, for example:

app launches and session information
screen views
app interactions
automatically collected events
technical device information
app version and operating system version
approximate region derived from technical connection data such as the IP address
device, app or installation identifiers
information about a completed or restored in-app purchase, where corresponding purchase events are recorded

The purposes of the processing are to analyse the use of the app, improve features and usability, identify technical problems and further develop the app.

The contents of selected or converted videos are not transmitted to Firebase Analytics as analytics events.

Firebase Analytics is initially technically disabled when the app starts. If the Google User Messaging Platform requires a consent dialog to be shown to a particular user, Analytics is enabled only where the required consent or approval has been provided.

If the regional and technical assessment determines that no consent dialog is required, Analytics may be enabled without displaying a prior dialog, provided that this is permitted under the applicable laws.

The legal basis is Article 6(1)(a) GDPR where consent is obtained. Where processing without consent is legally permissible, Article 6(1)(f) GDPR may serve as the legal basis. Our legitimate interest lies in analysing, improving and stabilising the app.

9. Firebase Crashlytics

The app may use Google Firebase Crashlytics for error analysis. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Crashlytics may process the following data in particular:

crash logs and stack traces
non-fatal error reports
app version
device type and technical device characteristics
operating system version
time of a crash or error
technical diagnostic and performance data
Crashlytics and Firebase installation identifiers
relevant technical app states at the time of an error
technical FFmpeg or media-processing error messages

In older app versions, if a conversion fails, a technical FFmpeg error report may be sent to Firebase Crashlytics; depending on the error, this report may include filenames, local file paths, content URIs, or embedded media metadata.

Starting with app version [1.1.1] or build [23], the error report is sanitized before transmission. In particular, filenames, local paths, content URIs, and embedded media metadata are removed. The selected video and audio content is not transmitted.

The purposes of the processing are to identify, analyse and resolve crashes, failed conversions and technical errors, and to improve the stability and compatibility of the app.

Firebase Crashlytics is initially technically disabled when the app starts. If the Google User Messaging Platform requires a consent dialog to be shown to a particular user, Crashlytics is enabled only where the required consent or approval has been provided.

If the regional and technical assessment determines that no consent dialog is required, Crashlytics may be enabled without displaying a prior dialog, provided that this is permitted under the applicable laws.

10. Advertising with Google AdMob

The app may use Google AdMob to display advertising. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

The following data may in particular be collected, processed and shared with Google:

IP address and approximate location derived from it
device, app and installation identifiers
Advertising ID or App Set ID, where available and permitted
app interactions such as app launches, touches, screen interactions and ad interactions
device and app information
diagnostic and performance data, such as app launch time, hang rate or energy consumption
ad impressions and information concerning ad delivery
fraud-prevention, security and compliance data

The purposes of the processing are:

displaying and technically delivering advertising
personalising advertising where appropriate consent has been provided
measuring and analysing advertising performance
limiting, selecting and controlling advertisements
fraud prevention, security and compliance
financing and further developing the app

In regions where consent is required, personalised advertising is used only where appropriate consent has been provided.

If consent to personalised advertising is not provided, non-personalised, restricted or otherwise privacy-reduced advertising may be displayed where technically and legally possible. Certain technical processing may still be required for ad delivery, security, fraud prevention and compliance, even when non-personalised or restricted advertising is used.

The legal basis for personalised advertising and related access to device information is Article 6(1)(a) GDPR and, where applicable, Section 25(1) of the German Telecommunications Digital Services Data Protection Act, or TDDDG.

For technically necessary ad delivery, restricted advertising, security, fraud prevention and misuse detection, Article 6(1)(f) GDPR or a statutory exception for technically necessary processes may serve as the legal basis where legally permissible.

11. AdMob Mediation and Additional Advertising Partners

AdMob may be used as a mediation platform through which advertisements from other advertising networks are also delivered. The advertising partners actually used may depend on the AdMob configuration, region, consent status, availability of advertisements and app version.

The app contains technical integrations for the following possible AdMob mediation partners:

Meta Audience Network, provided by companies within the Meta group
Pangle, provided by companies within the ByteDance group

These advertising partners may process the following data as part of an advertising request, to the extent permitted by the consent status and applicable law:

IP address and approximate location
Advertising ID and other device or app identifiers
device model, operating system and language
app and SDK information
ad impressions and ad interactions
technical diagnostic information
information used to detect fraud and misuse

The specific processing depends on the advertising partner used and its applicable privacy terms.

Further information can be found in the Meta Privacy Policy and the Pangle Privacy Policy.

12. Consent Management with the Google User Messaging Platform

The app uses the Google User Messaging Platform, or UMP, to determine whether a consent or privacy dialog must be displayed to a particular user and to manage the corresponding privacy choices.

Depending on the region, app version, device configuration and Google configuration, a dialog concerning advertising, analytics, error analysis and participating advertising partners may be displayed. Users can grant or refuse consent through this dialog.

Where Google requires or provides a permanently accessible entry point for privacy options, users may subsequently change their choices through the corresponding privacy feature within the app.

If a corresponding consent dialog is required for a user and the necessary consent has not been provided, Firebase Analytics and Firebase Crashlytics remain disabled.

Depending on the consent status, availability and technical configuration, advertising delivery may be restricted, non-personalised or, where applicable, prevented.

UMP may locally store or process technically necessary information concerning consent status, regional classification, permitted purposes and advertising partners, as well as information required to provide the dialog. The provider is Google Ireland Limited.

13. In-App Purchase through Google Play

The app offers an optional one-time in-app purchase through Google Play Billing that removes advertising.

Payment processing is handled through Google Play. Androho Software does not receive complete credit card, bank account or other payment details.

However, the app and Google Play services may process or display technical purchase and order information where this is required for payment processing, activation, restoration, verification of purchase status, support, fraud prevention or legal record-keeping obligations.

This may include:

product ID
purchase status
information indicating whether a purchase is pending, completed, failed or restored
order or transaction identifier
purchase time
price and currency
country or region

The purchase is voluntary. Purchase-related data is processed only where a user retrieves product information, completes a purchase, restores a purchase or where the app verifies the existing purchase status.

The app additionally stores the ad-free status locally on the device. The purchase status may be verified through Google Play when the app starts or when purchases are restored.

The legal bases are Article 6(1)(b) GDPR for contract performance and activation, Article 6(1)(c) GDPR for statutory obligations, and Article 6(1)(f) GDPR for support, verification and fraud prevention.

14. Open-Source Components and Source Code

The app uses FFmpeg, libx264 and the ffmpeg_kit_flutter_new component for local processing of video and audio files.

FFmpeg and the included libraries are subject to their respective open-source licence terms. Because GPL-licensed components are used, particularly libx264, the project is published under the GNU General Public License Version 3 in accordance with the licence information provided in the repository and the app.

The app’s source code is publicly available in the following GitHub repository:

github.com/Androho24/SimpleVideoConverter

Opening the GitHub link is voluntary and loads the GitHub website. GitHub’s privacy terms apply when the repository is visited. Access to the repository is not required in order to use the app’s conversion functions.

Further licence information can be found in the licence notices displayed within the app and in the licence files contained in the repository.

15. Recipients and Categories of Recipients

Depending on the region, consent status, app version, purchase status, AdMob configuration and feature used, personal or pseudonymous data may be transferred to the following recipients or categories of recipients:

Google Ireland Limited
Google LLC
Google Firebase Analytics
Google Firebase Crashlytics
Google AdMob
Google User Messaging Platform
Google Play and its payment and processing services
Meta Platforms Ireland Limited or companies within the Meta group, where Meta Audience Network is used
companies within the ByteDance group, where Pangle is used
processors and technical service providers used by Google, Meta or Pangle
Android or device backup services, where users have enabled a system backup and local app data is included under the applicable backup rules

Further information about data processing by Google can be found in the Google Privacy Policy and the privacy and security information concerning Firebase.

16. International Data Transfers

The use of the Google, Meta, Pangle and GitHub services described above may result in personal data being transferred to countries outside the European Union or European Economic Area, particularly the United States and, where applicable, other countries in which the relevant companies or service providers operate.

Such transfers may be based on appropriate safeguards, for example an adequacy decision, certification under the EU-U.S. Data Privacy Framework, Standard Contractual Clauses or other mechanisms provided for by law.

The safeguards used in each individual case depend on the respective provider, service, recipient country and the legal situation applicable at the time of processing.

17. Retention Periods

Local app settings generally remain stored on the device until they are reset within the app, deleted through the Android settings or removed by uninstalling the app. Certain settings may be restored following a reinstallation through Android system backups.

Temporary conversion files are generally stored only for as long as they are required for processing, previewing, saving or sharing. The app may clean temporary files following cancellation, discarding, errors or the next app launch.

Video and audio files saved in the gallery or in a selected folder remain there until they are deleted by the user.

Firebase Analytics data is stored in accordance with the data-retention settings configured in Google Analytics or Firebase. For standard properties, the configurable retention period for user-level and certain event-level data is generally 2 or 14 months. Aggregated reports may remain available for longer periods.

Firebase Crashlytics retains crash stack traces, technical error reports, related diagnostic data and installation identifiers for a limited period. According to Firebase privacy information, the standard retention period for certain Crashlytics data is generally 90 days before the removal process from active and backup systems begins.

AdMob data, advertising reports and associated technical information are stored in accordance with the applicable Google policies, account settings, security requirements and statutory obligations. Retention periods may differ depending on the type of data and the purpose of processing.

The respective retention rules of Meta Audience Network and Pangle apply to data processed by those services.

Google Play purchase, payment, billing and order data may be stored in accordance with statutory retention periods, tax obligations, Google policies and billing requirements.

The Google Play Console may provide us with aggregated statistics and reports relating to installations, uninstalls, usage, performance, stability, advertising, ratings, purchases and revenue. These reports may remain available for different periods depending on the Google feature, selected reporting period, minimum thresholds and account settings.

18. Data Security

Data transferred through the online services used by the app is generally transmitted through encrypted HTTPS or TLS connections.

The app does not transfer video or audio files selected for conversion to Androho Software for server-side media processing.

Please note that the security of locally stored media and app data also depends on the security settings of the device, Android version, screen lock settings, permissions granted to other apps and any backup service being used.

19. Legal Bases for Processing

Where applicable, personal data is processed on the following legal bases:

Processing Activity	Legal Basis
Local selection, preview, analysis, conversion, compression, audio extraction and storage of media files	Article 6(1)(b) GDPR for providing the app functions requested by the user
Local app settings, temporary files, progress displays and notifications	Article 6(1)(b) GDPR for the technical provision of app functions; where applicable, Article 6(1)(f) GDPR for stability and usability
Firebase Analytics	Article 6(1)(a) GDPR where consent is obtained; otherwise, only where legally permissible, Article 6(1)(f) GDPR for analysing and improving the app
Firebase Crashlytics, including technical conversion error reports	Article 6(1)(a) GDPR where consent is obtained; otherwise, only where legally permissible, Article 6(1)(f) GDPR for error analysis, stability, compatibility and technical security
Personalised advertising and related access to device information	Article 6(1)(a) GDPR and, where applicable, Section 25(1) TDDDG
Technical ad delivery, restricted or non-personalised advertising, ad measurement, fraud prevention, security and compliance	Article 6(1)(a) GDPR where consent is required; otherwise, only where legally permissible, Article 6(1)(f) GDPR or a statutory exception for technically necessary processes
Consent management using the Google User Messaging Platform	Article 6(1)(c) GDPR for compliance with legal transparency and accountability obligations, and Article 6(1)(f) GDPR for the legally compliant management of privacy choices
Optional “Remove ads” in-app purchase	Article 6(1)(b) GDPR for contract performance and activation; Article 6(1)(c) GDPR for statutory retention obligations; Article 6(1)(f) GDPR for support, verification and fraud prevention
Compliance with statutory obligations, accounting and record-keeping requirements	Article 6(1)(c) GDPR

Where processing is based on Article 6(1)(f) GDPR, our legitimate interests include the technical provision, financing and improvement of the app, stability and security, troubleshooting, compatibility testing, fraud prevention, support and misuse detection.

20. User Rights

Subject to the requirements of the GDPR, users have the following rights in particular:

right of access
right to rectification
right to erasure
right to restriction of processing
right to data portability
right to object to certain processing activities
right to withdraw previously granted consent with effect for the future
right to lodge a complaint with a data protection supervisory authority

For general privacy-related enquiries, please contact us at:

info@androho.com

Please note that selected videos, temporary files, saved results and most app settings are stored exclusively locally on the user’s device. We do not have direct access to this local data.

Local app data can be deleted in particular by:

discarding a conversion result that has not yet been saved
deleting saved results through the gallery or file manager
deleting the app data through the Android settings
uninstalling the app

The app does not provide its own user account and does not operate its own personal cloud database. It therefore does not provide an automated account-based deletion process for SDK data stored by third-party providers.

We are often unable to directly associate technical data from Google, Meta or Pangle services with a particular person because we do not link names or email addresses to technical installation, advertising or device identifiers.

Where a technical association is possible using the information available and is legally permissible, privacy requests will be reviewed in accordance with the applicable legal requirements.

Where data is processed directly by Google, Meta, Pangle or another provider acting as an independent controller, users may also exercise their rights directly against the respective provider. This particularly applies to Google account, payment, advertising, device and system-backup data.

Statutory retention obligations, particularly for purchase, billing, tax or accounting information, may prevent certain data from being deleted immediately.

21. Changing Consent and Privacy Options

Where a consent dialog or an entry point for privacy options is displayed, users can grant, refuse or subsequently change consent concerning advertising, analytics, error analysis and participating advertising partners.

Changes can be made through the corresponding privacy function within the app, where this function is available based on the region, app version and Google configuration.

The withdrawal of consent applies with effect for the future. It does not affect the lawfulness of processing performed on the basis of consent before its withdrawal.

Users can also manage the Advertising ID, personalised advertising, Google privacy settings, purchase and payment options, and Android backup settings through the Android or Google settings on their device.

22. No Automated Decision-Making by Androho Software

Androho Software does not use data processed through the app for its own automated decision-making or profiling that produces legal effects concerning users or similarly significantly affects them.

Depending on consent, region and their own privacy terms, advertising services and advertising partners may use automated processes to select, measure or personalise advertisements.

23. Changes to this Privacy Policy

We may update this Privacy Policy if the app’s functions, services, mediation partners, permissions, legal requirements or technical processes change.

The current version will be made available on our website. In the event of material changes, additional information may be provided within the app or through the applicable app store.