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: 31 August 2026 · Last updated: 6 September 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

For the separate website closed-test signup form, including your name, Google Play email, consent, and removal options, see closed-test signup privacy.

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 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.

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, metadata, hashes, quality measurements, classifications, and scan state; compression batches and items, processing state, sizes, savings, errors, timestamps, and recovery information; local review decisions and media relationships; 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; development builds may write aggregate diagnostic messages 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.

When advertising is enabled, Google Mobile Ads may automatically collect and share data such as your IP address, interactions with the app and ad, diagnostic information, and device or account identifiers such as the Android advertising ID or app set ID for advertising, analytics, and fraud prevention. Sweeply uses Google's User Messaging Platform to request consent information and present consent and privacy-options forms where required. Sweeply does not send your media or local media-analysis data through these services. Declining advertising consent does not block core features or the Lifetime Pro purchase route.

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 payment, account, purchase, transaction, and fraud-prevention information. Telryq Labs does not receive full payment credentials. Sweeply receives the product identifier, purchase state, purchase token, and acknowledgement state, stores entitlement details locally, and 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 Google Play Billing for the Lifetime Pro purchase, Google Mobile Ads for user-requested rewarded ads, and Google User Messaging Platform for consent information and privacy choices.

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

Data retention and deletion

Your original media and completed outputs remain in the shared media library until you delete them or choose a confirmed replacement operation. Clearing Sweeply's storage or uninstalling it does not delete completed media outputs. The local inventory and analysis cache are refreshed during successful scans; stale records are pruned after a successful scan, while completed compression history is pruned to the ten most recent terminal batches. Private temporary files are removed with pruned jobs where possible.

Local preferences, analysis, active job data, purchase-entitlement cache, and monetization records remain for the installation's lifetime or until replaced by normal app operation. Clear Sweeply's app storage or uninstall it to delete private local data. 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 and Android's advertising privacy controls where available.
  • 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. 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.

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 other countries, 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 Labs.