Terms of use

The PowerQueue public service at powerqueue.link is free to use, needs no account, and comes with no guarantees. By using it you accept these terms.

The service

• The service is free. There are no accounts, no payment and no paid tier.
• No account is required: you do not sign up or tell anyone who you are. A tenant identifier you generate names your tenant, and anyone who knows it can use that tenant.
• It is provided as is, without warranty of any kind. There is no guarantee of availability, performance, durability, correctness or support.
• The only promise: the service will be down from time to time for maintenance, without notice.
• Your data is not guaranteed. Data normally persists across maintenance restarts, but nothing is backed up, and any or all data may be lost at any time, for example when a storage format changes. Lost data cannot be recovered.
• Messages are kept at most 1 hour, and a tenant holds at most 16 MiB of messages at once. A tenant with no activity for 7 days is deleted automatically, with every queue, topic, subscription and message in it.
• The service, these terms and the limits may change or end at any time.

Your identifier is a secret

• Your tenant identifier is the only thing that protects your tenant. Anyone who has it can read, send and delete everything in it.
• Generate it at random (this site's generator does so in your browser). Do not choose a memorable or guessable one, and do not share it or publish it, for example in a public code repository.
• The identifier appears in URLs and resource names, so it can turn up wherever those are logged on your side.
• Do not send confidential, personal or sensitive data through the service. Tenants are separated by name on a shared machine, not by encryption.

Acceptable use

You must not use the service:

• for anything illegal, or to store or pass on illegal content;
• to distribute malware, to control malware or botnets, or for spam or phishing;
• to store or exchange other people's personal data;
• to harass anyone, or to infringe anyone's rights;
• to attack, probe or overload the service or anyone else, or to get around its limits (for example by spreading load across many addresses or identifiers);
• for anything whose failure or loss of data could cause harm, such as safety, medical, financial or production systems.

Access may be blocked, and data deleted, at any time and without notice, for any client that breaks these terms or harms the service for others.

Limits

Every tenant and client address is held to the service's caps: messages up to 256 KiB (Azure Queue Storage 64 KiB), 100 queues, topics and subscriptions per tenant, 1,000 messages per queue, 16 MiB of messages per tenant, message lifetimes up to 1 hour, implicitly created entities deleted after an hour idle, tenants deleted after 7 days idle, 50 connections and 100 requests a second (bursts of 200) per client address, 20 new tenants per client address per hour, and 10,000 tenants in all. The documentation gives the details and the error each limit produces.

What is collected

No account, name, email address, cookie or analytics. This website loads nothing from other sites, and its pages set no cookies. The identifier generator runs in your browser; when it makes an identifier, the page keeps it in your browser's local storage so other pages of this site can fill it into examples. It is never sent to the server by the website. The Forget button removes it.

The service does process, and in some cases record:

• Client addresses, in memory. The broker keeps each client IP address with its counts of connections, requests and recently created tenants, to enforce the per-address limits. These are held in memory only, forgotten after an hour without activity, and lost at every restart.
• What you send. Your tenant identifier, entity names and messages are stored on the broker's disk until they are deleted or expire (messages within 1 hour), or until the tenant is deleted after 7 days without activity. The broker also stores when each tenant was last active, for that purpose.
• The broker's log. Usage is logged. The broker logs every request it serves on the API endpoints (SQS, Azure Queue Storage, Pub/Sub and the Service Bus administration API): the time, the client IP address, the tenant identifier, the operation and path, the response status and size, how long it took, and the client's User-Agent. It also logs every AMQP connection (AMQP 0-9-1 and Azure Service Bus) when it ends: the time, the client IP address, the tenant identifier, how long it was open and how many messages it published, received and acknowledged. Credentials, signatures and message contents are never logged. Requests and connections refused for exceeding the limits, and those from a temporarily banned address, are logged as counts per address and minute. Other events name a tenant identifier or entity name, for example when a queue expires or a storage error occurs.
• Website logs. The web servers in front of this website (Caddy) log every request for its pages: the time, the client IP address, the method, host and path, the response status and size, and the client's User-Agent. These logs, and the broker's, are used to investigate abuse and faults.