All answers.

Security keys prove device possession. KEYRA proves human approval — biometric verification bound to hardware-rooted cryptographic consent for each action.

Biometric templates never leave the device. Authorization proofs are generated locally in the secure element — there is no cloud biometric vault to breach.

KEYRA complements passkeys and FIDO2 flows. It adds an explicit human approval layer for high-stakes actions that software alone cannot guarantee.

Your phone may be compromised; KEYRA remains a separate physical trust object. Critical approvals still require your fingerprint on the device you carry.

Yes. Challenges are cryptographically bound. A fake site cannot complete authorization without your physical approval on KEYRA.

No. KEYRA is human authorization infrastructure — it proves you approved an action, not merely that a device is present.

Use your recovery card and enrolled backup flows to revoke the lost unit and provision a replacement. Founder support assists within one business day.

The recovery card stores recovery material generated at setup. Store it securely offline — it is required to regain access if your device is lost.

Yes. Multiple fingerprints can be enrolled locally on-device for accessibility and backup approval — templates never sync to the cloud.

Contact founder support for warranty replacement. Until then, backup enrollment and recovery procedures documented in your quick-start guide apply.

Factory reset requires an enrolled fingerprint on-device. This wipes keys and biometrics — full re-enrollment is required afterward.

Yes. iOS is supported for pairing, passkeys, and authorization flows via the KEYRA app ecosystem.

Yes. Android support includes BLE challenge-response, passkeys, and offline verification.

Desktop platforms are supported for WebAuthn/FIDO2 and enterprise integrations.

Yes. Use KEYRA as a FIDO2 security key for GitHub and developer platforms that support hardware keys.

AWS enterprise integrations are on the roadmap. Founders receive early access announcements before public availability.

Never. Biometric verification occurs entirely inside the device. No biometric data is transmitted or stored in the cloud.

KEYRA is designed with minimal telemetry. Authorization events are user-controlled; we do not monetize identity data.

Yes. Local biometric storage and explicit consent architecture align with GDPR principles for data minimization and purpose limitation.

Enterprise deployments support policy-controlled logging with user visibility — you always know what was approved.

You do. Keys are generated and held in your secure element — not in a vendor-controlled identity silo.

Capacitive fingerprint verification performed locally on-device with liveness-aware enrollment.

Enrollment and verification include anti-spoofing measures. High-stakes approvals still require live presence on the device.

Re-enroll in suitable conditions and clean the sensor. Accessibility options include multiple enrolled fingers.

Any user who can enroll a fingerprint can authorize. We recommend testing enrollment for comfort and repeatability.

Yes. Core verification and TOTP-style flows operate offline — human proof does not require constant connectivity.

No. Ever. Verification is local-only by architecture — not policy.

AI can act autonomously — transact, communicate, and access systems. Society requires proof that a real human approved each high-stakes action.

Yes. Agents request challenges; you approve on KEYRA. The relying system receives cryptographic proof of human consent.

No. KEYRA ensures humans remain in the loop for actions you configure as requiring explicit approval.

Voice alone cannot authorize. Financial and sensitive flows require your fingerprint on KEYRA — not verbal confirmation.

Partner integrations are expanding. Founders receive early SDK access for AI agent authorization patterns.

No. Consent requires a human. KEYRA provides cryptographic proof that you — not an algorithm — approved the action.

Yes. Banks and fintechs can require KEYRA authorization before funds move — proof a human approved the transaction.

Pilot programs are underway with financial institutions. Founder reservations include updates as bank partners go live.

KEYRA addresses authorization, not card rails directly — but human approval layers reduce social engineering and APP fraud.

Yes. Wallet providers can bind high-value transfers to KEYRA human approval proofs.

Each human should have their own KEYRA. Authorization is personal — not shared across household devices.

Yes. KEYRA is pocket-sized and operates offline for verification when connectivity is limited.

KEYRA contains standard electronics. Follow airline guidance for portable devices; no special restrictions beyond typical consumer hardware.

BLE challenge-response enables presence-based access where partners support KEYRA authorization.

Use recovery procedures immediately to revoke the device, then contact founder support for expedited replacement guidance.

No for on-device verification. Some relying-party checks may need network access on your phone or laptop.

Yes. Healthcare systems can require KEYRA proof before records are shared — explicit patient consent.

Architecture supports HIPAA-aligned deployments with local biometrics and audit-friendly authorization logs.

Policy is set by the healthcare provider. KEYRA always proves which enrolled human touched the device.

No. KEYRA stores authorization keys and biometric templates locally — not medical records.

Yes. Telehealth partners in pilot can bind session consent and prescription approval to KEYRA.

Enterprise kits include provisioning, policy management, and integrations guides for IAM and zero-trust stacks.

KEYRA integrates with FIDO2 and WebAuthn flows used by modern SSO providers.

Enterprise policies define recovery. Consumer founders use personal recovery cards; enterprise uses managed recovery.

Issue dedicated KEYRA units or temporary credentials per your authorization policy.

Yes. Developer documentation covers challenge issuance, attestation verification, and agent patterns.

Pilot discussions are active for citizen services requiring explicit human consent and high-assurance authorization.

KEYRA complements — rather than replaces — national ID; it proves human approval for digital actions.

Designed in Ireland with hardware-rooted security and EU-aligned privacy principles.

Election use requires jurisdiction-specific certification. Contact enterprise for sovereign deployment discussions.

We cannot extract biometrics from devices. Legal requests are handled per published policy with minimal data principles.