AI Use and Data Policy

This AI Use and Data Policy explains how LeenOps supports AI agent workflows and how customers should govern the use of AI systems inside their organization.

1. Product purpose

LeenOps helps teams configure, run, monitor, and review AI agents for business operations. Agents may draft content, analyze information, generate reports, prepare tasks, triage support, or connect to approved business tools.

LeenOps is designed for operational oversight, not fully unsupervised decision-making.

2. Customer responsibilities

Customers are responsible for:

• Choosing which workflows are appropriate for AI assistance.
• Reviewing outputs before relying on them.
• Setting permissions for users, agents, tools, and integrations.
• Ensuring submitted data can lawfully be processed.
• Evaluating model-provider terms and data practices.
• Maintaining human review for high-impact decisions.

3. AI outputs

AI outputs may be incorrect, incomplete, biased, outdated, or unsuitable for a specific context. Outputs should be treated as drafts, recommendations, or operational artifacts unless a qualified human reviews and approves them.

Customers should not represent AI outputs as human-reviewed when they have not been reviewed.

4. Data sent to model providers

Depending on configuration, LeenOps may send prompts, instructions, files, retrieved context, tool results, or output history to AI model providers to complete customer-requested workflows.

If a customer uses bring-your-own-key access, that customer's selected provider processes data under the customer's provider account and provider agreement.

5. Restricted data

Customers should not submit sensitive personal data, regulated health data, payment card data, government identifiers, confidential third-party data, or secrets unless the customer has approved the workflow, provider, retention settings, and access controls.

API keys, passwords, private keys, and tokens should be stored only in approved product settings or secret-management systems.

6. Prohibited AI uses

Customers may not use LeenOps AI workflows for:

• Malware, phishing, credential theft, or evasion.
• Adult content distribution or sexual exploitation.
• Deceptive impersonation or fraud.
• Unlawful surveillance or doxxing.
• Fully automated high-impact decisions without appropriate legal basis and human review.
• Bypassing safety controls, rate limits, or third-party terms.

7. Logs and observability

LeenOps may store run history, logs, prompts, outputs, tool calls, approvals, and status data to provide observability, debugging, auditability, and abuse prevention.

Customers should configure retention and access according to their internal policies.

8. Model improvement

LeenOps does not claim ownership of customer workspace content. Use of customer content for model training or improvement depends on the selected provider, customer configuration, and applicable agreement.

Customers using external model providers should review provider-specific training and retention settings.

9. Human oversight

LeenOps recommends human review for:

• Legal, finance, security, medical, HR, or compliance outputs.
• Customer-facing communication.
• Code changes or infrastructure actions.
• Public content publication.
• Actions that modify third-party systems.

10. Contact

Questions about AI governance or vendor review can be sent to hello@leenops.com.

Policy changelog