Last updated October 2026

Privacy policy

The short version: we don't keep your photos, we don't track you to advertisers, we don't run any ML on what you upload. The long version follows.

The short version: your images are deleted within an hour. No account, no profile, no photo gallery. We use exactly enough cloud services to make the editor work.

1. What we collect

When you use the editor we touch four classes of data:

  • The images you upload.Stored on Amazon S3 in a private bucket for up to one hour, then auto-deleted by the bucket's lifecycle policy.
  • The detection regions and blur settings. Held in your browser, sent to the API only as part of a single export request, never persisted server-side.
  • Standard request metadata — IP address, user agent, request path — held in CloudWatch and WAF logs for up to 24 hours, used only for abuse prevention.
  • Usage counters. To enforce the free allowance of 5 images per 30 days per computer we keep small counters: a random id in a first-party cookie; a hash computed in your browser from its technical characteristics (via an open-source library); a hash of your operating system, screen size, time zone and touch support; a keyed hash of your IP address; and hashes of these combined. The counters expire after 31 days and are never linked to a name.

We do not currently use any analytics product on the editor page. The marketing pages may use a privacy-respecting analytics tool (Plausible or similar) that does not set cookies or track individuals.

2. What we don't collect

  • Names or account profiles — there are no accounts.
  • Your email, unless you buy credits; then we keep it for support and refunds (see section 5).
  • Cross-site browsing data or ad-targeting cookies.
  • Anything about the content of your images beyond the seconds needed to process them.

3. How long we keep things

  • Uploaded images: ≤ 1 hour, then deleted by S3 lifecycle policy.
  • Exported images: ≤ 1 hour, same mechanism.
  • Request logs (CloudWatch / WAF): 24 hours.
  • Detection regions: never persisted server-side. They live in your browser tab only.
  • Usage counters: 31 days, rolling.
  • Purchase records: kept for as long as we need them to restore your credits and handle refunds; deleted on request.

4. Who we share data with

To do its job, the editor sends each uploaded image to one or more vision-API providers for detection. We currently use:

  • Amazon Web Services (S3, Rekognition, Lambda, CloudFront, WAF) — for storage, face detection, and infrastructure.
  • Google Cloud Vision API — for license plate detection (Object Localization) and document text OCR.
  • Stripe — payment processing when you buy credits or leave a tip. Stripe.js loads only when the payment dialog opens; card details go to Stripe and never reach us.

AWS and Google have data-usage terms that prohibit retaining your image content for training purposes. We do not share data with advertising networks, data brokers, or analytics SDKs.

5. Payments

Credits are bought through Stripe Checkout and charged by Devware Solutions, the company that runs Blurify. Stripe collects your card details and email; we never see the card. We store your email, the amount, the pack and Stripe's customer and payment ids for as long as we need them to restore your credits and process refunds, and delete them on request. Credits are tied to the random id in your cookie. The email you paid with is kept with your credit balance so Blurify can show it to you in the editor and restore the credits on another device with a code sent to that address.

6. Cookies

The editor sets one first-party cookie, bf_id, holding a random identifier for the usage counters and your credits. It lasts 400 days, is not readable by scripts, is sent to Stripe as the purchase reference when you buy credits, and is shared with nobody else. Browser-side preferences (color scheme) and a copy of that identifier, for browsers that block cookies, live in localStorage.

7. Your rights

Because we hold essentially no data about individuals, most data-subject rights are automatic — your data is already gone within an hour. If you uploaded something and want it deleted before the auto-expiry, use the contact form on the About page; we can purge a specific S3 prefix if you can give us the rough timestamp. If you want your purchase record deleted once your credits are used up, ask via the same form.

EU/UK residents: under GDPR, Devware Solutions (Tuscaloosa, Alabama, USA) acts as the data controller for the limited request metadata noted above, and a processor for the image bytes during the brief window we hold them. Our retention windows are below most regulatory thresholds because we actively delete.

8. Security

  • HTTPS everywhere; HSTS preload.
  • S3 buckets have Public Access fully blocked. The only read paths are short-lived (~15 min) presigned URLs.
  • SSE-S3 server-side encryption on all stored objects.
  • API requires an HMAC-signed request from the BFF; direct browser calls are 403'd.
  • AWS WAF in front for rate-limiting and bot defense.

9. Changes

If we change this policy in a way that meaningfully affects users, the change will be announced on the home page and the "Last updated" date above will reflect it. We won't retroactively make our retention windows worse.

10. Contact

Blurify is operated by Devware Solutions, Tuscaloosa, Alabama, USA. Privacy questions can be sent to support@blurify.ai or via the contact form on the About page.