Privacy Policy
Last updated: May 8, 2026
1. Overview
Redact.ID is a privacy tool that helps you blur faces, remove tattoos, and strip metadata from photos. We designed it to handle your images with as little data exposure as possible. This policy explains exactly what happens to your data at each step.
2. In-Browser Processing
The following operations run entirely in your browser and never send your image to any server:
- Face detection and blurring
- Metadata extraction and stripping (EXIF, GPS, timestamps)
- Mask editing and adjustments
- Image export and format conversion
These features use on-device machine learning models that run locally in your browser. Your original image stays on your device throughout.
3. Server Processing
Tattoo removal requires AI processing that cannot yet run in-browser. When you use this feature, your image and the mask you draw are sent to our processing server, where an AI model fills in the area you marked and returns the edited image to your browser.
We use these images solely to generate and return your result. We do not sell them, share them with third parties, or use them to train AI models.
4. Local Storage
To let you resume interrupted work, Redact.ID stores a temporary copy of your in-progress session (your image, any mask edits and blur settings, and the face-detection coordinates used to draw those edits) in your browser's local storage (IndexedDB). This data:
- Never leaves your device
- Is automatically discarded after 4 hours
- Can be cleared at any time by clearing your browser storage
5. Analytics
We collect pseudonymous usage events to understand how the app is used and improve it. Each browser session is assigned a random session identifier; events are tied to that identifier and not to you personally. We do not set advertising cookies or build cross-site profiles. Collected data includes:
- Event names (e.g., image_uploaded, apply_clicked)
- Device class (mobile vs. desktop), screen size, browser
- The page you came from (HTTP Referer)
- Your IP address: transient, used only for rate-limiting and abuse prevention; not stored alongside long-term analytics
Analytics never include your images, image content, EXIF data, or anything you draw or paint. We don't share or sell this data.
6. Cookies and Tracking
Redact.ID itself does not set tracking cookies on redactid.app. State on your device is stored in localStorage (theme, resolution preferences, your promo code if redeemed) and IndexedDB (the temporary in-progress session). No advertising pixels run on the main app.
Some embedded third-party services may use their own cookies or storage on their own domains: the AppLixir rewarded-video ad player when you watch an ad, and Stripe Checkout if/when paid subscriptions launch. We don't control these and they're governed by their own privacy policies (see Section 7).
7. Third-Party Services
Redact.ID uses the following third-party services:
- Netlify: hosts the web application and serverless functions; access logs include IP addresses. Netlify's Privacy Policy.
- Cloudflare: provides the secure tunnel between your browser and our tattoo-removal processing server. Cloudflare's Privacy Policy.
- Supabase: database that stores pseudonymous analytics events, promo-code redemption counts, email-based subscription state, and feedback you submit. Supabase's Privacy Policy.
- Sentry: crash and error reporting. Crash events include browser metadata and stack traces but are not tied to your identity unless you submit feedback that includes personal info. Sentry's Privacy Policy.
- AppLixir: rewarded-video ad provider. When you watch a rewarded ad to earn an extra tattoo-removal credit, AppLixir loads in an embedded player and may collect device and ad-interaction data. AppLixir's Privacy Policy.
- Stripe: payment processor for subscriptions. Currently dormant; activates only if you start a checkout. When active, Stripe collects payment and billing details directly. We never see your card number. Stripe's Privacy Policy.
8. Children's Privacy
Redact.ID is not directed at children under the age of 18. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us through the in-app feedback page and we will take steps to remove it.
9. Data Retention
We retain as little data as possible:
- Images: Never stored on our servers. Processed in memory only and discarded immediately after the result is returned.
- Session data on your device: Stored in IndexedDB for up to 4 hours, then automatically discarded.
- Email and subscription state: Retained while your account is active. Deleted when you delete your account (see Section 10).
- Promo codes: Stored on your device in localStorage until you sign out. The code itself is shared and can be redeemed elsewhere; we keep a redemption counter on the server to know how widely it's been used.
- Analytics events: Pseudonymous events keyed by session ID, retained indefinitely for product improvement. Not tied to you personally.
- Feedback: Messages you submit are retained for product improvement. If you included contact info that matched your account email, that contact field is anonymized when you delete your account (the message body stays).
- Crash reports: Sentry retains crash events according to its own retention policy (typically 30–90 days).
10. Your Rights and Account Deletion
You can delete your account and the data we hold about you at any time. The data deleted includes:
- Your email and subscription record (if any)
- Any active Stripe subscription, which we cancel via the Stripe API
- Promo-redemption rows associated with your email
- The contact field on any feedback you submitted (the message body is retained anonymously for product improvement)
- Local credentials on your current device (email, promo code, credits)
To delete from inside the app: open Redact.ID, go to Account, and tap Delete account. Confirmation is required; the deletion is immediate and cannot be undone.
To delete by email (e.g., if you have already uninstalled the app): write to drice233@gmail.com from the email address associated with your account. We'll process the request within 30 days.
You can also request a copy of the data we hold about you, or ask us to correct inaccurate data, by emailing the same address.
Pseudonymous analytics events that aren't tied to your identity are not deleted (they cannot be linked back to you, so there's nothing to delete). Anonymized feedback message content remains in our improvement records.
11. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date above. Material changes will be communicated through an in-app notice.
12. Contact
Questions about this Privacy Policy, or requests under Section 10: drice233@gmail.com.