solves.
Menu
Legal

Our policies, in plain English.

The home for the Solves policies: privacy, terms, cookies, acceptable use, data retention, pilot terms and the Data Processing Agreement. Solves is an early pilot, so we are honest that the full, signable documents are still being completed before public paid launch.

These policies govern your use of Solves during the pilot. Where a document is still being finished, we say so on its page rather than implying it is final.

Plain EnglishWritten to be read, not decoded
Honest about pilotFull documents in preparation before paid launch
Encrypted at restPer-organisation keys, authorised access only
Metadata-only logsNo message bodies, addresses or payloads

The short answer

One place for every Solves policy

This hub links every Solves policy in one place, each in plain English. They cover how we handle personal data, the terms you agree to, how cookies are used, what counts as acceptable use, how long data is kept, the pilot arrangement, and the DPA for your customers' support content.

We are straight about our stage. The full, signable documents are in preparation before public paid launch, and we would rather hand you policies we can stand behind than publish hurried templates. Where a document is still being finished, its page says so and describes our intended handling truthfully, alongside the controls already running.

The policies

Every document, and what it covers

Each card links to a policy. Open any one to read it in full and see honestly where it stands during the pilot.

Privacy notice

What personal data Solves holds, why, how we protect it and the rights you and your customers have.

Read it

Terms of service

The general terms that govern your use of Solves: what you can expect, and what we ask in return.

Read it

Cookie policy

The cookies and similar storage Solves uses, what each is for, and how to control them.

Read it

Acceptable use

How Solves may and may not be used, so the service stays safe, lawful and dependable.

Read it

Data retention

How long Solves keeps your support content and account data, and what happens when you leave.

Read it

Pilot terms

What beta status means, the early-adopter offer, cancellation, export and data handling during the pilot.

Read it

Data Processing Agreement

Controller and processor roles, the security measures and the sub-processors involved. A signable DPA is in preparation, available to pilot customers on request.

Read it

How they fit together

Which policy answers which question

For the support content your customers send you, the privacy notice and the Data Processing Agreement work together. You are the controller of that content and Solves is your processor, handling it on your instructions and for nothing else. We do not sell it or use it to train models. The data retention policy explains how long it is kept and what happens when you leave.

What these pages do not claim

We do not claim UK GDPR compliance as a badge, and we carry no certification marks. We do not name a hosting provider beyond a UK or EU cloud host, promise an uptime figure, or claim guaranteed email delivery, because final delivery depends on receiving mail servers we do not control.

A signable agreement is available to pilot customers on request

If your team needs a signed Data Processing Agreement before going live, get in touch through our contact page and tell us you are running the Solves pilot. We will share the current draft and put a signed agreement in place.

FAQ

Legal questions, answered

Are these the final legal documents?

Not yet, and we say so plainly. The full, signable documents are still in preparation before public paid launch. The pages here describe our intended handling truthfully and set out the controls already running.

Which policy covers my customers' data?

The privacy notice explains what personal data we hold and why, and the Data Processing Agreement sets out the controller and processor roles. You are the controller of your customers' enquiries and Solves is your processor, handling that data on your instructions.

Does Solves claim to be UK GDPR compliant?

We do not make a blanket compliance claim, because whether a deployment is compliant depends on how you configure and operate it. We can state concretely that support content is encrypted at rest under per-organisation keys, access is authorised and scoped, and our logs are metadata only.

How do I get a signed agreement in place?

Get in touch through our contact page and tell us you are running the Solves pilot. We will share the current draft, work through any clauses your team raises, and put a signed agreement in place before you go live.

Questions about any policy?

Read how we protect your data, or get in touch and we will work through the detail with you.