Privacy Policy for Quick Share for Android

1. Local transfers and cloud transfers

Local network transfers. When you send files directly between devices on your local network, the transferred file contents do not pass through Quick Share's cloud storage. Device discovery and transfer use information such as local IP addresses, device names or aliases, device identifiers, and file details needed by the receiving device. Local transfer does not mean that the entire app is offline: advertising, diagnostics, configuration, or other online features may still contact their service providers.

Cloud Transfer. If you choose Cloud Transfer, the selected file is uploaded to cloud storage provided through Cloudflare R2 so that recipients can download it using a sharing link. Our service processes the file contents and associated information, including file name, size, upload identifier, account association where applicable, expiration time, access-code settings, and transfer status. Cloud Transfer is not described as end-to-end encrypted. An access code restricts access to a sharing link; it is not a promise that only you and your recipient can decrypt the stored file.

Anyone who obtains a sharing link, and its access code if enabled, may be able to download the file while access remains available. Share these details only with intended recipients. Recipients may keep their own copies after a link expires or you delete an upload.

2. Information we process

Depending on the features you use, we process:

• Files and selected content: files, photos, videos, text, or application packages you select to send, receive, upload, or save. Files may contain personal information or embedded metadata, such as photo location information.

• Account information: Firebase account identifiers and information supplied through Google Sign-In, such as email address, display name, and profile photo URL when provided. We do not receive your Google password.

• Device and network information: information needed for discovery, compatibility, security, diagnostics, and online requests, such as device type, operating system and app version, local network addresses, IP address, and installation or service identifiers.

• Cloud service records: upload metadata, expiry settings, account entitlements, quota information, access and error records, and abuse reports where applicable.

• Purchase information: product identifiers, Google Play purchase tokens, subscription status, and related verification records. Google Play handles payment credentials; our app does not ask you to provide a payment card number directly to us.

• Usage and diagnostic information: feature interactions, transfer counts, broad file types and sizes, outcomes, performance information, error details, crash stack traces, and associated device or installation identifiers. Usage analytics and crash reporting are separate processing activities.

• Advertising information: Google advertising and installation identifiers, IP-derived approximate location, app interactions, and diagnostic information processed by Google's advertising services, depending on device settings, consent, SDK behavior, and applicable law.

• Support communications: your email address, message, attachments, and information you choose to provide when requesting assistance or exercising privacy rights.

Choosing a file for local transfer does not by itself upload that file to Cloud Transfer. Advertising and analytics providers are not the recipients of your files as part of delivering a file transfer. Error reports can contain technical context, so avoid including sensitive material in support logs or screenshots unless necessary.

3. Why we use information

We use information to provide transfers and sharing links; discover receiving devices; manage accounts, storage limits, and subscriptions; deliver advertising; understand feature use; diagnose crashes; maintain service configuration; prevent fraud and abuse; respond to support and privacy requests; and meet legal obligations.

Where applicable data protection law requires a legal basis, processing necessary to provide requested account, transfer, or paid services is based on performing our agreement with you. We rely on legitimate interests for proportionate security, fraud prevention, service reliability, and support, subject to your rights; legal obligations where required; and consent for processing that legally requires it, including relevant advertising or analytics activities. Accepting service terms is not a substitute for consent where consent is required.

4. Android access and permissions

Android permissions and available controls vary by operating system version. Relevant access includes:

You can manage available permissions in Android settings. Denying access may prevent the related feature from working. A permission declaration does not mean that every item accessible under that permission is uploaded to our servers.

5. Service providers and other recipients

We use the following services for the purposes described above:

• Google / Firebase: authentication, usage analytics, crash diagnostics, Remote Config, and App Check for app attestation and abuse prevention.

• Google advertising services and User Messaging Platform: advertising delivery, measurement, fraud prevention, and consent messaging.

• Google Play: app distribution, purchases, subscription management, purchase verification, and app updates.

• Cloudflare: cloud file storage, application hosting, database services, and supporting network infrastructure.

Providers process information under their applicable terms and privacy arrangements. Some, including Google advertising and payment services, may also process information for their own purposes as described in their policies. Learn more in Google's Privacy Policy, Firebase's privacy information, Google's advertising information, and Cloudflare's Privacy Policy.

We also disclose information to recipients you choose through transfers or sharing links; where reasonably necessary to comply with legal requirements, investigate abuse, or protect rights and safety; and to professional advisers or a successor if the service is transferred, subject to applicable safeguards. This policy does not promise that advertising-related disclosures are outside every legal definition of a “sale” or “sharing”; those definitions differ by jurisdiction.

6. Analytics, crash reporting, and advertising choices

The app provides a usage-analytics choice, which you can change in settings. That setting controls app-managed usage analytics; it should not be interpreted as a switch for every Firebase service, crash reporting, security request, or advertising activity. Crash diagnostics may be sent separately to Firebase Crashlytics.

Google's consent messaging may be shown where applicable. Advertising privacy choices depend on your region, available app controls, Google settings, and Android advertising settings. You can manage available advertising identifier and ad-personalization controls through your device or Google account settings. Changing advertising choices does not necessarily remove advertising or stop processing needed for security and ad delivery. Contact us if you need help exercising an advertising-related privacy right.

7. Retention

Cloud uploads. Cloud files are stored temporarily and automatically deleted after the selected retention period expires. Available periods depend on the plan and are displayed in the app. You can also delete an upload earlier through the available file-management controls. Deleting an upload does not remove copies already downloaded by recipients.

Accounts and service records. We retain account information while needed to provide your account. On a verified deletion request, we delete associated account data and uploads through our account-deletion process. Purchase, security, support, or legal records may need separate retention where necessary to resolve transactions, prevent fraud, handle disputes, or comply with law. Any retained information remains subject to this policy and is not kept indefinitely merely because it might be useful.

Provider records. Analytics, crash, advertising, and infrastructure records have separate retention arrangements, which are not necessarily the same as file expiry. For example, Firebase describes a 90-day Crashlytics retention period before removal begins from live and backup systems. Provider backups and independently held Google Play records may not be erased at the same time as a Quick Share account.

Device storage. Received files, downloaded copies, local history, and cached settings may remain on your device until you remove them or use relevant system controls. Deleting a cloud upload or account does not remotely delete copies already saved by recipients.

8. Account deletion and privacy requests

You can initiate account deletion using the account-management screen in the app. You may need to sign in again to verify ownership. You can also email support@quick-share.app with the subject Quick Share Android account deletion. Use the email associated with your account where possible. We may request information reasonably necessary to verify the request; do not send your password or full payment card details.

Account deletion removes your Quick Share account and associated data through the deletion process described above. It does not delete your Google account, retrieve recipient copies, or automatically cancel a Google Play subscription. Manage or cancel that subscription separately in Google Play.

Depending on your location, you may have rights to access, correct, delete, or obtain a copy of personal information; restrict or object to certain processing; withdraw consent; or opt out of legally defined sale, sharing, or targeted advertising. Contact us to exercise an applicable right. We respond within the period required by applicable law and explain relevant limitations or retention requirements. You may also have a right to complain to your local data protection authority and, where applicable, appeal our decision by replying to our response.

9. International processing and security

Our providers operate internationally, so information may be processed outside your country, including in countries with different privacy laws. Applicable transfer requirements and provider arrangements must be considered for those transfers. Contact us for information about the arrangements relevant to your data.

We use technical and organizational measures appropriate to the service, including authenticated account operations and access controls. No storage or transmission method is completely secure. Use trusted devices and networks, protect your sharing links, and keep separate backups of important files.

10. Children

Quick Share is not intended to solicit personal information from children below the age at which they can lawfully use the service or provide any necessary consent in their location. If you believe a child has provided personal information without required authorization, contact us so we can investigate and take appropriate action. This statement does not replace the app's Google Play target-audience declaration.

11. Changes and contact

We may update this policy when the service or our practices change. The published version will display its effective or last-updated date. We will provide additional notice or request consent when required by applicable law.

For privacy questions, requests, or complaints, contact Jump Dong at support@quick-share.app.