Last updated

Privacy Policy of Masaar Foundation

Browsing data, correspondence and newsletters: how your data is used, the choices available to you and your rights.

This version takes effect on the date it is published on the website.

Submit a privacy request

Policy summary

This policy explains how we handle data when you browse Masaar’s website, use its search functions, contact us or subscribe to the email newsletter. We collect the data needed to provide and protect these services, and we associate each use with a specified purpose and a stated retention period. We do not sell your data or use it to target you with personalised advertising.

Optional analytics operate only after you have given your consent. You can refuse or withdraw consent without losing access to the content. Consent to the newsletter is separate from any other communication with us. We use service providers for hosting, security, analytics and email. These providers may process data outside Egypt, as detailed below.

You may request access to, correction or erasure of your data, withdraw consent or object to processing, subject to the conditions governing each right. To submit a request, use the contact page and write “طلب خصوصية” (“Privacy Request”) in the subject line or at the beginning of your message. Do not send identity documents or highly sensitive information with your initial request.

Data controller and scope of the policy

Masaar Foundation operates masaar.net and is the controller of personal data collected through the website’s services. It is referred to in this policy as “Masaar” or “we”. We determine the purposes and means of processing and are responsible for protecting the data and responding to requests from the individuals concerned.

The Foundation’s Data Protection Officer oversees the implementation of this policy and receives privacy requests and complaints. You can contact the officer through the contact page, writing “إلى مسؤول حماية البيانات” (“For the Data Protection Officer”) in the subject line or at the beginning of your message. Requests are referred to the designated officer, and access is limited to those who need it to handle the request.

This policy covers the Arabic and English versions of the website, including browsing, search, contact and newsletter services. Any new data collection form will display a notice explaining its purpose, required fields, retention period and data recipients before submission. We do not treat a visit to the website as consent to subscribe or to be tracked.

We apply Egypt’s Personal Data Protection Law No. 151 of 2020 and its Executive Regulations issued under Decree No. 816 of 2025 where applicable. Where a particular processing activity falls within the scope of the EU General Data Protection Regulation (GDPR), we comply with its provisions in relation to that activity. This policy does not diminish any legal rights or obligations.

Data we collect and why we use it

Personal data is information that can identify an individual directly or when combined with other information. It includes online identifiers where they make such identification possible. Processing includes collecting, using, storing, sharing and erasing data. The table sets out the scope of processing for each service.

ServiceDataPurpose and legal basis
Displaying pages and protecting the websiteIP address, request time, page address, browser and device information, request outcome and indicators of abuse.Providing the service, diagnosing faults and preventing attacks. We rely on the necessity of fulfilling obligations to protect the service and exercising lawful rights, to the extent permitted by law, while balancing these against visitors’ rights and freedoms.
Site search and the laws aggregatorSearch terms and filter criteria, which may appear in the request URL recorded in technical logs.Displaying the requested results, based on our legitimate interest in providing the search function, while taking your rights and freedoms into account. We do not infer political opinions from searches or build a personal profile of the reader. Optional measurement of search use is subject to consent for analytics.
Contact formEmail address needed for a reply; name or pseudonym; message subject and text; and technical data necessary to prevent abuse.Responding to and following up on your request, based on the specific consent you give when submitting the form after reading its notice. We retain what is necessary to demonstrate that we responded or to meet a legal obligation, in accordance with the retention schedule. Sending a message does not constitute consent to the newsletter.
Newsletter subscriptionEmail address, preferences you select, a record of consent and changes to it, and delivery, bounce and unsubscribe data.Sending the newsletter you agreed to receive and managing its delivery. Sending is based on separate, withdrawable consent; retention of the consent record is based on demonstrating compliance and meeting applicable legal requirements.
Optional analyticsPages visited and visit times, device and browser type, referral source, interactions with links and downloads, and technical identifiers.Understanding how content is used and improving the website after you have given consent. We do not substitute legitimate interest as the legal basis for continued analytics after you have refused consent.

Each form identifies which fields are required and which are optional. You may use a pseudonym. We do not require an identity number or telephone number merely to browse or subscribe. Without a valid email address, we cannot reply to your message or deliver the newsletter. We do not collect message content or form-field values in analytics events, and we exclude personal data that might appear in URLs or search terms from data sent to measurement tools.

Cookies, analytics and your choices

Cookies are small pieces of data stored in your browser. Other storage and measurement technologies perform similar functions. We use what is necessary to provide a function you have requested, protect the connection or remember your privacy choice. We keep these functions separate from optional traffic measurement, even when the same provider supplies both.

The “Privacy Settings” panel offers equally clear options to accept or reject analytics or customise your choices. Analytics remain disabled until you make a choice; closing the panel or continuing to browse does not constitute acceptance. A link to reopen the settings remains available on the website.

We block connections to Google Analytics and Jetpack Stats until you consent to analytics, including measurements that do not use cookies. If you refuse or withdraw consent, we stop sending further data for these purposes and remove the analytics cookies that the website is able to remove. Withdrawing consent does not automatically erase data transmitted previously; you may request the erasure of data that can be linked to you, as explained in the section on your rights.

We retain your consent choice for no more than six months unless you change it or delete your browser data. The settings panel lists the cookies actually in use, their providers, purposes and expiry periods, including security cookies. We do not classify a cookie as necessary merely because its provider describes it as such. Your choices may differ between devices and browsers, and you can also use your browser’s blocking and deletion tools. We do not rely on the Do Not Track signal alone as a dependable way to change these choices.

We disable personalised advertising features, Google Signals, advertising integrations and the transmission of user-provided data to analytics tools. Masaar receives aggregated statistical reports, but a provider may process personal data or identifiers before aggregation. We do not describe data as anonymous merely because names or email addresses are absent, nor do we link analytics to your messages or newsletter subscription.

Email newsletter

Subscribing to the newsletter requires separate consent and confirmation that you control the email address through a verification message. We do not add addresses obtained from correspondence or public sources to the mailing list. We use subscription data to send the Masaar content you have chosen to receive, and we do not share the list with other organisations for them to send their own messages.

We disable tracking of opens and clicks at the individual subscriber level and do not build a record of your interests based on your reading of the newsletter. Delivery, bounce, complaint and unsubscribe data remain necessary to administer it. Disabling click reports does not necessarily stop security processing by Mailchimp: depending on account type and settings, the service may redirect links to check for abuse, as described in its documentation.

You can unsubscribe using the link in every message, without signing in or giving a reason. Unsubscribing stops subsequent mailings, although it may not be possible to recall a message already sent. A request to erase data is separate from stopping delivery. When we delete data, we remove information that is no longer needed, but may retain a limited record to prevent your accidental re-enrolment or to demonstrate legal compliance, in accordance with the retention schedule.

Service providers and data sharing

We limit access to data within Masaar’s team to those who need it to perform their duties. Service providers have different roles depending on the processing activity. Some process data on the Foundation’s behalf; others determine independent purposes and means for certain processing activities under their service terms. Where a provider acts as our processor, the applicable processing terms govern the scope of instructions, confidentiality, safeguards and deletion.

ServiceProcessing associated with the website
InfomaniakHosting the website, its database, logs and backups included in the service. The company states that it hosts customer data in its data centres in Switzerland.
CloudflareDelivering website pages, protecting connections and preventing attacks. Data processed for these functions includes IP addresses, request and browser data, and security indicators.
Google Analytics 4Measuring use after consent, subject to the safeguards described in the analytics section. Message text and subscription data are not sent to it.
Jetpack by AutomatticEnabled security, performance and statistics features. Jetpack Stats requires consent and is kept separate from protection functions. If Jetpack forms are used, responses may be stored in the website database, sent by email and synchronised with the service, depending on its settings.
Akismet by AutomatticChecking messages submitted through forms connected to the service to combat spam. It may receive message content, sender details, IP addresses and browser information. This is stated in the notice displayed on any form using it.
MailchimpManaging subscribers, sending and delivering the newsletter, and processing bounces, complaints, unsubscribes and consent records.
Gmail by GoogleReceiving, replying to and storing the Foundation’s correspondence through a standard Gmail account. Processing includes message content, submitted attachments, email addresses and delivery information, and may take place outside the sender’s country.

We remain responsible for selecting these services, configuring their use and informing you what data the website sends to them. Referring you to a provider’s privacy policy does not remove that responsibility.

Processing correspondence through Gmail

We use a standard Gmail account for correspondence. Google’s processing of data is subject to its terms of service and privacy policy. Gmail’s documentation explains that the service processes email data to provide its functions, including spam detection, and that certain smart features and personalisation depend on account settings. Google states that it does not use message content to select ads within Gmail. This does not mean that the processing required to operate and protect the email service does not occur.

We do not publish your message or use it for publicity without separate consent for that purpose. If we need to use it for another purpose that requires your consent, we will seek that consent before doing so.

External content and cross-border data transfers

The website includes links to external platforms, including podcast listening platforms. When you open an external link, your visit to that platform is governed by its policies. An embedded player, map or video on Masaar, however, may connect to its provider without your leaving the page. We block optional external content from loading until you choose to activate it after being informed of the provider and the data it receives. We also offer an external link if you do not wish to load that content on the website.

We also review the loading of fonts, images and files from external sources and host them locally wherever possible. Any external connection that processes visitor data is included in our inventory of services and its associated notice, even if it does not use cookies.

Website data is hosted by Infomaniak in Switzerland. Mailchimp data is stored in the United States, with subprocessors in other countries. Google services, including Gmail and analytics, use globally distributed infrastructure and may process data on servers outside your country. Automattic and Cloudflare also use international infrastructure and services. Hosting the website in Switzerland therefore does not mean that all browsing, correspondence and newsletter data remains there.

Each service’s terms and policies specify the parties’ roles, processing locations and applicable safeguards. Google explains its data transfer frameworks, including adequacy decisions, data privacy frameworks and standard contractual clauses where applicable. The policies of Cloudflare, Automattic and Mailchimp describe their international processing practices. The applicability of these mechanisms depends on the country of origin, the recipient and the type of service; they are not one universal safeguard covering every transfer.

We undertake to meet the cross-border transfer requirements applicable to the Foundation, including any safeguards, licences or permits required by Egyptian law. Consent to the newsletter or analytics does not replace these requirements. Where the GDPR applies, a transfer must be based on the appropriate legal mechanism and necessary safeguards. You can ask the Data Protection Officer for information about transfers of your data and the applicable safeguards, or copies of documents that may lawfully be disclosed.

Retention periods and deletion

We delete data when the purpose for which it was collected ends or in response to a valid erasure request, unless limited retention is required for a specified legal reason. The following are maximum periods for data whose retention Masaar controls; they do not justify keeping data that is no longer needed.

Data categoryRetention period or criterion for its expiry
Contact messages and working copies in email and the website databaseUntil the request is closed, followed by no more than 90 days for necessary follow-up, including deletion from the account’s Trash folder. We review open requests every 90 days to ensure that no request remains open without a genuine purpose.
Messages classified as spam by Masaar30 days for review and correction of misclassification, followed by deletion.
Operational and security logs whose retention period Masaar controls30 days from recording. Data related to a specific incident is segregated until the investigation or legal obligation ends, with the need for retention reviewed every 90 days.
Newsletter data in the mailing listFor the duration of the subscription. We stop sending messages on unsubscription and delete unnecessary profile details within 30 days, keeping the evidence and suppression records below separate.
Evidence of newsletter consent and changes to itWhere direct marketing provisions apply, three years from the last message sent, under Article 18 of Egyptian law. Otherwise, 12 months after the subscription ends to demonstrate compliance, unless the need ends earlier.
Minimum suppression record to prevent unintended resubscriptionWhile the mailing list operates and there remains a genuine need to prevent messages being sent to the address, with an annual review and deletion when the need ends. It is not used for analytics or sending messages.
Record of rights requests and how they were resolved12 months after the request is closed, to demonstrate a response and follow up on complaints, with the content reduced to what is needed for that purpose.
User and event data subject to the retention setting in Google AnalyticsTwo months, with the option to reset the user identifier’s retention period on new activity disabled. This limit does not cover standard aggregated reports that are not subject to that setting.
Jetpack Stats logs containing visitor identifiers28 days at Automattic, according to the service documentation. This applies to Stats logs only and must not be generalised to Jetpack’s other functions.
Backups managed by Masaar or whose retention periods it controlsA cycle of no more than 90 days, with restricted access and no use for routine purposes. If a backup is restored, we reapply erasure requests before returning the data to active use.

Google Analytics deletes data subject to its retention settings through a monthly deletion cycle. We therefore distinguish between the configured retention period and the provider’s execution date. Statistics that cannot be used to identify individuals may be retained without being linked back to people. Google explains the scope of its retention setting, and Jetpack explains the retention period for Stats logs.

We distinguish between deleting a message from the Gmail account and its complete erasure from Google’s systems. A message remains in Trash for up to 30 days unless permanently deleted sooner; meeting the Foundation’s retention limit therefore includes deleting it from Trash. Google’s retention policy explains that deletion from its systems usually takes around two months and that data may remain in encrypted backups for up to six months, with specific retention exceptions for security or legal obligations. These are the provider’s timeframes and do not entitle the Foundation to keep an active copy after its stated retention period has expired.

Akismet states that it retains most anti-abuse data for between two weeks and 90 days, with limited categories retained longer. Automattic explains that it normally retains web server logs for around 30 days and deletes other visitor information when it is no longer needed, unless legal retention is required; the Stats period in the table remains specific to that service. Cloudflare determines retention according to the processing purpose, the nature and sensitivity of the data, security needs, and legal or contractual obligations. Its general privacy policy does not specify one uniform retention period for all this data.

We follow up deletion requests with providers and explain what has been deleted and what continues to be retained for a specified reason. We do not describe data as erased from a third party’s systems before verifying this. Copies managed by the Foundation, or whose retention periods it controls, remain subject to the limits stated in the table.

If an ongoing dispute or legal provision requires data to be kept longer, we document the reason, category and period or criterion for its expiry, restrict access and use, and delete the data once the reason no longer applies. We explain why erasure cannot be completed and the applicable date or criterion, unless disclosure is prohibited by law. The existence of a backup does not justify retaining an active copy after its purpose has ended.

Your rights and how to exercise them

You may ask us to confirm whether we process data about you, access it and obtain a copy, and learn its purposes, sources, recipients and retention periods. You may request correction, completion or erasure, or restriction of processing to a specified scope, and object when processing conflicts with your rights and freedoms. You may withdraw consent without retroactively affecting the lawfulness of previous processing, and obtain your data in a machine-readable format where the conditions for data portability are met.

Submit your request to the Foundation’s Data Protection Officer through the contact page, specifying the service, the right you wish to exercise and an email address for the reply. We verify your connection to the data by proportionate means, such as confirming that you control the email address concerned. We do not routinely request an identity document; if additional information is needed, we explain why and limit the request to what is necessary without disclosing another person’s data.

We respond within six working days of submission, stating the action taken or providing a reasoned decision explaining any applicable legal restrictions. We fulfil valid requests without undue delay and observe the implementation deadlines set by the applicable law. An automated acknowledgement of receipt alone is not treated as a substantive response, and we do not leave a response indefinitely pending while corresponding with an external provider. This is the response period provided for in Article 32 of Egyptian law.

If we cannot securely link analytics data to you, we explain this and identify what action is possible. We do not collect new identifying information solely to de-anonymise statistics that do not identify individuals. Requests concerning data included in research materials or published documents are handled with due regard for privacy, freedom of expression, the public interest and applicable law. Deleting your subscription data does not automatically require the removal of a published work.

You may ask for a review of our response or complain to Egypt’s Personal Data Protection Center through its official channels, without first having to exhaust our internal review process. Your right to seek judicial redress remains unaffected. Where the GDPR applies, you also retain the right to lodge a complaint with the competent supervisory authority under its rules.

Data security and disclosure requests

We use HTTPS connections, restrict permissions according to need, and secure administrative and service accounts with multi-factor authentication where available. We regularly review access, updates, backups and deletion procedures. Connection encryption protects data in transit, but does not make the contact form an end-to-end encrypted channel or prevent processing needed by the hosting and email services.

The contact form is intended for general correspondence. Do not use it to send passwords, identity documents or sensitive details about yourself or others. If you need to share sensitive material, use a brief initial message to request arrangements for a suitable channel. Masaar’s team does not upload contact messages or subscriber lists to public generative AI tools, nor use them to train models for Masaar’s benefit. Automated message screening by the anti-abuse service remains subject to the service’s stated scope and agreements, including checks on whether the provider uses the data to improve its systems.

When a data breach is detected, we contain the incident, assess its impact and document our response. Where Egyptian law applies, we notify the Center within 72 hours of becoming aware of the breach, and immediately in cases where the law requires immediate notification. We notify the individuals concerned within three working days of notifying the Center. The notification describes the nature of the incident, the affected data, known consequences, actions taken and steps individuals can take to protect themselves. We update it when material new information emerges.

We do not disclose your data to the authorities merely because they make an undocumented request. We examine the requesting body’s authority, the legal basis and the scope of the request, restrict disclosure to what the law requires, and seek to challenge unlawful or excessive requests through available legal means. We notify you where the law permits and where notification would not endanger anyone’s safety. We cannot promise absolute confidentiality in the face of a legally binding order, and we document each disclosure and its reason.

Children’s data

We do not offer services specifically directed at people under 18, nor do we request dates of birth to verify the ages of all visitors. Technical logs may record a child’s visit without our knowing their age; data minimisation and protection measures also apply to those logs.

If we learn that a child’s data has been submitted through a form or subscription without the legal requirements being met, we stop unnecessary use and delete or restrict the data pending a lawful resolution. Any intentional collection of a child’s data requires an appropriate notice and compliance with applicable parental consent, protection, and licensing requirements before collection. You can report such cases through the contact page without sending additional sensitive information in the initial report.

Changes to this policy

We review this policy when a service, processing purpose, retention period or transfer safeguard changes, or when legal requirements change. We publish the date of the latest update, the effective date and a brief record of material changes, and notify those affected by important changes through an appropriate channel. If a new purpose requires fresh consent, we seek it before processing begins.

Continuing to browse does not constitute consent to new optional processing, and updating this policy does not extinguish an existing right. We keep the commitments in the Arabic and English versions consistent and make earlier dated versions available.

The Foundation’s Data Protection Officer

Submit a privacy request