LAWCTL API Terms

These terms govern access to the LAWCTL APIs.

1) Access, Auth & Rate Limits

• Access credentials are personal to you and must not be shared. We may rotate or revoke them to maintain security.
• Automated rate limits may apply. Excessive or abusive traffic may be throttled or blocked.

2) Permitted Use & Restrictions

• Use the APIs to build features consistent with your agreements and applicable law.
• Prohibited: scraping other customers’ data, attempting to bypass rate limits or auth, or use for unlawful/unsafe purposes.

3) Data & Retention

• By default, LAWCTL does not retain PII beyond transient processing unless expressly enabled by policy or an SOW.
• You must not send secrets or live credentials in request bodies/headers that are destined for public logs.

4) Logging & Provenance

• When enabled by policy, each call may write a content-addressed identifier (CID), timestamp, and capability context for audit.
• Do not log payloads that contain personal data to public systems.

5) IP, Changes & Deprecation

• API specifications and SDKs remain our IP (subject to OSS licenses, if any). We may modify or deprecate endpoints with reasonable notice; breaking changes are versioned.

6) Availability & Support

• Provided “as is” during evaluation; support/SLA terms are governed by your SOW. Maintenance windows and incident updates will be announced via standard channels.

7) Warranty & Liability

• No implied warranties; liability is limited and capped as per the SOW/master terms; no indirect/special damages.

8) Compliance & Export

• You must ensure lawful basis and transparency for any personal data processed via the APIs and comply with export/sanctions law.

Implementation reminders: separate dev/test/prod keys; enforce least privilege; use vault references, not raw secrets, in requests.