Sweeply · Privacy policy

Your media stays yours.

This policy explains how Sweeply accesses and processes media on your Android device, what it stores locally, and what Google services may process for ads, consent, and purchases.

Effective and last updated: 31 August 2026

At a glance: Sweeply analyzes and optimizes photos and videos on your device. Telryq Labs does not operate a Sweeply backend and does not receive your media. Optional Google services for rewarded advertising, consent, and a Lifetime Pro purchase may process limited data as described below.

Scope

This privacy policy applies to the Sweeply Android application provided by Telryq Labs. It does not replace the separate Telryq Labs website privacy information.

Sweeply does not require an account or login. Telryq Labs does not operate a server or cloud account system for Sweeply. The app's core scanning, review, and optimization features are designed to work on the device.

Information Sweeply accesses

With the media permissions you grant through Android, Sweeply can access photos and videos in the device's shared media library. Depending on your Android version and permission choice, access may cover the full library or only media you select.

To identify, analyze, display, compress, and help you manage that media, Sweeply may read:

  • the photo or video bytes and generated thumbnails;
  • MediaStore identifiers and content references;
  • file name, media type, file size, dimensions, dates, duration, orientation, volume, folder or album information, and owner package where Android exposes it; and
  • embedded media metadata needed to preserve an item during optimization, which may include the location metadata already embedded in that item.

Sweeply does not request device location permission and does not determine your current location. It does not request access to contacts, the microphone, or the camera. It does not request all-files access or crawl arbitrary files outside Android's shared media library.

Android may also ask for notification permission so Sweeply can show the status of long-running compression work. Notification permission does not give Sweeply access to the contents of other notifications.

On-device media processing

Sweeply processes media locally. It reads image and video data to create thumbnails, calculate exact file hashes, compare perceptual similarity, estimate image quality or blur, identify likely screenshots, group potential duplicates, and calculate storage information.

Video compression is performed on the device using Android media codecs. Temporary working files are created in Sweeply's private app storage, checked before an output is committed, and then removed when no longer needed. If recovery is needed after an interruption or failure, a temporary result may remain until Sweeply resolves or prunes that job.

When you choose to preserve metadata during compression, Sweeply may copy metadata from the source to the output. Embedded GPS coordinates, when present in the source, may be held temporarily in the local job record for that purpose and are cleared when the job reaches its terminal or verified-recovery state.

Sweeply does not upload photos, videos, thumbnails, hashes, analysis results, file names, or media metadata to Telryq Labs or to Google for media processing. Deleting or replacing shared media is a user-initiated action and uses Android's system confirmation where required.

Local app data, preferences, and history

Sweeply stores operational data on the device in its private database and preferences. This can include:

  • onboarding, theme, permission-state, output-mode, preset, and optimization preferences;
  • a local media inventory and analysis cache containing media identifiers and metadata, exact and perceptual hashes, quality measurements, classifications, and scan state;
  • compression batches and items, processing state, input and output sizes, estimated or actual savings, errors, timestamps, and temporary-file recovery information;
  • your local review decisions and media relationships used by the app;
  • local optimization allowance, reward grants, reservations, and consumption history; and
  • a cached Lifetime Pro entitlement, including the Google Play purchase token, acknowledgement state, and last successful verification time.

This data supports app functionality, recovery after interruption, consistent results across scans, purchase restoration, and the local storage allowance. Sweeply excludes its private database and preferences from Android cloud backup and device-to-device transfer.

Sweeply does not include an active analytics or crash-reporting service. Its analytics interface is a no-operation implementation that sends nothing. Development builds may write aggregate diagnostic messages, such as counts, durations, and memory measurements, to the local Android debug log.

Rewarded advertising and consent

Sweeply's intended release includes an optional rewarded-ad feature provided by Google Mobile Ads. A rewarded ad is requested only after you choose the ad route to add local optimization allowance; Sweeply does not use banner, interstitial, native, or app-open ads. You can use the app without watching an ad, although the associated reward will not be granted.

When advertising is enabled, the Google Mobile Ads SDK may automatically collect and share data such as your IP address (which may be used to estimate general location), interactions with the app and ad, diagnostic information, and device or account identifiers such as the Android advertising ID or app set ID. Google states that it uses this data for advertising, analytics, and fraud prevention. The specific advertising mode may be personalized, non-personalized, or limited depending on your region, consent choices, device settings, and Google's requirements.

Sweeply uses Google's User Messaging Platform (UMP) to request consent information and, where required, present a consent message and privacy-options form before the rewarded-ad route is used. Google may process device, consent, and regulatory-region information to provide this service. Sweeply does not send your media or local media-analysis data through UMP.

Declining advertising consent where a consent message is required prevents the rewarded-ad route from proceeding; it does not block Sweeply's core features or the Lifetime Pro purchase route. Where Google requires a privacy-options entry, you can reopen it from Sweeply's settings to change or withdraw your choice.

Google Play purchases

Sweeply's intended release offers Lifetime Pro as a one-time, non-consumable in-app purchase through Google Play Billing. It is not a subscription. Google Play processes the payment, Google account, purchase, transaction, and fraud-prevention information needed to complete and manage the purchase under Google's own terms and privacy policy.

Telryq Labs and Sweeply do not receive your full card number or other payment credentials. Sweeply receives purchase information from Google Play, including the product identifier, purchase state, purchase token, and acknowledgement state. It stores the entitlement details locally and communicates with Google Play to query, restore, and acknowledge the purchase. Sweeply does not send the purchase token to a Telryq Labs server because Sweeply has no backend.

Data sharing and third-party services

Telryq Labs does not sell your media or local app data. Sweeply does not share media content or media-analysis data with advertisers, Google Play Billing, Google Mobile Ads, or UMP.

The release-intended app integrates the following Google services, which may receive and process the limited data described in their own documentation:

  • Google Play Billing for the Lifetime Pro purchase, entitlement checks, restoration, acknowledgement, payment processing, and fraud prevention;
  • Google Mobile Ads for user-requested rewarded ads, ad delivery and measurement, diagnostics, and fraud prevention; and
  • Google User Messaging Platform for consent information, consent messages, and privacy choices.

For more information, review the Google Privacy Policy, Google's Mobile Ads data disclosure, and Google Play billing information.

Data retention and deletion

Your original media and any completed outputs remain in the shared media library until you delete them or choose a confirmed replacement operation. Clearing Sweeply's storage or uninstalling Sweeply does not delete completed media outputs from the shared library.

The local media inventory and analysis cache are refreshed during successful scans, and records for media no longer visible to Sweeply are pruned after a successful scan. A failed or cancelled scan does not perform that pruning. Completed compression history is automatically pruned to the ten most recent terminal batches; obsolete private temporary files are removed with pruned jobs where possible.

Local preferences, analysis, active job data, purchase-entitlement cache, and monetization records otherwise remain for the installation's lifetime or until replaced by normal app operation. You can delete them by clearing Sweeply's app storage or uninstalling the app. A local purchase record may be recreated when Sweeply checks an owned Lifetime Pro purchase with Google Play. Google retains purchase, advertising, consent, and diagnostic data according to its own policies and controls.

Your privacy choices

  • Use Android settings to grant, limit, or revoke photo and video access.
  • Choose whether to optimize, delete, replace, or keep each media item; Android confirmation is used where required.
  • Do not select the rewarded-ad route if you do not want to request an ad.
  • Use Sweeply's privacy-options entry where available, and Android's advertising privacy controls, to review applicable advertising choices.
  • Clear Sweeply's storage or uninstall the app to remove its private local database and preferences.

Security

Sweeply limits media access through Android permissions and stores its database, preferences, and working files in app-private storage. Media processing is kept on the device, and Sweeply does not expose a Telryq Labs backend that could receive the media library. Communications made by Google SDKs use the security mechanisms provided by those services and Android. No method of storage or transmission is completely secure, but Sweeply is designed to minimize network disclosure of user content.

Children's privacy

Sweeply is a general-purpose media storage utility and is not designed specifically for children. It does not provide accounts or ask users to submit a name, email address, birth date, or similar profile information. Google services used for purchases, rewarded advertising, and consent may process data as described above. A parent or guardian who believes a child has provided information in connection with Sweeply can contact Telryq Labs at the address below.

International users

Media processing and Sweeply's private app data remain on your device regardless of where you use the app. Google may process data for billing, advertising, consent, diagnostics, and fraud prevention in countries other than your own, subject to Google's privacy policy and applicable transfer safeguards.

Changes to this policy

This policy may be updated when Sweeply's features, SDKs, or data practices change. Material updates will be published at this URL and the date at the top of the policy will be revised. If a change requires an in-app notice or renewed consent, it will be provided where appropriate.

Contact

Sweeply is provided by Telryq Labs.

For privacy questions or concerns, email privacy@telryq.com or visit telryq.com.