Privacy Policy

This page is under legal review. The policy takes effect on the date shown and we will tell you before any material change.

Who we are: FOODX WORLD LIMITED, Companies House Registration No. 16406719, registered in England and Wales.
Contact: hello@foodx.network

1. The Short Version

  • Your record is yours. We keep it for you. You can take it and leave any time.
  • What you and your devices sign is signed with your key. We cannot change it.
  • We do not sell your data. We do not show ads. We do not train AI models on it.
  • We only read your email and calendar when you connect them, and we only read. We never change or delete anything there.

2. What We Hold

Blocks

Your record is made of blocks: small signed notes (an order, a promise, an offer, a payment confirmation). Each is signed with your key and linked to earlier ones. They are append-only: new blocks are added; old ones are not edited.

Your Keys

On your phone, the passkey is your signing key (stored in Secure Enclave on iOS or Android Keystore). Hosted nodes keep agent keys in an encrypted keystore. Recovery uses the identity module's recovery key.

Account Details

Name, email, phone number, and what you choose to add.

Messages

If you use SMS, USSD, WhatsApp or email with us, the message and the number or address it came from.

Payments

We record that a payment was confirmed by your provider (for example M-Pesa). We do not hold your money and we do not store card numbers or bank logins.

Technical Information

Device type, app version, error logs.

Photos and Voice

Only what you give the app.

3. What We Read From Other Places (Only When You Connect Them)

Google (Gmail and Calendar)

You choose to connect. We read mail and calendar events to find your orders, receipts, bookings and contacts and turn them into entries in your record. You see them and decide. We never send, change or delete anything in your Google account.

Google API Services User Data Policy

FoodX's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Platform Exports

If you upload a data download from a platform (for example a delivery app), we read it for you.

Public Web Pages

Your own website, if you point us to it.

4. How We Use It

To run your account and your record; to read, summarise and suggest, for you; to send the messages you tap send on; to keep things safe; to obey the law. Nothing else.

5. AI Models

To understand your messages, receipts and photos we send the relevant text or image to AI model providers we pay under their API terms. At launch, we use: TypeSafe (Jev), OpenAI, and Google Gemini. We may also use: Qwen (Alibaba Cloud), Mistral, and Moonshot. We send the least needed. Under our agreements with these providers, they are prohibited from training on your data. A model only suggests. It cannot sign for you or send a message without your tap, unless you gave it a limited permission that you can see and cancel.

Important: We do not train AI models on your data. AI providers process your content only to provide you with the features you request, and under terms that prohibit them from training on it.

6. Who Sees Your Blocks

  • You and the people or businesses you share a block with.
  • Public blocks (for example an offer you choose to publish) can be seen by anyone.
  • Sealed blocks: a public header, and a body that only the named people can open. Servers that carry them cannot read them.
  • Service providers that run our systems: hosting (AWS), message carriers (Twilio for SMS, Africa's Talking, Meta WhatsApp Cloud API, our own SMTP provider for email), payment providers, AI providers (TypeSafe, OpenAI, Google Gemini, and possibly Qwen, Mistral, Moonshot). They act on our instructions.
  • Optional messaging channels you may choose to connect: Telegram, LINE, Viber, KakaoTalk, Zalo. These are used only if you enable them.
  • Law: If a court or authority requires it, we tell you first unless the law forbids.

We never sell data or share it with advertisers or data brokers.

7. Leaving, Access and Deletion

  • Take your record: Export your blocks any time and move them to another node.
  • Leave: Close your account. We delete your Google tokens and your personal account details, and stop reading and messaging you.
  • Honest limit: A block you signed and shared with someone else is, by design, a copy in their record too, and signed history cannot be edited. We will delete what we hold of yours that we can, and stop using the rest.
  • Rights: Access, correction, deletion, objection, portability, complaint to your data authority (in the UK, the ICO). Ask at hello@foodx.network. We answer within one month.
  • Disconnect Google any time in Settings, or at https://myaccount.google.com/permissions

8. Messages and STOP

Reply STOP to any SMS or WhatsApp from us and we stop. A person who said STOP is never messaged again. We do not send a first message to a business or stranger ourselves; you tap send.

9. Security

Encryption in transit (TLS 1.3+) and at rest (AES-256-GCM). Signed blocks. Keys in an encrypted keystore. Access limited. We tell you and the regulator about a serious breach as the law requires.

10. Where Data Goes

Our servers are primarily located in AWS regions (eu-west-2 and us-east-1). International data transfers are protected with appropriate safeguards including standard contractual clauses.

11. Children

FoodX is for people 16 and over.

12. Changes

We tell you before a material change, and give you time to leave.

Contact Information

For privacy-related inquiries, contact us at hello@foodx.network

Company Details:
FOODX WORLD LIMITED
Companies House Registration No. 16406719
Registered in England and Wales

Effective Date: 16 October 2026

Version: 3.0