Attest for Gmail™ privacy notice

The email information it accesses

When you select Use email details, the add-on reads the open email’s subject and visible From, To and Cc addresses to suggest agreement details. Opening the sidebar alone does not read those fields. You review and edit the suggestions before submitting them.

The add-on does not read email bodies, attachments or Bcc addresses. Google provides a temporary Gmail access token and message ID to access the current message; these stay within the Google-hosted action and are not saved by the add-on or sent to Attest.

What is sent to Attest

Prepare in Attest submits the title, chosen signer addresses, whether you sign too, and your optional note. Attest can read these agreement details and uses them to prepare your private form. This step sends no invitation. When you finish sending in Attest, the agreement workflow uses the reviewed details to contact the selected signers.

The add-on also requests your Attest account identity, agreement lists and signing progress. It sends a reminder request only after your confirmation. Attest checks your authority, eligible recipients, signing order and reminder limits.

Your document and connection

You attach and review the PDF in Attest, where the existing browser encryption and passkey signing flow applies. The add-on does not receive the PDF or its encryption keys.

Google runs the add-on. Its per-user storage holds your Attest access and refresh tokens, the connected Attest email address, and authorization and action state. Google’s execution environment and trusted maintainers of the deployed code are part of this connection’s trust boundary. Your Google and Attest accounts can have different email addresses.

How we protect this information

• Least access. The add-on asks Google only for metadata of the email you have open, and reads the subject and visible From, To and Cc addresses only after you click. It has no access to email bodies, attachments, Bcc addresses or the rest of your mailbox.
• Encryption in transit. The add-on talks only to https://attest.datahubz.com, over HTTPS (TLS). Attest accepts HTTPS only and tells browsers to use it for two years (HTTP Strict Transport Security), and the add-on never follows redirects.
• Encryption at rest. Attest's database is hosted by Neon, which encrypts stored data at rest with AES-256. Your documents themselves are encrypted in your browser before upload; the add-on never receives a document or its keys.
• Protected connection tokens. The connection uses OAuth with PKCE (S256), an exact redirect address and a single-use, ten-minute state. Attest stores authorization codes and access and refresh tokens only as SHA-256 hashes, never in readable form. Access tokens expire after one hour; refresh tokens are replaced on every use, and a refresh token used twice revokes the whole connection.
• In Google. The add-on keeps your Attest tokens in Google's per-user script storage, never in logs, links or cards, and its exception logging is turned off.
• Restricted access. Only authorized DataHubz personnel can reach production systems, with credentials kept in our hosting providers' secret stores. Keys that sign Attest's blockchain records run in a separate service and are never stored with the application.
• Security reports. Report a security issue to contact@datahubz.com, as described in our security policy.

Use and sharing

We use information obtained through Google for the agreement features described here. Google hosts the add-on; Attest and its service providers process the reviewed details to provide those features. Selected signers receive the agreement notifications you authorize. Access for support or investigation is limited to your consent, security needs or legal requirements.

We do not sell Google user data or use it for advertising. We do not use Google Workspace API data to develop, improve or train generalized AI or machine learning models. Our handling of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

Kept out of AI assistants and other apps. Attest sends no Google user data to any AI or machine learning service, and has no integration with one. Separately, you can connect your own AI assistant or other apps to your Attest account, and create API keys. An agreement prepared from Gmail is kept out of all of them: its title, sender and recipients, and the receipts that name it, appear only in Attest and in this add-on. They are never returned to another connected app, an AI assistant, an API key or Attest's record verification tool. Its certificate always stays private. If one of its signers chooses to share a zero-knowledge proof that they signed it, that proof shows only the email addresses they choose to reveal, to the people they share it with.

Retention and removal

Prepared forms expire after 72 hours. Attest’s scheduled cleanup removes expired forms; sending or discarding a form removes it earlier. Existing agreements and signing records are separate from the add-on connection and follow Attest’s record retention and the DataHubz Privacy Policy.

Connection tokens and cached identity remain in Google’s per-user storage until replaced or successfully disconnected; expiration or revocation can make tokens unusable sooner. Temporary authorization and confirmation state expires after ten minutes and is replaced or cleared during use, reconnection or successful disconnection.

Disconnecting and your choices

Choose Disconnect Attest in the add-on to revoke that connection and clear its local connection state. You can also revoke access in Attest under Security → Connected apps. Revoking there ends access immediately; the add-on clears its unusable credentials when its next request is rejected.

Uninstalling the add-on in Google and revoking its Attest connection are separate actions. Neither action deletes existing agreements or signing records. For access, correction or deletion requests, contact contact@datahubz.com. We handle requests under the DataHubz Privacy Policy and applicable retention obligations.