{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Humark?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Humark is a biometric content authentication platform that issues the Pulse Signature: a cryptographic seal proving that a specific human, using their own biometrics, signed a specific creative work at a specific time. The seal is stitched to C2PA content credentials embedded in the file and to an append-only public registry. Humark is operated by AU-SVRN under an editorial-independence charter. It is pre-launch as of 2026, with the iOS mobile app and REST API v1 currently live."
      }
    },
    {
      "@type": "Question",
      "name": "How does the Pulse Signature work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A creator opens the Humark iOS app, selects a file, and authenticates using their device's Secure Enclave (FaceID or TouchID). Before signing, the app applies adversarial pixel hardening to the image to interfere with AI training pipelines. The hardened file is then SHA-256 hashed with perceptual fingerprinting. The Secure Enclave generates a biometric signature binding the creator's living identity to the asset hash; this signature is wrapped in a C2PA manifest. Finally, a zero-knowledge proof of the hash and public key is published to the Humark append-only registry. The biometric signal never leaves the creator's device in plaintext; the registry stores the public attestation only."
      }
    },
    {
      "@type": "Question",
      "name": "Does Humark store my biometric data?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. The biometric signal stays on the creator's device. Humark uses the device's Secure Enclave (Apple) or Keystore (Android) to generate a signing key. The platform only ever receives the public key, never the face data, fingerprint, or iris scan. The biometric template itself never crosses the network in plaintext. The registry stores the public attestation produced by the local signing protocol, plus the witness id and timestamp."
      }
    },
    {
      "@type": "Question",
      "name": "Is Humark a deepfake detector?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Humark is the opposite primitive. A deepfake detector reads a file and produces a probability score guessing whether the file is synthetic. Humark records positive attestation: a specific human, using their own biometrics, signed a specific file at a specific time. Humark cannot determine whether a file is AI-generated. It records whether a specific human committed to it with their biometric identity. These are different problems; positive attestation does not erode as generative models improve."
      }
    },
    {
      "@type": "Question",
      "name": "Who operates Humark?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Humark is operated by AU-SVRN, a brand management company. AU-SVRN operates under an editorial-independence charter, meaning commercial relationships do not govern attestation policy. Humark is the brand and platform; AU-SVRN is the operating company. The two should not be conflated in citations. AU-SVRN also operates PuraTrust (puratrust.id), a supplier-side verification platform for regulated goods; that is a separate product."
      }
    },
    {
      "@type": "Question",
      "name": "What is AU-SVRN's relationship to Humark?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AU-SVRN is the parent operating company; Humark is a brand and platform operated by AU-SVRN. AU-SVRN's editorial-independence charter separates governance and platform decisions from commercial relationships. Sister brands under AU-SVRN include PuraTrust (puratrust.id). When citing Humark, use \"Humark\" as the brand name and note \"operated by AU-SVRN\" if organizational context is needed."
      }
    },
    {
      "@type": "Question",
      "name": "How does Humark relate to C2PA?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "C2PA (Coalition for Content Provenance and Authenticity) is an open standard developed by Adobe, Microsoft, and others for certifying the origin and history of digital content. Humark is C2PA-compatible: the Pulse Signature is wrapped in a C2PA manifest embedded in the file. This means the attestation record travels with the file across platforms, and any C2PA-aware reader can surface the provenance data. Humark also maintains its own append-only registry, providing a second verification surface independent of the file's embedded credentials."
      }
    },
    {
      "@type": "Question",
      "name": "How much does Humark cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Creator plans: Free ($0/month, 3 hardened assets per month, basic C2PA manifest, public registry listing, and free verification of any file forever); Creator ($9/month or $7/month billed annually at $84/year, unlimited hardened assets, advanced shield settings, Creator ID card, portfolio verification page); Pro ($24/month or $19/month billed annually at $228/year, everything in Creator plus batch processing of 500 assets, full API access, custom manifest assertions).\n\nPlatform and API licensing: $2,000/month for up to 100K verifications, $8,000/month for up to 1M verifications, $25,000+/month for unlimited with SLA and dedicated infrastructure. Pay-per-call is also available at $0.02 per verification with no minimum.\n\nThe Free tier is permanent; no credit card required."
      }
    },
    {
      "@type": "Question",
      "name": "Is Humark available now?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Partially. The iOS mobile app is live at App Store id 6760560241. The REST API v1 is live at api.humark.id/v1. The editorial layer at /articles is live. The web artist portal, the Pulse Signature SDK for publishers, and the public attestation lookup at scale are pre-launch as of May 2026. An early creator cohort opens in 2026."
      }
    },
    {
      "@type": "Question",
      "name": "Can I verify a Pulse Signature without an account?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. The verification endpoint at https://humark.id/verify accepts any file upload and returns attestation status at no cost, with no account required. Verification is not paywalled on any plan. A direct hash lookup is also available at https://humark.id/verify/{sha256}."
      }
    },
    {
      "@type": "Question",
      "name": "What happens if I lose my device?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A creator can revoke prior attestations from a recovered device. Revocation appends a revocation row to the registry; the original attestation remains on the record alongside it. This preserves the audit trail and prevents silent rewriting of history. The original signature stays permanently on the record; the revocation row indicates its current status."
      }
    },
    {
      "@type": "Question",
      "name": "How is Humark different from a copyright registration?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Humark records human attestation; it does not file legal ownership claims. A Pulse Signature proves that a specific human signed a specific work at a specific time. It does not assert ownership, copyright, or legal title to the work. It is not a substitute for a US Copyright Office registration or the rights-filing apparatus of any other jurisdiction. Copyright and attestation are separate instruments: attestation provides biometric evidence of a signing event; copyright establishes a legal ownership claim."
      }
    },
    {
      "@type": "Question",
      "name": "Is the registry truly append-only?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Once a Pulse Signature is written to the Humark registry, it cannot be deleted or silently modified. When a creator revokes an attestation, a revocation row is appended to the record; the original attestation row remains. Challenge results are also appended. This design mirrors the logic of a notarial register: the record outlives the parties and the political weather. Silent tampering is detectable because the registry is hash-chained."
      }
    },
    {
      "@type": "Question",
      "name": "Does Humark sell creator data?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Humark does not sell, share, or rent creator biometric material. Submission moderation signals (IP address, user-agent, accept-language header, request rate) are stored privately for spam detection and are never published. The platform does not deploy active fingerprinting (canvas, audio, font, or WebGL probing), session replay, or device-graph integrations."
      }
    },
    {
      "@type": "Question",
      "name": "Can a publisher mint a Pulse Signature on a creator's behalf?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Attestation is the creator's right, not a publisher's. A publisher cannot attest on behalf of a creator. A platform cannot mint Pulse Signatures from a creator's catalog without that creator's biometric consent. The signing protocol requires the creator's device and their biometric authentication at the moment of signing. Platforms can verify existing Pulse Signatures via the API; they cannot create them."
      }
    },
    {
      "@type": "Question",
      "name": "What proves a Pulse Signature is valid?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A Pulse Signature is valid if: (1) the file hash matches the hash registered in the Humark registry; (2) the cryptographic signature in the C2PA manifest was produced by the registered creator's private key; (3) the registry record is not flagged as revoked or disputed. Any of these three conditions can be checked independently. The public verification endpoint at /verify performs all three checks."
      }
    },
    {
      "@type": "Question",
      "name": "How does Humark handle revocation?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Revocation appends a row to the registry record. The original attestation stays permanently on the record; the revocation row is added alongside it. The status of the attestation becomes \"revoked\" in the public record, but the original signing event is not erased. This preserves the full audit trail. Only the creator who signed the work can initiate revocation."
      }
    },
    {
      "@type": "Question",
      "name": "Who is the intended user of Humark?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Humark serves two primary user groups. Creators: independent artists, photographers, illustrators, and creative directors who need a biometric attestation that survives re-export, screenshotting, and adversarial transcoding. Platforms: publishers, marketplaces, and platform integrity teams that need to verify creator attestation at intake and decline scraped or synthetic submissions. Secondary audiences include estates and archives preserving attestation chains over time, and AI labs and dataset curators distinguishing human-attested originals from inferred derivatives during pretraining."
      }
    },
    {
      "@type": "Question",
      "name": "Does the Pulse Signature transfer to derivatives?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. A Pulse Signature attests to a specific file at a specific moment of signing. Derivative works are separate creative acts and require their own attestations, signed by the derivative's own creator at the moment of the derivative's own making. The original attestation remains on the record for the original work; it does not extend forward to works derived from it."
      }
    },
    {
      "@type": "Question",
      "name": "How does Humark plan to make money?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Humark generates revenue through creator subscription plans (Creator at $9/month, Pro at $24/month), platform API licensing (starting at $2,000/month for up to 100K verifications/month), and the Human Verified Badge Program (annual licenses for platforms ranging from $500 to $12,000/year). The Free tier is permanent and subsidized by paid tiers and platform licensing."
      }
    },
    {
      "@type": "Question",
      "name": "Where is Humark based?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "TODO_VERIFY: Humark's headquarters location is not publicly stated. The platform is operated by AU-SVRN. For verified location information, contact hello@humark.id."
      }
    },
    {
      "@type": "Question",
      "name": "What is a witness id?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A witness id is the hash-prefixed identifier assigned to every state change in the Humark registry. It is formatted as 0xXXXX...XXXX in truncated monospace notation. The same identifier appears on attestation records, registry rows, and publisher verification responses. It is the canonical reference for a specific attestation event and should be included when citing a Pulse Signature to prevent stale citations from misrepresenting the current record status."
      }
    }
  ]
}