Terms of Service

1. Service

AEGIS Sentinel provides an oversight and action-control layer for AI agents, workflow automations and connected systems. The service can observe activity, validate action requests, create human review tasks, apply policy decisions and keep audit records.

During early commercial pilots, some features may operate in learning, dry-run or assisted configuration mode.

2. Accounts And Access

Customers are responsible for keeping API keys, login credentials and integration secrets confidential. You must notify AEGIS Sentinel if you believe an account, key or integration has been compromised.

Agent API keys are shown once. If a key is lost, the customer should rotate it and update the connected agent runtime. Rotating a key does not reset the billing period, retention period or usage limits.

3. Free Trials And Abuse Controls

Free trials are intended for one legitimate evaluation workspace per customer. A free trial lasts 7 days and is limited to the published free-trial event, agent, connector and retention limits. Email verification is required before a trial workspace is created.

To prevent abuse, AEGIS Sentinel may limit, reject, block or manually review repeated trial attempts using email, browser, network, IP, account, device or similar security signals. These controls are used for fraud prevention, service protection and fair use.

When a trial expires, new event processing is paused until the customer upgrades. Existing workspace data, audit history and API-key metadata remain subject to the Data Retention Policy and are not immediately deleted on the expiry date.

4. Customer Data

You control the content you send to the service. Do not send passwords, private keys, payment card data, health data, biometric data or other highly sensitive regulated data unless a written agreement explicitly allows it.

You are responsible for making sure you have the rights and notices required to send event, user, system or workflow data to AEGIS Sentinel.

For customer event payloads, AEGIS Sentinel normally acts as a processor and processes the payload only to provide the service, unless a written agreement says otherwise. The customer remains responsible for deciding which data is sent, minimizing payloads and instructing connected agents.

5. Data Processing And Customer Instructions

Where AEGIS Sentinel acts as a processor, we process customer event payloads, review records and operational metadata only to provide, secure, troubleshoot and improve the service, or as otherwise instructed by the customer in writing.

Customers are responsible for having a valid legal basis, notices, internal approvals and data minimization practices before connecting agents, users, logs, workflows or systems to AEGIS Sentinel.

6. Acceptable Use

You must not use AEGIS Sentinel to:

• break the law or violate third-party rights;
• gain unauthorized access to systems or data;
• send malware, secrets or intentionally harmful payloads;
• monitor people or systems without a valid legal basis;
• attempt to reverse engineer, copy or bypass protected service logic;
• use the service to make fully automated decisions about people where law requires human review or additional safeguards.

7. Proprietary Technology

AEGIS Sentinel's engine logic, scoring methods, policy strategy, internal rules, source code, private prompts, security controls and platform administration workflows are proprietary. Customers receive access to the service, documentation and integration snippets needed to use the product, not a license to copy, reconstruct or reproduce the protected implementation.

8. Customer Control And Execution

AEGIS Sentinel is review-first by default for customer pilots. The service may recommend that an action should be allowed, blocked, delayed, limited in scope or reviewed by a human. Customers remain responsible for configuring their agents so that they wait for review when required and confirm approval before execution.

Controlled gateway execution, automated blocking and similar autonomous controls are optional and must be explicitly enabled by the customer or agreed in writing. AEGIS Sentinel does not replace the customer's own access control, incident response, backup, compliance or approval procedures.

If a customer chooses to rely on automated allow, block, routing or execution behavior, the customer is responsible for testing that setup, defining safe scopes, monitoring false positives and false negatives, and maintaining a fallback process for urgent work.

9. Availability And Changes

AEGIS Sentinel may change during pilot operation. We aim to maintain a stable production service, but pilots may include updates, maintenance windows and feature adjustments.

10. Payments

Paid plans, pilot fees and setup fees are described on the public site or in a written order. Payments, renewals, taxes and cancellations are governed by the applicable order form or checkout terms.

Unless the checkout or order says otherwise, subscriptions renew until cancelled. Cancelling renewal keeps access until the end of the current paid period. Plan upgrades keep the same workspace, audit history and agent keys, but change the applicable limits and billing.

11. Suspension

We may suspend access if there is abuse, non-payment, security risk, illegal use, excessive load or use outside the agreed scope.

12. Warranty Disclaimer

AEGIS Sentinel is provided as an operational control tool. It does not guarantee that every unsafe action, fraud pattern, anomaly or incident will be detected or blocked. Customers remain responsible for their systems, agents, approvals and final operating decisions.

AEGIS Sentinel outputs are risk signals, recommendations and workflow controls, not legal, financial, security or operational guarantees. The service may produce false positives, false negatives, delayed alerts or incorrect classifications.

13. Liability

To the maximum extent allowed by law, AEGIS Sentinel is not liable for indirect, incidental, special, consequential or lost-profit damages. Liability limits may be set in a signed agreement for paid pilots or commercial plans.

14. Data Protection

The Privacy Policy and Data Retention Policy explain how personal data and operational records are handled. Customers with regulated data, large-scale monitoring or special compliance requirements should sign an appropriate data processing agreement before production use.

15. Legal Review And Contact

These public terms are designed for self-service pilots and early commercial use. Customers with regulated data, high-risk automated workflows, financial operations or safety-critical systems should complete a written agreement and legal review before production use.

Questions about these terms can be sent to aegis.sentinel.team@gmail.com.