Legal

    Privacy Policy

    Term #115

    A document on the site explaining what data is collected, how it's used, who it's shared with, and users' rights. Legally required in Israel (Privacy Protection Law), under GDPR, and under CCPA.

    In practice

    A privacy policy isn't just a legal requirement — it's a trust signal. Customers who read it (a minority) plus customers who simply notice it exists (the majority) create a signal that you're a serious business. A store without a privacy policy is a warning sign.

    Common misconception

    'All privacy policies are alike — you can just copy one.' Not true. A privacy policy needs to reflect the data you actually collect. If you use Google Analytics, the Facebook Pixel, and Klaviyo, all of them need to be listed. A privacy policy that doesn't reflect reality is worse than having none.

    How to fix it

    Outdated privacy policy? (1) Check every tool receiving data from your site (GA4, Meta Pixel, Klaviyo, Hotjar) — all must be listed, (2) update it every year — any tech-stack change means a policy update, (3) free generators: Termly, PrivacyPolicies.com — 15 minutes.

    Example

    An accessories store had a 2019 privacy policy that didn't mention the Meta Pixel or Klaviyo. An EU customer requested a data report (a GDPR subject access request). The policy didn't match reality — a legal exposure. Fixing it took 3 hours plus a one-hour legal consultation.

    Priority

    Update your privacy policy before any campaign targeting Europe. It takes 30 minutes with a generator plus a 15-minute review. Not a huge investment, but the downside (fines, lost trust) is significant.

    Jimmy tracks your Privacy Policy, automatically

    WhatsApp alerts when something important changes. No dashboards, no hassle.