Queuebeam

Legal

Privacy Policy

Last updated: July 12, 2026. This policy explains how Queuebeam processes and protects personal and operational data.

What Queuebeam processes

Queuebeam receives outbound operation data submitted by tenants, including operation type, destination configuration, payload metadata, attempts, delivery responses, error information, quota usage and operational audit events.

Tenant data isolation and encryption

Tenant operational data is stored in tenant-scoped physical tables. Payloads, endpoints, credentials, responses, errors, metas and AI analysis inputs/results are encrypted before storage. If database tables are copied without application secrets, the stored operational content should remain unreadable.

Email and provider credentials

When tenants configure BYO email providers such as SMTP, Cloudflare Email Workers, Mailgun, Postmark, Resend or Amazon SES, Queuebeam stores provider credentials encrypted and uses them only to execute requested transactional deliveries.

AI failure analysis

Failure analysis is optional and asynchronous. By default, Queuebeam sends only sanitized technical metadata to the configured AI provider. Payloads, credentials, cookies, authorization headers, recipients, full email content, query strings and customer metas are excluded unless a user explicitly opts in for a specific operation.

Website analytics and consent

Queuebeam uses Google Analytics with Consent Mode on its public website. Analytics storage is denied by default; before acceptance, Google may receive limited cookieless technical signals. If accepted, Google may also process information such as visited pages, approximate location, device and browser information. Advertising storage, advertising signals and ad personalization remain disabled. Visitors may reject analytics or change their choice at any time through Cookie settings in the footer. Analytics is not loaded on the authenticated tenant dashboard or administration area.

Retention and access

Operational data is retained according to the configured tenant retention policy. Administrative access to tenant data should be limited to operational support, security, abuse prevention and debugging, and should be audited.

Contact

For privacy questions, contact legal@queuebeam.cloud.