Privacy notice

This notice says what Brio stores about you, why, where, for how long, and what you can do about it. It applies when you use Brio at the web address it is served from, and through Claude.

Who is responsible for your details

The data controller is workbrio.uk, London, UK. You can contact us at info@workbrio.uk.

What Brio is

Brio helps you look for work. It searches job boards for jobs that fit your brief, sorts them with a reason, keeps a record of your applications, and helps you write a CV and cover letters from what you have given it. The work is done by your own Claude, in your own Claude account. Brio runs no AI of its own and never calls a model. Your own Claude writes your CVs and cover letters from your profile and brief, and from your master CV only when there is no profile.

Why we use your details, and the lawful basis

We use your details to run the job search, to write your CV and letters, and to keep your work-search record. Our lawful basis is your consent. You give it when you agree to this notice in the Brio web app. You can withdraw it at any time, which deletes your data (see "Your rights").

What we store

Before you agree. When you ask to sign in, Brio stores your email address and a one-time sign-in code before the consent screen, because sign-in cannot work without them. The code is stored only as a hash, not as the code itself, and it stops working after 15 minutes. Once you have signed in, Brio also keeps a sign-in session and an account record with your email address, the time the account was made and your last sign-in. Brio also counts sign-in requests, as described under limit counters below. Everything else waits for your agreement.

After you agree, Brio also stores what is in this list.

• Sign-in record: your email address, when your account was made, and when you last signed in. Sign-in sessions, short-lived sign-in codes and links, and access and refresh tokens for Claude's connection.
• Your agreement: the name you choose for Brio to use, the time you agreed, and the version of this notice you agreed to.
• Your brief: the work you want, job areas, place, nation, licences you hold, travel, hours, the lowest pay you would accept, anything that rules a job out, experience, skills, and words to search with.
• Your master CV: the text you give Brio, up to 20,000 characters.
• Settings: how many CVs and letters Brio should write for each search.
• Jobs: the adverts found for you: title, employer, place, pay, closing date, the job board, the link, and the reason each one was sorted as it was.
• Applications: the jobs you are interested in or have applied for, with their status, dates, next steps and your notes.
• Documents: the CVs and cover letters written for jobs you chose, and their Word and PDF versions.
• Profile documents: the text of the documents you add, such as your CV, certificates and references, up to 10 documents of up to 60,000 characters each. Brio stores the text, not the file. A PDF is read in your own browser and only its text is sent. A Word file is sent to Brio so that its text can be read, and the Word file itself is not kept.
• Profile: one profile for you, which your own Claude writes from your documents and what you tell it, and which you can edit in the web app.
• Work-search record: the applications above, and any activity you add yourself, with its date, type, employer, role, how it happened and the outcome. The work-search PDF you download prints your email address at the top, under "Prepared by". If you pass that file on, the address goes with it.
• Search runs: when each search ran, how many jobs it found, and for each job board whether it could be read, with the search address used. A search address can include your place and search words.
• Limit counters: a count of sign-in emails and requests, kept under a hash of your email address or of the network address the request came from, so that abuse can be stopped.
• Server logs: for each request, the page address asked for, the request method, the reply code and a short event name, such as "link sent". When something fails, the error log also holds the last part of the error trace. That can include text from the error, such as an email address. Logs are kept for 14 days.

Brio does not ask for your National Insurance number, date of birth, health details or benefit claim details. Brio asks you not to put them in your brief or CV, and its instructions to Claude say to leave them out of what Claude saves for you. Nothing in Brio checks for these details or removes them, so they can still be stored if they are typed or pasted in. If they are, they are kept for the same time as the rest of your record, and you can change or remove them in the web app, or delete all your data.

Where it is kept

Your records are kept in Amazon DynamoDB in the UK (London) region, and are encrypted while stored. Brio's code runs in the same UK region. Connections to Brio use HTTPS.

The web app and its files are delivered through Amazon CloudFront, a content delivery network. It holds copies of the web app's files and does not hold your records.

Who else handles your details

Brio uses these Amazon Web Services, as sub-processors:

• Amazon DynamoDB: stores your records.
• AWS Lambda: runs Brio's code.
• Amazon Simple Email Service (SES): sends your sign-in emails from sign-in@workbrio.uk.
• Amazon CloudFront: delivers the web app and passes requests on to Brio.
• Amazon S3: holds the web app's files.
• AWS Systems Manager Parameter Store: holds a secret that Brio uses to check requests.
• Amazon CloudWatch Logs: holds the server logs.
• AWS Certificate Manager: holds the certificate for the site.

Claude. Brio works through your own Claude account. Claude reads your brief, CV and jobs to do the work, so Anthropic, which provides Claude, handles them when you use Claude. Claude also reads your profile and your documents. That is covered by your Claude account's terms and privacy policy. Brio does not hold your Claude login, and Brio itself does not send your details to Anthropic.

Job boards. When Claude searches a job board for you, it sends that board the search words and place from your brief. Brio never sends anything to a job board itself.

How long we keep it

• Brief, master CV, jobs, applications, documents, work-search record and settings: up to 365 days.
• Profile documents: up to 365 days from when each was added. Profile: up to 365 days from its last save.
• Search runs: up to 90 days.
• Sign-in sessions: 30 days. Refresh tokens: 30 days. Access tokens: 1 hour.
• Sign-in codes and links: 15 minutes. Claude's one-time authorization code: 5 minutes.
• Invites: 90 days.
• Account record: until you delete your data, and up to 365 days after your last sign-in or change to your account.
• Limit counters: up to 2 hours. Server logs: 14 days.

Records are kept until they expire, and Brio stops using an expired record straight away. The database removes expired records automatically, usually within a few days. Brio keeps no backups, so when you delete your data it is removed from Brio's account at once, apart from that automatic removal.

Who can see your details

You can see your own data in the Brio web app. Only the people who run Brio's AWS account can reach the stored records, and only to run the service. Other people, and other jobseekers, cannot see your data.

Your rights

• See and take a copy. Under Your data in the web app, download everything Brio holds about you as one file, with your CVs and letters as Word and PDF files. That file includes your profile and the text of your documents. You can also ask Claude to export your Brio data.
• Correct it. Change your brief, CV, applications and activity in the app. To correct anything else, contact us at info@workbrio.uk.
• Delete it. Under Your data, type DELETE to delete everything Brio holds about you. This also signs you out. You can ask Claude to do the same. Deleting takes your invite and your account with it, so you would need a new invite to use Brio again. Your profile and your documents are deleted with everything else.
• Remove one document. Under My profile in the web app, remove any one profile document. Its text is removed from Brio at once.
• Withdraw consent. Withdrawing consent runs the same deletion.
• Complain. You can complain to the Information Commissioner's Office (ico.org.uk) about how we handle your details.

Cookies

Brio sets brio_session, which keeps you signed in. When you sign in from Claude, it also sets a cookie that holds that sign-in request for 15 minutes. Both are needed for the service to work. Brio uses no advertising or tracking cookies and no third-party scripts.

Changes to this notice

If we change this notice, you will be asked to agree to the new version before Brio stores anything more about you.