Privacy Policy
Transparent, zero-BS data practices. Because user privacy isn't a feature; it's a baseline requirement.
1. The Philosophy
I build high-performance systems. Bloatware and invasive trackers are the antithesis of performance. By JTT aims to minimise the data it handles. We do not use personal data for advertising or cross-site tracking, and each tool describes the information it needs to work.
2. What Is Collected (And Why)
The interactions on this site are designed to be fast and local whenever possible.
- Engagement Data (Likes & Views): When you interact with the EngagementDock (liking a post), that state is stored in your browser's
localStorage. It stays on your device. Period. - Comments (Giscus): The comment system is powered by Giscus, which interfaces directly with GitHub Discussions. When you comment, you authenticate with GitHub, and your public GitHub profile (username, avatar) is associated with your comment. Check GitHub's Privacy Statement for how they handle that data.
- VibeCheck scans: When you submit a public GitHub repository URL, VibeCheck fetches supported, publicly accessible repository files to analyse them and produce your report. VibeCheck does not intentionally persist repository contents after the request. No GitHub authentication is required from the person using the scan form.
- VibeCheck feedback: If you submit feedback after a scan, the form sends the answers, comments, and submitted repository URL to our email through FormsSubmit so we can review it.
3. What Is NOT Collected
We do not use tracking pixels or cookies for advertising or cross-site tracking. Privacy-focused Plausible analytics may be enabled for this site; when enabled, it measures aggregate site usage without advertising profiles. The traffic to this domain is not monetized through your data.
4. Third-Party Services
To keep this infrastructure running and provide functional features, the site relies on minimal third-party services:
- Hosting/CDN: This site is statically generated and served over a CDN. Basic connection data (IP address, user agent) is inherently logged by the hosting provider for security and routing purposes.
- GitHub (Giscus): As mentioned above, interacting with the comments requires a GitHub account.
- FormsSubmit: VibeCheck feedback is transmitted to FormsSubmit so it can be delivered to our email for review.
- Plausible: If enabled for this deployment, Plausible provides privacy-focused aggregate analytics without advertising cookies.
5. Project-Specific Privacy
LabelKit (Chrome Extension)
LabelKitis a Chrome extension for visual Gmail label and filter management. It accesses Gmail data exclusively through the official Google Gmail API. Key privacy points:
- Data accessed: Gmail labels, messages, and filter settings — only what is necessary to display and manage your inbox organisation.
- Data processing: All processing happens locally in your browser. No email content or metadata is sent to any external server beyond the Gmail API calls required for functionality.
- Storage: Label and rule configurations are stored in
chrome.storage.local— your browser's built-in encrypted storage. - No tracking: Zero analytics, telemetry, or tracking code is included in the extension.
- Authentication: Uses Google OAuth 2.0 via Chrome's identity API. Tokens are managed by Chrome and never exposed to third parties.
LabelKit complies with theGoogle API Services User Data Policy, including the Limited Use requirements.
Other Projects
All projects on this site follow the same data-minimal philosophy:
- XbX API — API service. No user data collected.
- InkNest — Creative tool. All data stored locally.
- Murmur — Journaling app. Data encrypted at rest. No third-party access.
Each project's repository contains a PRIVACY.md with project-specific details. Links to all repositories are available on thework page.
6. Changes
If the architecture changes and requires new data practices, this document will be updated. The core philosophy of minimalism will not change.
Last updated: August 6, 2026