Privacy Policy

Account: your email address, and if you sign in with Google, the name and profile picture Google shares with us. We do not receive your Google password.

Orders: the phone number, pickup or delivery address and notes you enter when ordering, and the order history itself. Shop owners see the contact details of their own customers so they can hand over the goods.

Payments: card payments are handled by Stripe. Stripe receives your card details; we receive only a token, the card brand and last four digits, and the payment result. Shop owners who accept Zelle or Venmo list their own handles, which you see only after placing an order.

Shop owners: if you accept card payments, the business details you give Stripe during that setup are held by Stripe. We store your shop name, pickup address, service area, the Zelle or Venmo handle you choose to publish, and the status flags Stripe reports back (whether charges and payouts are enabled, and what documents are still due).

Transfer proofs: if you pay a shop owner by Zelle or Venmo and upload a screenshot, we store that image and an automated reading of it. The reading is done by an AI model and typically extracts the amount, the date, the sender’s name and the last four digits of the account shown in the screenshot. See “Automated reading of transfer screenshots” below.

Technical: server logs with IP address, browser type and the pages requested, kept for security and debugging.

We set a session cookie so you stay signed in, and a language cookie (eg_locale) so the site remembers whether you read it in English or Chinese. We do not use advertising or cross-site tracking cookies.

To run the market: show you shops, take and fulfil orders, charge the right amount after weighing, send the emails and text messages an order needs (order confirmations, sign-in links, pickup notices), pay shop owners, and handle refunds.

To keep it honest: detect fraud, reused transfer screenshots, duplicate accounts and abuse.

We do not sell your personal information and do not use it for third-party advertising.

Shop owners see the contact details and order contents of their own customers. Stripe processes card payments, and the identity checks for shop owners who accept cards, under its own privacy policy. Amazon Web Services hosts the site, database, images and email sending. Google provides sign-in if you choose it. Where AI is used to read a transfer screenshot, the image is processed by a model hosted in our AWS account and is not used to train it.

We disclose information when the law requires it, or to protect the safety of users and the platform.

When you pay a shop owner by Zelle or Venmo, you can upload a screenshot of the transfer so the shop owner can match it against their own bank or app. To save them squinting at a phone photo, we send that image to an AI model — Claude, running on Amazon Bedrock inside our own AWS account — and ask it to read the values off the screen.

What the model extracts is stored with the screenshot: the payment app, the amount, the date, the name shown as the sender, the payment memo, and the last four digits of the account if the screenshot shows them. We also compute a fingerprint of the image so we can tell when the same screenshot is submitted for two different orders.

Three things about how this is set up. The image is processed inside our AWS account and region; it is not sent to a third-party AI service and it is not used to train any model. The result is advisory only — it never approves or releases an order by itself. A screenshot is not proof that money arrived, so the only thing that releases an order is the shop owner confirming they saw the payment in their own account.

You do not have to upload a screenshot at all; it is a convenience for the shop owner. If you delete your account, the screenshots and everything read off them are deleted with it.

You can view and change your language and contact details in the site. You can stop text messages by replying STOP.

You can delete your account yourself, at any time, from the Account page on this site or from the everygrocer app. Deleting removes your email address, name, profile picture and sign-in, the contact details and delivery address on your past orders, any transfer screenshots you uploaded and everything read off them, and your family & friends list. It takes effect immediately and cannot be undone. What we have to keep is the amount, date and status of orders you already placed — tax rules require it and the shop owner has to be paid — and those records no longer carry your name, email, phone number or address. The full explanation, including the few cases where deletion has to wait (an order still in progress, or a shop owner with money not yet settled), is at everygrocer.com/account-deletion.

California residents have the right to know what personal information we hold about you, to receive a copy, to have it deleted, and to not be discriminated against for exercising these rights. Deletion is self-service, as above. For a copy of your data, or if you cannot sign in to delete the account yourself, email privacy@everygrocer.com from the address on your account; we will verify it is you and respond within 45 days.

Residents of other places with similar rights may use the same address.

We keep account data while your account is open and order records for as long as accounting and tax law requires. Data is stored in the United States. We use encrypted connections and limit access to the people who need it, but no system is perfectly secure.

The site is not directed at children under 13 and we do not knowingly collect their information.

We may update this policy; the date at the top tells you when. Questions go to privacy@everygrocer.com.