Security and the dataSecurity you can hold us to.
Passport numbers, dates of birth and background checks are what an accreditation system holds. Here is how we handle them, and every line of it is in the agreement you sign.
At a glance
Hosted where you need it
On Amazon Web Services in London as standard, with backups copied to Ireland. If your data has to stay in the US, the EU or elsewhere, we host it in the AWS region you choose. Either way, where it is held is written in the agreement.
Kept apart
Your records are kept apart from every other organisation's at the database itself, not only on the screen.
Sensitive means sensitive
A passport number or a date of birth is marked as such, and is never sent anywhere but to the person it belongs to.
Only what you publish
The public sees only the pages and the fields you put in front of them. A team's contact reaches their own people and nobody else's.
An agreement with every customer
A data processing agreement, signed before your data arrives, with the sub-processors listed and 30 days' notice of any change to either.
Yours to take away
Export your records as a spreadsheet whenever you want. Your account stays open for twelve months, and nothing renews by itself.
Support from the people who set you up
By email while applications are open, answered within one working day, and on the phone on badge day and your event days.
The company
bluebric is made by JTW Software Ltd, a software company registered in England. The terms, privacy notice, data processing agreement and sub-processor list are linked below and sent with every order.
The measures, in plain words.
The agreement lists the technical and organisational measures we take, and promises we will not reduce them. These are the same measures, without the legal form.
Separation between customers
Every table that holds your data enforces row-level security in the database itself, so a request for one organisation cannot read another's rows even if the application makes a mistake. Automated tests check every such table, and are written to prove one customer cannot reach another's data.
Least privilege
The application reaches the database through restricted roles that cannot get round those rules, and your public portal through one that sees only what the signed-in person may reach.
Encryption
All traffic is encrypted in transit with TLS. The database and its backups are encrypted at rest with keys held in AWS Key Management Service, stored files are encrypted at rest, and secrets are held encrypted.
Accounts and signing in
Passwords are stored only as scrypt hashes that nobody can read back, your administrators and us included. Sessions end after 30 days, or 7 unused. Signing in is rate-limited and every sign-in is recorded, and changing permissions or exporting data asks for the password again.
Who sees what, and who did what
Your administrators decide who sees what through roles that grant access type by type and refuse everything not granted, and can sign anybody out or block them at once. Every change to a record is written to a history the application cannot alter.
Payments
Card and bank payments are taken on Stripe's own hosted page, so card details never reach our systems. We keep what was asked for, whether it was paid, and the address given for the receipt.
Infrastructure
The service runs on Amazon Web Services behind a web application firewall with rate limits. Threat detection (Amazon GuardDuty) and an audit trail of administrative activity (AWS CloudTrail) are switched on, and software is pinned to exact versions.
Backups
The database is backed up automatically and each backup kept for 7 days, with a copy in a second region. Earlier versions of stored files are kept for 30 days, and restoring from either follows a written procedure.
Our own access
Production is administered with multi-factor authentication, through audited sessions and never shared credentials. We sign in to your workspace only to set it up, to support it when you ask, to keep it secure, or where the law requires it.
AI
Off until your administrator switches it on. It runs on Amazon Bedrock in the same region as your data: Anthropic receives nothing, and Bedrock keeps nothing and trains no model on it. A value you class as sensitive is never sent, unless you choose to have that field's uploads checked.
If something goes wrong
If a breach affects your data we tell you without delay, and within 48 hours at most, with what we know, so you can meet your own deadline to the regulator.
At the end
Ask for an export within 30 days of the end. After that your data is deleted from our live systems and overwritten in our backups within a further 35 days. A person can be erased permanently at any time before then.
Who else handles your data.
Three companies, each under a written contract no less protective than ours. We tell your administrators at least 30 days before we add or replace one.
| Company | What it does for us | Where the data is |
|---|---|---|
| Amazon Web Services | Hosting, backups, the email and text messages you send, and the AI features | London, with a copy of the database's backups in Ireland; or the region you choose |
| Stripe | Your checkout, for a workspace that takes payments on its own Stripe account | The EU and the US, under Stripe's transfer safeguards |
| Our own email: what you send us, and the files you send to set your workspace up, deleted once imported | The US and elsewhere, under the UK extension to the EU-US Data Privacy Framework |
Read the documents for yourself.
The texts your order refers to, each with its version and the day it took effect, and sent with every order.
Data processing agreement
Signed before your data arrives: what we do with it, the measures, breaches and the end.
Sub-processors
Who else handles data for us, what for, and where it is.
Artificial intelligence
What each AI feature does, what it is sent and what it may change.
Terms of Service
The agreement for using bluebric, with your order form.
Privacy notice
What we decide about ourselves: the accounts people sign in with, and our dealings with you.
Acceptable use
What a workspace may and may not be used for.
Cookies
The one cookie we set, to keep you signed in. No advertising or tracking.
Tell us about your event.
A few lines are enough. If you'd rather talk first, say so and we'll call you, or email hello@bluebric.com.
What happens next
- 1We reply within one working day
From hello@bluebric.com, with times for a first call. We never add you to a list.
- 2A call about your event
Who comes, how they apply and what the badge carries. Bring last year's spreadsheet if you have one.
- 3Your plan, in writing
The order form and the data processing agreement to sign before any data arrives, and a setup timed back from your event's date.
Thank you.
We reply within one working day, from hello@bluebric.com, with a date for the first call.