Privacy Policy

Last updated: 11 November 2026

This policy explains what emdaad.io collects, why, and how to reach us about it.

Scope

This policy covers emdaad.io: the website, its blog, and the forms on it. It does not cover the Emdaad platform itself — the buyer portal and the admin console that Emdaad's customers and their trading partners use. Data processed inside the platform (customer records, orders, pricing, buyer accounts, and everything else a customer's own tenant holds) is governed by that customer's own contract with Emdaad, not by this document. Where the platform's own data is hosted, and what security or residency commitments apply to it, are matters agreed per customer — this policy makes no statement about the platform.

This policy also describes, in a separate section below, how Emdaad sources contacts for direct sales outreach outside of this website.

1. Who we are

Emdaad is a product of CairoIT Solutions, which operates this website and is responsible for the personal data described here.

2. What we collect, and where it comes from

Browsing the site

Visiting emdaad.io generates:

Usage data via Google Analytics (property G-XSCF3W3BNF) — pages viewed, general usage patterns, and your IP address, which Google uses to derive an approximate location. This runs on every page of the site.
A request to Google Fonts for the page's typeface (Inter Tight on English pages, Tajawal on Arabic) — this sends your IP address to Google as an ordinary part of loading the font file. Per Google's own Fonts FAQ, this request sets no cookies and isn't tied to a Google account — Google receives the IP address only because that's how any request over the internet works, the same as loading an image from any server.
Server logs, kept by our hosting provider, InMotion Hosting — your IP address and request details, the way any web server logs its traffic.

Filling in a form

Each of the forms below exists in English and Arabic.

Request a Demo — full name, job title, company, country, industry, current ordering method, number of buyers/accounts, ERP system, an optional note on what you'd like the demo to cover, and work email. If you arrived from the ROI calculator, the figures you entered there are carried into the same submission.
The Pricing Dispute Workbook download — first name, last name, work email, company, and an optional role, through a HubSpot form. This form asks for two confirmations before it can be submitted: one required ("I agree to allow Emdaad to store and process my personal data") and one optional ("I agree to receive other communications from Emdaad").
The B2B Ordering Scorecard — if you ask for the full breakdown after answering its questions: email, first name, company, and an optional job title, through a HubSpot form. The form also stores your answers to the scorecard and the market you chose in it (Egypt, Saudi Arabia, or other). Like the workbook form, it asks for two confirmations before it can be submitted: a required one, to store and process your personal data, and an optional one, to receive other communications from Emdaad.
Emdaad Weekly sign-up (English and Arabic) — email address (required), and optionally first name and company name, through a HubSpot form. The form also records which language's form you used, English or Arabic, so the email reaches you in that language. It asks for one required confirmation before it can be submitted: that you want to receive Emdaad Weekly.

The HubSpot forms on this site also run Google's reCAPTCHA to filter automated submissions.

Joining Emdaad Weekly without the form. If you tell a member of our team in writing, by email or WhatsApp, that you'd like to receive Emdaad Weekly, we add you in HubSpot ourselves: your email address, your language, and your name and company if we already have them. In your HubSpot record we note when you said yes, how, and who on our team received it, and keep a copy of your message there. We don't add anyone without that written yes.

3. Why we use it

To respond to a demo request, a workbook download or a scorecard breakdown request — replying to you, and, for a demo request, using what you told us about your operation to prepare a relevant session.
To send what you asked for — the workbook you requested, and other communications from Emdaad if you opted in via the optional checkbox on the workbook or scorecard form.
To send Emdaad Weekly, if you signed up or asked us to add you — a short email on Tuesday, in weeks when we've published new articles, with that week's Emdaad articles. Each issue also includes the week's posts from Emdaad's LinkedIn company page, a link to one of our free tools, and a link to request a demo. HubSpot records whether each issue was opened and which of its links were clicked, and the links carry tags that let Google Analytics count visits that came from the email. We use both to see which parts of the email readers find useful.
To measure how the site is used — Google Analytics, for understanding traffic and content performance in aggregate. We do not use it to identify individual visitors by name.
To notify our own team of a new submission, so a request doesn't go unseen.

We do not sell personal data.

4. Who we share it with

We use a small number of outside services to run the site and its forms. Each receives only what's needed for its own job:

Service	What it receives	Where it processes it
Google — Analytics, Fonts, and reCAPTCHA	Analytics: pages viewed, usage patterns, and your IP address, on every page. Fonts: your IP address only, no cookies, when a page loads its typeface. reCAPTCHA: interaction signals used to tell humans from bots, on the HubSpot forms on this site.	Google's global infrastructure.
Formspree, Inc.	Whatever the Request a Demo form collects (see above)	The United States, per Formspree's own published privacy policy. Submissions are forwarded by email to members of the Emdaad team who handle sales and marketing inquiries.
HubSpot	What you enter in the HubSpot forms on this site (see §2: the workbook download, the B2B Ordering Scorecard, including your answers and market, and the Emdaad Weekly sign-up), and contact records used for direct outreach (see §8). For Emdaad Weekly: the sign-up details above, your language, the record of your consent, and whether you opened each issue and which links you clicked. HubSpot also sends Emdaad Weekly for us, so the sender address you see may be a HubSpot address rather than an emdaad.io one.	The European Union (HubSpot's EU data region).
InMotion Hosting	Server logs for every visit to emdaad.io and for the privacy@emdaad.io mailbox	Los Angeles, California, United States

Apart from the services above, and the email providers our team uses to send and receive messages, we don't share personal data with anyone.

5. How long we keep it

Google Analytics keeps event-level data for 2 months and user-level data for up to 14 months, refreshed each time you're active on the site — in practice, a visit resets the 14-month window for that data. Formspree submissions, HubSpot form contacts, and the copies of form submissions forwarded to our team's mailboxes are kept for up to 3 years.

Emdaad Weekly. While you're subscribed, we keep your details in HubSpot. We also keep the record of your consent: how and when you gave it, and when you unsubscribed, if you do. Egyptian law (Law No. 151 of 2020, Article 18) requires that record to be kept for 3 years from the last message sent to you. So for Emdaad Weekly, the 3 years above count from the last issue we sent you, not from when you signed up. After you unsubscribe, your record stays in HubSpot marked as unsubscribed, and that mark is what stops further issues reaching you.

6. Cookies and analytics

Google Analytics sets cookies in your browser to tell visits apart and group activity into sessions; Google Fonts sets none. You can limit this through your browser's own cookie settings, or by installing Google's Analytics opt-out browser add-on, which stops your activity from being sent to Google Analytics on any site that uses it.

The HubSpot forms on this site (the workbook download, the B2B Ordering Scorecard and the Emdaad Weekly sign-up) load from HubSpot. Loading a HubSpot form sets no cookies on emdaad.io itself. HubSpot's own domains, which the forms load from, receive a short-lived security cookie from Cloudflare (__cf_bm) that lasts only for your browser session. The forms also use Google reCAPTCHA (see §2), which sets its own cookie on google.com.

7. Your rights

Egypt's Law No. 151 of 2020 on the Protection of Personal Data and Saudi Arabia's Personal Data Protection Law (issued by Royal Decree M/19 of 2021, amended by Royal Decree M/148 of 2023) both give people rights over their own personal data, generally including the right to know what's held about you, to ask for it to be corrected, to ask for it to be deleted, and to withdraw a consent you previously gave. This section describes how to reach us to ask about any of that; it is not a statement of our specific obligations under either law.

To ask about your data, or to ask us to correct it, delete it, or withdraw a consent, contact privacy@emdaad.io.

Emdaad Weekly. Each issue has an unsubscribe link at the bottom. It opens HubSpot's unsubscribe page, which is in English, where a single button unsubscribes you. On our current HubSpot plan, this unsubscribes you from all marketing email from Emdaad, not only Emdaad Weekly. You can also write to privacy@emdaad.io and we'll unsubscribe you.

8. How we source contacts for direct outreach

Separately from anyone who visits this website, Emdaad's sales team identifies and contacts potential customers directly, using information found through business research tools (including Apollo and LinkedIn Sales Navigator) and public sources such as company websites and LinkedIn profiles. This processing exists to identify companies that may benefit from Emdaad's platform, and to reach the right person at that company. If you've received an outbound message from Emdaad and would like to know what we hold about you, or would like us to stop, contact us at privacy@emdaad.io.

9. Changes to this policy

We'll update this page when what we actually do changes, and revise the date at the top.

10. Contact

privacy@emdaad.io