Privacy policy

Last updated 2. August 2026

DLKeep resolves and downloads videos on your device. Your video goes straight from the site you are saving from to your disk — it does not pass through a DLKeep server, and there is no DLKeep account. We do not receive your video files. To keep downloads working across sites, the app does send us the link and outcome of each save, along with diagnostics, remote configuration, and (on desktop) update checks — exactly what each of those sends is listed below.

What stays on your device

• The videos you save. Written to ~/Movies/DLKeep on desktop and to your gallery on Android. We never receive a copy.
• The links you paste. Used to fetch the video. For each video you save we are sent the link, whether it worked, and the response the site returned to the app. That response is how we tell a working site from one that quietly changed, a bot check from a video that was simply deleted. It can include that video's title, and if you are signed in to that site, what the page shows about your account. It never includes your downloaded file, your password, or your login token.
• Your download history. A local list so the app can show what you already saved. Clearing it in the app deletes it.
• Sign-in sessions. If you sign in to a site to reach a video, the session is stored on your device and sent only to that site.

What we receive

A few things leave the app so it can run and stay reliable. None of them is your videos or your sign-in, and none is tied to your name or an account. The links you save are sent, so a site that breaks can be fixed — that one is spelled out below.

• Diagnostics. Crash reports and coarse, per-save usage counts through Google Firebase (Crashlytics and Analytics), plus the link, the outcome, and the site's response for each save to our own server, so a platform that breaks is noticed in hours and can be diagnosed rather than guessed at. These reports carry a random per-install identifier — it lets us tell one install's activity apart from another's, which is how we measure whether the app actually works after it is installed; it is not tied to you, and clearing app data or reinstalling replaces it. Those site responses are stored privately and deleted automatically after 30 days. These keep downloads working and are always on.
• Remote configuration. On each launch the app fetches a small settings file — a kill-switch and up-to-date extraction rules — from Google Firebase Remote Config. This is what keeps sites working, so it always runs; the request carries your IP and a random per-install identifier, and nothing else.
• Update checks (desktop). The macOS app periodically asks our own update server whether a newer version exists, which sends your IP, the app version, and your operating system. Nothing else is sent.
• What none of these include: your downloaded files, your password, or your login token. (The links to the videos you save are sent, as described above, along with the site's response — which can include that video's title.) The identifiers above are pseudonymous — random per install, never your name, email, or account, because the app has none.

Your clipboard

Clipboard monitoring is a setting you control. While it is on, DLKeep checks the clipboard for a supported link and offers to save it — it never starts a download on its own, and the clipboard contents are neither stored nor transmitted. Turning the setting off stops the checks entirely.

Signing in to a site

Some videos are only reachable while signed in to the site that hosts them. Signing in is optional and always your choice. It happens in a normal web view against that site, the session is kept on your device, and it is used only for requests to that same site. It is not sent to us, and the app has no path that would carry it to us.

Permissions

• Network access — to fetch the video from its source.
• Notifications (optional) — to tell you a download finished.
• Saving to your gallery (Android) — the finished file is written through the system media store, so no storage or media-library permission is requested.

Others involved

• The site you are saving from. Your device connects to it directly, so it sees that request the same way your browser would. Its own privacy policy applies to it.
• Google Firebase. As our processor, Google receives the diagnostics and the remote-configuration request described above, along with your IP and a per-install identifier.
• Our update and configuration servers. The desktop update check is served from our own infrastructure (Cloudflare), which necessarily sees your IP, the app version, and your OS when your device asks it whether an update exists.
• App stores. If you install through Google Play or the App Store, that store handles the purchase and knows you installed the app. We receive only what the store reports to any developer.

This website

The dlkeep.com website uses Cloudflare Web Analytics to count visits. It is cookieless — it stores nothing on your device and collects no personal information, only aggregate page views. The site sets no advertising or tracking cookies.

Children

DLKeep is not directed at children and does not knowingly collect personal information from children under 13. The diagnostics described above are pseudonymous and are not used to identify anyone.

Changes and contact

If this policy changes in a way that affects what leaves your device, the app will say so before the change takes effect. Questions go to [email protected].