macOS asks to use your keychain when Omitly seals

When Omitly seals a redacted PDF, it signs the audit report with a sealing key that lives in your macOS login keychain. The signature lets anyone check later that the report hasn’t changed since it was sealed. (It shows integrity, not who sealed it: see what the certificate proves.)

With only Omitly installed

You shouldn’t see a keychain prompt at all. Omitly creates the key the first time it seals, and macOS lets that same signed app use it from then on, including after updates.

With both Omitly and Omitly Beta installed

Omitly and Omitly Beta share one sealing key, so documents sealed in either app carry the same key fingerprint. Because the key belongs to whichever app created it, macOS asks the other app for permission the first time that app seals:

1. macOS asks for your login password to let the app use the key.
2. Enter it and click Always Allow.

That’s it: macOS won’t ask that app again, including after updates. If you click Allow instead, macOS asks again the next time that app seals.

If you keep seeing the prompt

If macOS asks every time you seal with only one Omitly app installed, or keeps asking after you clicked Always Allow, that isn’t expected. Contact support and include your Omitly version and macOS version (how to find them).