Terms & Conditions
Terms & Conditions
1. PROTOCOL DATA INTAKE (PRIVACY POLICY)
-
1.1 Data Capture: KIBR Systems collects operational data via our strategic diagnostic intake terminals (including names, enterprise details, software configuration diagnostics, and friction metrics).
-
1.2 Zero-Distribution Guarantee: This data is captured strictly to evaluate system performance and analyze legacy bottlenecks. KIBR Systems will never lease, sell, or distribute enterprise operational data to external third parties.
-
1.3 Storage Security: All internal system records and database inputs are held within secure, authenticated pipelines to protect your architecture from unauthorized breach.
2. THIRD-PARTY DEPENDENCIES & SYSTEM UPTIME
-
2.1 API Infrastructure: KIBR Systems builds custom automation pipelines that rely heavily on third-party cloud applications and API endpoints (including but not limited to Make.com, HubSpot, Google Cloud, and OpenAI).
-
2.2 Liability Limitation: KIBR Systems holds zero liability for systemic operational interruptions, database synchronization failures, or lost enterprise revenue caused by external API downtime, endpoint changes, or platform policy updates enforced by these third-party vendors.
3. PROPRIETARY BLUEPRINTS & INTELLECTUAL PROPERTY
-
3.1 Technical Logic Ownership: All workflow configurations, custom scripting loops, webhooks, and engineering logic schemas presented on this platform or engineered during advisory sprints remain the sole intellectual property of KIBR Systems.
-
3.2 Usage Restriction: Clients are granted a non-transferable runtime license for their internal systems. Replicating, reverse-engineering, or repackaging KIBR Systems' operational blueprints for external sale or distribution is strictly prohibited.
4. DIAGNOSTIC EXECUTION BOUNDARIES
-
4.1 Preliminary Scope: All initial "Strategic System Diagnostics" or exploratory workshops are strictly evaluative. They do not constitute a binding guarantee of project delivery, system maintenance, or continuous integration.
-
4.2 Definitive Scope: Full technical engineering sprints, continuous deployment support, and system maintenance SLA schedules require an independent, signed Statement of Work (SOW).
