Security and privacy
How we protect the data entrusted to us
QueuePower processes personal data on behalf of its customers. Under the UK GDPR and the EU GDPR, your organisation is the controller and we are the processor. The data we hold on your behalf comprises the content of support conversations, the names and email addresses of the customers who raise them, any account context you choose to attach, and the analysis the AI produces from that material. We do not request payment card details, identity documents or other special-category data. Should a customer include such information in a ticket, it is subject to the same safeguards described below.
Data location. The database and application servers are located in the United Kingdom (AWS London and Vercel London). A small number of subprocessors process limited categories of data outside the United Kingdom, for sign-in, payments, email delivery and AI; each is identified on the subprocessor list together with the data it receives.
Two principles
The design rests on two safeguards that apply regardless of configuration.
Each organisation's data is isolated at the database
All customers are served from a single deployment, but the database enforces the separation. PostgreSQL row-level security policies apply to every read, write, update and delete on every table that holds customer data, and the application connects under a role that cannot bypass those policies. A query that omits the tenant condition returns no rows. This protection does not depend on the application code being correct.
Customer names and email addresses are withheld from the AI provider
Before any ticket content is submitted for AI processing, customer names and email addresses are replaced with placeholders. The original values remain in our database and are reinstated in the draft only after the response has been received. This safeguard is applied to every request and cannot be disabled for an individual organisation.
Technical and organisational measures
Encryption
Customer email addresses and all stored third-party credentials (CRM tokens, mailbox refresh tokens and IMAP passwords) are encrypted with AES-256-GCM at the application layer before being written to the database, in addition to the storage provider's encryption of data at rest. Lookups by email address use a one-way hash, so no plaintext address is held in an indexed column. All traffic is encrypted in transit.
Authentication and access control
Sign-in runs on a dedicated identity provider (named on our subprocessor list), with organisation-level membership, short-lived session tokens, email verification when a new device signs in, lockout after repeated failed attempts, bot protection on sign-up, and cookies restricted to HTTPS. Roles (administrator, manager and agent) and individual permissions are held in our database and enforced on the server for every action, independently of the user interface.
Audit trail
Every action on a ticket, by a person or by the AI, is recorded on its timeline. Every administrative change (settings, autonomy, API keys, team, integrations, exports) is written to an append-only audit log, with the state before and after the change: the application can add entries but never change or remove them. Administrators may export the log in CSV format at any time. Audit records are retained when the underlying record is deleted, so the history remains complete.
Public endpoints
Public endpoints are authenticated as appropriate to each (API keys for the intake API, signed single-use links for satisfaction ratings, signature checks with constant-time comparison for webhooks), reject replayed requests, limit request size and apply rate limits. Security headers, including HTTP Strict Transport Security, frame denial, content-type protection and referrer and permissions policies, are sent with every response.
Data-subject rights
As processor, we assist your organisation in responding to requests from the individuals whose data it holds. Requests received directly from those individuals are referred to you as controller.
Measures in place
- Tenant isolation by row-level security under a non-bypass database role, verified by a cross-tenant isolation test
- Application-layer encryption of customer email addresses and stored credentials
- Customer names and email addresses replaced with placeholders before every AI request
- Email attachments never copied: fetched from your own mailbox, for signed-in members of your workspace, only when opened
- Automatic replies only to senders whose email passes authentication, and only from sources your team has approved
- Each inbound email processed exactly once, even if it reaches two connected mailboxes
- Complete audit log with CSV export
- Deletion and export on request, carried out by our team, with a 30-day recovery period before permanent removal
- Authentication, replay protection and rate limiting on public endpoints
Handling of requests
- Access and portability (Articles 15 and 20): a structured export of your organisation's data, provided on request within one month.
- Erasure (Article 17): records are removed from every application read path on request and permanently deleted after a 30-day recovery period. Each request is confirmed to you in writing.
- Rectification and restriction (Articles 16 and 18): carried out within your workspace, or on request.
- Personal data breach: you will be notified without undue delay, and in any event within 48 hours of our becoming aware.
- Requests should be sent to the privacy address given below.
Standards and frameworks
Our controls are designed against the following. We have not yet been independently audited or certified against any of them.
- UK GDPR and EU GDPR
- OWASP Application Security Verification Standard 4.0.3
- SOC 2 Trust Services Criteria (Security, Availability, Confidentiality, Privacy)
- NIST Privacy Framework
- CIS Controls v8
Subprocessors
We engage 7 subprocessors to provide the service, each under written data-processing terms, together with any mailbox provider your organisation elects to connect. The full list, with the purpose and location of each, is published and maintained.
View the subprocessor listSecurity concerns or suspected vulnerabilities may be reported to security@queuepower.com. Reports are acknowledged within two working days, and we will not take action against researchers who act in good faith.
Due-diligence questionnaires, requests for a countersigned data processing agreement, and all privacy correspondence should be addressed to privacy@queuepower.com. The Data processing agreement and Privacy policy are published in full.
Ready for your security review, and for your customers
Try it on real tickets with these controls in place from the first email. Your first 100 tickets are free, with no card and no time limit.
Start free on 100 tickets