Clipsy is a video-downloader utility for Android. This policy explains what limited information the app handles, why, and what your choices are. Plain English, no dark patterns.
Summary
- Clipsy has no account and no login. We do not collect names, emails, phone numbers, photos, or contact lists.
- The app uses Google AdMob for advertising. AdMob collects an anonymous advertising ID (Android AAID) under Google's policies to serve and measure ads.
- Downloaded videos are saved to your device only. They stream directly from the source platform's CDN to your device — we do not host, cache, or proxy any video bytes on Clipsy servers.
- Firebase Analytics and Crashlytics are enabled. They record anonymized event counts and crash traces tied to a random Firebase installation ID, not to you. See *Diagnostics and crashes* below.
- The one thing you can send us on purpose is a feedback message, from the in-app feedback form. It is the only place Clipsy stores anything you have written on a server, and it is entirely optional — see *Feedback you send us*.
Advertising ID (via Google AdMob)
Clipsy displays ads through Google AdMob. AdMob reads the anonymous advertising ID on your device — an ID Google issues to every Android device that can be reset or opted out from Settings → Google → Ads.
We use this only to let AdMob:
- Show ads inside the app.
- Measure ad performance (impressions, clicks, retention) so we get paid.
- Prevent showing the same ad to you repeatedly (frequency capping).
Google acts as an independent controller of the advertising ID under its own privacy policy — see https://policies.google.com/privacy and the *How Google uses information from sites or apps that use our services* page at https://policies.google.com/technologies/partner-sites.
In the European Economic Area, the United Kingdom, and Switzerland, the app shows a Google-certified consent dialog (UMP) before any ad is loaded — you can accept, decline, or manage your ad-personalization choices there.
Approximate location (via Google AdMob)
AdMob may derive approximate location from your IP address to serve region-relevant ads and to comply with regional advertising laws. This is at the country / region level, never a precise location; we do not request the Android location permission.
Videos you download
- You give Clipsy a URL. The app resolves it to a direct media link on your device — the extraction engine runs locally and the URL you paste is not sent to any Clipsy server.
- The video streams directly from the source platform's CDN to your device.
- The MP4 file is written to
/Movies/Clipsy/via the Android MediaStore, visible in your gallery apps. - We do NOT record which videos you download, upload them to any server, or share the list with any third party. The Downloads list is stored locally on your device in a Room database and never transmitted.
Diagnostics and crashes
Clipsy uses Firebase Analytics and Firebase Crashlytics.
- Analytics records anonymized event counts — which screen was opened, whether a download succeeded or failed, and which ad slot was shown — tied to a random Firebase installation ID, not to you. To diagnose failures it also records the host and the shape of a link that failed (for example
instagram.com/reel/<id>), with every identifier masked. The full URL is never recorded, so what a report cannot tell us is *which* video you tried to download. - Crashlytics sends anonymized stack traces plus device model and Android version when the app crashes — never your name, email, or the videos you downloaded.
Feedback you send us
Clipsy has an in-app feedback form (Settings → Send feedback, and from the error screen). It is entirely optional and nothing is sent unless you fill it in and tap Send.
- What is sent: the problem categories you tick, the message you write, and basic context to reproduce the bug — app version, Android version, device model, and language/region.
- What is NOT sent: your name, email, advertising ID, any device identifier, the list of videos you have downloaded, or any link you have pasted. There is no field for contact details and we do not attach any.
- Where it goes: Google Cloud Firestore, in our Firebase project. Access is restricted to the Appmetrics team — the app itself can only write a report, never read one back, so no user can ever see another user's message.
- Please don't put personal details in the message. It is a free-text box, so it will store whatever you type. Write what the app did, not who you are.
- We cannot reply. There is no account and no address attached to a report, so the form is one-way by design.
- Deletion: because reports carry no identifier, we usually cannot find yours on request. If you want one removed, email support@appmetrics.studio with enough of the wording to identify it and we will delete it.
Permissions the app requests
| Permission | Why |
|---|---|
INTERNET + ACCESS_NETWORK_STATE | Fetch the video-extraction result + stream the download. |
POST_NOTIFICATIONS (Android 13+) | Show progress + completion notifications for downloads running in the background. Optional — you can decline; the app still works. |
AD_ID | Read the advertising ID for AdMob, per Google's requirements. Governed by the section above. |
No camera, microphone, contacts, calendar, location, SMS, phone, or all-files-access permissions are requested or used.
Data sharing
- Google (AdMob) — advertising ID + approximate location, for ad serving + measurement. See Google's policy links above.
- Google (Firebase Analytics / Crashlytics / Firestore) — as processor, for the anonymized analytics, crash traces, and feedback reports described above. Nothing here is used for advertising.
- No one else. We do not sell any data, ever. We do not have a marketing list.
- Nothing you send is used to build a profile of you, and none of it is linked to your identity — there is nothing to link it to.
Retention
- Advertising ID / approximate location — Google's retention policy applies (see their links above); Clipsy does not store either.
- Downloaded videos — kept on your device until you delete them from Clipsy or from your gallery. No copy exists off your device.
- Downloads list metadata — stored locally in Clipsy's Room database until you clear the app data or uninstall.
- Feedback reports — kept while the issue is open and reviewed periodically; we delete reports older than 24 months.
- Analytics / crash events — Firebase's retention applies (analytics events default to 14 months); Clipsy does not keep a separate copy.
Your choices
- Reset or opt out of the advertising ID anytime: Android Settings → Google → Ads → Reset advertising ID (or *Delete advertising ID*, on Android 12+).
- Change your EEA/UK ad-consent choices anytime: Clipsy → Settings → Privacy options (available where UMP requires it).
- Delete a downloaded video from Clipsy's Downloads tab or from your gallery app.
- Clear all Clipsy data by uninstalling the app or via Settings → Apps → Clipsy → Clear storage.
Children
Clipsy is not directed to children under 13. We do not knowingly collect information from children under 13. If you believe a child under 13 has used the app, please email support@appmetrics.studio so we can investigate.
International users
Clipsy is available worldwide. The video-extraction service currently operates from cloud infrastructure in the United States. If you use the app from outside the US, your paste queries transit to US servers for that lookup only. Ad serving is handled by Google's global infrastructure.
Copyright / DMCA
Clipsy is a tool for saving videos you own or have the copyright holder's permission to save. If you are a rights-holder and believe content is being downloaded via Clipsy in violation of your rights, please email support@appmetrics.studio with:
1. A description of the copyrighted work. 2. The URL or content in question. 3. Your contact information. 4. A statement that you have a good-faith belief the use is not authorized. 5. A statement that the information is accurate, under penalty of perjury, and that you are authorized to act. 6. Your physical or electronic signature.
We do not host any video content ourselves — downloads stream directly from the source platform's CDN — so takedowns are typically most effective addressed to the source platform.
Changes to this policy
We will update this policy when we change how the app handles information. The "Last updated" date at the top reflects the most recent change. Continued use of Clipsy after an update indicates acceptance.
Contact
Questions or complaints? Email support@appmetrics.studio. We read every message.