Vimpse is published by I Enterprise Ltd (company 13225768, VAT GB372459574), Suite 2.06b, C4di @TheDock, 31–38 Queen Street, Hull HU1 1UU, United Kingdom. Privacy contact: info@vimpse.com.
The company’s wider policy is at https://i-enterprise.co.uk/privacy. This page describes how Vimpse handles information. It is public HTML and does not require a login.
1. About Vimpse
Vimpse is a personal library of saved video moments on Android. You can use it without creating a Vimpse account.
2. Information Vimpse stores locally
On the device, in private app storage, Vimpse may store:
- Walls (name, order, style metadata)
- Vimpse records (title, notes, tags, favourite, order, timestamps)
- Start, finish and duration in milliseconds
- YouTube video ID, public title, public thumbnail URL
- Copied phone-video files used by saved Vimpses
- Appearance and settings preferences
- A local cache of whether Pro is unlocked
Android backup is disabled (android:allowBackup="false").
3. Information Vimpse does not require
No Vimpse account, no mandatory profile, no Vimpse-operated cloud database for the library. The only Android permission declared is INTERNET, used for YouTube embeds, YouTube oEmbed, public thumbnails, and Google Play purchase checks.
4. YouTube
If you add a YouTube Vimpse, the embedded player loads from YouTube (IFrame player via the android-youtube-player library). Titles may be requested from YouTube’s public oEmbed endpoint. Thumbnails may load from img.youtube.com. YouTube may collect data as described in Google’s privacy policy and YouTube’s Terms of Service. Vimpse does not download YouTube video files. YouTube may show its own ads in the embedded player.
When the player loads, YouTube’s own services receive what they need to render the video, including client identification required by YouTube’s Required Minimum Functionality. That is YouTube’s processing, not a Vimpse analytics SDK.
5. Local videos
You explicitly pick or share a video. Vimpse copies it into private storage so a saved moment still plays if picker access is later withdrawn. We do not scan the rest of your gallery.
6. Sharing
If you share a Vimpse or Wall, Android’s share sheet sends the content you chose to the app you pick. I Enterprise Ltd does not receive that share unless you email us.
7. Google Drive
The current app does not request Google Drive access and does not use OAuth. If Drive sharing is added later, this policy will be updated first to name the scopes (the intended least-privilege scope is https://www.googleapis.com/auth/drive.file), what files are created, who owns them, whether tokens are stored, and how to revoke access in your Google account.
8. Payments
Vimpse Pro is a one-time product processed by Google Play Billing. I Enterprise Ltd does not receive your full payment-card details. Google’s terms and privacy policy apply to the purchase. Entitlement is cached on the device and restored through Play.
9. Analytics and advertising
Vimpse does not include an analytics SDK, advertising SDK, or Vimpse ad network. This website does not set non-essential cookies and does not load Google Analytics, Meta Pixel, Hotjar or Clarity. YouTube and Google Play remain third parties when you use them.
10. Summary of data practices
| Data | Collected by Vimpse servers? | Shared by Vimpse? | Notes |
|---|---|---|---|
| Library content (titles, times, local files) | No | Only if you share | On-device |
| YouTube ID / public metadata | No | To YouTube when you play or fetch | You invoke YouTube |
| Purchase entitlement | No | Handled by Google Play | Play is the merchant |
| Device identifiers for ads | No | No | No ads SDK |
11. Retention and deletion
Your library remains until you delete individual Vimpses, clear app storage, or uninstall. Because there is no Vimpse account, there is no remote account to erase. If you email a privacy request, we can only act on what we actually hold (for example an email you sent us), not on the copy on your phone.
12. Children
Vimpse is a general-audience utility. It is not directed at children and is not part of the Google Play Families programme. It does not knowingly collect personal information from children.
13. Security
Local files sit in the app’s private directory. Traffic to YouTube and Play uses HTTPS. The website worker upgrades HTTP to HTTPS and sends HSTS. No method is perfect; do not put secrets in Vimpse titles.
14. International users
The developer is in the United Kingdom. The app is intended for use in the United States, United Kingdom, Canada, Australia and other countries where Google Play distributes it. This policy is written to be readable, not as a jurisdiction-by-jurisdiction legal opinion.
15. Changes
We will change this page when the app’s data practices change. The dates at the top tell you which version you are reading.
16. Contact
info@vimpse.com · postal address in section 1 · contact page.