Privacy in AI editing: your own API key

When you upload a property photo to an AI tool, the data leaves your machine. With most providers it lands on a server you never see, processed through accounts the provider owns. For a kitchen shot that is harmless. For the front view of an occupied family home with a visible house number, a nameplate on the doorbell and a parked car, the picture changes. You are now processing other people's personal data and you need to know who else touches it along the way.

Your own API key flips that relationship. Instead of the image platform routing your photos through its own pooled account at the AI provider, the requests run through your own contract directly with the model provider. You hold your own data processing agreement there, your own settings and your own billing. The platform becomes the interface, not the middleman for your data. That is the decisive difference when an owner or a data protection authority asks how images are handled.

In practice this means you open an account with the AI provider you trust, generate a key there and store it once in the platform. Make sure to disable training on your data with that provider. The major providers now offer paying API customers the option that input images are not used for model training and are deleted after a short period. That setting is your most important lever and it belongs in your documentation.

For your processing records this creates clean lines. You need one processing agreement with the image platform as operator of the interface and one with the AI provider as processor of the images. It sounds like paperwork, but it is exactly what you should hold for any service that sees property data anyway. With your own key the chain is short and nameable, rather than a pooled account obscuring the view.

An often underrated side effect is cost control. Because usage runs through your own contract, you see exactly how many images you processed and pay the real model price without a markup. For ten listings a month that is often only a few euros. You can also set a spending limit so an accidental bulk upload does not turn into a nasty surprise on the invoice.

A note on care around people and neighbours: retouching exposure, colour and cropping is uncritical. As soon as you remove people, licence plates or someone else's property such as the neighbouring house, or you furnish rooms virtually, you leave the purely technical zone. Virtual furnishing and other generative additions have been subject to labelling rules since August 2026. State transparently in the listing that an image was digitally furnished. Your own API key protects your data paths, the label protects your credibility.

The bottom line is that your own key is not a nerdy technical detail but a business decision. You give up a bit of convenience, the one-time setup, and in return you get control, accountability and fair costs. For an agent who works with other people's properties and their residents every day, that is not a luxury but sound practice.