Privacy Policy

The short version of this privacy policy: this site collects the minimum it needs to operate, and nothing it collects is ever sold. If you fill the contact form, I receive your name, email and message so I can answer you. That is the only moment you actively hand over personal data, and it goes to my inbox and CRM, nowhere else.

Passively, the site uses analytics to understand which pages help visitors and which do not. That runs through Google Analytics 4 and PostHog, with traffic served through Cloudflare. Each processor is bound by its own privacy terms, linked here so you can read exactly what they do.

Your rights under this privacy policy are practical, not theoretical: ask what data exists about you, ask for a copy, ask for deletion, or withdraw consent for analytics cookies entirely. Cookie specifics live in the cookie policy, engagement terms in the terms of service, and access commitments in the accessibility statement. Requests go to the email at the top of this page and get answered by a person, not a queue.

Nothing on this site requires an account, there is no advertising network dropping third party trackers, and no data broker relationship exists. A privacy policy should be boring; the practices behind this one are deliberately boring too.

Contact form submissions. What: name, email address, company, message text. Why: to answer your inquiry and, if an engagement follows, to run it. Where: email inbox and the CRM. Lawful basis: your explicit action of sending the form. Retention: while the conversation or engagement is live, deleted on request. This privacy policy treats a form submission as the start of a business conversation, nothing more.

Analytics events. What: pages viewed, time on page, referral source, country-level location, browser and device class. Why: to learn which content helps visitors and which channels bring them. Where: Google Analytics 4 and PostHog, both configured without advertising features. Lawful basis: consent given through the cookie banner. Retention: the processors' standard windows, after which data is aggregated. No cross-site tracking, no remarketing audiences, no profile building.

Server and security logs. What: IP addresses and request metadata, held briefly by Cloudflare and the hosting layer. Why: protection against attacks, spam and abuse. Lawful basis: legitimate interest in keeping the site online. Retention: short, rolling windows defined by each provider.

What this privacy policy excludes by design. No accounts and no passwords, so no credential database can leak. No payment processing on this domain: invoicing happens through licensed accounting software, separately and lawfully. No advertising pixels owned by social networks. No purchase of third party data about visitors, ever.

International transfers. The processors named here operate global infrastructure, so analytics data may be stored outside Israel or the EU. Each processor maintains its own transfer safeguards, documented in the linked privacy terms. If you want your data excluded from this entirely, decline analytics in the banner; the site works identically.

Changes to this policy. Material changes appear on this page with an updated date. The practices described here are stable by intent: the site collects little because it needs little.

Access requests. Email with the address you used on the form. You receive a copy of every record tied to that address: the submission itself, any notes, and whether analytics consent exists for your browser. Verification is by reply from the same address, nothing more invasive.

Deletion requests. Same channel. Form records are deleted from the inbox and CRM; you receive written confirmation listing what was removed. Where an engagement created invoices, the lawful accounting records remain, because tax law outranks any privacy policy, and that boundary is stated here rather than discovered later.

Consent withdrawal. Clear your cookies for this domain or use the banner to revoke analytics consent. From that moment the analytics tags stop firing for your browser. Historical aggregated counts are not re-identified or retroactively edited because they cannot be tied back to you.

Timelines and escalation. Requests are acknowledged within days and completed without bureaucratic delay. If you believe a request was mishandled, you can escalate to the Israeli Privacy Protection Authority; this privacy policy will never treat that as hostility.

Questions this page did not answer. Privacy questions that fall outside this privacy policy, such as how a specific engagement handles your company data, belong in the signed scope and its confidentiality clause. For anything else, the contact page reaches a person who answers privacy mail with the same priority as sales mail, because trust converts better than any landing page.