# US 2026/0074901 A1 · Methods and system for secure transmission and storage of signature data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0074901 A1
- Document ID: US20260074901A1
- Status: Published application
- Kind: A1
- Application number: 19/322,866
- Filed: 2025-09-09
- Published: 2026-03-12
- Earliest claimed: 2024-09-10
- Assignees: Software Automation Holdings, LLC
- Applicants: Software Automation Holdings, LLC
- Inventors: Zachary BORNHEIMER
- Web page: https://patentgrep.com/patent/US20260074901A1

## CPC

- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0838: {Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these (network architectures or network communication protocols for key exchange in a packet data network H04L63/061)}
- H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials}
- H04L 9/3247: {involving digital signatures}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A request is generated including a session identification (ID), an access code, and a sign ID. A lookup key is created using the sign ID and the access code. A contents key is created using the access code, the session ID, and the sign ID. The contents key encrypts content associated with the request. The encrypted content, the look up key, and the contents key are stored at a database. A link is sent to a client device. The link includes the sign ID and the session ID. The access code is received at the facilitation webpage. The sign ID, session ID, and the access code are sent from the facilitation webpage to the database. The content is decrypted based on the contents key, the sign ID, the session ID, and the access code. A captured signature is encrypted using the contents key and stored at the database.

## Claims

### Claim 1

A method for secure transmission and storage of signature data, the method comprising:
generating a request including a session identification (ID), an access code, and a sign ID;
creating a lookup key using the sign ID and the access code;
creating a contents key using the access code, the session ID, and the sign ID, wherein the contents key is used to encrypt content associated with the request;
storing the encrypted content, the look up key, and the contents key at a database;
sending a link to a client device, wherein the link includes the sign ID and the session ID;
sending the sign ID and the session ID from the client device to a facilitation webpage;
receiving the access code at the facilitation webpage;
sending the sign ID, the session ID, and the access code from the facilitation webpage to the database;
decrypting the content at the database based on the contents key, the sign ID, the session ID, and the access code;
displaying the content at the facilitation webpage;
capturing a signature corresponding to the content at the client device or the facilitation webpage;
encrypting the signature using the contents key; and
storing the signature at the database.

### Claim 2 (depends on 1)

The method of claim 1, further comprising retrieving the signature from the database upon receipt of the sign ID, the session ID, and the access code.

### Claim 3 (depends on 1)

The method of claim 1, further comprising deleting the lookup key from the database.

### Claim 4 (depends on 1)

The method of claim 1, wherein the access code is a segmented encryption factor.

### Claim 5 (depends on 1)

The method of claim 1, wherein the sign ID is a code related to the signature.

### Claim 6 (depends on 1)

The method of claim 1, wherein the session ID relates to a browser session.

### Claim 7 (depends on 1)

The method of claim 1, further comprising generating the lookup key using an encryption algorithm.

### Claim 8 (depends on 7)

The method of claim 7, wherein the encryption algorithm uses a salt.

### Claim 9 (depends on 8)

The method of claim 8, wherein the salt includes a random string of characters.

### Claim 10

A method for secure document management, the method comprising:
generating an encryption key;
generating a lookup key from a subset of the encryption key;
generating an access key from an omitted part of the encryption key;
encrypting a PDF document with the encryption key;
storing the lookup key in a database;
presenting the access key with the lookup key;
finding the encrypted PDF document by the lookup key;
recreating the encryption key through the provided access key and the lookup key; and
attempting to decrypt and return the PDF document with the recreated encryption key.

### Claim 11 (depends on 10)

The method of claim 10, further comprising providing an error message or alert if the encrypted PDF document cannot be located or decrypted.

### Claim 12 (depends on 10)

The method of claim 10, further comprising deleting a related database entry in the database after the encrypted PDF document is retrieved.

### Claim 13 (depends on 12)

The method of claim 12, further comprising deleting the encrypted PDF document from the database.

### Claim 14 (depends on 10)

The method of claim 10, wherein the document management includes document storage, access, or retrieval.

### Claim 15

A method for secure transmission and storage of signature data, the method comprising:
creating a lookup key using a sign identification (ID) and an access code;
generating a contents key using the access code, a session ID, and the sign ID, wherein the contents key is used to encrypt content;
storing the encrypted content, the look up key, and the contents key;
sending a link to a client device, wherein the link includes the sign ID and the session ID;
sending the sign ID and the session ID from the client device to a facilitation webpage;
receiving the access code at the facilitation webpage;
sending the sign ID, the session ID, and the access code to a database;
decrypting the content at the database based on the contents key, the sign ID, the session ID, and the access code;
capturing a signature corresponding to the content at the client device or the facilitation webpage;
encrypting the signature using the contents key; and
storing the signature at the database.

### Claim 16 (depends on 15)

The method of claim 15, further comprising displaying the content at the facilitation webpage.

### Claim 17 (depends on 15)

The method of claim 15, wherein the content is associated with a request.

### Claim 18 (depends on 17)

The method of claim 17, further comprising generating the request including the session ID, the access code, and the sign ID.

### Claim 19 (depends on 15)

The method of claim 15, further comprising retrieving the signature from the database upon receipt of the sign ID, the session ID, and the access code.

### Claim 20 (depends on 15)

The method of claim 15, further comprising deleting the lookup key from the database.