Security

Your catalogue and customer RFQs are commercial data. RFQ5 treats them that way.

Name: RFQ5
Author: LeadAfrik

RFQ5 is designed so a model can help interpret a request without becoming the source of truth for products, prices, or the decision to send a quotation.

Tenant-scoped customer data

Paid distributor catalogues, mailboxes, RFQs and quotes are stored against an organisation identifier so each customer is operated separately.

Prices come from your data

The quotation engine does not treat model output as a valid selling price. Prices are derived from the catalogue and the reviewer's explicit edits.

Human approval

RFQ5 drafts; a person sends. Inbox automation prepares work for review rather than silently committing a customer-facing quote.

Snapshot quotations

Approved/sent quotation lines are stored as quote snapshots so a later catalogue update does not silently rewrite what was promised.

Expiring review links

Private approval links expire. They are not public catalogue URLs and should not be indexed.

Audit trail

RFQ5 records important quote and review actions so operator activity can be traced.

Live desk vs paid account

Data

Live desk

Paid account

Price list

Used for the active session; not kept unless you explicitly save a reviewable quote.

Stored privately for the organisation so staff do not re-upload it.

RFQ

Processed to make the draft.

Can arrive through the connected quoting workflow and be tracked with the quote.

Quote

Only persisted when the user explicitly creates a review/approval link.

Saved for review, audit and later export.

Sending

Requires an explicit user action.

Requires human review/action; inbox automation drafts rather than autonomously sending.

Questions for a security review

If your organisation has a security or data-processing questionnaire, email it toinfo@leadafrik.com. We will answer against the deployed configuration rather than make unsupported certification claims.