Update to Attest by DataHubz

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

plugin.json →

plugin.json

− removed · + added

--- before
+++ after
@@ -1,10 +1,11 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "attest",
-  "version": "1.0.0",
-  "description": "Attest by DataHubz is document signing and verifiable records. The Attest connector lets your assistant list the agreements you sent or must sign, remind signers, prepare new agreements, verify signed documents and records anchored on the Horizen blockchain, and create Share proofs, zero-knowledge proofs verified on zkVerify. It never reads a document and never signs: documents stay end-to-end encrypted, and each signer signs in Attest with their own passkey.",
+  "version": "1.0.2",
+  "description": "Attest by DataHubz is document signing and verifiable records. The Attest connector lets your assistant list the agreements you sent or must sign, remind signers, prepare new agreements, verify signed documents and records anchored on the Base blockchain, and create Share proofs, zero-knowledge proofs verified on zkVerify. It never reads a document and never signs: documents stay end-to-end encrypted, and each signer signs in Attest with their own passkey.",
   "author": {
     "name": "DataHubz",
+    "email": "contact@datahubz.com",
     "url": "https://www.datahubz.com"
   },
   "homepage": "https://attest.datahubz.com/docs/connector",
@@ -22,8 +23,8 @@
     "com.openai": {
       "interface": {
         "displayName": "Attest by DataHubz",
-        "shortDescription": "Track and verify signatures",
-        "longDescription": "Attest by DataHubz is document signing and verifiable records. The Attest connector brings your Attest records into your assistant.\n\nWhat you can do:\n- See your agreements: the ones you sent and the ones waiting for your signature, with their status, signers, whose turn it is and the audit trail up to completion.\n- Remind signers of an agreement you sent: the signing link goes again to those whose turn it is, at most once a day each.\n- Prepare a new agreement: give the title, signers, order, a note and an expiry date, and get a link to Attest's New agreement form, filled in. You attach the PDF and send it in Attest, where your browser encrypts it.\n- Verify a signed document: give the code on its signature stamp (ATT-XXXX-XXXX), an agreement, receipt or proof ID, or the file's SHA-256 fingerprint. Attest reports who signed, whether every passkey signature checks out, and the record's anchor on the Horizen blockchain. Anyone can run this check, without an account.\n- Prove you signed an agreement without revealing it: a Share proof is a zero-knowledge proof that shows your email address (and a co-signer's, if you name one) and the day the agreement was completed, never the document, its terms or its title. Each proof is submitted to zkVerify for independent verification.\n- Record a receipt: anchor a SHA-256 fingerprint on Horizen as proof that the content existed, unchanged, at that time.\n\nWhat it can't do, by design:\n- It can't read your documents. They are end-to-end encrypted in the sender's browser and stored only as ciphertext Attest can't read, so no tool returns a document.\n- It can't sign. Each signer signs in Attest with their own passkey (Face ID, Touch ID, Windows Hello or the device PIN).\n- It doesn't send documents. You send them from Attest.\n\nYou sign in to Attest when you connect and choose what the assistant may do: check records, read your records, or act on them. You can disconnect it at any time from Attest's Security page.",
+        "shortDescription": "E-signatures you can verify",
+        "longDescription": "Attest by DataHubz is document signing and verifiable records. The Attest connector brings your Attest records into your assistant.\n\nWhat you can do:\n- See your agreements: the ones you sent and the ones waiting for your signature, with their status, signers, whose turn it is and the audit trail up to completion.\n- Remind signers of an agreement you sent: the signing link goes again to those whose turn it is, at most once a day each.\n- Prepare a new agreement: give the title, signers, order, a note and an expiry date, and get a link to Attest's New agreement form, filled in. You attach the PDF and send it in Attest, where your browser encrypts it.\n- Verify a signed document: give the code on its signature stamp (ATT-XXXX-XXXX), an agreement, receipt or proof ID, or the file's SHA-256 fingerprint. Attest reports who signed, whether every passkey signature checks out, and the record's anchor on the Base blockchain. Anyone can run this check, without an account.\n- Prove you signed an agreement without revealing it: a Share proof is a zero-knowledge proof that shows your email address (and a co-signer's, if you name one) and the day the agreement was completed, never the document, its terms or its title. Each proof is submitted to zkVerify for independent verification.\n- Record a receipt: anchor a SHA-256 fingerprint on Base as proof that the content existed, unchanged, at that time.\n\nWhat it can't do, by design:\n- It can't read your documents. They are end-to-end encrypted in the sender's browser and stored only as ciphertext Attest can't read, so no tool returns a document.\n- It can't sign. Each signer signs in Attest with their own passkey (Face ID, Touch ID, Windows Hello or the device PIN).\n- It doesn't send documents. You send them from Attest.\n\nYou sign in to Attest when you connect and choose what the assistant may do: check records, read your records, or act on them. You can disconnect it at any time from Attest's Security page.",
         "developerName": "DataHubz",
         "category": "Business & Operations",
         "capabilities": [
@@ -33,13 +34,13 @@
           "Prepare a new agreement for you to attach the PDF and send in Attest",
           "Verify an agreement, a stamp code, a receipt, a Share proof or a SHA-256 fingerprint",
           "Create a Share proof that you signed an agreement, without revealing the document",
-          "Record a receipt for a SHA-256 fingerprint, anchored on the Horizen blockchain",
+          "Record a receipt for a SHA-256 fingerprint, anchored on the Base blockchain",
           "List your receipts and their anchors",
           "See what your account has left to use, and whether your signing key is set up"
         ],
         "websiteURL": "https://attest.datahubz.com",
         "supportURL": "https://www.datahubz.com/contact",
-        "privacyPolicyURL": "https://www.datahubz.com/privacy-policy#attest-connector",
+        "privacyPolicyURL": "https://attest.datahubz.com/docs/connector/privacy",
         "termsOfServiceURL": "https://www.datahubz.com/terms-of-service",
         "defaultPrompt": [
           "Which agreements are waiting for my signature?",
@@ -70,7 +71,7 @@
               "description": "Verify a completed agreement",
               "prompt": "Check that the Sample: Consulting agreement with Mary Ruiz is genuine and anchored on the blockchain.",
               "tools_triggered": "list_agreements, verify_record",
-              "expected_behavior": "Runs Attest's public check on the agreement's ID and reports that it was completed and signed by both signers, that every passkey signature checks out and that its record is anchored on Horizen, naming the signers by name only and giving the link to its certificate on attest.datahubz.com."
+              "expected_behavior": "Runs Attest's public check on the agreement's ID and reports that it was completed and signed by both signers, that every passkey signature checks out and that its record is anchored on Base, naming the signers by name only and giving the link to its certificate on attest.datahubz.com."
             },
             {
               "description": "Prepare a new agreement for the user to finish in Attest",
@@ -105,7 +106,7 @@
         "commerce_description": "The plugin sells nothing and takes no payments: it works with the user's own Attest records."
       },
       "publication": {
-        "release_notes": "First release of the Attest connector, version 1.0.0. Nine tools: list_agreements and get_agreement show your agreements, their signers, status and audit trail; remind_signers emails the signing link again to the signers whose turn it is; prepare_agreement fills in the New agreement form for you to attach the PDF and send in Attest; verify_record runs Attest's public check on an agreement, stamp code, receipt, Share proof or SHA-256 fingerprint; record_receipt and list_receipts record and list receipts anchored on Horizen; share_proof creates a zero-knowledge Share proof verified on zkVerify; get_account shows what your account has left to use and whether your signing key is set up. Lists come in pages with a cursor. Sign-in is OAuth 2.1; apps identify themselves with a client ID metadata document (as ChatGPT and Claude do) or register dynamically, and you choose the permissions on Attest's consent page."
+        "release_notes": "Version 1.0.2. A dedicated privacy notice for the connector, at https://attest.datahubz.com/docs/connector/privacy, lists what is collected, each tool's inputs and outputs, why they are used, who receives them, how long they are kept and how to disconnect or delete them. The listing adds a support email, contact@datahubz.com. Since 1.0.0, Attest anchors records on the Base blockchain, and agreements prepared with Attest's Gmail add-on are kept out of every assistant and other app, as Google's user data policy requires. The nine tools, their inputs and their permissions are unchanged."
       },
       "apps": "./.app.json"
     }