Privacy Policy

01Your photos stay on your device

The editor lives at app.lumaowl.app. It downloads the software from our servers and then does all the work in your browser. Once it has loaded, you can keep editing if your connection drops.

Your gallery stays on your device too. For each photo you open, the app keeps a small preview, the file name, its size and dates, and your edits, in your browser's own storage. In Chrome, Edge and other Chromium browsers it also keeps a link that lets the app reopen the original, with your permission. The LUTs you load are kept the same way, so a photo opens again with its look.

All of this stays until you remove the photo from the gallery or clear your browser data. A LUT that nothing uses any more is cleared after 30 days. The app asks your browser to protect this storage from automatic clean-up, and the browser decides. None of it is sent to us.

What does leave your device is account data, listed in section 4. It never contains an image, a preview, a file name, a size, a location or any other metadata.

02What we do collect

Di Capitan Ltd, registered in the United Kingdom, is the data controller for the data described here. We collect what we need to run your account and your plan, to handle access requests, and to see how much Luma Owl is used.

• Account: your email address and your password, which our account provider stores only in hashed form. If you gave us your name, it is saved with the account, together with the short note, if any, that came with your invitation.
• Plan: which plan you have (trial, Pro or beta), when it starts and when it ends, how many devices it allows, and its license number.
• Devices: for each device you use, a random ID created by the app and a label such as "Chrome on macOS", with the first and the last time it checked in. The ID is not linked to your hardware or its serial numbers.
• Device in use: which of your devices has the editor open, with its ID, its label and the time of its last signal. Only the latest signal is kept, not a history.
• Usage log: a line each time you open the editor, open a photo or export, with the date and time. Exports also carry the kind of export, the export format and whether the trial watermark was on.
• Security log: our account provider records sign-ins, session renewals and account changes, such as a new password or a reset link, with the IP address they came from.
• Access requests: what you send through the form, described in section 3.
• Support emails: whatever you write to us, kept so we can help you.

We use your email to sign you in, to send your invitation and your password reset links, and to reply to you. No marketing without your explicit opt-in.

Legal basis under UK GDPR and EU GDPR: performance of a contract (your account, your plan and its device limit), legitimate interest (the usage log, the security log, managing access requests, preventing license abuse and answering support) and legal obligation (tax and accounting records, once paid plans open).

03The access request form

The "Get early access" form on lumaowl.app asks for your email. Your name and what you shoot are optional. If you tick the beta tester box, it also asks where you post your work, with the links, and whether you plan to make a promo video or photo.

The request travels over HTTPS to a Cloudflare Worker of ours at access.lumaowl.com and is stored in its D1 database, together with the IP address it came from, your browser type and the date. If that address cannot be reached, the form tries a second address of the same Worker. We keep the IP address and browser type to spot spam and abuse. For the same reason the Worker keeps a short count by IP address and by email. It only looks back one day, and older entries are cleared as new requests come in.

A copy of each request, IP address included, reaches our inbox as an email delivered by Resend, our email service. If the form cannot reach our server at all, it offers to send the same details from your own email app instead.

We use requests for one thing: deciding and managing who gets access, who joins the beta and who gets the promoter year. If we invite you, your email, and your name if you gave it, are used to create your account, and the invitation reaches you through Resend. Requests are never sold, never shared for advertising and never used for a mailing list. Ask us and we delete yours.

04What leaves your device, and when

• When you sign in or set a password. Your email and password go to Supabase, our account provider, over an encrypted connection. They go straight there: our own servers never receive your password. Signing out tells Supabase to close that session.
• Each time the editor opens with a connection. The app asks Supabase which plan you have and registers the device you are on: its random ID and a label such as "Chrome on macOS". It also adds a line to your usage log saying you opened the editor. While the editor stays open, your sign-in is renewed about once an hour.
• While the editor is open. Luma Owl runs on one device at a time. Every 30 seconds, while the editor is on screen, the app tells Supabase that this device is still the one in use. It sends the device ID, plus its label when the session starts. When you close the page or sign out, the app lets go. If you open Luma Owl on another device, "Use it here" moves it there. The first device finds out at its next signal and pauses exporting until you take it back.
• Each time you open a photo. One line in your usage log saying a photo was opened. Nothing about the photo itself. Opening or reloading the same photo again adds another line. Opening a video clip adds nothing.
• Each time you export a photo, a LUT, a preset or a video. One line in your usage log with the kind of export, the export format you chose and whether the trial watermark was on.
• When you ask for a new password. Your email goes to Supabase, which issues the reset link.
• When the app loads its own files. The app itself, and the film stock data it needs as you work, are downloaded from app.lumaowl.app.
• When you send an access request. What section 3 describes.

Never sent: pixels, previews, file names, folder paths, sizes, camera or EXIF data, GPS data, your edits, your presets, your LUTs or your looks. Without a connection the app sends nothing, and nothing is saved up to send later.

Who receives it. Supabase runs our account service and database: it receives your sign-in, stores your account, plan, devices and usage log, and keeps the security log from section 2. Cloudflare serves lumaowl.app and app.lumaowl.app and runs the service behind the access request form. Like any server your browser talks to, both see your IP address and browser type when you connect. The sign-in code the app runs is served from app.lumaowl.app itself, not from an outside code network.

Why. To sign you in, to apply your plan, to keep a license on one device at a time and within its device limit, and to see how much each account uses Luma Owl, so we can spot a license being shared or misused and know what to build next.

How long. Your account, plan, device list and usage log stay while your account exists and are deleted with it, which we do whenever you ask. Section 8 has every case.

05Payments

Paid plans are not on sale yet, so today Luma Owl takes no payments and holds no payment data. Before they open, this section will name our payment provider and list exactly what it shares with us. We will never receive or store your card details.

06Cookies and local storage

lumaowl.app and app.lumaowl.app set no tracking cookies. The app uses your browser's own storage on this device to remember:

• your sign-in session, which the app sends to Supabase with each request to show it is you;
• your device ID, which the app sends when it registers the device and while the editor is open (section 4);
• the last plan check, with your email, which the app trusts for up to a day if your connection drops;
• your gallery: previews, file names, sizes, dates, edits and, in Chromium browsers, the link to each original (section 1);
• the LUTs you loaded, your presets, references, signature, calibrations and preferences;
• a copy of the app itself, so it can open without a connection;
• a count of failed sign-in attempts, so the sign-in page can pause after too many.

Only the first two ever leave your device. Signing out removes the session from this browser, and the rest stays. Clearing your browser data removes all of it. Your account stays, and you can sign in again.

07No third-party analytics

We do not use any analytics service, advertising pixel, session recording, fingerprinting script or social media widget, on the website or in the app. The only usage data is the usage log from section 4: it is ours, it stays in our account database, and nobody else gets it. We do not sell data and we do not share data for advertising.

The fonts are ours. The typeface is served from lumaowl.app and app.lumaowl.app themselves, so no font service sees your IP address when a page loads.

08How long we keep it

• Account, plan, devices and usage log: while your account exists. When we delete an account, all of it goes with it, and we delete yours whenever you ask.
• Older usage log lines: until version 1.7.5 of the app, released on 2 October 2026, the log also recorded the size in pixels of each photo you opened or exported, and the file type of each photo you opened. Lines written by older versions may still hold those details. They never held an image or a file name.
• Replaced devices: when a new device takes an old one's place on your list, we keep a note of both labels for as long as your account exists.
• Deleted accounts: after deleting an account we keep one line with its email, plan, license number and the dates it was created and deleted, so we can answer questions about it later. Ask us and we remove that line too.
• Security log: kept by Supabase. We have set no automatic expiry on it yet. Ask us and we delete your entries.
• Access requests: up to 24 months, or until you ask us to delete yours.
• Purchase records: once paid plans open, 6 years, as required by UK tax law.
• Support emails, and the copies of access requests in our inbox: up to 2 years after the last message.
• Connection logs at Supabase, Cloudflare and Resend: as long as each provider keeps them under its own policy.

09Who we share it with

Only with the providers that make the service work:

• Supabase, our account service and database: sign-in, accounts, plans, devices, the device in use, the usage log and the security log.
• Cloudflare, which serves lumaowl.app and app.lumaowl.app and runs the Worker and the D1 database behind the access request form.
• Resend, which delivers the emails we send: invitations, password reset links and the copy of each access request that reaches our inbox.
• Proton, which hosts our mailbox, lumaowl@pm.me, where support emails and the copies of access requests arrive.

When paid plans open, our payment provider joins this list. Some of these providers process data in the United States. Where that happens we rely on the UK International Data Transfer Agreement or on EU Standard Contractual Clauses. We also disclose data if the law requires it.

10Your rights

Under UK GDPR and EU GDPR you can ask us to:

• give you a copy of the personal data we hold about you;
• correct it if it is wrong;
• delete it, unless we must keep it for tax or legal reasons;
• restrict or object to how we use it;
• hand it over in a portable format;
• withdraw any consent you gave, at any time.

Email lumaowl@pm.me and we reply within 30 days. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or to your local data protection authority in the EU.

11Security

Every connection uses HTTPS. Passwords are hashed by Supabase and never stored in clear text. In the account database each account can read only its own records. Only we can see all accounts, through an admin panel that asks for a second code on top of the sign-in. Because your images never leave your device, the most valuable thing you work with is not exposed to us, or to any breach on our side.

12Children

Luma Owl is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has given us personal data, write to us and we delete it.

13Changes

This policy may change. When it does, we update the date at the top. Please check this page from time to time.

14Contact

Di Capitan Ltd and associated companies
Edinburgh, Scotland, United Kingdom
lumaowl@pm.me