Privacy
Privacy policy
DepthField Photo is a photo editor that runs on your Mac, and your work stays there. This page explains, part by part, what the app, DepthField Cloud and this website collect, why, who else handles it, how long it's kept, and how to have it changed or deleted. It's the long form of the data pledge.
Last updated · Questions: hello@depthfield.photo
The short version
- Your work stays on your Mac. Photos, layers, prompts and file names leave it only when you use a cloud AI feature, and then only for the AI service doing that job.
- Nothing is sold. No advertisers, no data brokers, no ad targeting.
- Usage statistics are off unless you turn them on, and they never include your work or who you are.
- This website counts visits without cookies, and can't follow you from one day to the next.
- A few automatic requests keep the app working: an update check, the AI price list, a one-time download of the on-device AI models, a status check when a cloud AI request fails, and a daily license check on licensed copies. Each one is spelled out below.
- Offline works forever. None of this is needed to edit.
- Ask me what I hold about you, or to delete it: hello@depthfield.photo.
Who's responsible
DepthField Photo, DepthField Cloud and this website are made and run by Jens Roland. The controller of your personal data, in the terms of the EU's General Data Protection Regulation (GDPR), is:
- Controller
- Jens Roland Johansen (Enskild näringsverksamhet, a Swedish sole proprietorship)
- Address
- Ängsliden 11, 641 50 Katrineholm, Sweden
- hello@depthfield.photo
There's no privacy department to get lost in: email that address and it reaches me.
The app on your Mac
Editing happens on your Mac. Your photos, layers, masks, documents, prompts and file names are stored and processed there, and so is everything the on-device AI does: depth, selecting subjects and objects, recognizing what's in a picture, and more. I never receive any of it.
The app also keeps a few things for itself on your Mac: your settings, any API keys you add, your DepthField Cloud sign-in, a random install ID (licensed copies only), and a log of its recent actions that helps diagnose crashes.
What the app sends on its own
Apart from the features you use, the app goes online by itself only for the following. None of it includes your work, none of it is needed to edit, and offline it's simply skipped.
- Update check
- At most once a day. It sends the version of DepthField Photo and of macOS you're running, whether your copy is licensed or in the free trial, and whether this is your copy's first check ever, this week or this month — that last part is how new and active copies are counted without an ID. Nothing else: no ID, no account. The server also notes which country the request came from, never your IP address. I keep only a count per day of each combination. The check goes to DepthField Cloud, then to depthfield.photo for the update's details; an update itself downloads from GitHub.
- License check
-
Licensed copies only, at most once a day. It sends exactly five things: the
product (
photo), your license's purchase ID, a random install ID the app creates once and keeps (not derived from your Mac's hardware), the app version, and the platform name your Mac reports (such asMacIntel). It tells me which versions licenses run and how many installs each has. Nothing in the app depends on it: it never blocks, limits or verifies anything. Because the purchase ID belongs to your license, this check is linked to the email address your license was issued to. - AI price list
- At launch, so the prices the app shows are current. Nothing about the request is recorded.
- Service status
- Only when a cloud AI request fails: the app reads depthfield.photo/status so the error can say whether the AI provider is having problems. It sends nothing about you or your edit.
- On-device AI models
- Downloaded automatically the first time the app runs, and again only when an update adds new ones. They come from DepthField's download server, with Hugging Face as a fallback.
- Fonts
- The app's own fonts are built in. A Google Font you choose for a text layer is downloaded from Google Fonts when you choose it.
Like any internet request, each of these shows your IP address to the server that answers it. DepthField Cloud uses it only to limit abuse, in memory for about an hour, and doesn't store it. The other services involved (Cloudflare, the web host, GitHub, Hugging Face and Google) see it too.
Cloud AI
Some features run on cloud AI models: generating and replacing with AI, restoring photos, the chat assistant and others. They run only when you use them, and you can hide them all with Settings → Privacy → Disable cloud AI features. There are two ways to power them.
Through DepthField Cloud
When you're signed in to DepthField Cloud, the app sends what the job needs: the picture, or the part of it being edited, and any mask, prompt, reference images and settings. DepthField Cloud passes them to the AI provider (fal.ai or Runware for pictures and video), and the app downloads the result from that provider.
The provider doesn't always run the model itself. For many models it passes the job on to the company that made the model, such as Google, OpenAI, ByteDance or Alibaba, which may process it in the US, in China or elsewhere. The model picker in the app shows who made each model.
DepthField Cloud doesn't keep your pictures or prompts. To bill you correctly it records each job in your account's usage history: the feature and model, the price, how long it took, and the provider's reference for it. If a provider refuses a job, its error message is kept too, and those sometimes quote the prompt. The working record of each job is deleted about an hour after it finishes.
What happens to your picture after that is up to them, not me. How long a provider or a model's maker keeps what it receives, and whether it uses it to improve its models, is set by their terms. Those terms differ, and nobody outside their data centers can check what really happens there. So treat a cloud AI edit as uploading the picture. If a picture mustn't leave your Mac, use the on-device features instead: they never send anything.
The chat assistant
Each message you send the assistant goes with the conversation so far, a snapshot of your picture (at most 1024 pixels on the long side) and a one-line description of the document: its name, size, the names of its layers, whether something is selected, and your current colors. That's how it sees what you see. Through DepthField Cloud it goes to Google's Gemini API with no account or user ID attached, and DepthField Cloud keeps nothing of the conversation, only the usage record (tokens and price).
With your own API keys
If you add your own key for fal.ai, Replicate, Wavespeed, Runware, Google AI Studio or OpenRouter, the app sends the same things straight from your Mac to that provider, under your own account and agreement with them. They don't pass through DepthField Cloud and I never see them. Your keys stay on your Mac and are only ever sent to the provider they belong to.
Your DepthField Cloud account
DepthField Cloud is the optional service that runs cloud AI on a prepaid balance. Signing in takes an email address and no password: Stytch, the sign-in service, emails you a link that works for an hour, and clicking it signs the app in for 30 days at a time.
For your account I keep your email address, the account ID Stytch assigns you, your balance and how much has been added to it, your usage history (see Cloud AI), and when the account was created. If you were given the beta's starting balance, your address is on the list that grants it. If you click to buy more balance while top-ups aren't open yet, I note that you did. While you're signed in, the app fetches your balance and prices when it starts.
Buying a license or balance
Licenses and balance top-ups are sold through Stripe, acting as the merchant of record: Stripe takes the payment, collects your payment details and billing information, handles tax and fraud checks, and treats that data under its own privacy policy. I never see your card details.
From Stripe I get your email address, what you bought, the amount, the payment's ID and, later, whether it was refunded. A top-up adds its amount to your DepthField Cloud balance. A license creates a license record: your email address, the purchase ID, the edition (if any) and when it was issued, plus, from the license check, the app versions and install IDs it has been used with. That record is what lets me re-send a lost license and honor upgrades. It also notes where the purchase started — which Buy button in the app (such as the second reminder screen), or a campaign link on this website — and, if you answer it, the optional “How did you hear about DepthField?” question at checkout.
Your license arrives by email (sent through Resend) as an activation link that works for 72 hours. The license itself is checked on your Mac, offline; no server is ever asked whether it's valid.
Feedback
The Feedback button in the app sends me:
- your message, and your name and email address if you give them (both optional)
- the app version and build, and your Mac's chip, memory and macOS version
- your settings, and which connections are set up, as yes or no (never the keys)
- your most recent crash or graphics-error report, if there is one: a log of what the app was doing just before, its memory use and its error messages
- up to three screenshots, if you attach them
The contact form on this website sends me only what you type into it: your message, your email address, and your name if you give it. It's handled the same way as feedback from the app.
Never your other images, prompts, file names or API keys. Feedback is stored in DepthField Cloud's database and emailed to me through Resend. Sending is rate limited by IP address, in memory; the address isn't stored. The app remembers the name and email you typed, to fill them in next time.
What happens next
- If you gave an email address, I use it to reply, and to tell you how your request is doing: when it's added to the public roadmap, when it ships, or if I decide against it. Every one of those emails has a one-click unsubscribe.
- To turn a request into a roadmap item, its text may be processed by Google's Gemini API to draft a public summary with personal details removed. Only the message goes: never your name, email address, settings, crash report or screenshots.
- Your original message, name, email address and screenshots are never published. To fix the issue I may share them with the services I work with, AI coding assistants included.
The public roadmap
Anyone can read the roadmap at depthfield.photo/roadmap. To vote or comment, you first confirm your email address with a one-time link, which works once, within 30 minutes.
- Votes are up or down, one per email address and item. Your address is stored with your vote. If you vote an item up, I use the address to send you updates about it, with a one-click unsubscribe in every email.
- Comments are published only after I've reviewed them, under the display name you choose, never your email address. I may edit one before it goes up, for example to take out personal details. An address used to abuse the roadmap can be blocked from voting and commenting.
- IP addresses are used briefly to limit abuse and are never stored with votes.
- Staying signed in uses a random token kept in your browser's local storage on depthfield.photo. No cookies, no tracking.
Usage statistics
Off unless you turn them on. The app asks once, the first time it opens, and you can change your mind any time in Settings → Privacy. Until you say yes, the analytics code isn't even loaded.
If you opt in, the app sends anonymous events to PostHog's EU cloud. They cover:
- which tools, features, styles and AI models you use, with their settings, and how long AI jobs take and what they cost
- the app version, macOS version, whether you use DepthField Cloud or your own keys, and whether your copy is licensed or in the trial, with its edition (such as First 25)
- how big the images you work on are, how many layers they have, and how long sessions last
- errors and crash reports, with where in the app's code they happened
- graphics and memory measurements
- what kind of object the app recognized when you select something, from a fixed list of about 825 words such as "dog" or "sky", and the general kind of picture, from a short fixed list
- the words you type into the search box, lowercased and at most 40 characters, and dropped entirely if they look like an email address, a file path or a file name
Never your images, layers or layer names, prompts, the text in your text layers, file names or paths, your email address or your account. Screen recording and automatic click tracking are switched off. The app strips your IP address from every event, and PostHog is set to discard it. Each installation gets a random ID, stored in the app, so its events can be told apart. It's never linked to you or your account, which also means I can't look up your statistics by name.
If the statistics ever collect something new, it's only collected from people who opted in after the change was disclosed.
This website
depthfield.photo has no ads and sets no cookies. It counts visits, without following anyone.
- Visits are counted by PostHog, in its EU cloud: which pages get read, the site or campaign link that led there, and clicks on a download link (and which button it was). PostHog tells visits apart by a code it makes from your IP address and browser that changes every day, so no one can be followed from one day to the next, and it's set to discard the IP address itself. Nothing is stored in your browser. A browser with Do Not Track on isn't counted, and neither is the roadmap page.
- The web host logs each request (IP address, page, browser and time) to keep the site running and secure.
- Its fonts are served by this site itself, so no font service sees your visit.
- App downloads come from GitHub, and depthfield.photo/buy, where the app's Buy button goes, forwards you to Stripe's checkout page.
- The pages DepthField Cloud shows in your browser, for signing in, activating a license, finishing a purchase or unsubscribing, load their fonts and an image from this site, and don't pass on the address you came from. Their visits are counted the same way, by DepthField Cloud's server rather than a script in the page, and what it reports is the page without its sign-in, checkout or unsubscribe token.
The waiting list
The waiting list closed at launch, on November 6, 2026. Its form saved your name, email address and answers (what you do, which editor you use, the optional annoying task, and whether you'd like a beta seat), along with the time, your IP address and your browser's user agent, which helped me spot spam. The signups are stored on the web host and were emailed to me. I use them only to email you about the free trial; nothing else. To be taken off the list, email me.
Why, and on what legal basis
The GDPR (Article 6) lets me use personal data only on a legal basis. These are mine:
- Your consent
- Usage statistics, and the waiting list. You can withdraw it any time: in Settings → Privacy for statistics, by emailing me for the waiting list.
- Contract
- DepthField Cloud: your account, sign-in, balance, cloud AI jobs and usage history. Purchases and license records: delivering, re-sending and upgrading what you bought. Feedback: answering it, and using what you send, screenshots included, to fix the problem or build what you asked for.
- Legal obligation
- Keeping accounting records of purchases for as long as the law requires.
- Legitimate interests
- Keeping the app working and up to date (the update check, the price list, the status check and the model downloads); knowing which versions licenses run and how many installs each has (the license check); keeping you posted on your request and running a fair roadmap; counting visits to this website; and protecting the services from abuse (rate limits, request logs, and the waiting list's IP address and user agent). You can object to any of these.
Who else handles your data
I don't sell or rent personal data, and I don't share it with advertisers or data brokers. These service providers handle some of it for me, each only for the job described:
- Amazon Web Services
- Hosts DepthField Cloud and its database backups, in Frankfurt, Germany. Everything sent to DepthField Cloud.
- Cloudflare
- Carries all traffic to DepthField Cloud, cloud AI jobs included, and serves the on-device AI model downloads. Sees IP addresses.
- Neon
- DepthField Cloud's database, in Frankfurt, Germany. Accounts, usage history, license records, feedback, and roadmap votes and subscriptions.
- Stytch
- Signs you in to DepthField Cloud and sends the sign-in emails. Your email address and sign-in sessions.
- fal.ai, Runware
- Run the cloud image and video models. The pictures, masks, prompts and settings of jobs run through DepthField Cloud.
- Google (Gemini API)
- Runs the chat assistant and drafts public roadmap summaries. Chat messages with their snapshot and document description; feedback text.
- Resend
- Sends license emails, feedback replies and roadmap emails, and forwards feedback to me. Email addresses and the content of those emails, feedback screenshots included.
- Stripe
- Payments, as merchant of record. Your purchase; Stripe collects your payment details itself.
- PostHog
- Usage statistics, only if you opt in (the anonymous events described above), and this website's visit counts.
- Google Fonts
- Only when you choose one of its fonts for a text layer, which the app then downloads from Google. Your IP address.
- GitHub
- Hosts app downloads and updates. Your IP address when you download.
- Hugging Face
- Fallback download for the on-device AI models. Your IP address.
- Web host
- Nordicway ApS, Denmark, on servers in Germany. Hosts depthfield.photo and its email, hello@depthfield.photo included: request logs, waiting-list signups and the emails you send me.
- AI coding assistants
- Currently Anthropic's Claude Code, and possibly others such as OpenAI, always with model training turned off. They help me fix reported issues and see the details and screenshots of the issue being fixed.
With your own API keys, the providers you pick receive your requests directly, under your agreement with them (see Cloud AI). Beyond this list, I would disclose personal data only if the law required it.
Data outside the EU
DepthField Cloud's servers and its database are in the EU (Frankfurt), and the website and its email are hosted in the EU too. Some of the providers above are US companies or process data in the United States. Each transfer is protected by one of these, except Runware's (below):
- The EU–US Data Privacy Framework, which the companies certify to: AWS, Neon (Databricks), Stytch (Twilio), Google, Resend, Stripe, Cloudflare, GitHub and PostHog. Their data processing terms add the European Commission's Standard Contractual Clauses as a fallback.
- The Standard Contractual Clauses in the provider's data processing terms: fal.ai.
- Their own terms, as independent companies: Hugging Face and Google Fonts receive your IP address directly when the app downloads a model or a font you chose from them, and AI coding assistants see the details of the issues they help fix, under their own terms.
Runware is a UK company, but it runs jobs in the United States, Germany or Romania. DepthField Cloud uses it on its standard terms and privacy policy, which include no data processing agreement or transfer clauses, and I have no separate agreement with it. So what happens to a job there is governed by Runware's own terms, and I can't promise more than they do.
When fal.ai or Runware pass a job on to a model's maker, it's processed under that company's own terms, wherever the company is, China included, and the safeguards above don't reach that far. Choosing a model also chooses where the picture goes, which is why the app shows each model's maker.
Ask me and I'll send you a copy of the safeguard that applies.
How long it's kept
- Update checks
- Kept only as daily totals per version, which identify no one.
- Rate-limit counters
- In memory, for about an hour.
- Sign-in
- A sign-in link works for an hour; a session lasts 30 days.
- DepthField Cloud account
- Until you ask me to delete it.
- Cloud AI jobs
- The working record goes about an hour after the job finishes. Its line in your usage history stays, as below.
- Usage history and purchases
- Seven years after the end of the year they're from, as Swedish bookkeeping law requires (Bokföringslagen 7 kap. 2 §).
- License records
- As long as the license exists, so it can be re-sent and upgraded. Activation links expire after 72 hours, and only a scrambled fingerprint (a hash) of each one is stored.
- Feedback
- Until the issue is resolved, then up to two years; junk after 30 days. The anonymous roadmap item stays. Sooner if you ask.
- Roadmap
- Your address, votes and subscriptions: until you ask, or two years after your last sign-in or vote. Published comments stay with their item, under the name you chose, unless you ask me to remove them. Sign-in links stop working after 30 minutes.
- Usage statistics
- Seven years, PostHog's fixed period on its paid plan. The events carry a random ID, never your name or email address, and I can delete yours if you ask.
- Website visits
- Seven years in PostHog too, with no IP address and no code that lasts beyond a day.
- Waiting list
- Until you ask to be removed, and no longer than three years after you signed up.
- Server logs
- DepthField Cloud's: 30 days. The website's: up to two months (the web host archives them monthly and deletes the previous month's archive at the end of each month).
- Emails to me
- As long as needed to answer you and deal with any follow-up.
- Backups
- DepthField Cloud's database is backed up every night to encrypted storage at AWS in Frankfurt. Daily backups are deleted after 35 days and monthly ones after 400.
When you ask me to delete your data, I delete it, except what the law requires me to keep, such as accounting records, which I then keep only for that purpose. Deleted data drops out of the backups as they expire.
Your rights
Under the GDPR you can ask me to:
- show you the personal data I hold about you, with a copy
- correct it if it's wrong
- delete it
- restrict how I use it
- hand it over in a machine-readable format, to take elsewhere
- stop using it where I rely on legitimate interests
Where I rely on your consent, you can withdraw it at any time; that doesn't undo what was done before. To use any of these rights, email hello@depthfield.photo, ideally from the address concerned; I may ask you to confirm it's yours. I'll answer within a month, free of charge. You can also turn off usage statistics in Settings → Privacy, and unsubscribe from roadmap and feedback emails with the link in any of them.
If you think I've mishandled your data, please tell me first so I can put it right. You also have the right to complain to a data protection authority in the EU country where you live or work, or where the problem happened. The authority responsible for DepthField is Sweden's Integritetsskyddsmyndigheten (IMY), the Swedish Authority for Privacy Protection.
Cookies and local storage
- This website sets no cookies and stores nothing in your browser, except on the roadmap, which remembers your Board or List choice and which columns you show and, once you confirm your email address to vote or comment, keeps a random sign-in token in local storage on depthfield.photo. Clearing your browser's data for the site signs you out. DepthField Cloud's own pages set no cookies either.
- Stripe's checkout page is Stripe's, with its own cookies and policy.
- The app keeps its own data on your Mac: settings, your consent choice, when it last checked for updates and your license, the random install ID (licensed copies), recent crash logs, and the name and email you used for feedback. With usage statistics on, PostHog's random ID is kept there too.
Children
DepthField Photo is made for adults. It isn't aimed at children, and I don't knowingly collect personal data from them. If you believe a child has sent me personal data, email me and I'll delete it.
Changes to this policy
When something here changes, I'll update this page and the date at the top. If a change affects what happens to your data in a way that matters, I'll also tell you in the app or by email before it takes effect.