OrionsLock Pulse Terms of Service

Last updated: April 24, 2026

Service Use

Pulse is an AI gateway and dashboard for routing, spend controls, ThreatPrint scanning, observability, incident briefs, and related developer workflows. You are responsible for the prompts, credentials, provider accounts, models, and downstream systems you connect to Pulse.

Acceptable Use

Do not use Pulse to attack, disrupt, or access systems without authorization; bypass usage limits; exfiltrate data; send unlawful content; test against other tenants; or place secrets in public chats, logs, screenshots, or support threads. Security testing must be limited to accounts and systems you control unless OrionsLock gives written permission.

Keys and Credentials

Keep Pulse keys, upstream provider credentials, GitHub tokens, and billing secrets confidential. Rotate credentials if they are pasted into the wrong place, exposed in logs, or shared with an unauthorized person. Pulse may reject or suspend traffic that appears abusive, compromised, or unsafe.

Plans, Billing, and Limits

Plans define request volume, seats, retention, payload storage mode, eval/replay caps, archive/export caps, support level, and private deployment availability. Overage, add-on, or enterprise terms must be agreed separately. Failed payments or canceled subscriptions may reduce access according to the active billing state.

Responsible Disclosure

Report vulnerabilities to security@orionslock.com. Include reproduction steps and request IDs where possible. Do not access other tenants, destroy data, or publish exploit details before we have had a reasonable opportunity to remediate.

Support and Termination

General support is available at contact@orionslock.com. OrionsLock may limit or terminate access for security risk, abusive use, non-payment, or violation of these terms.