Built by people who have watched their work leak. And decided that a copy should know who received it.
dipmark comes out of photography, software and information security: people who had seen proofs forwarded, drawings photographed off a screen and lookbooks turn up where they should not, and who were tired of watermarks that die at the first screenshot. So we built the thing we wished existed, to the standards we would demand of anyone else.
The problem was never the attack. It was the fourth person on the list.
Leaks rarely come from hackers. They come from someone who was allowed to have the picture: a client who forwards it, a subcontractor who photographs a monitor, an editor who shares a page early. Every tool on the market protected the file. None of them could say, afterwards, whose copy it was.
We set one goal before writing a line of code: read the copy back after a real chain, screenshot to screen to phone camera, and name the recipient. Not a watermark that survives a download. A mark that survives people.
Standards we would demand of anyone else.
Measured, not promised
Every claim on this site comes from our own stress series and real chains, and the lab lets anyone repeat them. Where something is not measured yet, the page says so.
Proof that does not need us
Every registration is sealed by an independent timestamp authority (RFC 3161) and can be anchored in the public Bitcoin blockchain through OpenTimestamps. The proofs can be checked with open tools, without trusting dipmark.
Privacy by construction
Location data is stripped from every file that leaves your account. Your owner signature is never shown to others unless you allow it. For timestamps and anchors only a fingerprint leaves the service. GDPR and the Swiss FADP, whichever applies to you.
Honest limits
No mark survives everything. A full AI redraw creates a new image; a blurry phone photo at a steep angle is read about half the time. We write that down instead of hiding it.
Nothing about the engine leaves
Users and integrators get an answer, never a method. Keys and thresholds stay on our side. That is what keeps the mark readable only by us, and that is what protects you.
Access by request
While we test, we open accounts one at a time, read every request ourselves and answer by hand. Fewer users, each one known.
Small, direct, no layers in between.
dipmark is run by a small team that builds, tests and answers the mail itself. There is no sales floor between you and the people who made the engine.
We work in pilots: a few photographers, studios and companies at a time, with real images and real distribution chains, and we change the product with what we learn. If you want to be one of them, ask for access and tell us what leaks for you.
Try it first. Then write to us.
The lab marks a copy with your name and lets you try to destroy it. If it holds, ask for access, or write to info@dipmark.com and tell us about your case.