How it works

How licensing works

This is an outline of how a licence of business records is usually put together, for record holders and for AI teams. It is not a contract and there are no default terms. Every deal is agreed in writing for its own records, buyer and permitted uses.

The stages

  1. Describe. A record holder describes what they hold, or an AI team describes the task and the records it needs. No files, logins or passwords.
  2. Review. We talk through fit, ownership, authority and restrictions, and say plainly if it isn't a fit.
  3. Confidentiality, if needed. Where more detail is needed, confidentiality terms are agreed first. A confidentiality agreement is not permission to use records for AI.
  4. Agree terms in writing. Scope and permitted uses are settled before anything is shared.
  5. Sample or assessment, if agreed. A limited, prepared sample may be reviewed under those terms. A sample is not automatically licensed for later training or redistribution.
  6. Licence. Only on a signed agreement. The record holder decides whether to go ahead, and the AI team decides whether the records fit its task.

For record holders

You stay in control throughout. You choose what is in and what is out: whole clients, projects, folders or record types can be left out, and many businesses leave out HR and payroll entirely. Before any detailed review, we check who holds the rights to the records and what personal information they contain. You and the buyer agree how records are prepared and how personal details are handled, and the files are supplied only to the named licensee. Payment terms are set out in the agreement before anything moves. See licensing your business records.

For AI teams

We start with your task, not with an archive. The brief sets out what you want a model to do, the records and links it needs, the formats, date ranges and scale, and the intended uses: training, fine-tuning, evaluation, retrieval or building environments. If there is a fit, we introduce you to a record owner. The owner and the buyer agree rights, preparation, personal-data handling and any bounded evaluation directly. Our introduction fee is paid by the buyer. The Maevar approach sets this out in five steps.

What a written agreement usually covers

  • Exactly which files, systems, years and versions are included, and what is excluded
  • Permitted and prohibited uses, and whether the licensee can share or sublicense
  • Whether it is a licence or an outright sale, and any exclusivity by dataset, use, period or territory
  • How long the licence lasts, and what happens to copies, derived data and trained models when it ends
  • Who prepares the records, how personal and confidential information is handled, and who pays for preparation
  • How the licensee reviews or rejects a delivery
  • Price, when payment is due, and delivery
  • Who owns the originals and any prepared copies, and what the record holder can keep doing with its own records
  • Which law governs the agreement and how disputes are resolved

Every one of these is agreed for the specific deal. We don't publish standard positions, and we can't promise a buyer, a price or a completed deal. Each party should have its own adviser review any agreement before signing. More on the clauses themselves is in data licensing agreement: key terms.

See also rights, authority and how records are handled and the FAQ.

Start a conversation

Use the Maevar enquiry form or email hello@maevar.com. A short, non-confidential description is enough to begin.

Maevar privacy notice

21 October 2026

Who we are

Maevar is operated by Marcias Limited, company number SC653353. Marcias Limited is responsible for the personal information covered by this notice.

Registered office: 51 Watt Road, Hillington, Glasgow, G52 4RY, United Kingdom.

For privacy questions or requests, email hello@maevar.com.

This notice covers this website and enquiries sent to Maevar. Any proposed introduction of a record owner to a buyer, or any sale or licence they agree, requires a separate review of the relevant rights, privacy requirements and agreed terms.

Enquiries and information you provide

The enquiry fields help you prepare an email containing your work email address, organisation, task summary and any optional format or timing details. The draft is prepared on your device. The website does not submit or store it: you choose whether to open, review and send it using your email app. There is no file-upload facility.

Please provide only a non-confidential summary. Do not include datasets, personal records, passwords or other sensitive information.

When you send an email, we receive the message, your contact details and any other information you choose to include. Richard McKay handles enquiries. Authorised service providers and connected tools, including AI-assisted tools, may support the handling of correspondence.

Why we use your information

We use enquiry information to respond, understand your requirements, assess whether we can help and discuss relevant business opportunities. We rely on our legitimate interests in managing business enquiries and developing appropriate business relationships, while considering your rights and reasonable expectations.

We also have a legitimate interest in keeping the website and email services secure and reliable. Where we must retain or disclose information to meet a legal obligation, we rely on that obligation.

Website and email services

We use OpenAI's ChatGPT Sites to host this website, Cloudflare for website delivery, security and email routing, and Google Workspace to receive and manage email enquiries. These services process information needed to deliver and protect the website and email service. This can include IP addresses, browser information, access times and technical or security logs, as well as email information when you contact us.

Optional analytics is controlled separately from necessary hosting and security services. Cloudflare uses a bot-protection cookie called __cf_bm, which normally expires after 30 minutes of inactivity. More information is available in Cloudflare's cookie documentation.

Optional analytics and your choice

Google Analytics loads only after you accept analytics. Rejecting keeps optional analytics off.

We load Google Analytics only after you accept it. Rejecting does not stop you using this website or contacting us. Necessary hosting, delivery and security services continue to operate, including their technical logs.

With your permission, analytics measures page visits and limited website interactions. We use fixed page information without search queries or URL fragments. We do not send your name, email address, organisation, enquiry text, form answers or the contents of email-draft links to Analytics. Analytics is not a record of the contents of your enquiry.

The email preparation tool may record that an email draft was prepared, without any of its contents. This is an expression of interest only: the website cannot tell whether you send the email. It is not counted as a submitted enquiry.

No Google Ads, Meta or LinkedIn advertising tags are activated by these controls. Advertising storage, advertising user data and ad personalisation remain disabled. We do not use enhanced conversions or upload contact details to Analytics.

Your privacy choice is stored on this website in your browser for up to six months. If you accept analytics, Google Analytics may set first-party cookies named _ga and _ga_ followed by the property identifier. Our code sets a maximum cookie lifetime of six months; your browser may apply a shorter limit. Google processes the analytics information and may process it outside the UK. See Google’s privacy policy. Our Google Analytics property retains user-level and event-level data for two months, without restarting that retention period when you return. This setting does not limit how long Google retains standard aggregated reports. Optional Google data sharing, Google Signals, user-provided data collection, granular location and device collection, and advertising personalisation are switched off.

Use Cookie settings in the footer to change your choice. Withdrawing analytics consent stops new measurement and reloads the page into a no-analytics state, so save any unfinished enquiry first. It also removes the relevant first-party analytics cookies where the browser permits. This does not erase information already sent to Google. We do not replay interactions that happened before you consented.

Our service providers may process information outside the UK. Their published data-processing terms describe the applicable international-transfer safeguards, including recognised adequacy arrangements and contractual safeguards:

Contact hello@maevar.com if you would like further information about these arrangements.

How long we keep information

We review unsuccessful enquiries 12 months after the last substantive contact and delete them unless there is an ongoing business or legal reason to retain them. For example, information may still be needed for an active discussion, to meet a legal obligation, or to establish, exercise or defend legal claims. Where we retain information longer, we keep it only for as long as that reason applies.

Enquiries that lead to a business relationship and related contract records are kept according to the needs of that relationship and applicable legal requirements. The 12-month enquiry review period is not a guarantee that every provider's security log or backup is erased on the same date; those records are subject to the relevant service's retention and deletion arrangements.

Your rights and complaints

Depending on the circumstances, you may ask to access, correct or delete your personal information, restrict its use, or receive a portable copy. You may also object to processing based on legitimate interests. These rights are subject to applicable conditions and exceptions.

Email hello@maevar.com to make a request or raise a concern. You can also complain to the Information Commissioner's Office through ico.org.uk/make-a-complaint.

Changes to this notice

We will update this notice when our website or information-handling arrangements change. The date above identifies the version you are reading.