1. Policy scope
This policy applies to information handled through the OKKI Go informational website. It does not automatically govern data handled by an installed package, your AI-agent environment, a data provider, a CRM, a spreadsheet platform, an outreach system, or another connected service. Those systems may have independent controllers, processors, retention rules, and security measures.
2. Website information
This generated site does not include an inquiry form, account registration, newsletter field, booking widget, or product checkout. A copy-command button attempts to write the exact installer text to your clipboard and displays a local status message. The site should not claim that copying has installed the package or created an account.
Normal web infrastructure may process technical request information such as IP address, user agent, requested URL, timestamps, and security logs. The actual hosting configuration determines whether such data is collected, where it is stored, and how long it is retained.
3. Installation and runtime data
Running the installer occurs in the terminal and environment you choose. Before installation, review package behavior, requested permissions, filesystem access, network requests, logs, caches, histories, update behavior, and uninstall steps. Do not place API keys or private customer information in prompts, public repositories, screenshots, or support messages.
Use the secret-management method supported by your runtime. Separate test from production credentials where practical, restrict provider scopes, and revoke keys that are no longer required.
4. Prospecting and enrichment data
If you connect company, professional-contact, email-verification, intent, enrichment, or CRM services, those providers determine available fields and may impose restrictions on collection, storage, export, and communication. Record provenance, checked context, and unresolved conflicts. Do not treat a provider match as permanent, complete, or automatically lawful for every purpose.
Your organization is responsible for determining an appropriate legal basis, honoring applicable access or deletion rights, processing opt-outs, and limiting retention. Human review should occur before consequential exports, writes, or communications.
5. Cookies and local storage
This template does not require advertising cookies to copy the installer. Hosting, analytics, embedded media, or future integrations may introduce cookies or local storage. If enabled, document their purpose, duration, providers, and available controls, and obtain consent where required.
6. Security and retention
No website or connected workflow can promise absolute security. Use access controls, scoped credentials, environment separation, updates, audit logs, and incident procedures appropriate to the sensitivity of the data. Map retention across the runtime, provider accounts, generated files, exports, backups, and downstream systems. Removing the package does not automatically erase copies held elsewhere.
7. International use and rights
B2B research may involve people and systems in multiple jurisdictions. Privacy, marketing, and electronic-communications rules can differ by location and context. Review the obligations that apply to your organization, providers, prospects, and communication channels. Where applicable, individuals may have rights to access, correct, delete, restrict, or object to processing; direct requests to the responsible organization or provider.
8. Policy updates
This policy may change as the website and deployment guidance evolve. The version displayed on the page should be reviewed together with the current package, runtime, and provider documentation before production use.