Frequently Asked Questions

Autograph’s can only be applied to real photographs, giving you piece of mind when reviewing user uploaded content.

Built using industry leading digital signatures making them tamper-resistant, and non-repudiable, even in airplane mode.

Over half of all iOS and Android devices in active use today qualify. Apple's Secure Enclave has shipped on every iPhone since the 5s (iOS 13+). Android StrongBox ships on Pixel 3+ and most flagship/mid-range Android devices from the last four years. For devices that don't qualify, claims route through the existing manual review fallback — no claim is blocked outright.

They use their native camera app as normal. The photo arrives without a hardware signature, which automatically routes it to the existing manual adjuster review queue — the same workflow that exists in your operation today. Nothing breaks. Nothing is denied outright. As device upgrade cycles continue, the volume of unsigned claims decreases on its own. The goal is to shrink the fallback queue over time, not eliminate claims from day one.

Not yet — it still requires legal review. The Autograph builds on the C2PA manifest and cryptographic signature constitute strong technical evidence of a photo's origin and integrity, but legal admissibility in court or arbitration depends on jurisdiction, opposing counsel, and the specific claim. AutographOS provides the evidence; your attorneys assess its weight. What we can say: the evidence is mathematically verifiable, auditable, and produced by an open standard — which is a materially better position than "our AI said it looked suspicious."

The claimant's smartphone — and only the smartphone. Private keys are generated inside the device's secure element (Apple Secure Enclave or Android StrongBox/Keymaster) and are cryptographically bound to that hardware. They are never exported, transmitted, or accessible to any software — including AutographOS. We hold no keys. We can't access them. Neither can anyone else.

We're still defining pricing. We're currently in the Design Partner phase — working directly with a small number of carriers to shape the product and define the model together. Design Partners get significant input into pricing structure, integration priorities, and product roadmap. If you're evaluating us for your operation, reach out directly and we'll build a proposal around your claims volume.

Yes — coming soon. The ability to revoke a device's public key (e.g. if a device is compromised or a manufacturer is deregistered) is on the roadmap. Revoked keys will be published to the open registry so any verifier can check them without trusting AutographOS infrastructure.

Yes — coming soon. A formal SOC 2 Type II audit is currently in progress. We expect completion alongside our first carrier pilot. In the meantime, our architecture is fully open-source and auditable by your security team on request.

No — only the hash. Photos never touch our servers. We receive a cryptographic hash of the image, verify the signature against that hash, and return a verdict. The image itself stays on the claimant's device and in your existing claims workflow.

We build on top of the giant open standards the world already relies on. Signatures use Ed25519 and ECDSA-P256 — the same algorithms securing TLS, SSH, and passkeys on billions of devices. Images are hashed with SHA-256. Provenance data is embedded using the C2PA content authenticity standard backed by Adobe, BBC, Microsoft, and the camera industry. Device key derivation follows BIP32 hierarchical deterministic keys, the same scheme securing Bitcoin wallets. No proprietary crypto. Any cryptographer anywhere in the world can audit a verification using only public open-source specifications.