Privacy Policy

The site owner who embeds the widget is the controller of their visitors' data and their site content. We act as a processor on the owner's behalf, and Google Cloud is a sub-processor (Vertex AI Search / Discovery Engine and Gemini for indexing, search, and answer generation; Cloud Storage for intermediate index-import storage; Firestore for accounts, configuration, query logs, and audit records; and Firebase Authentication / Identity Platform for authentication and sessions). For the owner's own account (email, payments) we are the controller.

We also process visitor query text to a limited extent for our own purposes — quality metrics and abuse protection; in that narrow part we act as an independent controller. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in keeping the service operational, secure, and accurate; we carried out a legitimate-interests assessment (LIA), and this interest does not override data-subject rights.

Payments are handled by Paddle as Merchant of Record: with respect to the payment transaction, Paddle acts as the merchant of record and an independent controller of payment data, not as our sub-processor.

• Site content — the owner's public pages are indexed so answers can be grounded in them.
• Visitor queries — question text is sent to Google Vertex/Gemini to generate an answer.
• Visitor technical data — the IP address is processed transiently in memory for abuse protection and rate limiting and is not stored in logs or a database (data-minimization principle).
• Usage metrics — query counts and answer quality (no content beyond what's needed).
• Owner account — email and billing data (payments are handled by Paddle as Merchant of Record; we don't store card details).

Our public site may use analytics cookies — these are set only with your consent; see the Cookie Policy for details.

Children's Privacy. The service is a B2B product and is not directed to children under 16. We do not knowingly process personal data of children.

Answer generation, indexing, and supporting processing run in the service's configured Google Cloud region under Google's enterprise terms. Under those terms, Google does not use data submitted to Vertex AI and the Gemini API to train its models. We likewise do not use your content or queries to train any models.

The service operator is established in Israel. Transfers of personal data from the EU to Israel rely on the European Commission's adequacy decision for Israel; transfers to Google's services are governed by Google's Cloud Data Processing Addendum and, where needed, Standard Contractual Clauses (SCCs) and/or the EU-US Data Privacy Framework.

AI transparency. Answers are produced by artificial intelligence from indexed content; the widget interface indicates that the AI is answering, and answers carry links to their sources.

• Google Cloud — Vertex AI Search (Discovery Engine) and Gemini — indexing, search, and answer generation.
• Google Cloud Storage — intermediate staging of extracted text for import into the index.
• Google Cloud Firestore — owner accounts, service configuration, query logs, and audit records.
• Firebase Authentication / Identity Platform — account authentication and session management.

Paddle processes subscriptions and payments as Merchant of Record and, in that role, acts as an independent controller rather than a sub-processor.

A current list of sub-processors is available on request. We give advance notice of planned changes to our sub-processors and provide an opportunity to object.

Before you make a choice in the banner, the Google tag operates with storage denied and may send Google LLC cookieless technical signals—such as the page URL, referrer, consent state and whether ad-click information is present—for aggregate reporting and modelling. Analytics and advertising cookies are not set or read. The basis for this minimal processing is our legitimate interest (Art. 6(1)(f) GDPR) in measuring the effectiveness of our public site while applying data minimisation.

If you consent to advertising-measurement cookies, Google receives the fact that a conversion occurred and the identifier of the ad click that preceded it. This is used solely to measure how our advertising performs. The legal basis for full measurement is your consent (Art. 6(1)(a) GDPR); you may withdraw it at any time via the “Cookie settings” link in the site footer. We do not enable advertising personalisation, and this data is not used to build profiles for advertising on other sites.

Retention periods:

• Visitor IP addresses — not stored: processed only transiently in memory for abuse protection and discarded immediately after the request is handled.
• Visitor query text — 90 days, after which it is anonymized or deleted; aggregated metrics without personal data may be kept longer.
• Indexing artifacts in intermediate storage — deleted on a schedule, typically within 7 days.
• Site index — while the project is active; when a project is closed, the index and related resources are deleted.
• Owner account data — while the account is active; after closure it is deleted, subject to mandatory retention periods (for example, accounting and tax).

Data subjects may request access to their data, its correction, deletion, or restriction of processing, and may object to processing; under the CCPA — to know the categories of data, request deletion, and opt out of a “sale” (we do not sell data). Because the operator is established in Israel, the Protection of Privacy Law (PPL) as amended by Amendment 13 also applies: rights of access and correction, transparency requirements, and notification of serious security incidents to the regulator.

How to submit a request (DSAR). Requests about visitor data are directed to the site owner as the controller — we, as the processor, assist them (locating and deleting data, log clean-up, project deletion). Requests about owner account data should be sent to us via the contact form. We respond within the timeframes set by applicable law (under GDPR, generally within one month).

We cannot contract away mandatory GDPR/CCPA/PPL obligations — responsibility is allocated by law.

Data is transmitted over TLS; service-account access follows least privilege. Queries are sanitized and rate-limited before any paid service is called (protection against injection and denial-of-wallet). Projects are isolated: each runs against its own index. When enabled, Google reCAPTCHA Enterprise is used in optional monitor-only mode for bot and abuse detection and may process visitor interaction signals subject to Google's privacy terms; the widget may send no token.

In the event of a serious security incident affecting personal data, we notify the competent authority (in Israel, the Privacy Protection Authority, PPA) and, where required by law, affected individuals and the site owner, within the applicable deadlines.

Beta service privacy and DSAR requests: submit them through the contact form.

For requests about visitor data, contact the owner of the client site as the data controller.