Security and document handling

Company accounts and access

Each employee uses an individual account. Clank reviews access and connects approved users to their company; company roles determine which information and actions are available. Payment does not grant account approval or access to another company’s workspace.

Clank staff accounts require authenticator-based multi-factor authentication. Account and company permissions are checked on the server when protected information is requested.

Who can see your work

Sourcing requests and their documents are private company work, separate from published supplier profiles. Authorized company colleagues can access the work their roles permit. Authorized Clank staff can access sourcing requests and documents to provide support.

Submitting a sourcing request does not send it or its documents to suppliers. In a supplier conversation, you choose the details and files to share. Inquiries for suppliers that have not joined stay with their company profile. Clank must approve the company connection before a supplier account can access those inquiries.

Shared messages and files are available to authorized company members, subject to their current subscription access. Before first payment, approved suppliers see a message count only. Suppliers whose paid access has ended see anonymous message activity until they renew. Buyer identities, message content, attachments and replies require active supplier membership. Clank can review reported messages when handling a report.

Supplier profile content intended for publication is available to approved marketplace users. Keep confidential project details out of those profile fields.

Document protection

Clank uses HTTPS for marketplace connections and encryption at rest for the application database and uploaded documents. Document storage blocks public access.

Uploaded files undergo malware scanning and file-integrity checks before they can be used. Files awaiting a clean scan or failing the checks remain unavailable. Downloads require an access check and use short-lived links.

How document prefill uses AI

When you choose document prefill, Clank extracts text from your requirements PDF and sends that text to Amazon Bedrock to identify equipment and prepare draft requirements. This processing uses AWS regions in the United States.

We store the source PDF, extracted text, model outputs and resulting draft in private application storage to support the workflow, review and troubleshooting. Prefill can miss or misinterpret details. Review and correct the requirements before submitting; you can also enter requirements manually.

Uploading an ordinary supporting file or sending a conversation attachment does not by itself start document prefill.

Retention and deletion requests

Records have different retention needs. Temporary upload copies expire, while retained sourcing documents, messages and processing records can remain with the account. Removing a file from a draft, letting a draft expire or canceling a membership does not immediately erase all stored copies.

For an account closure or data-deletion request, email sales@clankindustries.com. We may need to verify your authority and identify the records involved. Some information may need to be retained for billing, security or legal obligations.

Questions about your information

Read the privacy notice for the information we handle and our service providers. Contact sales@clankindustries.com with security or document-handling questions. Please do not include passwords, verification codes or card details.