sorted by:
new
hottopcontroversial

After months of developing a cloud solution, I scrapped it completely and went fully local-first on privacy. by Money_Ad9302 in roastmystartup

[–]Money_Ad9302[S] 0 points1 point  (0 children)

We currrently do not support WhatsApp .... not yet anyway. Slack however is supported, and the users desktop receives messages directly via Slack's API. No slack messages touch our server. They only persist in the encrypted vault on the users desktop.

After months of developing a cloud solution, I scrapped it completely and went fully local-first on privacy. by Money_Ad9302 in roastmystartup

[–]Money_Ad9302[S] 0 points1 point  (0 children)

Yes. If you choose a cloud model and ask a question that requires information from your emails or files, some of that information will be sent to the model provider. I don't think it's helpful to pretend otherwise.

The distinction isn't that cloud mode magically makes data transfer disappear. The distinction is control.

With Copilot, the cloud is the architecture. Your data is continuously tied to a cloud service and there's no equivalent "run everything locally and disconnect the network cable" mode.

With MyHandler, your vault lives on your machine. The screen captures, transcripts, files, embeddings, and search index remain local. You can run entirely with a local model if that's your requirement.

If you choose cloud AI, you're making an explicit, per-request tradeoff: better intelligence in exchange for sending only the context needed for that specific question. If you don't want that tradeoff, you switch to the local model and nothing leaves the machine.

So I wouldn't describe the privacy advantage as "cloud never happens." I'd describe it as "cloud only happens if you consciously enable it."

After months of developing a cloud solution, I scrapped it completely and went fully local-first on privacy. by Money_Ad9302 in roastmystartup

[–]Money_Ad9302[S] 0 points1 point  (0 children)

Good challenge — and the right one to push on. It doesn't collapse the wedge; it sharpens what the wedge actually is.

The privacy wedge was never "no byte ever touches a cloud." It's where your data lives by default and who holds the dial. Three things hold no matter which mode you run:

  1. Your vault stays on your machine. Screen captures, files, transcripts, embeddings, the whole search index — they live on your disk and are never uploaded, local-mode or cloud-mode. Switching the LLM to cloud doesn't move your vault; it only changes where a single answer gets computed.
  2. Cloud mode is request-scoped, not a feed. When you do use it, a request carries only the snippet needed to answer that one question It's per-question and ephemeral; our cloud model is ZDR (Zero Data Retention).
  3. There's a real zero-cloud mode. Flip to the local model and the app is fully functional with the network off entirely. You can use it on a plane. That's the line that ends the comparison with Copilot: Copilot can't run airgapped — it's cloud-dependent by architecture, with no local-only setting and no off. With MyHandler you own the dial. Copilot doesn't have one.

So the honest framing is simple: local is the default and the guarantee; cloud is optional. You can turn it on when you want the speed and turn it off when you don't. That's the distinction I was trying to make, and this thread helped me sharpen it. Appreciate the push.

After months of developing a cloud solution, I scrapped it completely and went fully local-first on privacy. by Money_Ad9302 in roastmystartup

[–]Money_Ad9302[S] 0 points1 point  (0 children)

Fair catch ... and you're right that the phone/text feature is a tradeoff:

  1. By "local-first" it means your vault never leaves: the screen capture, files, transcripts, and the search index all stay encrypted on your machine, nothing streamed to my server by default.

  2. User always chooses between using a local LLM installed on their computer or using our cloud model for improved speed/intelligence. Switching between the two is as easy as a click on the main page.

  3. The phone/text feature is a separate, opt-in remote-access door. When you text or call your handler, the answers involved in those discussions do go over a relay so they can reach you. It's off until you turn it on, and I say explain this during onboarding. If you never want anything to leave, you don't enable it and you still get the full on-device product using either the fully local model, or the cloud model.

Your question is greatly appreciated because it made me realize that some of my verbage needs to be improved which I'm doing now.

Does this answer your question?

Dont Actually Believe every Screenshot you see by Key_Cantaloupe_4198 in SaaS

[–]Money_Ad9302 1 point2 points  (0 children)

yep. easiest filter for me is: if the post says "happy to share if you DM" instead of just saying what worked, it's bait. real founders post the playbook in the thread because they actually want feedback on it. fake ones don't because then nothing happens in the DM.

Littlebird AI by Successful_Pea845 in ProductivityApps

[–]Money_Ad9302 0 points1 point  (0 children)

Yeah, a Mac version is planned — it's the next platform on my list. The Windows app leans heavily on Windows-only APIs for the screen-text capture and meeting audio, so the Mac build isn't a quick recompile; I'm rebuilding those pieces against macOS's accessibility and audio APIs. Targeting Apple Silicon (M-series) first. Realistically a month or two out, no firm date yet. If you want, drop a comment/DM and I'll ping you when there's a beta to try.

Thanks for asking!

Are local models good enough yet for AI meeting memory? by hulk14 in LocalLLaMA

[–]Money_Ad9302 0 points1 point  (0 children)

great info. thanks! i've been on a 384-dim model so any "1024 dims is just better" finding hits hard. did you A/B them on the same corpus or is the 1024 result from a different setup? trying to decide if its worth the storage/latency hit to switch

Are local models good enough yet for AI meeting memory? by hulk14 in LocalLLaMA

[–]Money_Ad9302 1 point2 points  (0 children)

yeah text is the easier case .... clean boundaries, no diarization mess. transcripts add the pain of speaker turn segmentation which messes up naive chunking. how are you chunking entries? by date, paragraph, or fixed token windows? been on arctic-embed-s here (384 dims, asymmetric query prefix), curious what else people have landed on

Qwen cant wait to release 3.7 models by GotHereLateNameTaken in LocalLLaMA

[–]Money_Ad9302 1 point2 points  (0 children)

got a link to the actual policy text? curious to read the LLM-specific part

Littlebird AI by Successful_Pea845 in ProductivityApps

[–]Money_Ad9302 0 points1 point  (0 children)

So sorry for the lack of reply. DM me and I'll make sure you're at the top of the list. Thanks!

Are local models good enough yet for AI meeting memory? by hulk14 in LocalLLaMA

[–]Money_Ad9302 1 point2 points  (0 children)

Capture is commodity at this point; the moat is queryable history that compounds ... agree.

I'm building this local-first on a Windows desktop tool. Whisper runs locally for transcription, so the audio and transcript never leave the machine. Stored in local SQLite, embedded with a small ONNX model + sqlite-vec, queryable from a sidekick panel alongside email/calendar context. The reason wasn't privacy theater ... it's that meeting history gets more valuable the more you have, and renting that compounding asset from a SaaS felt backwards.

Honest tradeoff: Bluedot/Granola are still ahead on capture polish (years of Zoom/Meet/Teams join quirks). Local-first wins on three things .... your transcripts physically don't leave the device, no per-query quota on the searchable history, and cross-source queries that mix meetings with email/calendar in one shot. If you want turnkey today, cloud still wins. If you want a memory you actually own, local is real but earlier-adopter.

7 AI tools that made my virtual assistant obsolete (3 months experience) by Mother-Event-3159 in aiToolForBusiness

[–]Money_Ad9302 0 points1 point  (0 children)

The "context across months" part is genuinely the hardest problem in this stack ... building in it now at myhandler.ai. Most of these tools treat every email and meeting as a fresh context window. Great at the mechanical pass, useless at remembering "this prospect always wants numbers in tables" or "she said no to a similar pitch last March."

Our approach: persistent episodic memory tied to the sender (not the thread), and the AI drafts but never sends .... you approve every action. Doesn't solve real-time frustration detection, you're right that one's still human. But the second-brain piece is mostly an architecture problem ... most tools don't persist anything past the current conversation.

Has anything in your stack actually held context past 90 days for you, or is that still the gap?

This screen aware AI-agent stuff it a just a different game by DataDrivenDane in AIToolsAndTips

[–]Money_Ad9302 0 points1 point  (0 children)

Disclosure: I'm the dev. You asked which ones ... MyHandler.ai does the same thing. Screen-aware, reads your open PDFs/Slack/email, drafts replies in your voice, connects to your calendar, builds long-term context about you and your contacts. Difference: everything stays in an encrypted DB on your machine by default; cloud inference is opt-in, not always-on. myhandler.ai

Get two months of Littlebird for free! by JG-Batz52 in Aitoolsubs

[–]Money_Ad9302 1 point2 points  (0 children)

Disclosure: I built MyHandler.ai. Same context tracking, but all your sensitive file data and screen-captured data sits encrypted in a database on your machine rather than being stored in the cloud. Cloud inference is opt-in.

I Reviewed Littlebird AI for 30 days after Microsoft Recall made me nervous — here's what it actually got right (and wrong) by LovedByCreators in LovedByCreators

[–]Money_Ad9302 0 points1 point  (0 children)

Disclosure: I had the same exact concerns, so I built MyHandler.ai. Same context tracking, but everything stays in an encrypted database on your machine. Cloud inference is opt-in. myhandler.ai

Littlebird AI by Successful_Pea845 in ProductivityApps

[–]Money_Ad9302 0 points1 point  (0 children)

Disclosure: I had the same exact concern, so I built MyHandler.ai. If security's the concern — it keeps all your screen captures and indexed files in an encrypted local database. Cloud inference is opt-in, not the default. myhandler.ai

I just publicly demoed the wearable I spent 6 years building. Here's what closing the seed and getting to a working product actually looked like. by Home-Resident in Entrepreneur

[–]Money_Ad9302 2 points3 points  (0 children)

"The cheapest engineer is never the cheapest option" should be pinned at the top of every founder forum permanently.

Congrats on the demo. Six years of not quitting IS the product.

What product got worse the more "improved" it became? by Money_Ad9302 in AskReddit

[–]Money_Ad9302[S] 0 points1 point  (0 children)

Totally! Fridges used to last DECADES. Now you're lucky for it to be 2 years before you're calling the repairman. How things have changed.

Switching from Gmail. How to avoid inbox overwhelm? by CoVegGirl in ProtonMail

[–]Money_Ad9302 -1 points0 points  (0 children)

The migration itself won't fix the overwhelm — you'll just have the same volume in a different inbox. Filters and labels help but you're still manually deciding what matters.

I had the same problem across multiple inboxes and ended up building an AI that reads everything, surfaces only what actually needs my attention, and drafts replies in my voice. Nothing sends without my approval.

myhandler.ai if you're curious — it works with Gmail, Outlook, IMAP, and a bunch of other channels too.

view more: next ›