Who I am
Hi, I'm Daniel Jurma. Dripp is a side project that turned into a full project — an AI photo editor for fit pics. I designed it, I wrote it, and I'm the person reading the support email when you write in. I run it as a registered Romanian sole proprietorship, Daniel Jurma PFA, which is the data controller for your information. Throughout this policy, “I”, “me”, and “Dripp” all mean the same thing.
If you ever want to reach me about your data, write to privacy@trydripp.com. That inbox goes to me directly and I try to answer within a few working days.
What this covers
This policy applies to:
- The Dripp iOS app on the App Store, and every feature you can reach inside it.
- This website at trydripp.com.
- Any email you send me at
hello@trydripp.comorprivacy@trydripp.com.
It doesn't cover third-party sites Dripp links to, or apps you open from inside Dripp (Instagram, TikTok, etc.). Those have their own privacy policies — read them.
What I collect
Account
- Your email address (for account recovery and receipts).
- A Sign in with Apple identifier — an opaque token Apple gives me. It's not your Apple ID.
- Your display name (the name you type during onboarding), an optional username, and an optional profile photo if you upload one.
- Anonymous accounts. If you start without signing up, the app creates an anonymous account: a random user id with no email, so your edits and daily AI quota work. If you later sign up, that account becomes your regular account.
Onboarding answers
- The answers you pick during onboarding: age range, style vibes, goals, the platforms you post to, how often you post, which photo apps you've tried, and similar preferences. They tune your edits. They're saved to your account once you sign in.
Photos & edits
- The photos you send for an AI edit. They're processed in memory for that request and not stored.
- The looks, tools and presets you pick.
- The edits Dripp produces, kept for up to 7 days so the app can fetch them.
- Saved edits — when you save an edit to your Dripp library, the image and its edit steps are stored with your account until you delete them or your account.
Notifications
- If you allow notifications, your device's push token (from Apple's push service), stored with your account so I can send the notifications you turned on — for example when an edit is ready or before a free trial ends.
Subscription
- A RevenueCat customer id — a pseudonymous string that lets me check whether you have Dripp Pro.
- Trial status, current entitlement, and renewal state.
- Not your card number or payment details. Apple holds all of that.
Device & diagnostics
- Device model, iOS version, app version, locale.
- A random per-install identifier (not a cross-app tracker).
- Crash stack traces (PII scrubbed before they're sent).
Analytics events
- Event names like
paywall_viewedand an anonymous distinct id. - I do not send your prompt text, photo bytes, or email to analytics.
Install attribution (app)
- When you install Dripp from one of my links or ads, AppsFlyer reports the install so I know which campaign worked: install and app-open events, the link you came from, device and app metadata, and your IP address.
- Dripp does not show the App Tracking Transparency prompt and never reads your device's advertising identifier (IDFA). Ad networks only get Apple's aggregated, anonymised SKAdNetwork reports.
Website
- Like any website, trydripp.com receives your IP address and browser details when it serves a page.
- If you accept analytics in the cookie banner: page views and clicks, sent to PostHog (EU) and Vercel Analytics.
- If you accept marketing in the cookie banner: the Meta Pixel, Google tag (Google Analytics / Google Ads) and TikTok Pixel load. They set their own cookies and send page views and clicks to Meta, Google and TikTok, which those companies can link to your accounts with them. Nothing loads before you opt in.
Approximate location
- Country level, derived from your IP. Used for App Store pricing and to apply the right privacy rules (GDPR, CCPA, etc.).
- I never ask iOS for precise location.
How I use it
- Run the service — sign you in, render the editor, sync your settings.
- Run AI edits — route your photo and prompt to the AI provider, return the result. See section 05.
- Run your subscription — unlock Pro features for people who have Dripp Pro.
- Prevent abuse — the AI providers' content-safety filters, Apple App Attest checks, and rate limits on obvious bots.
- Notifications — the push notifications you turned on in the app.
- Transactional email — receipts, security alerts, material updates to this policy.
- Marketing attribution — learn which campaigns bring installs (AppsFlyer in the app; ad pixels on the website, only with your consent).
- Aggregate analytics — see which screens convert and what to build next. Aggregate, not per-person.
- Legal obligations — respond to lawful requests, keep the records tax authorities can ask for.
For users in the EEA, UK, and Switzerland, the legal bases under GDPR / UK GDPR are:
- Running the service & edits
- Contract (Art. 6(1)(b)) — providing the app is the service you signed up for.
- Subscription
- Contract + legal obligation (tax records).
- Abuse prevention & security
- Legitimate interests (Art. 6(1)(f)) — keeping abuse, fraud and harmful content off the service.
- Transactional email
- Contract — receipts and account messages.
- Notifications
- Consent (Art. 6(1)(a)) — the iOS notification permission. Turn it off any time in iOS Settings.
- Aggregate analytics
- Website: consent (Art. 6(1)(a)), given in the cookie banner. App: legitimate interests (Art. 6(1)(f)) — you can object by emailing privacy@trydripp.com.
- Install attribution (app)
- Legitimate interests (Art. 6(1)(f)) — measuring which campaigns work, without IDFA or cross-app tracking.
- Website ad pixels
- Consent (Art. 6(1)(a)), given in the cookie banner. Withdraw it any time from “Cookie settings” in the footer.
- Legal obligations
- Legal obligation (Art. 6(1)(c)).
Photos and AI
Dripp uses third-party AI models to analyze your photo and produce edits. Per Apple's App Review Guidelines, I have to tell you who they are:
- Every AI call (photo analysis and image generation) goes through OpenRouter (OpenRouter, Inc.), a routing service that receives your photo and prompt and forwards them to the model provider. Depending on the task, that's a Google Gemini model or an OpenAI image model. OpenRouter's own policy is at openrouter.ai/privacy.
- All AI calls are server-to-server. Your phone never talks to OpenRouter, Google, or OpenAI directly — it talks to my backend, which forwards the call. The vendor API keys never reach the device.
- I send only the photo and the prompt — no email, no account id, no identifier. The vendor sees a stateless inference call.
- Every request tells OpenRouter to deny data collection, so it only goes to providers that don't store or train on your data. Google model requests go only to zero-data-retention endpoints.
- OpenAI's image model has no zero-data-retention route on OpenRouter, so for those requests OpenAI's own API data policy applies.
Your photos are never used to train any AI model — mine or anyone else's.
Retention. The photo you send is processed in memory for the request and not stored on my servers. Edit results sit in private Supabase Storage for at most 7 days; a daily job deletes older ones. Edits you save to your Dripp library stay until you delete them or your account. If you save an edit to your camera roll, that copy is on your device, not mine.
Who touches your data
These are the third parties (“sub-processors”) that process data on my behalf:
| Vendor | Purpose | Data | Jurisdiction |
|---|---|---|---|
| Supabase | Database, auth, file storage | Account data, content metadata | EU (Frankfurt) |
| RevenueCat | Subscription entitlements | Pseudonymous customer id, entitlement flags | United States |
| PostHog | Product analytics | Event names, pseudonymous user id, device and app metadata | EU Cloud (Frankfurt) |
| Sentry | Crash and error reporting | Stack traces, device + OS metadata; PII scrubbed | EU region |
| Vercel Analytics | Aggregate, cookieless website page-view counts | Coarse device/region from request headers; no cookies, no cross-site identifiers | United States (Vercel) |
| AppsFlyer | Install attribution (SKAdNetwork mode, no IDFA, no ATT prompt) | Install and app-open events, link click data, device and app metadata, IP address, SKAdNetwork postbacks | EU region |
| OpenRouter | Routes every AI call (photo analysis, image generation) to the model provider | Photo + prompt, forwarded to the provider; data collection set to deny | United States |
| Google Gemini (via OpenRouter) | AI photo analysis and image generation | Photo + prompt for the duration of the call; zero-data-retention endpoints only | Per OpenRouter routing; not limited to the EU |
| OpenAI (via OpenRouter) | AI image generation | Photo + prompt; OpenAI’s API data policy applies (no zero-data-retention route) | United States |
| Supabase Storage | Edit results (deleted within 7 days), saved edits, profile photos | Images in per-user folders; private buckets except profile photos | EU (Frankfurt); retention per section 12 |
| Vercel | Website hosting | IP address and request logs | United States (Vercel Inc.); global edge network |
| Meta Pixel (website, with marketing consent) | Ad attribution for Facebook and Instagram | Page views, clicks, _fbp cookie, IP address, browser details | EU (Meta Platforms Ireland) and United States |
| Google tag (website, with marketing consent) | Google Analytics and Google Ads conversion measurement | Page views, clicks, _ga cookies, IP address, browser details | EU (Google Ireland) and United States |
| TikTok Pixel (website, with marketing consent) | Ad attribution for TikTok | Page views, clicks, _ttp cookie, IP address, browser details | EU (TikTok Technology Ltd, Ireland), United States and other TikTok locations |
| Apple | App Store distribution, Sign in with Apple, App Attest, push notifications (APNs) | Per Apple’s policy | Per Apple’s policy |
When this list changes, I update this section and bump the effective date at the top.
Your rights
Depending on where you live, you have some or all of these rights over your data:
- Access — get a copy of what I hold about you.
- Correction — fix anything that's wrong.
- Deletion — tell me to delete your account and data.
- Restriction — pause processing while a dispute is sorted out.
- Portability — get your data in a machine-readable format.
- Objection — object to processing based on legitimate interests.
- Withdraw consent — for anything based on consent (website analytics and ad pixels, notifications).
- Complain — to your local data protection authority.
- Non-discrimination (CCPA) — exercising these rights never costs you anything.
Fastest path: open Dripp and tap Settings → Delete account. That deletes your account, your saved edits, your edit results and your profile photo right away.
Formal path: the DSAR page walks you through filing an access, export, or deletion request. Statutory response window is 30 days; deletions usually go through in seconds.
Children
You must be 18 or older to use Dripp. You may not create an account, upload photos, or buy a subscription if you're under 18, and you may not upload photos of anyone under 18.
If you believe a minor has used Dripp, email privacy@trydripp.com with whatever you can share. I purge the account and content within 7 days of a credible report.
International transfers
Dripp's primary processing region is the EU. Database, storage, analytics, and error tracking all run in EU regions.
For the vendors outside the EEA — RevenueCat in the US, AI calls, which go through OpenRouter in the US to Google or OpenAI and may be processed outside the EU, Vercel for website hosting, and, if you opt in on the website, Meta, Google and TikTok — I rely on the EU Standard Contractual Clauses, the UK International Data Transfer Addendum where applicable, plus encryption in transit and at rest and keeping what crosses the border to a minimum.
Security
- In transit: TLS between your phone, my backend, and every sub-processor.
- At rest: AES-256 on storage and database.
- App Attest: calls to my AI backend carry an Apple App Attest assertion. Calls without one are rejected.
- Private storage: edit results and saved edits sit in private buckets; the app gets them through signed links that expire within 15 minutes. Profile photos are the exception: they sit in a public bucket so your avatar can be shown.
- Row Level Security: you can only read and write rows tied to your own account.
- Logging: I never log raw photo bytes, prompt text, emails, or tokens.
Retention
- Photos you send for an AI edit: processed in memory, not stored.
- Edit results: ≤ 7 days, then auto-deleted.
- Saved edits: kept until you delete them, or until you delete your account.
- Account data (email, display name, username, profile photo, onboarding answers): kept until you delete your account.
- Anonymous accounts: deleted after 30 days if you never sign up, unless the account has saved edits or a purchase.
- Push tokens: kept until you delete your account or the token stops working.
- Billing records: retained as long as applicable tax law requires (typically several years). I can't shorten this even on request.
- Analytics events: 12 months, then aggregated into anonymous summaries.
- Crash diagnostics: 90 days, then purged.
Changes to this policy
I'll update this page from time to time as Dripp grows or as laws change. Whenever I do:
- I bump the effective date at the top of the page.
- For material changes (new data category, new sub-processor, change to your rights), I'll show an in-app banner next time you open Dripp and email you at your account address.
- Older versions live in git. Ask privacy@trydripp.com if you need an earlier snapshot.
Contact
For anything privacy-related — questions, requests, complaints — email privacy@trydripp.com. If you'd rather use the formal data-subject request form, go to /dsar. For general support or billing, see /contact.
- Operator
- Daniel Jurma (individual developer)
- Privacy email
- privacy@trydripp.com
- Supervisory authority
- You can complain to your local data protection authority — for EU users, the authority of your country of residence.