Skip to content

FAQ

Questions we are asked before the first call

If the answer you need is not here, the demo session is a working one — bring the question.

8 questions

Does FIQS certify our gold or our operation?

No. FIQS supports responsible sourcing workflows and produces audit-ready records. Certification of gold and accreditation under any assurance scheme remain with the recognised bodies and their approved assessors.

Which frameworks does FIQS follow?

The platform structures work around the OECD Due Diligence Guidance, the LBMA ASM Toolkit and the Responsible Minerals Assurance Process. It organises evidence in the shape those frameworks expect; it does not represent them.

Can our existing records be imported?

Yes. Existing policies, documents, monthly reviews, approvals and evidence can be moved into the platform, where they gain versioning, retention state and export.

What does the blockchain component actually do?

Selected custody and transaction events carry a reference recorded through Polygon, which provides a durable point of comparison for due diligence and audit. Not all platform data is held on-chain — documents and personal data stay in the platform under its access controls.

Can FIQS integrate with our existing systems?

The platform is designed to expose suppliers, custody events, transactions, screening results and documents through a REST API, with webhooks for event-driven integration. Published endpoint documentation is in progress.

Who can see our data?

Access is role-based, with single sign-on and enforced two-factor authentication for administrators. Records carry audit logs showing who saw and changed what.

How long does implementation take?

It depends on how much evidence already exists and what shape it is in. The guided onboarding produces a readiness report with a proposed sequence, which is the honest way to answer this for a specific operation.

How is the anonymous reporting channel protected?

A report can be filed without an account and without giving a name. Submission issues a reference code for checking status later, and internal case data is never exposed through that lookup.