Privacy policy
How this research workspace handles information.
Effective 1 November 2026. Estate Signal is a privately operated real estate research application. It helps its owner automatically discover Egyptian property projects and analyze keyword demand. It does not buy or publish advertising.
Information stored
The workspace stores automatically collected public project names, developer and location information, optional owner records, watchlist selections, generated keyword lists, research metrics, source URLs, discovery timestamps, public feed announcements, and synchronization logs in the operator’s MySQL database. It does not include a buyer lead collection form or a customer CRM.
Google account data
When the operator configures a Google Ads connection, the app uses authorization credentials to request keyword historical metrics for the selected advertising account. These include estimated search volumes, advertiser competition, bid ranges, and monthly search history. This release does not modify campaigns, budgets, or advertisements, and does not import customer contact lists.
Google OAuth credentials are configured in the server environment and are not displayed in the browser. The app uses them only to provide the requested research functionality. Estate Signal does not sell Google user data, use it for advertising to users, or use it to train generalized AI models.
Sharing and network requests
Keyword terms and the selected account identifier are sent to Google when refreshing research. Monitored developer and publisher websites receive scheduled requests from the server to retrieve public catalogues, robots policies and news feeds. Hosting and database providers used by the operator may process stored data as part of operating the service. No third-party advertising trackers or analytics scripts are included in this application.
Cookies and access
A required, HTTP-only session cookie keeps the workspace owner signed in for up to seven days. Signing out removes it. Login attempts are temporarily counted to limit repeated password guesses. Public product and policy pages do not expose private workspace records.
Retention and removal
Project and research records remain until the operator removes them from the database. Public feed entries, source-monitor state and worker heartbeat are retained in the same database. The owner controls database exports, deletion, and backup retention on their server. Removing Google credentials stops future Google synchronization; previously stored research remains until deleted. Google account authorization can also be revoked in Google Account permissions.
Contact and requests
For access, correction, or removal requests, contact bassem.aly.88@gmail.com.
Updates
This page will be updated when the app’s data handling changes. The effective date above identifies the current version.