Your customers' trust, kept.
Security and data handling for your AI shopping assistant
An AI assistant talks to your customers and touches your catalog and orders. This is how we keep that safe, in plain words.
- conversation ever trains an AI model
- No
- enforces the products you never sell
- Server
- encrypts every credential you give us
- AES-256
- confirms every order, every time
- Shopper
In short
Hephon Commerce never uses a conversation to train an AI model: every model request is sent with data collection refused. Its application and database run on servers in the European Union, platform credentials are encrypted, and shopper data is kept for the period the retailer sets and deleted on request.
Products a retailer never sells are removed by the server before the assistant sees the catalog, and no order is placed without the shopper's confirmation. Hephon Commerce holds no ISO or SOC certification and does not claim PDPL compliance.
Updated
Safe by design, not by policy alone.
- No training on your data
- Every AI request that can carry conversation data goes out with data collection refused.
- Rules on the server
- Products you never sell are removed before the assistant sees the catalog, so no prompt can bring them back.
- Encrypted secrets
- Platform credentials and webhook secrets are encrypted with AES-256-GCM, each bound to its own record.
- Invite-only access
- Accounts are created by invitation only, with roles per store and team.
- Passkeys
- Your team can sign in with passkeys instead of passwords.
- Hosted in Europe
- Application and database servers in Amsterdam; product embeddings in Google Cloud's Netherlands region.
Are our conversations used to train AI models?
No. Every request to an AI model that can carry a shopper's words, your catalog or a basket goes out with data collection denied, so it is routed only to model hosts that do not store or train on it. This holds on every channel: your app, your website, WhatsApp and calls. Our own test benches read only test conversations, never your shoppers' real ones, and a check in our build pipeline keeps it that way.
Where is the data stored and processed?
The application and its database run on servers in Amsterdam, in the European Union, and product search embeddings are computed in Google Cloud's Netherlands region. Writing a reply, turning speech into text and checking search results need AI providers, and some of them are in the United States. Each one is named on the subprocessors page with what it sees. Data is not stored in Saudi Arabia or the UAE today. If you need it to be, tell us and we will go through it with your team.
Who can see our shoppers' conversations?
Your team, in your inbox. Accounts are created by invitation only, with roles, and your team can sign in with passkeys. Every conversation, voice note and call is there with its transcript, and anyone on your team can take over a chat. Photos and voice notes shoppers send are served only to your signed-in team, never through a public link. Each retailer's data is kept apart by organization in every query. At Hephon, production access is limited to named staff, and admin actions are logged.
How are our credentials protected?
Platform credentials, WhatsApp tokens and webhook secrets are encrypted with AES-256-GCM, each bound to the record it belongs to, so a value copied to another record will not open. They are never shown again after you save them. API keys you create are scoped to what each one is for. Your app and website open the assistant with a launch token your server signs, and you can refuse every chat that does not have one. Only the websites you allow can frame the chat or talk to it.
How long is data kept, and can it be deleted?
You set the retention period, from 7 days to 10 years; it is 365 days by default. A daily job deletes conversations older than that, with their messages, baskets, checkouts and calls. Phone numbers and email addresses in shopper messages are masked in the stored copy by default. Call recording is off unless you turn it on.
A shopper can ask for their data to be deleted. Your team makes the request in the dashboard, or your systems send it through the API, and it removes the shopper's conversations, profile and sessions. You can follow each request, and your server receives a webhook when it is done.
How are product rules enforced?
On the server, never by the prompt alone. A retailer can hide alcohol, pork or tobacco, or all three for a Halal store. Each product is judged by an AI model, not a word list, and our server removes the hidden ones before the assistant sees the catalog, on every channel. A product that has not been checked yet stays hidden. On WhatsApp, alcohol and tobacco are always excluded. Only Hephon staff can loosen a restriction once it is live.
Orders follow the same idea. No tool the assistant can call places an order. An order is placed only by the shopper's tap on a checkout, a signed checkout page, or keypad 1 after the basket is read back on a call.
What about the PDPL in Saudi Arabia and the UAE?
We do not claim PDPL compliance: it depends on the whole processing, including yours. We explain how Hephon Commerce handles data under each law, and go through your requirements with your team before launch. The details, with dated sources, are on PDPL and your shoppers' data.
What we do not claim
- No certification. Hephon Commerce holds no ISO 27001 or SOC 2 certification.
- No compliance badge. We do not claim Saudi or UAE PDPL compliance.
- No local hosting today. Data is not stored in Saudi Arabia or the UAE, and some AI providers are in the United States.
- Legal pages are drafts. The data processing agreement, subprocessors list, privacy policy and terms below are drafts pending legal review.
Shopper privacy, built in.
- No shopper accounts with us
- Shoppers talk to your store. Their conversations belong to you.
- Deletion on request
- A shopper can ask for their data to be deleted, and your team follows each request in the dashboard.
- Private media
- Photos and voice notes shoppers send are served only to your signed-in team.
A security review in three steps.
- 1
Send us your requirements
Your security questionnaire, data residency needs and the laws that apply to you, such as the Saudi or UAE PDPL.
- 2
Go through them together
We answer each point with your team, with the data processing agreement and the subprocessors list.
- 3
Set your controls
Retention period, masking, team roles, product rules and who may open the assistant, before shoppers see it.
Security, answered.
See it on your own catalog.
We set up a demo with your products, your branches and your shoppers' languages.
