Embeddy Privacy

Privacy policy

Last updated 2026-10-31. Applies to the Embeddy Android app and the tools at embeddy.link.

Summary

  • No accounts, no advertising, no analytics, no crash-reporting SDKs, no tracking.
  • Converting, trimming, joining, compressing and reading metadata from a file happens entirely on your device.
  • Data leaves your device only when you explicitly use Upload or Inspect a URL, as described below.

Android app

Files you open

The app reads only the files you pick with the system file picker or share to it. It does not request access to your photo or video library. Intermediate and output files are written to the app's private cache and are deleted automatically within 24 hours; files you save go to your Downloads folder.

Settings

Your encoder and compression preferences are stored on the device. If Android backup is enabled on your device, these preferences may be included in your Google account backup; cached media is excluded.

Upload

When you tap Upload, the file you chose is sent directly from your device to the host you selected — 0x0.st or catbox.moe. Uploads are public: anyone with the link can download the file. The host receives your IP address and the file, and its own terms and retention rules apply. Embeddy's operator does not receive a copy. For JPEG, PNG and WebP files the app can strip EXIF metadata (including GPS location) before upload; it warns you when a format cannot be stripped.

Inspect a URL

When you inspect a web address, the app requests that page directly from your device to read its Open Graph and Twitter tags. The website you inspect sees an ordinary request from your IP address.

Browser tools (embeddy.link)

The site is static and served by GitHub Pages, which, like any web host, processes your IP address to deliver the pages. Fonts and code are self-hosted; no third-party scripts, cookies or analytics are loaded. A service worker caches the site for offline use, in your browser only.

Convert, trim/join and Squoosh run locally in your browser; files are never uploaded. Inspecting a local file also runs locally.

Inspect a URL and Upload cannot be done directly from a browser because of cross-origin restrictions, so they go through Embeddy's relay at api.embeddy.link, a Cloudflare Worker. The relay fetches the page you asked about, or forwards your file to the host you chose, and returns the result. It does not store files or page contents. Metadata stripping for uploads (JPEG, PNG, WebP) happens in your browser before the file is sent, and the upload is cancelled if stripping fails. Cloudflare keeps short-lived request logs (time, path, status and similar request metadata) for operating and debugging the relay; these are not used for any other purpose.

Children

Embeddy is a general-purpose tool and is not directed at children.

Changes and contact

Changes to this policy are published on this page and in the source repository. Questions: open an issue on GitHub.