Privacy Policy for Snip

Last updated: June 30, 2026
Effective date: June 30, 2026

I'm Ilya Razuvaev, an independent developer, and this is how the Snip app handles your data. Snip is one app that ships on both macOS and iOS, and this policy covers both. There is no login and no email or name to give. Read this together with the Terms of Use.

1. How It Works on Each Platform

The two platforms process your images differently, so it's worth being clear up front:

• On macOS: everything Snip does to your pictures — background removal, object erase, upscaling/enhancement, screen capture, and text recognition (OCR) — runs locally on your Mac using Apple's on-device frameworks (CoreML and Vision). Your images, screenshots, and recognized text never leave the device. There are no accounts.
• On iOS: OCR/text recognition runs on-device (Apple Vision), but the cloud editing tools — background removal, enhance/upscale, and object erase — upload your image to my servers over HTTPS for processing and send the result back. Uploaded images are transient: they are used to produce your result and are not stored afterward. To run the free-tier credit system, iOS also creates an anonymous account (no email, no name).

Throughout this policy I use short On macOS / On iOS callouts where the platforms differ. Because of this difference, I can't say "your images never leave your device" as a blanket statement — that's true on macOS, but on iOS the cloud tools upload the image (transiently), while OCR stays on-device.

Two kinds of data leave the device on both platforms: the purchase data needed to manage in-app purchases (Section 5), and product analytics (Section 6). Neither is tied to your name or email, and neither ever includes your images, screenshots, or recognized text.

2. Who I Am (Data Controller)

For the GDPR and similar laws, the controller is Ilya Razuvaev, an independent developer (no company). Contact: snipfeedback@gmail.com. Questions about your data go to that email.

3. What I Collect

• Image content (iOS cloud tools only) — when you use background removal, enhance/upscale, or object erase on iOS, your image is uploaded for processing and then discarded (Section 4). On macOS, no image leaves your device.
• Anonymous account & credit data (iOS only) — an anonymous user ID and the credit/usage records that run the free tier (Section 4).
• Purchase and subscription data — only if you buy something, handled through Apple and the subscription service Apphud (Section 5).
• Usage analytics — which features you use, diagnostic/error events, app version, OS version, device model, and a device-scoped identifier (Section 6).

I do not collect your name, email, login data, precise location, contacts, or microphone input. I do not collect an advertising identifier (IDFA), I do not run App Tracking Transparency prompts, and I do not do cross-app or cross-site tracking. I do not sell or "share" your personal information, I do not use data brokers, and I do not use your content to train any models.

4. Image Processing and the iOS Account

On macOS: all image processing is on-device. I receive nothing — no images, no screenshots, no recognized text, and no account data.

On iOS, cloud tools: when you run background removal, enhance/upscale, or object erase, the app sends your image to my servers over HTTPS as a compressed JPEG, downscaled to roughly 2048px on its longest side. The image is processed and the result is returned to your device. Object erase (inpainting), and any image generation, additionally use the cloud AI provider Replicate with your image and the erase mask. Background removal and enhancement run on my image-processing backend (the "Leximera" service at api.leximera.com), reached through my Supabase Edge Functions.

• Uploaded images are transient and not stored after processing. Only non-image metadata is logged for the credit/usage system: image size and type, which tool was used, processing time, a timestamp, and the status. OCR runs on-device and is not uploaded.

On iOS, the anonymous account: to run the free tier there's no login, no email, no name. The app creates an anonymous account identified by a device-scoped identifier (Apple's Identifier for Vendor, IDFV) and a server-generated anonymous user ID (a random UUID). The free tier gives a small daily credit allowance (about 3 per day); subscribers and Lifetime owners are unlimited.

• Stored on my servers (Supabase): the anonymous user ID, premium status and expiry, daily/total credit usage, and per-action usage history (which tool, time, status).
• Not stored: your email, phone, name, or your images.
• Stored locally on your device: the authentication tokens for this anonymous account, in the iOS Keychain.

On macOS there are no accounts; the free-tier limit is a simple local counter on your Mac (see Section 7).

Legal basis (GDPR). Processing your image in a cloud tool, and running the anonymous account and credit system that let you use it, is performance of a contract with you (Art. 6(1)(b)) — it's the service you asked for. Managing purchases is likewise contract performance and legal obligation (Art. 6(1)(c)) for tax/records. The analytics in Section 6 rely on legitimate interests (Art. 6(1)(f)).

5. Purchases (Apple and Apphud)

If you buy a subscription (Monthly or Annual) or the one-time "Lifetime" purchase, Apple processes the transaction through the App Store. To manage purchases, validate receipts, restore them, and apply the right entitlement (free vs. paid), Snip uses Apphud, Inc. for subscription management on both platforms.

Apphud receives a device-scoped identifier (Apple's IDFV — not a hardware serial or advertising ID) and purchase details from Apple (which product, transaction/receipt info, subscription status, renewal/expiration, trial status, storefront). Apphud does not receive any of your images, screenshots, or recognized text.

Apple handles your payment, billing, and App Store account as an independent controller under Apple's own privacy policy.

6. Analytics

Snip's analytics is on for everyone and helps me see how features are used and keep the app stable. It describes how the app is used, not what you process with it: your images, screenshots, and recognized text are never included.

• On both platforms — Amplitude, Inc. (US): product analytics — usage events (which tools and features you use, sessions, feature flows), diagnostic and error events, app version, OS version, device model, and a device-scoped identifier (IDFV / an app-instance ID) used to count distinct devices and group events from the same device.
• On macOS — Google Firebase Analytics (Google LLC, US): the macOS app includes the Firebase Analytics SDK as a secondary analytics destination. When Firebase is active it receives usage analytics of the same kind as above and typically also your IP address (which Google may receive in transit). Firebase is not active on iOS.

The device-scoped identifier is not your name or email, is not an advertising ID, and is not linked to your identity. There is no IDFA, no App Tracking Transparency prompt, no cross-app tracking, no data brokers, and no advertising use. There is no crash-reporting SDK and no push notifications.

Legal basis (GDPR). I rely on my legitimate interests under Art. 6(1)(f) — improving and stabilizing the app — which I consider proportionate because the data is device-scoped, contains no image content, and is not used for advertising or profiling.

Your choices. There is currently no in-app toggle to turn analytics off. You can email me at snipfeedback@gmail.com to ask about your options.

7. Data Stored Only on Your Device

These stay on your device:

• Free-usage counter. On macOS, the daily free-tier limit, in the macOS Keychain. (On iOS, the equivalent count lives in your anonymous server account — Section 4 — while the account's auth tokens are in the iOS Keychain.)
• History of recent edits and results, in your local app data folder.
• Preferences and settings, in UserDefaults.

Delete the app (and its data) or clear history in the app to remove this.

8. Recipients, Processors, and International Transfers

Apple separately handles payment, billing, and your App Store account as an independent controller. For the iOS cloud features, my servers and the processors above receive your IP address in transit (normal for any network request); I don't use it to identify you by name.

International transfers. Some providers may process data in the United States. Amplitude certifies under the EU–U.S. Data Privacy Framework (with the UK Extension and the Swiss–U.S. DPF) and uses the EU Standard Contractual Clauses (SCCs) as a fallback, and offers EU data residency. Google (Firebase) likewise relies on the DPF and/or SCCs. Apphud and Apple rely on SCCs or other lawful transfer mechanisms. Email me for more detail.

9. Data Retention

• Uploaded images (iOS cloud tools): not retained — used to produce your result, then discarded, not stored on my servers.
• Images, screenshots, recognized text on macOS, and OCR text everywhere: never received by me, so never retained by me. Local copies stay on your device until you delete them.
• Anonymous account & credit/usage logs (iOS): the anonymous user ID, premium status, and credit/usage history are kept on my servers (Supabase) to run and protect the free tier, then deleted or anonymized when no longer needed.
• On-device data (counter, history, preferences): until you delete it or uninstall.
• Purchase data: kept by Apple and Apphud as needed to manage your subscription and meet legal/tax obligations.
• Analytics: kept by Amplitude and Google under their own retention limits, then deleted or anonymized.

10. Permissions

On iOS, Snip asks for:

• Camera — to capture photos for you to edit.
• Photo Library (read) — to read photos you choose to import.
• Photo Library (add) — to save edited photos back to your library.

It does not ask for tracking, microphone, or location. Camera and photo-library access are mediated by iOS — you grant or revoke them in iOS Settings.

On macOS, Snip uses the built-in system screen-capture tool and asks for no such permissions.

11. Your Rights

GDPR / UK GDPR. You can request access, rectification, erasure, restriction, objection (including to the analytics covered by Section 6), and data portability, and you can lodge a complaint with your local data protection authority (supervisory authority). Email snipfeedback@gmail.com. Because there's no login and the analytics is not tied to your identity, I may be unable to locate your specific data without more information from you — on iOS, the anonymous user ID or IDFV can help me find your credit/account records. Some requests may need to go to Apple, Apphud, Amplitude, Google, Supabase, or Replicate — I'll help where I can.

California (CCPA/CPRA) and other US states. I do not sell or "share" personal information and have not done so in the past 12 months; analytics is first-party and not used for advertising. Categories that may be collected: identifiers (device-scoped ID, anonymous user ID), commercial information (purchase records), and internet/network activity (usage and diagnostic events). On iOS, the visual content of an image you submit to a cloud tool is transiently processed to produce your result and is not stored, sold, or shared. You have the right to know, delete, correct, and to be free from discrimination for exercising these rights. Contact snipfeedback@gmail.com. Because I don't sell, share, profile, or do targeted advertising, the related opt-outs under state laws don't apply to my processing.

12. Security

On macOS, your images never leave your Mac, so the main protection for them is the security of your own device. On iOS, images sent to the cloud tools travel over HTTPS (encrypted in transit) and are discarded after processing rather than stored; the anonymous account's auth tokens are held in the iOS Keychain. For purchase data I rely on Apple's and Apphud's safeguards. No system is perfectly secure, but Snip's design — on-device on macOS, and transient, no-name uploads on iOS — keeps the data exposed to a minimum.

13. Children

Snip is for general audiences and is not directed to children under 13 (or the higher digital-consent age in your country). I do not knowingly collect data from children under 13. If you believe a child has provided data, email snipfeedback@gmail.com and I'll delete it.

14. Changes

I may update this policy. The current version lives at https://sniperaser.com/privacy/ with an updated "Last updated" date. For material changes I'll take reasonable steps to notify you and, where required, get your consent first.

15. Contact

snipfeedback@gmail.com — I'll respond within the timeframes required by law.