Security and data handling
FoodQA handles recipes, supplier documents and QA decisions. Access, versions and accountability therefore need to be clear.
Access and company data
Access is controlled per company and user. Product data, documents and decisions remain separated between customers.
Documents and versions
FoodQA preserves the document version behind a result or QA decision so the basis can be retrieved later.
QA keeps the decision
FoodQA can analyse, propose and prepare work. Approvals and changes that become part of the company QA record require accountable review.
DPA and hosting
Data processing, hosting, retention and access are agreed with the customer and documented in the relevant agreements. Contact us for security and DPA material.
Security is part of the QA operating model
FoodQA is intended to hold product and supplier information that can influence controlled QA decisions. That makes permissions, source traceability, version history and accountable review part of the product design rather than separate administrative tasks. The goal is that users can see which source and version supported a conclusion, while controlled changes remain attributable to the people who reviewed them.
Security and DPA review before onboarding
Before production use, customers should validate the agreed hosting setup, data-processing terms, access model, retention requirements, integration permissions, backup and recovery expectations and incident contacts for their own environment. FoodQA provides the relevant security and DPA material for that review rather than relying on generic marketing claims.