Short privacy notice · 4 August 2026
Separate choices.
Separate records.
Prototype controller gate
HonourFood is currently a founder-run UK prototype, not a separate legal entity. Publishing the controller's legal name and a working privacy contact is a required gate before research recruitment or contribution intake begins. Public feedback, update sign-up, watches and pack uploads are now technically paused. This notice does not pretend that missing accountability detail has already been completed.
Feedback intake is paused
The prepared question set asks for no name, email, employer or company, but free text can still contain personal or workplace details. It therefore sends and stores nothing on the public prototype. Before it opens, HonourFood must publish the controller and rights contact, lawful basis, retention period and an enforceable participant boundary. The site host may still process routine request and security logs separately.
Project updates are paused
The future update route will request email only after a separate authenticated choice and will require a confirmed consent record. New sign-ups are currently disabled; the public prototype does not ask visitors to authenticate for updates.
Existing test records can still be withdrawn through authenticated access at honourfood.com/unsubscribe. That withdrawal route remains available while new collection is paused.
Authenticated pack submissions
Public pack uploads are disabled. The designed workflow would store product details, five supplied label photographs and a one-way site-user key in private storage, with no automatic publication. It cannot open until image-metadata handling, retention, controller information and contributor rights are operational.
Barcode lookup
Camera decoding happens on your device. HonourFood receives the barcode digits, checks its published catalogue and may request a field-limited record from Open Food Facts. The pilot does not store an account identity or per-person scan history. If the community connector is enabled, HonourFood derives a minute-rotating pseudonymous key from the connecting network address solely to enforce a three-lookups-per-minute, per-network-address anti-abuse limit. People sharing an address share that budget. The application does not store the raw address in that rate-limit table, and old minute buckets are removed during routine requests. Open Food Facts receives a service-level HonourFood identifier, not your account or email. The site host may still process routine request and security logs.
Case reactions and watches
New public reactions and public totals are currently gated. Reopening them requires a documented fake-review policy, abuse detection, investigation and appeal controls. New case watches are also paused. A later watch service would store the authenticated email, exact watch scope, consent wording version and timestamps and provide an authenticated stop route. Any later reactions can never determine HonourFood's editorial evidence status.
Respectful Shop prototype
The current shopping demonstration uses fictional products, offers and retailers and contacts no retailer. Before a live pilot, HonourFood must use authorised feeds or links, label affected affiliate relationships before engagement and assess whether link decoration, identifiers, cookies or connector permissions require consent. The first pilot should open retailer product pages without storing retailer credentials or a per-person shopping history. The retailer remains responsible for current stock, final price, account, substitutions and checkout.
Hosting and your rights
The site host may process routine security logs separately. Existing authenticated update test records can use the withdrawal route above. No new research or contribution record should be created while the named-controller gate is closed. A complete access, correction, deletion, restriction and complaint route is required before reopening. You may also complain to the UK Information Commissioner's Office.
Return to HonourFood ←