Pairing an e-reader with LingoBlend hands it a narrow, named set of permissions — download your books, send clipped words, optionally report reading time — and nothing else: it cannot see your saved words, your profile, or your subscription, and you can revoke it any moment from your readers page. This post lays out what a paired reader can and cannot do, plus two things worth being deliberate about: approving the right code, and using the reader's web page on WiFi you trust.
Pairing is the step underneath the parts of the CrossPoint integration that are yours: it's what lets books you've blended appear on the device without copying files by hand, and what lets clipped words make it back into the app. It isn't underneath the rest — the free library, the companion dictionaries, and the OPDS catalog all work with no account and no pairing at all.
How pairing actually works#
Pairing happens on the CrossPoint e-reader and the LingoBlend website — there's no pairing screen in the mobile app; pairing and management both live on the website. Two things need to be in place before any of it works: CrossPoint 1.7 or a Nightly build (1.7 has no release date yet), and the LingoBlend plugin, installed once from the reader's File Transfer web UI → Plugin Store by adding the catalog URL https://www.lingoblend.app/crosspoint/catalog.json. On a 1.6.x reader there's no LingoBlend plugin to sign in from, because the plugin system itself arrives with CrossPoint 1.7 — that's expected, not broken.
Once the plugin is installed: Settings → System → Plugins → LingoBlend → Sign in. The reader shows a QR code and the same code in text, as eight characters in the form XXXX-XXXX — so you can check it's the one that comes up after you scan.
- Scan the QR code with your phone.
- Sign in to LingoBlend if you aren't already — email and password, or Google.
- The page shows exactly what this reader is asking for, in plain language, including the eight-character code to check against your device.
- Approve it. The reader confirms the sign-in and shows your account is connected.
Nothing happens silently in the background — the device can't complete pairing until a human says yes on the website.
What a paired reader can do, and what it cannot#
A paired reader's access is scoped to exactly the things the integration needs and nothing broader. This is the full list in both directions:
| A paired reader CAN | A paired reader CANNOT |
|---|---|
| List and download the books you've blended | Read your saved words or dictionary |
| Send the words you clip while reading | Read your profile |
| Report reading sessions, but only if you turn that on | See your subscription or billing status |
| — | Change anything in your account |
That second column isn't a promise taken on faith — it's a boundary that's been through a dedicated security review. The device has no door to any of those rooms: the left column is the entire surface it was built to reach.
It's worth noting why the "can" side is that short. The reader doesn't need your saved-words list to show a blended book — the book already has everything baked in. It doesn't need your profile to know which words you clipped — clipping writes straight to the SD card. And it never needs your subscription status, since what you can blend is decided on the website. A narrow job gets narrow access.
The numbers that bound what a lost or stolen code could do#
Every pairing has a shelf life, on both ends — before you approve it, and after:
| Limit | Value |
|---|---|
| Pairing code validity | 10 minutes |
| Code reuse | Single-use — each code works once, then it's dead |
| Readers per account | Up to 5 |
| Access per reader | Expires after 12 months |
| Removing a reader | Takes effect immediately |
The ten-minute window and single-use rule mean a code has almost no shelf life for anyone but you, standing at the device, in that moment. The five-reader cap and twelve-month expiry mean an old pairing you forgot about doesn't sit active forever. And removal isn't a request that's "processed" later: the moment you remove a reader on your readers page, it drops straight back to its sign-in screen.
The one rule that actually matters: only approve your own code#
Everything above is a technical boundary. This one is a human one, and it's the part worth remembering even if you forget every number on this page: only approve a pairing code you are reading directly off your own reader, right now. If a code was sent to you — by email, by message, by anyone — close the page without approving it.
This matters because a pairing code can be put in front of anyone — the same shape as any login code sent to the wrong person. The approval page says exactly this in plain words, and it's the one scenario none of the technical limits above catch: approving is the thing that grants access, so a code approved by the wrong person defeats everything else here. The only safe habit is to approve a code you are reading off your own reader, right now, and nothing else.
What a clipping sync actually sends#
When you clip a word on a paired reader and sync it, here's precisely what travels, and what doesn't:
- Sent: the clipped word or short phrase, the book's title, and the page it came from.
- Not sent: anything longer than a few words — a clipped sentence or passage is counted and skipped, not synced as a dictionary entry.
- Capped: up to 200 clipped words a day sync to your account — clip as many as you like while you read, and anything over that waits for the next day.
- Never sent to an AI provider: a word from a blended book already carries the meaning the book gave it, so nothing is re-translated. A word the blend didn't touch is translated by LingoBlend's self-hosted translation service — never a large language model. Same on-device-versus-server question that matters for any tool reading your text.
- Only what's new: each sync sends just the part of your clippings file added since the last one, so syncing twice never creates duplicates, and the file itself —
My Clippings.txt, the same format a Kindle uses — is never modified or deleted on the card.
Reading time: opt-in, and kept away from your reviews#
One more thing a paired reader can report, only if you ask it to: reading time. The toggle lives on your readers page, it's off by default, and it's set per reader — pairing a second device doesn't inherit the first one's setting. When it's on, the reader reports when a session started and ended, how long it ran, and which book, sent over WiFi the next time it sleeps. That counts toward your daily goal and streak, same as reading time logged anywhere else.
What it never does is touch spaced-repetition scheduling. The reader has no way to know which words you actually reviewed, only that a page was open — so letting sessions influence when a word comes up for review would mean inventing review history that never happened. That's a line kept on purpose: scheduling only works if every signal feeding it reflects something actually tested.
Checking and removing readers#
Your readers page is the single place to see every reader paired to your account, and every control above lives there: each one shows the name it was given at pairing, when it was last seen, and how many words it's synced, plus a rename, the reading-time toggle, and remove — removal takes effect immediately, dropping the device back to its sign-in screen. There's no equivalent screen in the phone or tablet app; pairing and management both live on the website.
One more thing worth knowing: the File Transfer web UI itself#
Separate from pairing, but worth flagging: when you put your reader on WiFi for File Transfer (to sync clippings, install a plugin, or copy files), it serves its File Transfer web UI over plain http at a local address — anyone else on the same WiFi could, in principle, open that same address while File Transfer is on. The practical answer is simple — use File Transfer on WiFi you trust, your home network rather than a café or airport, and leave File Transfer mode when done. This is separate from account pairing: it's about the local page the reader serves on your network, not what your account grants it.
Where this falls short#
Being straightforward about the edges: pairing itself needs CrossPoint 1.7 or a Nightly build, and 1.7 has no release date yet — on a 1.6.x reader, the free library, USB and OPDS paths all work today, but pairing doesn't. Approval still depends on a human reading the page carefully, and the ten-minute window helps but doesn't replace that. There's no log of every individual sync: your readers page shows when each one was last seen and how many words it's synced in total, not a history of each sync. And because management lives on the website, checking your readers means opening a browser rather than a tab you're already in.
The takeaway#
Pairing grants a CrossPoint reader three things, one of them optional, and nothing beyond them — and every one can be checked, renamed, or pulled back in a click (with a confirmation) from your readers page. The approach leans on short-lived single-use codes and a plain-language approval screen rather than asking you to trust a black box. The one habit worth keeping: approve a code you are reading off your own reader, right now, and nothing else.