Your information

Privacy policy

Effective 23 September 2026

AutoLead is a private operator tool, currently preparing for launch. This policy explains this public website and the Google connections available to the authorized operator.

Who operates AutoLead

AutoLead at nonono.ai is operated by an independent operator based in Israel. For privacy questions, access requests, corrections, or deletion requests, contact yochai.akoka@gmail.com.

This public website

The public pages do not contain account-registration or lead forms, advertising pixels, analytics scripts, or embedded third-party content. They do not set advertising or analytics cookies.

Serving a page necessarily involves technical request information, such as an IP address, requested address, browser information, and request time. Hosting and network services may process this information to deliver the site and protect its availability and security.

The separate private owner workspace at app.nonono.ai uses an essential authentication cookie after sign-in. This cookie contains signed session information, not provider API keys. It expires automatically, and signing out removes it from the browser. It is not used for advertising or analytics.

If you email the operator, your email address and the information you choose to send are used to answer and manage your request. Email is handled by the operator’s email provider. Please do not email passwords, API credentials, or sensitive service-request information.

Google data and permissions

Google connections are for the operator’s explicitly authorized websites and advertising accounts. Visitors to these public pages are not asked to sign in with Google.

Search Console: aggregate website performance

The read-only connection checks access to an authorized Search Console property and imports daily, property-level clicks, impressions, and average search position. It also keeps the property identifier, dates, and technical records of the import. The current import does not request individual visitors, search-query-level records, Google email, contacts, or files.

The private workspace uses these observations to review website performance, evaluate research assumptions, and inform website-maintenance decisions. Missing data is not treated as evidence of zero traffic.

Optional sitemap submission

A separately authorized write connection can check property ownership, submit an approved sitemap URL, and read its registration status. It is used only when the operator enables the reviewed submission workflow. A successful submission is not proof that Google indexed the website.

Optional Google Ads connection

If separately authorized and enabled, the Ads connection reads the selected account’s configuration, campaigns, and aggregate cost and performance information. It can create and manage the operator’s reviewed search campaigns within approved limits. The public website does not enroll visitors in advertising audiences, use Google data for personalized ads, or upload visitor identities to Google Ads.

Storage, access, and sharing

Imported observations and operational records are stored in the private application database. OAuth client secrets and refresh tokens are kept in private server configuration. Access tokens are used by server processes to communicate with Google. These credentials are not included in public pages or sent to website visitors.

Access is limited to the authorized operator and infrastructure needed to run the service. Hosting and backup providers may process stored data on the operator’s behalf. The operator is based in Israel; infrastructure and service providers may process data in other countries. Data may also be disclosed when required by applicable law or necessary to investigate security incidents. It is not offered for sale.

Retention and deletion

Operational observations are kept while needed for performance comparisons, troubleshooting, and the history of reviewed actions. Aggregate Search Console records currently do not have a single automatic deletion deadline. Different records and backups have different operational and legal retention needs; this policy does not promise a universal number of days.

You can ask the operator to explain retained information, correct it, disconnect a Google connection, or delete information that is no longer needed. Requests are reviewed against applicable obligations and the need to preserve limited security, financial, or authorization records. If a record must be retained, the operator will explain the reason. Copies in backups may remain until those backups expire under their configured retention policy.

You may remove AutoLead’s Google access through your Google Account connections. Revoking access prevents further authorized API access; it does not automatically delete observations already stored in the private application. Contact the operator for a deletion request.

Consumer lead information

Consumer lead collection and call-routing services are not active on this public website. Any future consumer-facing service will need its own relevant notices, provider terms, and consent process before collecting or sharing lead information. Authorization to read Search Console data is not consent to collect consumer leads.

Changes and contact

This policy will be updated if the service or its data practices change. A materially different use of Google data will be disclosed and, where required, newly authorized before it begins. The effective date appears above.

Contact: yochai.akoka@gmail.com.