Igor Ganapolsky IgorGanapolsky

Hermes Mobile Privacy Policy

Effective date: July 4, 2026

Hermes Mobile is published by Max Smith KDP LLC. Hermes Mobile lets you connect your phone to your own computer so you can monitor and control Hermes workflows from the mobile app.

Data We Collect

Hermes Mobile collects limited data needed to operate and improve the app:

AI Agent Reliability Checklist

The 12-point audit for teams running AI coding agents in production.

Why this exists

After 6 months of ThumbGate telemetry across Claude Code, Cursor, and Codex installations, we identified the 12 failure patterns that cause 94% of all agent incidents. This checklist helps you find them in your setup before they cost you money.

Stop Your AI Agent Before It Breaks Production

The Problem

AI coding agents (Claude Code, Cursor, Codex) make the same categories of mistakes:

Editing files outside task scope — agent "helpfully" refactors a file you didn't ask it to touch
Hallucinating function signatures — calls a function with wrong params, breaks the build
Making unauthorized changes — modifies config files, env vars, or deployment scripts without confirmation
Ignoring instructions — skips test files, deletes comments, reformats code you told it not to touch

The 4 Stripe Connect failure modes that quietly cost marketplaces real money

A field teardown for anyone building split payments on a platform — and how to catch each one before it hits a real payout.

Most Stripe Connect integrations demo perfectly and then lose money in production, because the failure modes don't show up until real volume, real retries, and real disputes arrive. Here are the four I see most, ranked by blast radius, with the check that catches each one.

1. Non-idempotent charge creation → double charges on retry

A network blip makes your server retry a PaymentIntent/charge create. Without an Idempotency-Key, Stripe happily creates two. The customer is charged twice; you eat the refund and the dispute. Catch it: every create/capture call carries a stable idempotency key derived from your order id (not a random per-attempt UUID). Test it by firing the same request twice and asserting one charge.

LipoShield — Support

For questions, bug reports, or feedback about LipoShield, contact:

Email: iganapolsky@gmail.com

LipoShield is an educational wellness tool. It does not provide medical advice. For health concerns, please consult a qualified healthcare professional.

Privacy Policy: https://gist.github.com/IgorGanapolsky/7e5c32cd76f1cf8b31c963f4b0efe584 Terms of Service: https://gist.github.com/IgorGanapolsky/aaa78f12fbcef4824b2d4e9bd0dd7d8a

LipoShield — Terms of Service & End User License Agreement

Effective date: 2026-05-23 Last updated: 2026-05-23 Review status: Approved Approved by: Igor Ganapolsky Approval date: 2026-05-26

LipoShield — Privacy Policy

Effective date: 2026-05-23 Last updated: 2026-06-04 Review status: Approved Approved by: Igor Ganapolsky Approval date: 2026-05-26

Privacy Policy — Privacy Lens

Last updated: May 21, 2026

Privacy Lens ("the app") is an on-device privacy auditing tool. This policy explains what the app does and does not do with information.

Summary

Privacy Lens does not collect, transmit, sell, or share any personal or device data. All analysis happens entirely on your device.

	[
	{
	"id": "s1",
	"name": "Dr. Fuhrman's LDL Biotect",
	"category": "supplements",
	"emoji": "💊",
	"scientificInsight": "Contains aronia berry extract, phytosterols, and pomegranate, formulated to help protect LDL particles from oxidation.",
	"doseRecommendation": "Use only as directed on the product label and review with a clinician if needed",
	"tier": "recommended",
	"packageLabel": "240 capsules",

	<!doctype html>
	<html lang="en">
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<title>AI Voice Reliability Diagnostic</title>
	<style>
	:root {
	color-scheme: light;
	--ink: #171717;