FileConverterPro Privacy Policy

ByteVerse (“we”, “our”, or “us”) provides the FileConverterPro mobile application (“FileConverterPro” or the “App”). This Privacy Policy explains how the App accesses, processes, uses, shares, retains, and protects information when you use FileConverterPro.

1. Information We Process

Files you select

FileConverterPro accesses files that you actively select for conversion and files created by the App as conversion results. Depending on the selected conversion type, a file may be processed locally on your device or temporarily transmitted through ByteVerse-operated online conversion infrastructure. CloudConvert may be used as a fallback for certain online conversions when the self-hosted conversion path cannot complete the request.

File metadata and local conversion history

The App may process basic file information such as file name, file type, file size, MIME type, source and target formats, and local conversion history in order to perform conversions, display results, and show recent conversion activity.

Google account and authentication information

FileConverterPro supports Google Sign-In. When you choose to sign in, we may process account information provided through Google and Firebase Authentication, such as your unique account identifier, email address, display name, and profile image URL where available. This information is used to identify your FileConverterPro account and keep account-related data, including your credit balance, associated with the correct user.

Credit, reward, signup bonus, and transaction information

FileConverterPro operates a credit-based conversion system. We may store and process your current credit balance, signup bonus status, credit additions and deductions, conversion authorization records, refunds, reward-session records, daily rewarded-ad usage, and related transaction identifiers. These records are used to keep balances consistent, enforce daily reward limits, prevent duplicate rewards or duplicate charges, and investigate abuse or technical issues.

The signup bonus is intended to be granted only once per Google identity. To prevent repeated signup-bonus claims through account deletion and recreation, FileConverterPro retains a minimal pseudonymous anti-abuse record after account deletion. This record consists of a cryptographic hash derived from the Google account provider identifier together with limited claim metadata such as whether the bonus was previously claimed and the claim timestamp. The retained record does not contain the user's email address, display name, Firebase user ID, or the raw Google provider identifier.

Google Play purchase information

Credit packs are offered as one-time purchases through Google Play. To verify a purchase and grant credits, FileConverterPro and its backend may process information such as the Google Play product identifier, purchase token, purchase status, order or transaction metadata, and an account-linked identifier used for verification and fraud prevention. Payment processing is handled by Google Play. ByteVerse does not receive your full payment card details.

Rewarded advertising information

FileConverterPro may allow you to voluntarily watch rewarded ads to earn credits, subject to a daily limit. Reward verification may use a reward-session identifier and server-to-server verification information from Google AdMob, including an advertising transaction identifier. Credits are granted only after the backend verifies the reward.

Technical, analytics, crash, and advertising data

FileConverterPro uses Google Analytics for Firebase to understand how the App is used and to improve product reliability and user experience. Analytics may process information such as app interactions, session and device information, app version, approximate technical identifiers, and developer-defined events.

FileConverterPro may log limited developer-defined analytics events related to the conversion flow, such as when a file is selected, an output format is selected, a conversion starts, succeeds, or fails, whether the conversion is local or online, and the source and target file formats. We do not intentionally send selected file names, file paths, URIs, or file contents to Firebase Analytics.

FileConverterPro also uses Firebase Crashlytics to detect crashes, non-fatal errors, and application stability problems. Crashlytics may process crash stack traces, relevant app state, device metadata, app version information, installation identifiers, session identifiers, and developer-defined diagnostic data attached to error reports.

For conversion-related non-fatal error reports, FileConverterPro may attach limited diagnostic keys such as source and target file formats, whether processing was local or online, and the stage where the error occurred. We do not intentionally attach selected file names, file paths, URIs, or file contents to Crashlytics reports.

FileConverterPro uses Google Mobile Ads (AdMob). The Google Mobile Ads SDK may collect and share technical data such as IP address, device or advertising identifiers, app interactions, and diagnostic information for advertising, measurement, fraud prevention, and related purposes, depending on your device settings, region, consent choices, and Google’s SDK configuration.

Our backend infrastructure may also receive limited technical request information such as IP address, timestamps, authentication metadata, and request metadata as part of normal server operation, abuse prevention, security, and troubleshooting.

2. Local File Processing

Supported local conversions are performed directly on your device. Files used for those conversions are not intentionally uploaded to ByteVerse online conversion infrastructure, Cloudflare R2, Hetzner conversion workers, or CloudConvert. However, an internet connection is required before a paid local conversion starts so the backend can authenticate the account, verify the current credit balance, and reserve the applicable credits. For local conversions, reserved credits are deducted from the balance only after the requested output file has been successfully created. If the conversion fails or is cancelled before completion, the reservation is released and those credits are not charged.

Local conversion results and local conversion history may remain on your device until you delete them, clear the App’s history or data, or uninstall the App, subject to Android storage behavior.

3. Online File Processing

Some formats require online processing. When you explicitly start one of these conversions, the selected file is uploaded through a time-limited signed URL to temporary object storage provided by Cloudflare R2. A ByteVerse conversion worker hosted on Hetzner retrieves the input file, performs the requested conversion, and writes the converted result back to temporary R2 storage so the App can download it.

The ByteVerse backend keeps the credentials used to manage this storage and generates time-limited access URLs for conversion jobs. Temporary self-hosted conversion objects are used only for the requested conversion. On successful processing, the input object is deleted immediately, and an R2 lifecycle rule is configured to remove remaining conversion objects no later than one day after they are created. Incomplete multipart uploads are also configured to be aborted after one day.

If the self-hosted conversion path cannot complete a supported request, ByteVerse may use CloudConvert (Lunaweb GmbH) as a fallback conversion provider. In that case, the selected file is transmitted to CloudConvert only for the purpose of performing the requested conversion. CloudConvert states that uploaded files are automatically deleted from its servers no later than 24 hours after upload and that file transfers use encrypted connections.

ByteVerse does not use files processed online for advertising, profiling, or sale. Files transmitted through Cloudflare R2, Hetzner-hosted conversion workers, or CloudConvert fallback processing are used only to provide the requested conversion functionality.

4. Background Processing and Notifications

FileConverterPro may continue a conversion that you explicitly started while the App is in the background or while you navigate to another screen. For user-initiated local conversions, Android foreground-service functionality may be used to continue on-device media or file processing. For user-initiated online conversions, foreground-service functionality may be used to continue file upload, conversion-status monitoring, and result download.

While a conversion is active, FileConverterPro may display a persistent progress notification so Android can keep the user-visible task running. The App may also display completion, failure, or cancellation notifications. On supported Android versions, notification permission may be requested so these notifications can appear in the notification area.

Background processing and notifications do not cause locally processed files to be uploaded to ByteVerse online conversion infrastructure or shared with conversion providers. Files are transmitted through Cloudflare R2 and a Hetzner-hosted ByteVerse conversion worker only when you explicitly start a conversion that requires online processing. CloudConvert receives a selected file only if the fallback path is required, as described above.

5. Accounts, Authentication, and Cloud Database

FileConverterPro uses Firebase Authentication for account authentication and Cloud Firestore for server-side account and credit-related records. Signing in is not required simply to open the App, but an authenticated account is required when you start features that use the FileConverterPro credit system.

Server-side account records may include your FileConverterPro user identifier, basic Google profile information, credit balance, credit transactions, rewarded-ad usage, conversion credit records, and timestamps required to operate and secure the service.

You can permanently delete your FileConverterPro account from the Account & Credits screen in the App. Account deletion removes the Firebase Authentication account and FileConverterPro server-side account data associated with that account, subject to the limited anti-abuse retention described in Section 12 and any information independently retained by third-party providers under their own policies or applicable law.

6. Backend Infrastructure

FileConverterPro uses ByteVerse backend and conversion-worker infrastructure hosted on Hetzner servers to coordinate account authentication, credit verification, online conversion requests, rewarded-ad verification, Google Play purchase verification, anti-abuse controls, and related server-side operations. Cloudflare R2 is used as temporary object storage for input and output files involved in supported self-hosted online conversions. The backend is designed so that sensitive service credentials do not need to be embedded directly in the App.

Hetzner and Cloudflare may process technical request, network, storage, and infrastructure information as necessary to provide their services and according to their own privacy and security practices.

7. Credits and Rewarded Ads

Credits may be granted through signup promotions, rewarded ads, or Google Play purchases. Conversion costs and reward values may vary by conversion type or configuration. For eligible local conversions, credits may first be reserved and are charged only after the output file is successfully created. Online conversions may use a different authorization, charging, refund, or cancellation flow because server infrastructure or fallback-provider processing costs can be incurred during the requested conversion.

Rewarded ads are optional. A daily reward limit may apply. The App creates a reward session before showing an eligible rewarded ad, and the backend verifies completion using AdMob server-side verification before adding credits. Reward and transaction records may be used to prevent replay, duplicate rewards, fraud, and abuse.

8. Google Play Purchases

FileConverterPro offers one-time credit packs through Google Play Billing. Google handles the payment transaction. FileConverterPro sends purchase verification information to its backend, which verifies the purchase with Google Play before granting credits. Purchase verification records may be retained to prevent the same purchase from being claimed more than once and to maintain an accurate credit balance.

9. Advertising

FileConverterPro displays advertisements using Google AdMob, including ad formats that may include banner, interstitial, or rewarded ads. Google and its advertising partners may process information necessary to provide, measure, secure, and personalize or limit ads, depending on applicable law, consent status, user choices, and device settings.

ByteVerse does not sell your selected file contents to advertisers, and files selected for conversion are not provided to Google AdMob for advertising purposes.

10. How We Use Information

Information processed through FileConverterPro is used to:

• authenticate users and maintain FileConverterPro accounts;
• maintain and synchronize credit balances;
• record credit grants, deductions, refunds, and related transactions;
• perform file conversions requested by you;
• continue user-initiated conversions in the background and provide conversion-status notifications;
• display conversion history and file information;
• provide online conversion functionality where required;
• display and verify advertisements and rewarded-ad credits;
• verify Google Play purchases and grant purchased credits;
• enforce daily reward limits and prevent duplicate rewards or charges;
• measure feature usage and understand conversion flows through analytics;
• detect crashes, non-fatal errors, and application stability problems;
• prevent abuse and protect the App, user accounts, credits, and backend services;
• diagnose technical problems and improve reliability.

11. Third-Party Services

FileConverterPro may use the following third-party services:

• Google Sign-In / Firebase Authentication — account authentication and identity. Google Privacy Policy
• Cloud Firestore — storage of account, credit, reward, and transaction-related records. Firebase Privacy and Security
• Google Analytics for Firebase — app usage measurement and product analytics. Firebase Privacy and Security
• Firebase Crashlytics — crash reporting, non-fatal error reporting, diagnostics, and application stability monitoring. Firebase Privacy and Security
• Google AdMob / Google Mobile Ads SDK — advertising, measurement, diagnostics, fraud prevention, and rewarded-ad delivery and verification. Google Privacy Policy
• Google Play Billing — processing and verification of one-time credit-pack purchases. Google Privacy Policy
• Cloudflare R2 — temporary object storage and file transfer for supported online conversions. Cloudflare Privacy Policy
• Hetzner Online GmbH — backend and conversion-worker hosting. Hetzner Privacy Policy
• CloudConvert (Lunaweb GmbH) — fallback file-conversion provider used when the self-hosted conversion path cannot complete a request. CloudConvert Privacy Policy

12. Data Retention and Deletion

• Local files and conversion history: remain on your device until removed by you, cleared through the App or device settings, or removed when the App is uninstalled, subject to Android storage behavior. Deleting your FileConverterPro account does not automatically delete converted files or local conversion history stored on your device.
• Self-hosted online conversion files: temporary input and output objects may be stored in Cloudflare R2 while the requested conversion is processed by the ByteVerse worker hosted on Hetzner. On successful processing, the input object is deleted immediately. An R2 lifecycle rule is configured to remove remaining conversion objects no later than one day after creation, and incomplete multipart uploads are configured to be aborted after one day.
• CloudConvert fallback files: if a conversion uses the CloudConvert fallback path, CloudConvert states that uploaded files are automatically deleted no later than 24 hours after upload.
• Account and credit records: are stored while needed to operate your FileConverterPro account and credit balance. When you use the in-app Delete Account feature, FileConverterPro deletes the Firebase Authentication account and server-side account data associated with your account, except for the limited signup-bonus anti-abuse record described below and any information a third-party provider independently retains under its own policy or applicable law.
• Signup-bonus anti-abuse record: after account deletion, FileConverterPro retains a minimal pseudonymous record to determine whether the same Google identity has already received the one-time signup bonus. The stored document uses a cryptographic hash derived from the Google provider identifier and limited claim metadata. It does not store the user's email address, display name, Firebase user ID, or raw Google provider identifier. This record is retained for fraud and abuse prevention so deleting and recreating an account does not generate another signup bonus.
• Firebase Analytics data: is retained according to the Google Analytics / Firebase settings and retention controls applicable to the Firebase project.
• Firebase Crashlytics data: is retained according to Google’s Firebase Crashlytics retention practices.
• Technical logs: backend and third-party infrastructure providers may retain technical logs according to operational, security, and provider retention practices.

Signing out of FileConverterPro does not delete your account or server-side account data. To delete your FileConverterPro account, use Account & Credits → Delete Account in the App. You may also contact ByteVerse using the email address in the Contact section for privacy-related questions or requests.

13. Data Security

We use reasonable technical safeguards designed to protect information in transit and during processing. Backend requests use authenticated access where applicable, and network communications for backend operations and online conversions use encrypted connections such as HTTPS/TLS. Time-limited signed URLs are used for temporary conversion-file access where applicable. Server-side verification is used for rewarded-ad credits and Google Play purchases to reduce unauthorized or duplicate credit grants.

No method of electronic transmission or storage can be guaranteed to be completely secure.

14. Children’s Privacy

FileConverterPro is a general-purpose utility application and is not directed to children under the age of 13. We do not knowingly seek to collect personal information from children. If you believe a child has provided personal information through the App, please contact us.

15. International Processing

Third-party service providers may process information in countries other than your country of residence. Their processing is governed by their own privacy policies and applicable legal safeguards.

16. Your Choices and Rights

You control which files you select for conversion. You can delete converted files and local conversion history stored on your device. You may sign out of your Google-linked FileConverterPro account at any time, or permanently delete your FileConverterPro account from Account & Credits → Delete Account. You may also manage advertising privacy choices, advertising identifiers, and applicable consent settings through your device, Google services, or consent interfaces made available to you.

Depending on where you live, you may have additional rights regarding personal information, including rights to access, correct, or request deletion of certain information. You may contact ByteVerse regarding privacy questions or requests using the contact information below.

17. Changes to This Privacy Policy

We may update this Privacy Policy when FileConverterPro, our service providers, or legal requirements change. The latest version will be published on this page with an updated effective date.

18. Contact

Developer: ByteVerse
App: FileConverterPro
Email: [email protected]

For privacy-related questions, account-data deletion requests, or other privacy concerns, please contact us using the email address above.