Case notes / reviewed 2026-07-13
Why Rel8r Runs on Your Machine: A Local-First Privacy Explainer
How Rel8r keeps your dating screenshots, messages, and relationship memory off our servers — and why that matters in a market built on reading your screenshots.
Most AI dating assistants work the same way: you upload a screenshot of a conversation or profile, their servers read it, and their servers generate a reply. That is fast and convenient. It also means a company you do not know is storing, processing, and potentially training models on some of the most private signals in your life.
Rel8r is built on a different assumption: **your dating screenshots are yours.** The phone is just the intake surface. The thinking happens on your computer. The memory lives in files you can open, move, or delete.
What local-first actually means
When you send Rel8r a screenshot or pasted message through Telegram, the bot receives the image. Then the Rel8r runtime on your own machine downloads it, redacts sensitive metadata, runs the attachment-scene analysis, and writes the result into your local vault. At no point does JobCoffin see the screenshot, the message, or the coaching response.
The only data that leaves your machine is:
- The Telegram message itself, which travels through Telegram's infrastructure the same way any other Telegram message does. - Any API calls you choose to make to your own LLM provider, using your own key, under your own account terms.
JobCoffin does not operate a central database of your relationships. We do not have a dashboard where we can peek at your vault. We cannot train on your data because we never collect it.
How to verify it
Every Rel8r release ships with:
- A release manifest that lists every file in the package.
- A SHA-256 checksum you can compare against the download.
- A `START_HERE.md` that walks you through the local setup, including where the vault is stored and how to inspect it.
- Simulation mode, which lets you test the entire workflow before you add any Telegram bot token or LLM provider key.
If you are technical, you can open the runtime code, read the ingestion handlers, and confirm that screenshots are processed locally. If you are not technical, you can still see the vault files on your own computer — Markdown and JSON you own outright.
Why this matters compared to SaaS dating assistants
Apps like Winggg, YourMove AI, RIZZ AI, and CupidAI are hosted services. Their privacy policies generally say they collect the content you submit, device data, and usage analytics. Some reserve broad rights to use that content for product improvement. That is standard for SaaS. It is also the opposite of how Rel8r works.
With Rel8r, there is no vendor lock-in, no subscription to cancel, and no risk that a company pivot, acquisition, or data breach exposes your dating history. The worst-case scenario is a problem on your own machine — and you can unplug that machine at any time.
What about the optional cloud add-on?
Rel8r Cloud Operation is available for buyers who want 24/7 uptime without managing the daemon themselves. Even then, the runtime operates on infrastructure you control, using your credentials, and the memory layer remains portable. It is not a shared multi-tenant service where strangers' screenshots live alongside yours.
The short version
Rel8r is a tool you buy, not a service that farms your intimacy. Your screenshots stay on your hardware. Your patterns stay in your vault. Your skills stay with you even if you never open JobCoffin again.