Privacy

FutureSearch.ie is built around public web search, clear crawler identity, and separation between public results and private operational tooling.

Public web indexing

FutureSearchBot may collect public web pages and public metadata for search indexing, quality checks, snippets, and Irish-business discovery. It is not intended to collect private account content, password-protected pages, or material blocked by robots.txt or noindex directives.

Search usage

Like most web services, FutureSearch.ie may process technical request data such as time, IP address, browser information, requested URL, and error logs for security, abuse prevention, debugging, and service reliability.

FutureSearch.ie may also record aggregate search-quality signals, such as the search query, result counts, whether an empty state was shown, scroll-depth bucket, result-domain clicks, pagination clicks, search-submit events, and page-leave events. These signals are used to improve search quality and launch readiness.

FutureSearch.ie does not use third-party analytics on the public search page, does not set analytics cookies, and does not store IP addresses, user agents, auth tokens, or persistent visitor identifiers in search-quality telemetry. A short random page-event value may be created in memory for one loaded search page so actions on that page can be counted together; it is not stored in the browser and is not used to recognise a person across pages or visits.

Client and private API data

Client-index data, authenticated SEO analysis, prelaunch testing notes, and API-only features are kept separate from the public search surface. Public pages must not disclose API tokens, private crawler fields, or raw private index data.

Removal and corrections

Site owners can ask about crawler behavior, removals, corrections, or blocking at bot@futuresearch.ie. A robots.txt block for FutureSearchBot will be respected for future crawling.

Retention

Search indexes and logs are retained only as long as needed for search quality, security, abuse prevention, audit, or client-service purposes. Index entries may be refreshed, replaced, or removed as the crawler revisits public sources.