Privacy policy

In short

• Your photos and edits stay on your Mac. Redlamp develops, masks and exports them there, its AI included, and never uploads them.
• The app has no account, analytics, advertising or tracking. It sends something only when you ask it to, such as a report, camera bench results or a model download, and when it checks for updates and What's New, which send nothing about you.
• Reports you send from the app are public. They're posted as GitHub issues, where anyone can read them.
• This website sets no cookies. It counts page views with Vercel Web Analytics, which doesn't identify you.

Who's responsible

Redlamp is made by Pedro Gomes, who is responsible for the personal data this policy describes (its controller, in data protection law). Write to me at pdcgomes@gmail.com about anything on this page.

The policy covers Redlamp for Mac, whether downloaded from GitHub, installed with Homebrew or built from source; the redlamp command-line tool that comes with it; and redlamp.app.

What stays on your Mac

Redlamp opens, develops and exports your photos on your Mac. Edits are saved next to each photo, in a sidecar file such as IMG_1234.ARW.redlamp, and your recipes, looks, settings, thumbnails and downloaded models are kept in your user Library. AI masks and Generative Remove run on the Mac, with models downloaded to it: no photo is sent to a server to be processed. The command-line tool works the same way.

Photos leave your Mac only when you send them: screenshots you attach to a report, and photos you send with an ambassador application. If you keep your photos in iCloud Drive or another synced folder, that service syncs their sidecars too, under its own terms.

Report a Bug and Send Feedback

Reports are public. What you send with Report a Bug or Send Feedback is posted on GitHub, as an issue in Redlamp's repository, where anyone can read it, with or without a GitHub account. Its screenshots and diagnostics file are stored in another public repository, pdcgomes/redlamp-feedback. Before you send a report, the app shows you everything it holds, as it will appear on GitHub.

A report holds:

• what you write: its title, what happened, what you expected, the steps and how often it happens, with the kind of report and the part of Redlamp it's about;
• the screenshots you include: Redlamp's window, which shows the photo you're editing, or images you paste, with their metadata removed;
• the details you leave switched on: the photo's camera, lens, format, edit and history; what you did in the last 15 minutes and the editor's state; Redlamp's log; and the Mac and the build (Redlamp's version, macOS, the Mac's model, chip, memory, graphics and displays, its language and region, and the AI models you've downloaded);
• for a crash or a hang, what happened, with the threads' stacks, and what you did in the 15 minutes before it;
• your GitHub username, if you give it, so you're mentioned and notified of replies. This links the report to your GitHub account.

File names become Photo A, Photo B unless you choose to include them, and paths, folder names, location and serial numbers are never included. The app sends the report to redlamp.app, which passes it to GitHub as the Redlamp Feedback GitHub App, so it isn't posted under your name, and keeps nothing of it. A report that can't be sent waits on your Mac and goes the next time Redlamp opens. If redlamp.app can't take it, the app offers to open GitHub's new-issue page instead; an issue you file there is posted from your own GitHub account, under GitHub's terms.

I use reports to fix bugs, answer questions and decide what to build, and I answer on the issue. The legal basis is your consent, which you give by pressing Send after seeing the report, and which you can withdraw by asking me to take it down (see Your rights). I use AI agents in Cursor to help me read, sort and fix reports; I make every decision myself.

On your Mac

Redlamp keeps the reports you've sent, your drafts, any reports waiting to be sent, and a journal of recent activity that describes a crash, in ~/Library/Application Support/Redlamp/Feedback. The journal is Redlamp's activity log: the tools, panels and edits you use, the messages it shows, and the photos and folders you open. Turning off Keep an activity log, in Redlamp's Settings › Privacy, stops the log and deletes what it holds, and your reports then go without it. When Redlamp notices a crash or a hang, it offers to report it; one you don't report stays in Help › Your Reports for 30 days. Nothing about a crash is sent unless you send it.

Your Reports checks your reports for replies by sending their issue numbers to redlamp.app, which asks GitHub. Turning off Check for replies and changes, in Your Reports, stops it.

Test Your Camera

The camera bench (Help › Test Your Camera…) checks how your camera's raw files decode, on your Mac. When you press Send Results, it sends the measurements, which What's Sent shows you first, to redlamp.app. They're kept in a private GitHub repository with the day they arrived and the app's version, and without your IP address.

Results hold, for each photo, the camera, its mode, firmware and lens, the exposure settings and the camera's white balance, the decode's measurements, each check's result, timings, and a fingerprint (SHA-256) of the file, so that a photo sent twice counts once. For the whole report, they hold the versions of Redlamp and its decoder, the macOS version, the Mac's chip, your answers and notes, a name to credit if you give one, and a random contributor ID. They never hold pixels, file names, paths, location, serial numbers, owner fields or capture times. The contributor ID is made on your Mac, only counts contributors, and is replaced when you choose Reset Contributor ID.

The cameras page publishes what everyone's results add up to for each camera mode, without contributor IDs, file fingerprints or names. I use the results to learn which cameras Redlamp handles well and what to fix; the legal basis is your consent, given when you send them. If I start crediting contributors by name, I'll say so here first.

Downloads and update checks

These send nothing about you, your Mac or your photos. Like any request on the internet, each carries your IP address and the app's name and version, which the server receives in order to answer it.

• AI models download only when you choose, after Redlamp tells you their size, from Redlamp's releases on GitHub and from Hugging Face.
• What's New: on the first launch of each new version, and at most once a day after that, Redlamp asks redlamp.app for each release's highlights. The whole list comes down, and the app picks what its version has. Settings › About turns this off.
• Updates: a copy downloaded from GitHub or installed with Homebrew checks for updates with Sparkle. On its second launch it asks whether to check automatically, and Settings › About turns automatic checks on or off. A check asks redlamp.app for the update feed, which comes from GitHub, as do the updates. Sparkle's system profile is switched off, so no details of your Mac are sent. Builds from source never check.
• Optional features that need files from redlamp.app download them when you turn them on.
• Links in the app, such as those to GitHub, raw.pixls.us or a licence, open in your browser.

The legal basis is my legitimate interest in providing the features you use and keeping Redlamp up to date.

This website

Hosting. Vercel hosts redlamp.app and runs the services behind the app's reports, the camera bench and ambassador applications. As with any website, Vercel receives your IP address, your browser's details and the address of each page you ask for. The request logs I can see are kept for at most 30 days; Vercel's own use of them is set out in its privacy policy. The legal basis is my legitimate interest in running the site and keeping it secure.

Page views. Vercel Web Analytics counts page views: the page, the page you came from, your country, region and city as worked out from your IP address, your browser, operating system and kind of device, and the time. It uses no cookies. Vercel tells visits apart with a hash of the request, which it discards after 24 hours, and shows me only totals. The legal basis is my legitimate interest in knowing which pages are read.

Cookies. The site sets no cookies. The animation that invites you to star Redlamp on GitHub notes in your browser's session storage that it has played, so that it doesn't play again; the note never leaves your browser, and is cleared when you close the tab.

The film. The film on the home page loads from YouTube, in its privacy-enhanced mode, only when you press play; until then the page makes no request to YouTube. Once it plays, Google receives your IP address and may store data in your browser, under Google's privacy policy.

Ambassador applications. If you apply to be an ambassador, what you send (your name, email address, links to your work, what you shoot, your cameras, what you'd change first, and up to three photos you exported from Redlamp with their edit) is stored in a private GitHub repository that only I can access, passing through Vercel on the way. I use it only to consider your application and to reply, with the help of AI agents in Cursor to read and sort applications; I make every decision myself. The legal basis is taking the steps you ask for before we agree the ambassador terms. If you're not accepted, I delete your application within six months. If you are, I keep your contact details for as long as you're an ambassador, and delete them within six months after.

Email and Discord. If you write to me, your email is kept in my Gmail account, with Google, for as long as I need it to help you and follow up, and I delete it when you ask; the legal basis is my legitimate interest in answering you. If you join Redlamp's Discord, what you post there is visible to its members, under Discord's privacy policy.

Who receives it

I don't sell personal data, and none of it is used for advertising. These companies receive it, each under its own privacy policy:

Transfers outside the UK and the EU

GitHub, Vercel, Google, Cursor, Hugging Face and Discord are based in the United States, so what they receive may be stored and processed there. GitHub and Vercel take part in the EU–US Data Privacy Framework and its UK Extension, and also rely on the European Commission's standard contractual clauses; the others describe the safeguards they use in their privacy policies. Reports on GitHub are public, so they can be read from anywhere.

How long it's kept

• Reports stay public on GitHub until they're taken down, and on your Mac until you remove them from Your Reports. A crash or a hang you don't report is listed for 30 days.
• Camera bench results are kept for as long as they inform the cameras page.
• Ambassador applications are deleted within six months of a decision not to accept them, and an ambassador's contact details within six months of the end of their term.
• Request logs are kept for at most 30 days, and page-view totals, which identify no one, for at most 24 months.
• Email is kept for as long as it's needed to help you.

Your rights

Under the UK GDPR and the EU's GDPR, you can ask me for a copy of the personal data I hold about you, and ask me to correct it, to delete it, to restrict or stop using it, or to give it to you in a form you can take elsewhere. Where I rely on your consent, you can withdraw it at any time; that doesn't undo what was done before. Write to me at pdcgomes@gmail.com, and I'll answer within a month.

Taking a report down. Send me its issue number or link. I'll delete the issue and its screenshots and diagnostics file, remove those files from the attachments repository's history, and ask GitHub to clear any copies in its caches. While a report was public, others could copy it, such as services that archive public GitHub activity; I can't recall those copies.

Camera bench results. Send me the contributor ID shown in What's Sent, and I'll delete every result sent with it.

Complaints. If you're unhappy with how I've handled your data, please tell me first, so that I can put it right. You also have the right to complain to a data protection authority: in the UK, the Information Commissioner's Office; in the EU, the authority in the country where you live or work, or where you think the problem happened.

Children

Redlamp isn't directed at children, and I don't knowingly collect personal data from them. If you're under 16, ask a parent or guardian before you send a report or an application. If you think a child has sent me personal data, write to me and I'll delete it.

Changes to this policy

When this policy changes, I'll update this page and the date at the top. When a change affects what's collected or who receives it, I'll also say so on the blog. Every earlier version is kept in the page's history on GitHub.

Contact

Pedro Gomes, who makes Redlamp: pdcgomes@gmail.com. For help with the app, see Help and contact.