Effective date: July 4, 2026
Terms of Use
These Terms govern use of the OCO public website. The site is provided to explain OCO Engineering, LLC, its approved public positioning, and the engineering areas it may provide or develop. The site is informational and does not create a service engagement by itself.
By using the public website, you agree to use it only for lawful, non-disruptive, and non-misleading purposes. If you do not agree with these Terms, do not use the website. Separate signed documents control any paid engagement, client work, authorized testing, confidential exchange, or project delivery.
Public Website Use
You may view and reference the public website for general information about OCO. You may not use the site to attempt unauthorized access, interfere with operations, scrape at abusive volume, misrepresent OCO, copy protected material outside fair use or written permission, or imply a partnership, endorsement, authorization, or client relationship that does not exist.
Do not use the website to harvest contact information, attack infrastructure, overload forms, impersonate OCO, imply unauthorized association, or create derivative materials that confuse the source of OCO’s public identity. Reasonable linking to public pages is acceptable when it is accurate and does not imply endorsement.
No Client Relationship
No client, consulting, security, development, DevOps, legal, advisory, fiduciary, or confidential relationship is created by website use. A project requires written scope, authorization, commercial terms, and acceptance by OCO. Security testing requires separate written authorization and cannot be inferred from public security language.
A written engagement should identify the owner, scope, deliverables, environments, data handling rules, security authorization, communication path, payment terms, and acceptance process. Until those details are accepted, public conversation remains exploratory and OCO may avoid reviewing or receiving sensitive material.
Intellectual Property
The public website, text, design, names, marks, graphics, code, and published materials belong to OCO or their respective owners unless otherwise stated. Public descriptions of capabilities, ventures, protocols, engines, models, APIs, or systems do not grant a license to use private repositories, source code, data, confidential material, trademarks, or unreleased product work.
OCO may describe systems, names, acronyms, logos, technical categories, or ventures in public while keeping the underlying implementation private. Public reference to a name or concept does not transfer ownership, waive rights, open repositories, or authorize copying of the design, architecture, datasets, models, or operating methods.
Third-Party Services
The website may reference or rely on third-party services, browsers, hosting providers, analytics tools, email providers, or infrastructure vendors. OCO does not control every third-party service and is not responsible for their independent terms, privacy practices, outages, security posture, or content outside OCO’s controlled public materials.
Links or references to third-party services do not mean OCO endorses every statement, security practice, price, feature, availability, or policy of that third party. When a project uses a provider, the applicable provider terms, account controls, billing rules, and security obligations may also apply.
No Professional Advice
Public website material is not legal, financial, investment, medical, security, compliance, or professional advice. Capability descriptions explain engineering areas, not instructions for operating a regulated business, conducting security testing, making investment decisions, or relying on public material as a substitute for qualified professional review.
OCO’s public material may discuss security, software, AI, data systems, DevOps, chain records, protocols, and commercial data products. Those descriptions are educational and positioning material. They are not a substitute for legal review, compliance analysis, regulated professional advice, or a tested implementation plan for a specific organization.
Website Availability
The public website is provided as available. OCO may update, remove, correct, or reorganize content, routes, translations, forms, analytics, or public materials without notice. OCO does not guarantee that the website will be uninterrupted, error free, fully current, compatible with every device, or free of third-party service limitations.
Translations are provided for accessibility and clarity. If wording differs between languages, OCO may correct the translation or clarify intent in the applicable context. Technical examples may be simplified for public explanation and should not be treated as live system documentation.
Limitation
To the extent permitted by applicable law, OCO is not liable for losses arising from use of the public website, reliance on public materials, inability to access the website, third-party services, unauthorized use, or actions taken without a written OCO engagement. Nothing here limits liability that cannot be limited under applicable law.
You are responsible for your own use of the public website and for ensuring that any action you take based on public material is lawful, authorized, and appropriate for your situation. OCO is not responsible for unauthorized testing, misuse of examples, third-party interpretations, or decisions made without a written engagement.
Changes
OCO may update these Terms as the public website, company positioning, services, systems, laws, or operating practices change. The effective date reflects the current public version. Continued use of the public website after changes means the updated Terms apply to that use.
Older copies, cached pages, screenshots, or translated fragments may become outdated. The version published on the OCO website with the current effective date is the public version OCO intends visitors to rely on for website use.
Contact
Questions about public legal, privacy, security, governance, or disclosure information can be sent to info@oco.io. Do not send credentials, private datasets, exploit details, production secrets, or confidential third-party material through public email.
Public email is a triage channel. If OCO decides that a matter requires sensitive exchange, the next step may require a separate process, verified identity, written scope, secure transfer path, or owner approval. Until that exists, public email should be treated as unsuitable for secrets, regulated data, exploit material, or confidential project files.