A plain-language summary of the data the current BlinkQ application handles. Deployment operators remain responsible for their own privacy policy and infrastructure controls.
BlinkQ stores account names, email addresses, password hashes, projects, channel definitions, and hashed project API keys in its relational database. Raw project keys are returned only on creation or rotation.
Authenticated browser access uses an opaque HttpOnly session stored server-side in Redis. CSRF tokens are kept only in frontend memory. The frontend does not place passwords, session values, or project keys in local or session storage.
Published payload strings and queue member references are held in Redis. Payload keys receive the requested TTL in milliseconds. Reads are non-destructive, and BlinkQ does not expose durable message history. Deleting a channel or project removes its queue index; individual payload keys may remain until their TTL expires.