Privacy Policy

This policy explains how 626 Labs LLC ("626 Labs," "we," "us") handles information across our website, our email correspondence, the Claude Code plugins we publish, and the desktop and Microsoft Store apps we ship. We try to be honest about what we collect and why, in plain language.

---

01Who we are

626 Labs LLC is a Fort Worth, Texas studio that ships native apps, web tools, and Claude Code plugins. You can reach us at estevan@626labs.dev for any privacy question, request, or concern covered by this policy.

02The website (626labs.dev)

626labs.dev is a static portfolio site hosted on GitHub Pages. We do not place analytics scripts, advertising trackers, or persistent cookies on the site. We do not run any forms, sign-ups, or accounts.

What is collected automatically

When you visit any website — including ours — the hosting provider receives standard request information needed to serve the page. For 626labs.dev, that provider is GitHub Pages, and the data they collect (such as IP address, user agent, and referrer) is governed by GitHub's privacy practices. See GitHub's privacy statement for details. We do not see, store, or use that data ourselves.

Analytics. Every page on 626labs.dev, including this one, loads GoatCounter, a privacy-friendly, cookieless analytics service, to count page views. GoatCounter does not use cookies, localStorage, or any other browser storage, and it does not store your IP address, your full user-agent string, or any tracker ID that could follow you across sites — it briefly holds the site name, IP address, and user agent in memory for up to 8 hours to deduplicate a visit into a session, represented by a randomly generated string, then discards it; that intermediate step is never written to its database. What it does record is aggregate: page views and referrers by day and hour, along with browser, operating system, a coarse location derived from IP address, language, and screen width. GoatCounter does not share this data with any third party. See GoatCounter's privacy policy for the full details.

On the Conundrum shop page, clicking an outbound link — a "Shop on Etsy" link, an individual product listing, or the open-source repo link — sends GoatCounter an event recording which link was clicked, so we can see which links get outbound clicks. No other page on the site tracks individual clicks.

What is not collected

• No Google Analytics, Meta Pixel, Plausible, Fathom, PostHog, or any other advertising-linked analytics — GoatCounter, described above, is the one analytics tool we use, and it isn't built for advertising.
• No advertising or remarketing trackers.
• No first-party cookies set by 626 Labs.
• No contact forms, comment systems, or account systems.

External links

The site links out to third-party platforms such as GitHub, YouTube, Replit, the Microsoft Store, and Anthropic. Once you follow a link off-site, that destination's own privacy policy applies. We have no control over and take no responsibility for the practices of those services.

03Email correspondence

The site uses mailto: links rather than embedded forms. When you email us at estevan@626labs.dev, your message is delivered to a personal Gmail inbox operated by 626 Labs. We retain the email to respond and to keep a record of the conversation. We do not add you to any marketing list, and we do not share your email with anyone outside 626 Labs.

You can ask us to delete an email thread at any time by replying with that request, and we will remove it within a reasonable period subject to backups operated by our email provider.

04Claude Code plugins published by 626 Labs

626 Labs publishes plugins for Claude Code (Anthropic's coding assistant). Examples include Vibe Cartographer, Vibe Test, Vibe Doc, Vibe Thesis, and other tools distributed through Anthropic's plugin ecosystem. This section describes how those plugins handle data.

Local-first by design

Our plugins are designed to run locally inside your Claude Code installation on your own machine. They read and write files in your project directory and in your local Claude configuration directory (typically ~/.claude) so that they can do useful work — for example, saving a builder profile, a project plan, or a session log. 626 Labs does not operate a server that receives this data. We do not collect telemetry, usage analytics, or crash reports from our plugins.

What is processed by the plugin on your machine

• Files in the working directory — the plugin reads project files you point it at, the same way Claude Code itself does.
• Plugin profile and state files — preferences, session logs, and friction logs may be written to ~/.claude/profiles/, ~/.claude/projects/, or the plugin's own data directory. These files stay on your machine.
• Memory files — if you use auto-memory, your notes live in your local ~/.claude/projects/<project>/memory/ directory.

Anthropic and your AI prompts

Our plugins run inside Claude Code. The prompts and responses Claude Code exchanges with Anthropic's API are governed by your agreement with Anthropic and Anthropic's own privacy policy — not by us. We do not see, intercept, or log those exchanges.

Third-party integrations you configure

Some plugins offer optional integrations with third-party services — for example, posting a message to Discord, fetching a Figma design, reading from Google Drive, or rendering a document. These integrations are opt-in: they only activate when you provide your own credentials (an API key, an OAuth token, a bot token, etc.).

When you use such an integration, your data flows directly between your machine and the third-party service under that service's own privacy policy. 626 Labs does not receive, proxy, or store the credentials or the data exchanged. You should review each service's terms before connecting it.

Open source

Our plugins are published as source code across two GitHub accounts operated by 626 Labs: the company organization at github.com/626Labs-LLC and the founder's personal account at github.com/estevanhernandez-stack-ed, where most day-to-day work lives. You are welcome to inspect any plugin's code to verify its data behavior. If you find anything that contradicts this policy, please let us know — we will fix it.

05Desktop and Microsoft Store apps

626 Labs ships desktop apps through the Microsoft Store and GitHub Releases. They share one posture: they run on your device, they require no 626 Labs account, they show no advertising, and none of them sends telemetry, analytics, or crash reports to 626 Labs. One app, SnapSnip, keeps a diagnostic log that never leaves your machine; its subsection describes that log exactly. Uninstall behavior varies by app and install channel, so each subsection states what uninstall removes and what survives. Every app below answers the same five questions in the same order: what is collected, where data lives, what touches the network, which third parties are involved, and what removal looks like.

RoRoRo (ROROROblox)

What is collected. Nothing is collected by 626 Labs. RoRoRo contains no telemetry, analytics, or crash reporting, and no 626 Labs server appears anywhere in its network surface. To enable multi-account launching, the app captures your Roblox session cookie and basic profile details when you sign in; that data stays on your device.

Where data lives. Saved accounts live in an encrypted vault at %LOCALAPPDATA%\ROROROblox\accounts.dat, protected with Windows DPAPI and tied to your Windows user account. Settings and app logs are plain files in the same folder; logs stay local, are kept for 30 days, and never contain your session cookie. You sign in on Roblox's own login page inside an embedded browser window (WebView2); the app stores the resulting session cookie, not your password, and the temporary browser profile used for each sign-in is deleted after capture and again at startup. The optional account export is a file written to a location you choose, encrypted with a password you set.

What touches the network. While RoRoRo is running it makes periodic calls to Roblox services for your saved accounts, covering sign-in, launching, avatars, game details, friends, and a presence heartbeat that refreshes about every 25 seconds. It also contacts GitHub for two things: an update check, at most once every 24 hours, and a Roblox compatibility feed fetched at startup. The compatibility feed is signature-verified: the app checks an ECDSA signature against a public key pinned in the binary before reading the feed, and anything that fails verification is rejected in favor of built-in defaults. On the GitHub build only, opening the Plugins window fetches a plugin catalog from GitHub, and installing a plugin downloads it over HTTPS and verifies its SHA-256 hash; the Microsoft Store build has no plugin marketplace.

Third parties. Roblox Corporation, under Roblox's own privacy policy, for every Roblox call above. GitHub, for public, unauthenticated reads of releases and feeds.

Removal. A Microsoft Store uninstall removes the app's package data through standard Windows package removal. A GitHub (.exe) uninstall removes the install directory but leaves %LOCALAPPDATA%\ROROROblox\, which holds the account vault, settings, and logs; delete that folder to remove everything. The in-app diagnostics bundle is a zip file that only you create and only you send.

Sanduhr

What is collected. Nothing is sent to 626 Labs, and there is no telemetry, analytics, or crash reporting on either platform. Sanduhr works with data you give it: two Claude session cookies you supply (sessionKey and cf_clearance), the usage data it reads from claude.ai with those cookies, and your local Claude Code session logs (token, model, working-directory, and skill data) for per-project views. All of it stays on your device.

Where data lives. On Windows, your credentials are stored in Windows Credential Manager under the service name com.626labs.sanduhr, one set of entries per saved account. Usage history is a 30-day rolling window under %APPDATA%\Sanduhr\, alongside settings and a statusline snapshot that stores your account label as a short hash, never the raw label. An opt-in vault archive of your Claude Code logs lives at %LOCALAPPDATA%\Sanduhr\vault\ and is kept until you purge it from inside the app. Operational logs record status codes and error types, never credentials. On macOS, credentials are stored today in a permissions-restricted plaintext file at ~/Library/Application Support/Sanduhr/credentials.json: readable only by your user account, but not encrypted and not in the system Keychain. Migration to the Keychain is planned.

What touches the network. Sanduhr talks to claude.ai with your own session to read your organization list, your usage data, and, on Windows, the Daily Routines budget, and it loads claude.ai's sign-in page when you add an account. On Windows, live fetches run through a hidden embedded browser (Microsoft WebView2) with your cookies injected into that embedded browser only; the app does not read your regular browser's profile. Update checks are the only other traffic: the Windows GitHub (.exe) build checks GitHub Releases at most once every 24 hours, and the macOS build checks a Sparkle update feed hosted on GitHub Pages every 24 hours. The Microsoft Store build does not run the GitHub update check; it updates through the Store.

Third parties. Anthropic (claude.ai), under your own agreement with Anthropic, since every request uses your session. Microsoft WebView2 (embedded Chromium) as the fetch transport on Windows. GitHub, which hosts both update feeds. Sanduhr also ships a local MCP server: it listens only over stdio, never the network, and it can expose your usage and per-project token data to MCP clients you configure on your own machine, such as Claude Code.

Removal. On Windows, uninstalling Sanduhr does not remove the Credential Manager entries, on either the GitHub (.exe) or Microsoft Store install, and does not remove %APPDATA%\Sanduhr\ or %LOCALAPPDATA%\Sanduhr\. Use Sign Out in the app for each account before uninstalling: it deletes that account's credentials and history, and signing out of the last account also clears the embedded browser profile. You can also delete the com.626labs.sanduhr entries yourself in Windows Credential Manager and remove the two folders. On macOS, dragging Sanduhr to the Trash does not remove ~/Library/Application Support/Sanduhr/, including the credentials file; delete that folder to clear it.

626 Mod Launcher

What is collected. Nothing is collected by 626 Labs. There is no account, no telemetry, and no analytics. Crash and error information is written to a local log file and never transmitted.

Where data lives. Your Nexus Mods sign-in token is stored at %APPDATA%\ModManagerBuilder\nexus.json, encrypted with Windows DPAPI and tied to your Windows user account; it is never sent to 626 Labs. Settings, game registrations, and profile data live under %APPDATA%\ModManagerBuilder\; logs, caches, and update stamps live under %LOCALAPPDATA%\ModManagerBuilder\. When the launcher removes a mod file from a game folder, it moves the file to a holding area instead of deleting it.

What touches the network. Three distinct paths, each with a different destination:

• Game definitions. The launcher fetches its game manifest directly from GitHub (the public 626-game-manifest repository), verifies the manifest's ECDSA signature against a key pinned in the app before trusting it, and checks at most once every 24 hours, controlled by the auto-update definitions setting. Your IP address goes to GitHub, not to 626 Labs.
• CurseForge metadata. Mod lookups go to 626-mod-metadata-proxy.626labs.workers.dev, a Cloudflare Worker we operate for one reason: it holds the CurseForge API key server-side so the key does not ship inside the app. The Worker forwards a fixed allowlist of CurseForge lookup requests and returns the responses. 626 Labs does not log and does not retain requests to this proxy: the Worker's code contains no logging or storage, and its Cloudflare observability features are disabled. Cloudflare, as the network provider, processes standard request metadata such as your IP address in transit, under Cloudflare's own privacy policy.
• Nexus Mods. Signing in to Nexus uses OAuth directly between your machine and Nexus Mods; that traffic and your Nexus account are governed by Nexus Mods' privacy policy.

The launcher also checks GitHub Releases for its own updates at most once every 24 hours. The Microsoft Store build ships with no plugin feed; the GitHub build can fetch its optional Nexus integration plugin and verifies it before loading.

Third parties. GitHub (manifest and update reads), Cloudflare (hosts and carries the proxy's traffic), CurseForge (receives the lookup requests the proxy forwards, under CurseForge's terms), and Nexus Mods (direct OAuth, under Nexus's policy).

Removal. There is no server-side account or state to delete; everything the launcher stores is on your device. Uninstalling does not specifically wipe the stored Nexus token or the two data folders above; delete %APPDATA%\ModManagerBuilder\ and %LOCALAPPDATA%\ModManagerBuilder\ to remove everything. Mod files the launcher moved out of a game folder remain in their holding location until you delete them.

RBX15 Classic Shirt and Pants Maker

What is collected. Nothing. There are no accounts, no telemetry, no analytics, and no crash reporting.

Where data lives. Exported PNG templates and .r15proj project files are written through the standard save dialog to locations you choose, and the app persists no settings of its own. The embedded browser runtime the app is built on (Electron) keeps a standard runtime cache under %APPDATA%\RBX15 Classic Shirt and Pants Maker\, which includes cached copies of the fonts described below.

What touches the network. One destination: Google Fonts. The editor loads its typefaces from Google's font servers on every launch, so Google receives a standard web request, including your IP address, governed by Google's privacy policy. Nothing else: no update checks (the .exe build updates by downloading a new installer; the Store build updates through the Store), no APIs, no cloud sync.

Third parties. Google (fonts).

Removal. Uninstalling removes the app. The runtime cache folder at %APPDATA%\RBX15 Classic Shirt and Pants Maker\ may survive an .exe uninstall; delete it manually if you want every trace gone. Files you exported stay where you saved them.

SnapSnip

What is collected. SnapSnip is the one 626 Labs app that keeps a diagnostic log, and that log never leaves your device: there is no upload code, no cloud endpoint, and the app package declares no internet capability. The log records five event types (snip captured, redaction rule hit, pipeline failure, latency, and user feedback) as counts, categories, and timings, capped at 10 MB with one rotation file. No window-title text, no URLs, and no image content appear in any record; an automated check in our build fails the build if such a field is ever added. The app-name field in each record comes from a fixed 21-entry allowlist, and anything not on the list is recorded as "other". The log is on by default, and you can turn it off in Settings, effective immediately.

Where data lives. Screenshots are saved to your Pictures\Screenshots folder (or its OneDrive-redirected equivalent) as PNG files with embedded metadata. Settings and the diagnostic log live under %LOCALAPPDATA%\SnipSnap\; collections and rename-undo data live under %LOCALAPPDATA%\SnapSnip\ (the app's internal name is SnipSnap, so both spellings appear on disk). Window titles used for naming are processed in memory and redacted on your device before anything is written: financial numbers, SSN-shaped numbers, email addresses, phone numbers, currency amounts, and private-browsing or password-manager windows are stripped, the unredacted title is never written to disk, and any redaction failure falls back to a timestamp-only filename.

What touches the network. Nothing. The code contains no live network endpoint, and the app package declares no internet capability.

Third parties. None.

Removal. Uninstalling removes the app; your screenshots stay in your Pictures folder. If you enabled start-with-Windows, that setting writes a SnipSnap.Standalone entry under HKCU\Software\Microsoft\Windows\CurrentVersion\Run that uninstall may not remove: turn autostart off in Settings before uninstalling, or delete the entry manually. Delete the two data folders above to clear settings, the diagnostic log, and collections.

RTClickPng (Right Click to PNG)

What is collected. Nothing. The app has no accounts, no telemetry, and no analytics, and it ships with zero third-party packages, so no such SDK exists in it even indirectly.

Where data lives. Settings are three small preferences in settings.json inside the app's package folder at %LOCALAPPDATA%\Packages\626LabsLLC.RightClicktoPNG_wz1chhb2h2v4a\LocalState\. Converted images are written beside the source file; "Copy as PNG" and "Copy as JPEG" place the result on the clipboard and write no file at all. The settings app writes a small local crash log, type name and message only, never file contents, at %LOCALAPPDATA%\RTClickPng.Settings.crash.log.

What touches the network. Nothing. The app links no networking libraries and declares no internet capability. There are no update checks; updates come through the Microsoft Store.

Third parties. None.

Removal. Context-menu entries are registered declaratively through the app package, so Windows removes them at uninstall with no registry leftovers, and settings live in the package folder Windows deletes with the app. The crash log at %LOCALAPPDATA%\RTClickPng.Settings.crash.log may remain after uninstall; delete it manually if it is present.

06Children's privacy

Our website and our plugins are intended for a general developer audience and are not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has sent us personal information, contact us and we will delete it.

07Your rights

Depending on where you live, you may have rights under laws such as the EU/UK GDPR or the California Consumer Privacy Act (CCPA) — for example, the right to access, correct, delete, or port personal information that a business holds about you, and the right to object to certain processing.

Because the website does not collect personal information and our plugins keep their data on your own machine, the only personal information we typically hold is the content of email correspondence you have sent us. You can exercise your rights over that information by emailing estevan@626labs.dev. We do not sell personal information.

08Security

We take reasonable steps to protect the limited information we hold — including using a reputable email provider with two-factor authentication, and storing source code in version control with access controls. No system is perfectly secure, however, and we cannot guarantee absolute security of information transmitted over the internet.

09Changes to this policy

We may update this policy from time to time as our practices, the products we publish, or applicable law evolves. The "Effective" and "Last updated" dates at the top of the page reflect the current version. Material changes will be reflected by an updated effective date and, where appropriate, a note on the homepage. The previous version's substance can always be reconstructed from this site's git history at our public repository.

10Contact

For any privacy question, request, or concern, reach out: