Collo Privacy Policy

Effective November 15, 2026

Collo is a RAW photo developer for Mac, iPad and iPhone. This page says what the app does with your data, who is responsible for it, and what your rights are. The short version: your photos stay on your device. Nothing leaves it unless you set that up yourself (your own key for a cloud AI provider, or Sync to your own iCloud), and there is no Collo server and no account.

Who is responsible

Collo is made by Alex Goeke, a sole proprietor doing business as Alexander Creative.

Alex Goeke, doing business as Alexander Creative
San Antonio, Texas, USA
creative@alexandergoeke.com

For privacy law (GDPR, UK GDPR) Alex Goeke is the controller of the one thing we do receive: your support email (see "What we do receive"). For everything else on this page, the data stays on your device or goes to a service you deal with directly (Apple, or a cloud AI provider you chose), and we never see it.

No account, no tracking

Collo has no sign-in, no ads and no tracking of any kind. It adds no analytics code and no crash-reporting code. There is no Collo server. We do not sell or share personal information, we process no sensitive data, and we make no automated decisions or profiles about you.

If you have chosen, in your device settings, to share analytics with app developers, Apple may send us anonymous crash and usage reports about Collo. We do not get your name or your photos from them, and we cannot tell who sent a report. You can turn that off any time: on iPad and iPhone in Settings, Privacy and Security, Analytics and Improvements, and on the Mac in System Settings, Privacy and Security, Analytics and Improvements (the switch is called Share With App Developers).

Do Not Track: Collo has no web tracking, so it has no Do Not Track signal to respond to. No third party tracks you through Collo.

Your photos stay on your device

Collo opens the RAW files you choose and renders them on the device. It never uploads your photos to us, and it never modifies your originals. Edits are stored as small sidecar files next to the RAW on the Mac (or in Collo's own storage when that folder can't be written), and inside Collo's own storage on iPad and iPhone. If you turn Sync on, a copy of your edits also goes to your own iCloud account (see Sync below).

Because your photos never come to us, we can't use them for anything, and we don't train any model on them.

On-device AI

These features run on your device with no network and no key: AI Remove (including click to select an object, a wire or a cord), Spot Heal and the Healing Brush, Expand, Retouch (Clean Up Skin, Dodge & Burn), Enhanced Demosaic, AI Denoise, the Objects tool (Select), and the detected masks. Assisted Review and the HDR merge are computed on the device too.

  • The detected masks: Subject, People and Background use Apple's Vision framework on the device. Sky, Landscape, the room and garden masks (Ceiling, Walls, Floor, Windows, Lights, Grass, Trees) and Depth Range use models bundled inside Collo, and so do the Objects tool and click to select.
  • Clean Up Skin finds faces, facial features and body pose with Apple's Vision framework, on the device, each time it runs, only to decide where skin is in that photo. It does not recognise who anyone is, and it keeps no face data: the edit stores only which people (by their position in the photo's list) you chose to include. Nothing about faces is sent anywhere.
  • AI Denoise can start on its own. A photo shot at a high ISO (1600 by default, and you can change that or turn it off in settings) opens with AI Denoise already on. It runs on the device like everything in this section. On iPad and iPhone the automatic version is applied when you export, not while you edit.
  • Sync, the optional cloud AI providers and iCloud favorites are the only features that use the network (see below).

Your profiles, looks and styles

On the Mac, Collo reads the camera profiles that Lightroom and Capture One install, in place. Your own Camera Raw looks folder and Capture One styles folder are private to your account, so Collo asks once for permission to read them (you can change this under Collo, Library Access). It never copies or sends any of these files anywhere. On iPad and iPhone you import them yourself from a folder you pick. Collo ships none of these files.

Cloud AI providers: optional, your own account, off until you add a key and say yes

Every AI feature in Collo works on your device with no network, no key and no cost, and that is how Collo ships. As an option, you can connect your own account with one or more cloud AI services and use their models for these tools: Best quality (cloud), which fills an AI Remove stroke again with the cloud model you picked; the Generative brush, which removes what you paint (Generative Remove, with Bria) or paints what you type into it (Generative Fill, with the model you picked); and Generative Expand, which extends the photo past its edges (Bria only). Collo works with these providers, and with no others:

  • Bria (Bria Artificial Intelligence Ltd., offices in Tel Aviv, Israel and New York, USA). Bria Eraser and Bria Generative Fill, and the only provider for Generative Expand. Privacy policy: bria.ai/privacy-policy.
  • Black Forest Labs. FLUX 3, FLUX.1 Fill [pro] and FLUX Erase.
  • Google, through the Gemini API. Nano Banana 2.1 and Nano Banana Pro.
  • OpenAI. GPT Image 2.5 Flare and GPT Image 2.
  • Stability AI. Stability Erase and Stability Inpaint.
  • Ideogram. Ideogram 4.5 Precise Edit, for Best quality (cloud) and Generative Fill. Opt-in only: Collo never uses Ideogram on its own, only for a tool you pick it for. Ideogram's usage policy says its results must not be presented as an actual photograph of a real event, and asks you to have the rights and the consent of anyone in an image you send. Its developer terms ask that results be identified as made with Ideogram's model.
  • Higgsfield. Qwen Image 3 Edit and Grok Image 2.0, models made by other companies (Alibaba and xAI) that Higgsfield gives access to. How Higgsfield runs them, and whether those companies also handle your image, is governed by Higgsfield's terms.

Your own account and key

You create the account and the API key with the provider, paste the key into Collo (on the Mac: Collo, Settings, AI Providers, and for Bria also Collo, Settings, Cloud AI; on iPad and iPhone: the More menu, AI Providers, and for Bria also More, Bria Cloud AI), and the provider bills you directly for what you use. Collo does not provide, sell or share any key, and Alexander Creative has no account behind your use of any of them. Each provider is a service you deal with directly, under its own terms and privacy policy, which are an agreement between you and that provider. We can't verify how a provider protects what it receives, so read its policy before you allow it.

Your keys are stored in your own device's Keychain, only on that device. They are not written to a file, not put in your edits or exported metadata, not synced through iCloud or CloudKit, and not sent anywhere except to the provider they belong to. Test Key makes one check call to that provider that starts no job.

Nothing is sent until you allow it, and only for a use you start or choose

Adding a key is not enough. The first time Collo would send anything to a provider, it shows a sheet that names the provider, says what is sent and summarises its terms, and asks you to choose Allow or Use on-device only. Each provider asks separately, once per device. Nothing is sent until you choose Allow. After that, a photo is sent only for the one use you start (a Best quality (cloud) press, a Generative stroke, a Generative Expand); on-device AI Remove stays the default for every stroke. The one exception is a setting you turn on yourself: under AI Providers, Hard removals, the default is On this device only and changes nothing; Ask when the cloud would do better only shows a suggestion and sends nothing until you tap Try it; and Use the cloud for hard removals, which is off unless you choose it, sends a removal that Collo judges hard to the provider you picked right after the on-device fill, only if you have added that provider's key and chosen Allow, with one tap back to the on-device fill. Your consent is your legal basis for the transfer, and you can take it back whenever you like (see "How to turn a provider off and get your data deleted").

What is sent

  • Best quality (cloud), Generative Remove and Generative Fill send only the area round your stroke, as a newly rendered copy of that area at up to 2048 px on its longest side, with no camera, location or other file metadata. With it goes either a mask that marks where to edit, or, for models that take no mask (FLUX 3, the Gemini models and the Higgsfield models), the same area with the part to edit outlined in the picture.
  • The instruction: for a removal, a fixed wording written by Collo; for Generative Fill, the words you type.
  • Generative Expand (Bria only) sends the whole photo at full resolution, up to about 25 megapixels, so Bria can extend it.
  • What comes back is the filled area. Collo keeps it with your edit and marks the exported file as AI generated (IPTC).
  • Photos can contain people, house numbers and the inside of homes. Allow a provider only for pictures you are happy to send, and tell the people in them if you need to.

What a provider may do with it

That is up to each provider's terms, not ours, and their terms change. When we last read them (October 2026), in short: Bria said it does not train on what you send without your written consent and keeps personal data as long as necessary for its stated purposes; Google's Gemini API keeps a request unless asked not to, and Collo asks it not to store the request (free-tier use may be used to improve Google's products, paid use is not); OpenAI said API data is not used for training by default and may be kept up to 30 days for abuse monitoring; Stability AI said it may train on what you send unless you opt out in its privacy center; Higgsfield keeps request files 7 days by default, and Collo asks for 1 hour and deletes them as soon as the result is downloaded; Black Forest Labs' developer terms do not say, so check its privacy policy. Ideogram's developer terms (read November 2026) say it does not train on what you send through its API, except content flagged under its usage policy. Read each provider's current terms and privacy policy before you allow it. We never see what you send, and it does not come to us.

How to turn a provider off and get your data deleted

  • Stop sending: for that provider, choose Use on-device only, or remove its key (in the same AI Providers settings; for Bria, also Cloud AI on the Mac or Bria Cloud AI on iPad and iPhone). Collo is back to on-device only for that provider straight away. Nothing is sent to it after that.
  • Delete what a provider already has: that is the provider's data, so ask the provider, using the contact in its privacy policy (Bria's says to email hi@bria.ai). You can also delete or rotate your API key in your account with the provider.
  • Because Alexander Creative never receives these uploads, we can't delete them for you. We are glad to help you write the request.

None of this is on unless you add your own key and choose Allow.

Tethering a camera

On iPad and iPhone you can plug a camera into the USB-C port and shoot tethered. The system asks for permission to control the camera the first time. The photos you take are copied from the camera into Collo's own storage on the device (by default a folder shown in Files under On My iPad or On My iPhone, Collo, Collo Captures, so you can copy a shoot off without Collo). On the Mac, Library, Tethering does the same from a camera or a hot folder. Nothing about tethering uses the network or leaves the device.

Edit in Retouch4me and Edit in Affinity (Mac)

If you have one of these apps installed, Collo can hand it your photo as a 16-bit TIFF in a folder on your Mac and read back the file you save there. The file stays on your Mac (and in your own iCloud as part of Sync, if Sync is on). Collo sends it to nobody else; what the other app does with it is governed by that app's own terms.

Sync: optional, off until you turn it on

Sync keeps your work in step between your own Mac, iPad and iPhone. It is available in Collo 1.0 and off until you turn it on (on the Mac: Collo, Settings, Sync; on iPad and iPhone: the More menu, Sync). When it is on, Collo stores these in the private CloudKit database of your own iCloud account, and nowhere else:

  • The develop settings of each photo you edit: every slider, curve, crop, heal and look, as Collo saves them.
  • Each edited photo's stars, flag and color label.
  • What lets your other devices find the same photo: its file name and size, and two codes your device computes from the file. One comes from a few small pieces of the file's contents, the other from the camera's serial number and the time the photo was taken. Only the codes are sent, never those pieces, the serial number or the time.
  • Your Creative Stacks and your own export presets, including the name, copyright and contact details you typed into them.
  • The image of each AI fill (the pixels AI Remove, a cloud provider or Generative Expand made), up to 15 MB each, so a removal looks the same on your other devices. Each one is made from part of the photo; a Generative Expand fill covers the whole frame, so it holds a copy of the photo at the size it was made. A fill downloads only to a device that has that photo.
  • For each change, when it was made and a random code for the device it came from (not your device's name).

Your RAW files never go through Sync (apart from what an AI fill holds, above). To work on a photo on another device, put the RAW file there yourself (iCloud Drive, Files or AirDrop), and Collo applies your edit when you open it.

All of this lives in your iCloud account, run by Apple under your Apple account and Apple's privacy policy (apple.com/legal/privacy), and it counts toward your iCloud storage. We can't see it: only your Apple account can read a private CloudKit database. The edit data is kept in CloudKit's encrypted fields.

Turning Sync off stops sending and receiving and leaves what is already in iCloud. Remove Collo's Data from iCloud (in the same place) deletes all of it and turns Sync off on your other devices too. Your edits on each device stay. If a different Apple account signs in, Sync pauses until you turn it on again, so one account's edits never go to another.

Favorites sync

The looks and profiles you mark as favorites sync between your own devices through iCloud Key-Value Storage, under your Apple account and Apple's privacy policy, whether or not Sync is on. No photos, profiles or keys go through iCloud.

What we do receive

If you email support, we get your email address, your name if you give it, and whatever you write or attach. That is the only personal data we receive.

  • What we use it for: to answer you, fix the problem you wrote about, and keep a record of the conversation in case you write again.
  • Our legal basis (GDPR article 6): it is needed to answer your request and give you support, and it is in our legitimate interest to run support properly. Where you send us a photo or file, you chose to send it for this purpose.
  • How long we keep it: we delete the conversation, and any files you sent, within 12 months after the last message in it. If you ask us to delete it sooner, we will.
  • Who else sees it: our email provider, Google (Google Workspace), which hosts the creative@alexandergoeke.com mailbox for us under its own terms. We don't share it with anyone else, and we don't use it for marketing.
  • Where: we are in the United States, so your email is processed there. If you write to us from the EU or UK, you are choosing to send it to us in the US so we can answer you.

Who gets data, in one place

  • Alex Goeke / Alexander Creative: your support email only.
  • Google (Google Workspace): hosts our support mailbox.
  • Apple: iCloud and CloudKit (Sync and favorites, only if you use them), App Store purchases, and the opt-in crash and analytics reports described above. Apple deals with you directly under its own terms.
  • The cloud AI providers listed above (Bria, Black Forest Labs, Google, OpenAI, Stability AI, Ideogram, Higgsfield): only the provider you add your own key for and choose Allow, and only the images described in "What is sent", when you press the button or have turned on Use the cloud for hard removals. Each deals with you directly under its own terms.

Apple and the AI providers are services you have your own relationship with. We don't claim that they protect your data in the same way we do; their terms and policies govern what they do.

Transfers

We are in the United States. The cloud AI providers are based in different countries (Bria in Israel and the United States; the others mostly in the United States, Europe or the United Kingdom) and may process what you send elsewhere. The European Commission has found that Israel gives adequate data protection, and the same for US companies certified under the EU-US Data Privacy Framework. Check each provider's policy for how it handles transfers before you allow it. Your use of any provider is always your own choice.

Your rights

Whoever you are, you can ask us to tell you what we hold about you, to correct it, or to delete it. If you are in the EU, the UK or somewhere with similar laws, you also have the right to restrict or object to how we use it, to get a copy you can move, and to take back any consent you gave (taking it back does not undo what happened before). To use any of these, email creative@alexandergoeke.com. We answer within 30 days.

You also have the right to complain to your data protection authority. In the EU that is the authority in the country where you live or work (the list is at edpb.europa.eu). In the UK it is the Information Commissioner's Office (ico.org.uk). We'd like the chance to fix it first, but you don't have to ask us before you complain.

You are not required to give us any personal data to use Collo. Support email is entirely your choice.

Children

Collo is not directed at children and we do not knowingly collect data from them. The app itself collects nothing from anyone. If a child emails us, we delete it as soon as we know.

Changes

If this policy changes, we update this page and the date at the top, and we list the change below. A material change (for example a new way data could leave the device) is also called out in the app's release notes. Earlier versions are available on request.

Change log

  • November 15, 2026: Collo 1.0.3 adds Ideogram as an optional provider, only with your own key and only for a tool you pick it for, with what its terms say. Explained the optional Hard removals setting that came with 1.0.2: the default sends nothing, Ask only suggests, and Use the cloud for hard removals sends a hard removal right after the on-device fill, only with your key and your Allow. Added the new room and garden masks to the on-device list.
  • November 3, 2026: Collo 1.0.1 works with more cloud AI providers, all optional and only with your own key: Black Forest Labs, Google (Gemini API), OpenAI, Stability AI and Higgsfield, as well as Bria. Named each one, what is sent (including the outlined area for models without a mask, and your typed prompt), that each provider asks its own consent once and each use is a button press, and how to turn each off. Added Clean Up Skin (on-device face and body detection, no face data kept or sent), USB-C tethering on iPad and iPhone, and Edit in Retouch4me on the Mac.
  • October 23, 2026: Named who is responsible and added a postal address. Added legal bases, how long we keep support email (12 months), your rights and the right to complain, and who receives data (Google, Apple, Bria). Corrected "no crash reports" to explain Apple's opt-in reports. Added the Do Not Track, no-sale and no-automated-decisions statements and a children section. Updated the on-device AI and masks wording, and described automatic AI Denoise, Sync and how to turn off Bria and get its data deleted.
  • October 21, 2026: Customers use their own Bria account and key. Added the first-upload consent sheet, Sync and the on-device AI section.
  • October 1, 2026: First published.

Contact

Alex Goeke, doing business as Alexander Creative
San Antonio, Texas, USA
creative@alexandergoeke.com