Privacy Policy

Glue Labs Private Limited · Last updated 25 August 2026

This policy covers Glue, the macOS application. It is short because Glue is built so that there is little to describe: your mail, notes, tasks and calendar are stored on your own computer, and we have no copy of them.

What we do not collect

We do not collect your email, notes, tasks, calendar events, attachments, or anything derived from them. We do not collect device identifiers, IP-based profiles, or usage analytics. The one exception is training, which you start yourself, one run at a time — see Training your model below.

Glue contains no analytics and no telemetry. This is not a setting you have to find and switch off; there is no such code in the application.

Where your material lives

In a folder on your Mac, under your Library, which you can open, copy, back up or delete at any time. Notes and mail are stored as ordinary Markdown files. The search index is a SQLite database beside them, derived from those files and rebuildable from them.

Searching, indexing, and the language and speech models all run on your machine. Deleting the application's folder deletes everything Glue holds.

When Glue uses the network

Only for things you have asked it to do:

• Your mailbox. If you connect a Google account, Glue reads your mail and calendar from Google to index them locally. This is a direct connection between your computer and Google. Access is granted by you through Google's own sign-in and can be revoked there at any time. Reading is read-only; sending or deleting happens only when you click to approve it.
• Models. On first use, Glue downloads the local models it runs. This is a file download and carries nothing about you.
• Updates. Glue checks a file on gluelabs.com for a newer version. This is an ordinary web request; we do not associate it with an individual.
• Licence activation. When you activate a licence, Glue sends the licence key and an identifier for the machine so we can check the licence is valid and count how many computers are using it. The machine identifier is a one-way hash — we cannot recover which computer it came from, and it differs per licence, so two licences on the same machine cannot be linked.
• Training, if you start it. Glue sends the training set you approved, and downloads the adapter that comes back. Nothing is sent until you have seen what it contains. See Training your model.
• Anything you point it at. If you add a news feed or a meeting link, Glue fetches from that source. Images inside emails are not loaded until you ask, because remote images are commonly used to track when a message is opened.

Training your model

Glue learns from your corrections as you make them, on your Mac, with no training involved. You can also go further and train the local model itself. That is the one time material derived from yours leaves your machine, so this section says exactly what happens.

It is opt-in and one run at a time. There is no standing permission, no background training, and nothing happens unless you start it.

The training set is prepared on your Mac, before anything leaves. It is a small subset of your material: the examples relevant to the one thing you are teaching, not your corpus. It is stripped of personally identifying information here, on your computer. Names, email addresses, phone numbers, handles, postal addresses and account numbers are replaced. Glue can do this well because it already knows who the people in your material are, so it is matching against names it holds rather than guessing from the text alone.

You see the prepared set before you approve it, in the form it would be sent, and nothing is sent if you do not approve it. The map between the real names and their replacements never leaves your Mac, and is discarded when the run finishes.

The run itself happens on rented GPUs. What comes back is an adapter file — a small set of weights that runs on your Mac. The training set is deleted when the run finishes. We do not use it to train anything of ours, and we do not use it for any purpose other than the run you asked for.

Whether the result is any good is decided on your machine. Glue keeps a portion of your corrections back as a test, never sends them, and checks the returned adapter against them before offering to use it.

Claude, and other assistants

Glue can connect to Claude Desktop so that Claude can search and work with your material. When you use it this way, the parts of your material that answer your question are sent to Anthropic by Claude Desktop, under Anthropic's privacy policy, not ours.

Before anything is handed over, it passes an egress gate that removes credentials, API keys and similar secrets. This connection exists only while you are using it, and Glue works fully without it — the search, the index and the local models do not involve Claude at all.

What we do hold

If you buy a licence, we hold your email address, the licence, and the hashed machine identifiers registered against it, so that we can support you and honour the three-machine allowance. Payment is handled by our payment provider; we never see your card details.

If you have run a training job, we hold a record that it ran — when, and whether it succeeded — and the adapter it produced, until your Mac has collected it. The training set itself is deleted when the run finishes.

If you email us, we hold that correspondence.

Your rights

You can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted — though deleting a licence record ends the licence. Write to privacy@gluelabs.com.

For everything stored on your own machine, no request is needed: it is yours, in files you can read, and you can delete it yourself.

Changes

If this policy changes materially, we will say so in the application rather than quietly updating this page.

Contact

Glue Labs Private Limited · privacy@gluelabs.com