Why Markora watermarks stay on your iPhone
How on-device watermarking works in Markora — and why creators may prefer local processing over uploading media to a remote service.
Creators often need a clear ownership mark on finished photos and videos. The awkward part is not placing the mark — it is deciding whether the media has to leave the phone for that job to finish.
Local processing as the default path
Markora is built so watermarking runs on the iPhone. You import from Photos, Camera, or Files, compose text, logos, signatures, QR codes, or date stamps, then export. The product page states that media is not uploaded to a BoMoSi server for that workflow.
That matters when a shoot includes client work, unpublished inventory, or personal archives you do not want sitting in someone else’s processing queue.
What “on-device” does not mean
On-device processing is not a blanket privacy policy for every BoMoSi product, and it is not a substitute for reading store permissions. Photo library access is still required when you choose to import or save a file. Optional features in other apps may work differently.
Use the product page’s Privacy notes as the source of truth for Markora specifically.
When a cloud editor still makes sense
If your team already collaborates in a shared cloud editor, remote processing can be the right trade. Markora is aimed at the opposite case: you want a finished watermark without sending the files away for the stamp itself.
For a fuller feature list — batch limits, templates, and Pro options — see the Markora product page.