Privacy, consent and data deletion for Egyptian stores

Every order hands you a real person's name, a phone number that reaches them, a home address, and a list of what they buy.

That data makes cash on delivery and a WhatsApp follow-up possible — and makes you responsible for it. This is plain guidance, not legal advice, on what Egypt's Personal Data Protection Law (PDPL) asks of Egyptian stores. For anything binding, ask a lawyer.

Collect only what the order needs

A cash-on-delivery order needs a name, a phone someone answers, and a full governorate address. Not a national ID, not a date of birth, not a second "just in case" number. Every extra field is one more thing to store and secure.

• Open Design → Checkout fields. The page says it plainly: "Don't collect data you don't need; answers are stored with the order."
• You get up to 10 active fields; archive what a template added.
• If you must ask something unusual, explain why beside it.
• Plan note: custom checkout fields are blocked on Starter — lists look empty and saving fails with "You don't have permission to do that."

Say how you use it

Tell buyers four things: what you collect (name, phone, address, order history), why (to pack, deliver and support the order), who sees it (your team and the courier), and that you never sell it.

Write it in Arabic and English. Every store starts with a Privacy policy page under Design → Custom pages, public only after you replace the starter text, fill both languages, and press Mark reviewed and publish.

Marketing consent is a separate yes

A buyer gave you their number so their order arrives. That is not a yes to promotions.

1. Use a clear, unticked box: "Send me offers and updates on WhatsApp or email." A pre-ticked box is not consent.
2. Treat WhatsApp and email as different channels; a yes to one is not a yes to the other.
3. Make stopping easy: an unsubscribe link in email, and a "stop" reply on WhatsApp you honour fast.

Add it yourself: Design → Checkout fields → Add field, type Checkbox ("consent, confirmation, or yes/no acknowledgement"). The answer is stored with that order.

One honest limit: Storix keeps no consent ledger. Keep your own sheet — who agreed, to what, where, when. That dated line is your answer later.

When a buyer asks to be deleted

Customers send the deletion request themselves, from their account's privacy page.

1. Open Access & Security → Data access requests.
2. The table shows Request ID, User, Status, Submitted, Grace expires.
3. Click Review, then Approve or Deny.
4. Approve starts a grace period: the message says 14 days, but the real date is Grace expires, set between 7 and 30 days. The buyer can cancel inside it.
5. A daily job at 05:00 UTC anonymises the customer; the status becomes Anonymized.

Deny needs a reason: Outstanding orders, Open chargeback, Active dispute, Legal hold, or Other with an explanation. The customer reads it on their privacy page.

Only the store owner sees and decides these requests — no role delegates it. Customers can download their own data from the same page, once every 24 hours.

What "anonymised" removes

• Orders and their amounts stay, for tax records.
• Removed from the customer and their orders: name, email, phone, city, country, delivery address, your private note, order notes and checkout answers.
• Deleted: saved addresses, wishlist, carts, loyalty points, store credit, saved cards. Referral codes stop, and they can no longer sign in.

Storix gives buyers a privacy page to request or delete their data, and you one screen to approve — try it in your store.

Related lessons

• Essential trust pages for launch
• Team roles and permissions
• Lifecycle messaging on email and WhatsApp