Security

Supplier documents are confidential. The defaults should reflect that.

This page describes what the current build actually does. It is not a certification, and no SOC 2 or ISO 27001 claim is made.

Organization isolation

Every supplier, contact, requirement, version, request, notification, and activity record carries an organization identifier. Reads and writes resolve the caller's organization membership on the server before touching data. The browser never receives a query it could widen to another tenant.

Roles inside an organization

Owner, admin, member, and read-only. Read-only users can view suppliers, documents, and reports but cannot send requests or approve documents. Role checks run server-side on each mutation.

Private document storage

Uploaded files go to private storage. Downloads are issued as short-lived signed URLs after the server confirms the file belongs to a requirement in your organization. Public, permanent file URLs are never used for supplier documents.

Supplier link security

Each upload link contains a cryptographically random token. Only a hash of that token is stored, so a database read cannot reconstruct a working link. Links are bound to a single request, carry an expiry date, and can be revoked. An invalid, expired, or revoked token is rejected by the server.

No supplier accounts

Suppliers never register, so there are no supplier credentials to steal. The link is the authorization, scoped to one document request, and it cannot be used to browse your supplier list.

Known limitations

Malware scanning of uploaded files is not implemented in this release. Uploads are restricted to PDF, JPG, and PNG with a size limit, and files are stored privately, but we do not yet run antivirus inspection. Treat supplier uploads as untrusted input: open them in a sandboxed viewer where possible. Rate limiting on supplier links is enforced by submission counters rather than a distributed limiter.

Access, retention, and deletion

Organization owners can request a full export of their supplier, requirement, request, and activity data as CSV. Account deletion requests are handled by the founder while the product is in launch: deletion removes organization records and their document references, but we do not claim secure erasure from provider backups until that behaviour has been verified with the storage provider.

Historical document versions are retained by default so an approved file is never replaced by a newer submission. Retention can be shortened on request once that configuration is available in account settings.

Report a security concern