Privacy
What Sowo keeps
Sowo answers buyers on WhatsApp for a vendor's shop. This page says, plainly, what it stores to do that, who else sees it, and how to have it deleted.
Last updated 29 October 2026.
What a buyer's message brings with it
A buyer's WhatsApp phone number, the name they give us, and the messages they send.
The orders that come out of those messages: the items, the delivery area, the price the server agreed, and whether the buyer said they had paid by bank transfer.
What a vendor hands over
The vendor's email address, shop settings (owner name, WhatsApp number ID, alert phone), and the bank details shown to buyers when payment is by bank transfer.
Product listings and the floor prices the assistant is not allowed to go below.
Who reads the conversation
The vendor, in their dashboard, and the open-weight Qwen3 model served through Groq, which drafts each reply. A message is sent to that model only to answer it.
We do not sell data and we do not use buyer messages to train a model.
Money
Bank transfers happen between the buyer and the vendor, outside Sowo. A buyer's receipt is a note on the order, not a payment.
When card payment is switched on, Paystack handles the card and Sowo never sees the card number.
Where it lives
In a Postgres database hosted by Neon (AWS, London) and a web service on Render. The site itself is served by Vercel.
Access tokens and app secrets are held as environment variables, never in the code, and the source is public.
Keeping it, deleting it
Conversations and orders are kept while the shop uses Sowo, so the vendor can look back at a sale.
Ask for your shop and its conversations to be deleted and we remove them. Open an issue on GitHub and we will take it from there.
Questions
Sowo is open source. Open an issue at github.com/adeyanjufuhad/sowo/issues and we will answer there.