1. API Key Stewardship & License
Subject to your compliance with these terms, Consent Shield grants you a limited, non-exclusive, non-transferable, and revocable license to access our platform APIs, dashboard modules, and decentralized proxy scripts.
API credentials must be secured using appropriate server-side vaults Sharing keys across unverified client networks is strictly forbidden System blocks will trigger automatically upon detecting key leakage
2. Telemetry Isolation & Script Sanity
You agree not to modify the script sandboxing parameters or attempt to bypass Consent Shield's client-side proxy structures. All active pixels must be registered with the central dashboard console to prevent security alerts.
Failure to maintain script sanity may result in system isolation. Under isolated status, Consent Shield reserves the right to forcefully drop tracking requests on non-compliant nodes to preserve overall privacy ecosystem health.
3. Service Level Commitments & Latency Budgets
Consent Shield is committed to maintaining low latency budgets for our edge proxies, aiming for sub-10ms response latency on global nodes under normal operating configurations.
Enterprise compliance enclaves maintain hot-failover configurations across four availability zones to guarantee continuous script functionality.
System-wide optimizations are restricted to low-traffic hours and are hot-patched with zero service interruption.
4. Client Liabilities & Custom Integrations
Clients are solely responsible for ensuring that their custom tag configurations, SDK layers, and direct-to-database connections align with their local privacy frameworks. Consent Shield's suggestions do not constitute certified legal counsel.
5. Token Consumption & Billing Policies
Consent processing consumption is measured in secure token interactions, calculated based on the sheer volume of compliance requests processed across Consent Shield's edge nodes. Overages are subject to dynamic scaling charges as detailed in your tier agreement.