By using BlinkQ, you are responsible for protecting your account and project credentials and for the payloads you publish.
Keep project API keys in a secret manager and out of browser code, public environment variables, logs, and source control. Rotation immediately invalidates the previous key.
Do not use BlinkQ to distribute malicious or unlawful content or to access projects and channels you do not own. You are responsible for selecting appropriate payloads and TTL values.
BlinkQ is provided as is. Messages are retained Redis data with TTL expiry and non-destructive reads; the current service does not provide acknowledgement, consumption, retries, dead-letter handling, durable history, or a frontend uptime SLA. Design clients so repeated polls and service interruptions are safe.