Privacy notice

wwwebby (“we”, “us”) runs the marketing site you are on, the merchant account system and the store infrastructure behind it. For the personal information in a merchant account, we are the responsible party under South Africa’s Protection of Personal Information Act (POPIA) and the controller under the GDPR where it applies.

Write to hello@wwwebby.co.za for anything in this notice — access requests, corrections, deletion, or a question about a specific row of data.

• Account information. Your email address, a credential (either a password hash or a link to the Google account you signed in with), and your name if you give it to us. Used to let you into your account and to prove you own a store before we hand over its dashboard.
• Store configuration. The store name, web address, plan, storage size, number of bots and add-ons you selected. This is not bookkeeping — it is the instruction sheet for what gets built, and it is what provisioning is allowed to create.
• Your store’s content. Products, prices, images, orders and the details of the people who buy from you. These sit in a database provisioned for your store, reachable only by your store’s own processes. You own this data; we hold it to run the service you paid for.
• Messages you send to your bots. The instructions you type, the replies they draft, and the records they create as they work.
• Technical logs. Server logs, error traces and request metadata generated by the software. Used to keep the platform up and to investigate something that broke.
• Storefront visit counts. Aggregate counts of visits to a storefront, measured without cookies or fingerprints, so a merchant can see traffic without tracking their own customers.

We do not collect payment card numbers. Billing runs through our payment provider, which hands us a result.

One cookie is strictly necessary: the sign-in session. It exists only while you are using your account area, is not used for advertising, profiling or measurement, and when you sign out or it expires, it is gone.

Everything past that is a question we put to you rather than a decision we make. If you accept analytics, PostHog stores a cookie in your browser so a returning visitor counts as one person instead of several, and we learn which pages you read, which plan sheet you opened and whether you asked for a store. We do not send them your email address, your store name or anything from a storefront. If you decline, or never answer, no analytics cookie is set and the tracker is never loaded. There is still no marketing pixel and no social plug-in on this site.

We do not share merchant data with advertisers or data brokers. These providers process it because the service cannot run without them:

• Amazon Web Services (eu-north-1, Stockholm, Sweden) — the servers your store and its database run on.
• Neon — managed PostgreSQL for the account ledger and logins, plus the sign-in service itself.
• Cloudflare — domain name resolution for the addresses you point at us.
• Resend — the email we send you (receipts, setup confirmations, replies to your waitlist entry). They see the address and the message.
• Umami — the cookie-free analytics service reporting your storefront traffic.
• PostHog — product analytics for this marketing site, and only if you accepted. Page views and which buttons you press on our own pages, sent to their United States servers, with no email address and nothing from a storefront attached.
• Integration providers such as Composio — reached only when you connect one of your own accounts (a marketplace, a courier, a spreadsheet). They hold the credential you authorised and act on your behalf under their terms.
• Model providers — when you ask a bot to do something, the instruction and only the store context that task needs are sent to the model service we have configured. We do not send a whole database to a model when a few products will do, and we do not use your store data to train someone else’s model.

Law enforcement or a regulator may compel disclosure. We comply when we must, and we tell you about it unless we are forbidden to.

Merchant infrastructure sits in the Stockholm region of AWS, and the account ledger sits on Neon in the same European region. If you are in South Africa, your information is therefore processed outside the country. We do that under POPIA section 72: the receiving systems are subject to EU-level data protection, the transfers are for the service you asked us to provide, and the operators are bound to confidentiality.

• Each store gets its own database and its own application process. One store cannot read another’s rows, and the application layer cannot be talked into it.
• Access inside a store is scoped to that store: the API checks that the account asking owns the space it is asking about before it answers.
• Every address is served over HTTPS with certificates that renew themselves.
• Entering a store dashboard does not use a password. The account site asks the platform for a single-use entry that expires after one page load, and the platform mints it against the identity that already holds that store.
• Platform access is limited to what an outage or a support request requires, and it is logged.

• Account and store configuration: while your account is open. Close it and we keep the record of what we billed you for as long as tax law requires, and delete the rest.
• Store content (products, orders, customers): 30 days after a store closes, so a change of mind does not cost you your catalogue. Then it is deleted, including backups as they roll off.
• Server and error logs: about 30 days.
• Email we sent you: the delivery record stays with our mail provider for up to a year.

Access, correction, deletion, a portable copy of what you gave us, a say in automated decisions, or a hold on processing. Ask at hello@wwwebby.co.za and we will come back within the time POPIA allows (a month, extended if the request is large). You can also complain to the South African Information Regulator, or to your local data protection authority if the GDPR applies to you.

If your request is about your customers’ data rather than yours, we act on your instruction as the merchant — you are the responsible party for the personal information your store collects at checkout.

The platform is for businesses run by adults. We do not knowingly take accounts from under-18s, and a store built on wwwebby must not market directly to children.

Material changes get announced by email before they take effect, not discovered afterwards. The date at the top of this page is the version you are reading.