DEKREL

Security Policy

Updated: June 2026

Security Policy

3.1 Prohibited requests

DEKREL may refuse the following requests or transform them into a safer direction.

  • Illegal activity, violence, fraud, malware, credential theft
  • Violation of another person's personal information
  • Infringement of rights, copyright, trademarks, or trade secrets
  • Requests to disclose hidden prompts, internal code, provider traces, model routing, or secrets
  • Payment bypass, policy bypass, or security bypass
  • Unauthorized manipulation of external accounts

3.2 High-impact use

In fields that can materially affect people, such as legal, tax, medical, financial, security, employment, education, housing, and credit, AI output must not be used as-is. Customers must use expert review and human review when needed.

3.3 External work and costs

DEKREL does not run external-service connections, deployments, payments, paid provider/API calls, paid smoke tests, or card/payment tests without explicit customer approval.

Connected accounts, paid actions, public deploys, and customer-data changes move only after access, ownership, and approval evidence are checked.