Document Utilities

Safety & Guardrails

DEQLYNK applies a Zero-Trust approach to AI application safety: every request is treated as untrusted until validated, every session has bounded behavior, and every control is designed to reduce abuse without collecting unnecessary content.

Zero-Trust Privacy Model

Zero-Trust in this context means no implicit trust by network location, client type, or request frequency. The stack validates session state, applies anti-bot checks, and enforces rate controls before expensive inference work begins.

  • Authentication before chat access.
  • Queue/captcha challenge before high-value endpoints.
  • Origin policies to reduce hijacking and embed abuse.
  • Strict request throttling to contain automated spam.

Rate Limiting Abuse Controls

Standard users are constrained at the endpoint level. The 5 messages/minute limit acts as a burst-control mechanism to protect both model resources and community fairness. Daily quotas add a second horizon to prevent slow-burn abuse.

Abuse control layers:
1) Burst window (per-minute)
2) Daily quota (per-day)
3) Session gating + challenge checks
4) Owner monitoring in dashboard telemetry

Why Track IP/Country Without Reading Chat Content

Abuse response needs signals, but those signals should be privacy-minimal. IP and country metadata help detect suspicious patterns like repeated scripted traffic, rapid account farming, and geographic anomaly spikes. This can be done without inspecting the semantic content of user messages.

  • IP address: supports rate control and incident triage.
  • Country signal: supports coarse anomaly clustering and fraud heuristics.
  • Activity timestamps: support sequence analysis for abuse investigations.
Privacy principle: collect minimum telemetry required for safety operations; avoid unnecessary content surveillance.

Operational Guardrail Discipline

Guardrails are only effective if monitored and updated. As traffic evolves, so should thresholds, challenge policies, and incident response playbooks. Safety is not a static config file; it is a continuous operational practice.