Records

Record types

Short guides to the records we're asked about most: what tends to be useful, what usually stays out or needs care, and how to prepare. They apply whether you hold the records or want to license them. For the wider picture of how records connect, see the data families on the homepage.

Email

Email threads show who knew what, what it cost and what was decided. That context is hard to find anywhere else.

What tends to be useful

  • Threads with customers and suppliers about quotes, orders, changes and problems
  • Internal discussion where decisions were made
  • Attachments that link back to jobs, orders or drawings

What usually stays out, or needs care

  • Personal and HR email, payroll, and anything about individuals' health
  • Client material held under confidentiality, unless the client agrees
  • Payment details and passwords

Preparing: email accounts often close when the bills stop, so check what is still retained and exportable. A mailbox export does not by itself establish permission to license everything inside it.

Slack and Teams chat

Chat channels capture the quick fixes and decisions that never make it into a manual.

What tends to be useful

  • Project and operations channels where work was coordinated
  • Threads that link to tickets, orders or drawings
  • Support and engineering channels

What usually stays out, or needs care

  • Private messages and personal conversations
  • HR, disciplinary or health discussions
  • Shared channels with other companies, unless they agree

Preparing: export options and retained history depend on your plan and settings, so check them before an account is downgraded or closed.

CAD and engineering files

Drawings with their revision history show how designs changed and why.

What tends to be useful

  • Drawings with revisions, tied to the job or part
  • Calculations, specifications and technical reports
  • Change requests and the correspondence around them

What usually stays out, or needs care

  • Designs owned by clients or architects under your contracts
  • Material under export-control or defence restrictions
  • Files that can't be opened without lapsed software licences

Preparing: keep revisions together with the job or part they belong to, and check that the files still open.

Job and project files

A job file follows the work from enquiry to invoice. Linked together, these records show how a business really ran.

What tends to be useful

  • Quotes, estimates and take-offs, with the notes behind them
  • Job sheets, site diaries, inspection and completion reports
  • Project software histories, for example from Jira, Asana or Procore

What usually stays out, or needs care

  • Customers' personal details
  • Client-owned documents and anything under a confidentiality agreement
  • HR and health and safety records about individuals

Preparing: the links between records matter most, so keep job references, dates and versions intact where you can.

CRM and customer support records

Tickets and account histories record real problems, fixes and outcomes.

What tends to be useful

  • Support tickets and their resolutions
  • Account and order histories, with customers' details removed
  • Service notes and knowledge-base articles

What usually stays out, or needs care

  • Customer names, contact details and anything that identifies individuals: these need the most care
  • Payment details
  • Customer databases themselves, which raise separate legal questions

Preparing: customer records are heavily regulated, so expect careful scoping under the applicable privacy law.

Source code and software records

Code with its history, reviews and tickets shows how software was really built and fixed.

What tends to be useful

  • Repositories with commit history and code review
  • Linked tickets, incidents and design documents
  • Data team files such as pipelines and dashboards

What usually stays out, or needs care

  • Code written for clients who own it under contract
  • Third-party and open-source code under licences that restrict reuse
  • Secrets: keys, passwords and credentials. Never send these

Preparing: ownership is the first question, then whether history and linked tickets survive export.

Lab and research data

Raw results with the judgement calls, retests and notes show how real analysis gets done.

What tends to be useful

  • Test and assay results with the methods and notes behind them
  • Instrument outputs linked to samples and reports
  • Quality and calibration records

What usually stays out, or needs care

  • Patient and clinical data, and other health information: usually excluded
  • Data owned by clients or research sponsors under contract
  • Anything under ethics approvals or consent terms that don't allow reuse

Preparing: keep results linked to their methods, samples and reports.

Recorded calls

Recorded conversations between staff and customers can be useful to AI teams building voice and customer-service tools.

What tends to be useful

  • Everyday customer calls: sales, service, bookings and scheduling, dispatch and support, handled by the business's own staff
  • Calls the business owns. Calls recorded on behalf of a client are normally for that client to decide about
  • Volume and history. More hours over more years is generally more useful. Transcripts help but aren't essential

What usually stays out, or needs care

  • Health, payment and other sensitive details, which are usually left out
  • Calls where the recording terms, or the call-recording provider's terms, restrict reuse

Preparing: a "calls may be recorded" message tells callers that recording happens. On its own it does not give permission to use the recordings for AI training or to license them. Who owns the recordings, what callers and staff were told, and how personal data would be handled all need checking first.

Next step

Don't send files: describe what you have. How rights and personal data are handled is on rights, authority and how records are handled. Record holders can start at licensing your business records; AI teams can discuss a use case. Or email hello@maevar.com.

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.