Skip to content

Security and trust

Checkable claims, not reassuring ones.

Your recipes, your photos and your team's accounts sit on our platform, so here is what protects them today, what is being built, and what we are not claiming yet. Every line below is something your security team can hold us to.

What is true today.

Each of these is in the running product. Nothing here is a plan.

Enterprise-grade infrastructure on Cloudflare's global network: fast everywhere, protected by default.

  • Your data is scoped to you

    Every query is scoped to your brand, a host we do not recognise is refused rather than falling back to another customer, and the separation has its own tests.

  • Accounts are per person, with real limits

    Each person has their own account. What they can do and which countries they can touch is decided on the server, on every request, not hidden in the screen they see.

  • Invitations and resets expire

    Invitations and password resets use a one-time code that expires in ten minutes, is stored only as a hash, and stops accepting attempts after five wrong tries.

  • Removing someone takes effect immediately

    Access is checked against your live user list on every request, so when you deactivate a person the API stops answering them. No waiting for a session to expire.

  • Passwords are never stored

    Passwords are hashed with PBKDF2-SHA256 and a salt unique to each user. We cannot read yours, and neither can anyone who reads the database.

  • Deletion is reversible

    Content is retired rather than destroyed, and every change is recorded with who made it, what changed, when, and the values before and after.

  • Nothing is public until you publish it

    New work lands in a space only your team can see. Going live is a decision you make, per market.

  • Changes ship through review

    Every change goes through a pull request with tests and a second reviewer, development and production are separate, and database changes are applied through a ledger that is checked at deploy time.

  • Sign-in and access

    Only the right people get in.

    • Invitations and resets by one-time code, expiring in 10 minutes
    • Roles and markets per person, checked on every request
    • Two-factor authentication
    • Single sign-on with Google and Microsoft
  • Control and audit

    Every change has an owner.

    • Every content change recorded: who, what, when, before and after
    • Approvals per market
    • Deletions are reversible: content is retired, not destroyed
    • Every query scoped to your brand, with tests that prove it
  • Analytics

    Numbers you can take to the board.

    • Views by recipe, collection and market
    • QR scans by code, product and campaign
    • Content health: SEO, images, freshness
    • Your own Google Analytics 4, plus exports

What is coming.

Designed, being built, and deliberately not written above as though it already works. We are not putting dates on this page until they are dates we can keep.

  • Two-factor authentication, then passkeys
  • Single sign-on with Microsoft Entra and Google Workspace
  • Automatic joiners and leavers from your directory
  • Sign-in events in the activity log, alongside content changes
  • Approval before publishing, per market
  • A published SOC 2 report

Send us your security questionnaire.

We keep answers to the standard questionnaires written down and current, in the same tagged form as this page: what the code does today, what is designed, and what we do not do yet. Send yours and you get it back answered line by line, including the lines where the answer is no.

Found something?

Tell us through the contact form and mark it as security. We will come back to you, and we will not argue with you about whether it counts.