SEO NEURONS SPIDER - OPTIONAL EXTERNAL SERVICES Version 1.0 | Last updated: 26 October 2026 OPTIONAL INTEGRATION CONTROLS Google's account authorization remains a separate OAuth step. Spider shows the read-only reporting purpose before connection. AI and PageSpeed have one informed setup choice for the saved connection, covering connection checks and the tasks or URL tests you subsequently choose. MCP has a project access notice before its first launch. These are not repeated for every request with unchanged settings. Relevant recipient, credential, project or notice changes require a new choice. Startup reconnects do not obtain permission silently or infer it from old saved credentials. Full notices and withdrawal controls are available offline under About > Privacy & Data Sharing. Withdrawing prevents future requests and MCP reads; it does not recall information already shared or replace provider-side revocation/deletion controls. The PageSpeed Fetch screens continue to remind you about complete URLs and private query parameters. These conditions supplement the Spider EULA and privacy notice. Publisher: Ashok Kumar, sole proprietor trading as SEO Neurons, 252/6, Barwala, Hisar, Haryana, India - 125121. Contact: contact@seoneurons.com. The provider links below identify additional agreements and data practices; this file is not a replacement for them or a claim that a provider has endorsed Spider. Provider terms apply to your use of that provider. They do not expand the proprietary app restrictions over separately licensed components or waive mandatory rights or SEO Neurons' own responsibilities. 1. YOUR CHOICE AND AUTHORISATION Connect optional services only with accounts, API projects and data you are authorised to use. Before a request or data disclosure, obtain the rights, lawful basis, notices and permissions it needs. Publicly readable pages can still contain protected content or personal information. Do not send credentials, confidential client material or personal data to an unsuitable provider, plan or endpoint. Check permitted purposes, security, retention, international transfers and any required data-processing agreement. You pay charges under your provider account. A Spider licence does not include third-party API usage. Respect API quotas and safety/access controls; do not bypass them. A timeout or cancellation may occur after a provider has received or processed a request. Local deletion/disconnection does not undo a disclosure, guarantee a refund or delete the provider's copies. Use the provider's revocation, billing and deletion controls. 2. GOOGLE SEARCH CONSOLE AND GOOGLE ANALYTICS 4 These integrations use Google OAuth and read-only scopes. Search Console uses webmasters.readonly; GA4 uses analytics.readonly. Both also request openid and userinfo.email to read Google's stable account identifier and verified email, so a reconnect can be checked against the saved account. These identity details are stored locally with the account; refresh tokens are protected separately for the current Windows user. The integrations read available properties and requested reports for local SEO analysis; they do not grant website administration, Gmail/Drive access or permission to alter your Google reports/settings. Reuse and transfers of retrieved information remain subject to applicable Google restrictions and the privacy notice's Google data-use commitment. Do not sell it, use it for surveillance/advertising or general AI training, or transfer it for an incompatible purpose. User-directed exports and MCP access must remain lawful and within the applicable Google permissions. GA4 Page reports can include full recorded URLs and query strings; Landing-page reports include paths and query strings. Selected report dates, metrics, web-stream/website filters and optional channel, source, medium, device and country filters are sent to Google for those reports. Review imported URLs and reports before sharing them with another recipient. Review Google's consent screen. Disconnect/forget a local account and revoke its Google connection when no longer needed. Remove separately saved project/report copies when required. An enabled reconnect-on-launch setting can renew connections without repeating the authorisation screen. Official references: Google APIs Terms: https://developers.google.com/terms Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy OAuth policies: https://developers.google.com/identity/protocols/oauth2/policies Search Console API terms: https://developers.google.com/webmaster-tools/v1/terms Standard Analytics terms reference (your regional/account agreement controls): https://marketingplatform.google.com/about/analytics/terms/us/ Google privacy: https://policies.google.com/privacy Manage/revoke connections: https://support.google.com/accounts/answer/14012355 3. PAGESPEED INSIGHTS This feature sends the tested complete URL, strategy and your API key to Google. Google performs its own fetch; your local authenticated browser session is not sent with the request. Do not test a URL containing private tokens or confidential parameters without authority. A key-connection test uses example.com and can consume quota. Google APIs Terms and Google privacy above apply. API documentation: https://developers.google.com/speed/docs/insights/v5/get-started 4. OPENAI API Spider uses the OpenAI API with your configured API credentials; a consumer ChatGPT subscription is not the API billing arrangement. Inputs are the prompts/page fields/text you select for text, embedding or image tasks. Review generated content for accuracy, rights and required disclosures before relying on or publishing it. Do not bypass safeguards, misrepresent output as human-created, resell API keys or violate permitted use, geographic, age or data-handling restrictions. API input is not training data by default unless you opt in. Retention still applies: Responses has default stored state, and Spider currently does not send store=false. Do not assume a no-retention arrangement; check your API account's approved controls and exceptions before sensitive use. Official references: Services Agreement: https://openai.com/policies/services-agreement/ Service Terms: https://openai.com/policies/service-terms/ Usage policies: https://openai.com/policies/usage-policies/ API data controls: https://developers.openai.com/api/docs/guides/your-data Supported regions: https://developers.openai.com/api/docs/supported-countries 5. GEMINI API Gemini use requires age 18+, professional/business purposes and a supported region. Google's terms require Paid Services for API clients made available to users in the EEA, Switzerland or UK. Do not submit sensitive, confidential or personal information to Unpaid Services: Google can use inputs/outputs for improvement and human review. Paid-project treatment differs; verify the API project's active billing/tier. Spider does not automatically establish your billing status, age or location. If you cannot satisfy these conditions, leave Gemini disabled. Respect Google's prohibited-use rules and safety controls; review outputs before use. Official references: Additional terms: https://ai.google.dev/gemini-api/terms Google APIs Terms and Google privacy: see section 2. Available regions: https://ai.google.dev/gemini-api/docs/available-regions Prohibited-use policy: https://policies.google.com/terms/generative-ai/use-policy 6. CUSTOM ENDPOINTS, MCP AND OTHER RECIPIENTS Changing an endpoint URL directs credentials and content to that operator. A provider label is not proof of endpoint ownership. Verify URLs, use HTTPS for remote services and check that operator's terms and privacy practices. Plain HTTP can expose information in transit. Only use a local HTTP service in an appropriately secured environment. MCP can expose saved project data, including HTML and clean text, to a client. Its local read-only server has no separate per-client login or per-tool approval. Other programs able to reach it can read exposed data; clients can forward results to another provider. Connect only trusted clients, review their permissions/terms and stop the server when finished. Do not expose it remotely through a tunnel/proxy without separate security. Read-only access still requires authority to disclose the content. The same responsibilities apply when you export reports, share projects or send support files. Separate permissions may be needed for client data, website content and Google-derived data. Giving access to one recipient does not authorise unrelated recipients or purposes. 7. STOPPING USE AND CHANGES Stop or disable the relevant tasks, turn off connect-on-launch, disconnect accounts and remove saved credentials as appropriate to stop future requests. Use provider controls to revoke access and address retained content. Local stored results, exports and backups require separate care. Providers can change availability, models, quotas, billing and terms. Read the agreement applicable to your account and use at the time of access. If a feature cannot be used within those conditions, do not enable it. These conditions provide no blanket permission to crawl, reuse or disclose another party's data and do not transfer our own legal duties to you.