Privacy policy
Pre-launch draft. The operator identity, processor arrangements and purchase terms must be finalized before public launch. AI processing is disabled by default.
Your photo and selection
Choosing a file and drawing a selection happen locally in your browser. The editor converts the photo to PNG before upload, removing the original EXIF metadata through canvas re-encoding. Transparent areas are flattened onto white. Only start cleanup with an image you have permission to process.
When you start AI cleanup
When enabled, EraseSnap sends your prepared photo and mask to the Clipdrop Cleanup API to generate the edited photo. Files are stored in a private Cloudflare R2 bucket. Download and result routes require a browser-specific HttpOnly cookie; knowing an edit ID alone does not grant access.
EraseSnap does not implement a photo-training pipeline. This statement does not establish how a third-party processor retains or uses submitted images. Processor retention, training use and international processing terms must be confirmed before AI processing is enabled. See Clipdrop API documentation and Jasper privacy information.
Expiry and deletion
Access to an edit expires 24 hours after creation. A protected cleanup endpoint deletes original, mask and output files in batches. The deployment scheduler must be configured and verified before public launch. Physical deletion can occur after expiry because of scheduling, backlog or failures; unsuccessful deletions are retried. A private-bucket lifecycle rule is also required before launch as a backup. Job metadata is removed seven days after expiry once file deletion has succeeded.
Security and usage data
We store task state, timestamps, provider usage and a pseudonymous browser identifier. A daily rotating keyed hash of your connection IP is used for rate limits; raw IP addresses are not stored in the cleanup job table. Cloudflare may process connection data to provide hosting and abuse prevention. Turnstile verification is required before uploading. Read Cloudflare Turnstile privacy information.
Accounts, payments and support
Google or email-code sign-in uses the existing account system. Account records can include your name, email and profile image. Stripe processes payments when purchase functionality is enabled. The photo cleanup trial does not deduct account credits. Contact form submissions are handled by the existing support integration and can include your email, message and connection information. Do not include private photos or sensitive information in support messages.
Analytics
Google Analytics is disabled unless an EraseSnap measurement ID is configured. Cleanup events contain action names and tool identifiers; the new editor does not send image contents, filenames or selection coordinates to analytics. Applicable consent behavior must be configured before enabling analytics. Read Google privacy information.
Questions and data requests
Use the contact form for privacy questions, deletion requests or abuse reports. Include an edit ID where relevant, but never share the browser cookie that protects access. The operator must verify the support destination and complete the identity and jurisdiction disclosures before launch.