MYSYSAD is built on a "Privacy-by-Architecture" model. Unlike web tools that send your data to remote servers for processing, every MYSYSAD tool, from the quick tools on the dashboard to the advanced and AI tools, runs in your browser, using WebCrypto, WebAssembly, the File System Access API, and the browser's built-in JavaScript engine to do the work locally.
/api/dns) and five News page endpoints that fetch public content (/api/hackernews, /api/feeds, /api/cves, /api/status and /api/jobs). The DNS endpoint receives only the domain name and record type you look up; the News endpoints never touch your tool data.
There are a small number of tools that must make outbound network requests to perform their function — a DNS lookup tool has to actually query DNS servers, for example. These are clearly identified in this document. For most of them, the request goes directly from your browser to the relevant service and MYSYSAD servers never see it. The one exception is DNS Lookup, which sends the domain you query to MYSYSAD's own DNS endpoint (see the table below).
Here is a complete, honest accounting of every category of data and what happens to it:
| Data / Action | Where it goes | Details |
|---|---|---|
| Credentials, tokens, keys, hashes (JWT Decoder, JWT Forensic Analyzer, Hash Generator, SSH Key Generator, Password Generator, Certificate Decoder, SSO Autopsy, PKI Inspector, htpasswd Generator, OpenSSL Builder) | ▸ LOCAL ONLY | Processed entirely in-browser via WebCrypto and JavaScript. Nothing transmitted. |
| Log files, config files, Terraform plans, Docker Compose, K8s YAML, jq queries, crontab manifests (Log Analyzer, Log Scrubber, Terraform Analyzer, Compose Visualizer, K8s Builder, Line Patcher, jq Playground, Cron Orchestrator, DriftScope) | ▸ LOCAL ONLY | Parsed and processed in browser memory. Files are not uploaded to any server. |
| Images and screenshots (WebRSW Pro, Photo Organizer) | ▸ LOCAL ONLY | All editing, OCR, redaction, and export operations run client-side. Images never leave your device. |
| Local files accessed via File System API (Photo Organizer, Log Analyzer, WebRSW Pro, Line Patcher, Scratchpad disk sync) | ▸ LOCAL ONLY | You grant access per-session via a browser permission prompt. File contents are read and written directly on your device. MYSYSAD servers have no visibility into this activity. |
| Network topology designs, subnet calculations, firewall rules, permission simulations (NetBuilder Pro, Subnet Architect, VPC Planner, Firewall Builder, Permission Simulator, NGINX Simulator, Port Reference) | ▸ LOCAL ONLY | All calculations and visualizations run in-browser. No network diagrams, CIDR data, or rule sets are transmitted. |
| Statistical calculations (Statistical Tables, Sysadmin Calculator) | ▸ LOCAL ONLY | All numerical approximations (chi-square, Z-score, t-Student, RAID/SLA/transfer calculations) computed locally. |
| Email DNS records (Email DNS Generator) | ▸ LOCAL ONLY | SPF, DKIM, and DMARC records are generated locally. No DNS queries are made — the tool produces copy-paste records for you to add to your DNS provider manually. |
| Text diffing and JSON formatting (Advanced Diff Viewer, JSON Forensic Explorer, Base64 Forensic Architect, MAC Policy Translator, Data Transformer) | ▸ LOCAL ONLY | All parsing, formatting, comparison, and transformation runs in-browser. No text content is transmitted. |
| Python code (Python Sandbox) | ▸ LOCAL ONLY | Executed inside a WebAssembly sandbox in your browser. Code is not sent anywhere. |
| DNS queries (DNS Lookup) | ▸ TO MYSYSAD DNS ENDPOINT → RESOLVERS | Your browser sends the domain and record type you choose to the MYSYSAD /api/dns endpoint, which looks it up with public DNS resolvers and returns the answer. MYSYSAD's code does not log the domains you look up, but the endpoint is hosted on Vercel, whose request logs (kept for a limited time) may include the request and your IP address, per its policy. Do not query sensitive internal hostnames. |
| DNS propagation checks (DNS Propagation Checker) | ▸ TO DNS RESOLVERS | Queries are sent from your browser to public DNS resolvers (e.g., Cloudflare 1.1.1.1, Google 8.8.8.8). Each resolver sees the domain you queried and your IP address. |
| SSL / TLS checks (SSL Certificate Checker, SSL Forensics, Security Header Tester) | ▸ TO TARGET HOST | Your browser makes a direct request to the hostname you specify. The target server sees your IP. MYSYSAD does not proxy or log these requests. |
| IP reputation lookups (IP Reputation tool) | ▸ TO THIRD-PARTY API | The IP address you look up is sent from your browser to ipapi.co for location and network details; ipapi.co also sees your own IP. The tool also shows links to AbuseIPDB, VirusTotal and similar services, which receive the IP only if you click them. Consult each provider's privacy policy for handling details. |
| MAC vendor lookups (MAC Lookup tool) | ▸ TO OUI DATABASE API | The MAC address prefix (first 3 octets) is sent from your browser to the public OUI lookup API at api.macvendors.com. Your browser IP is visible to that provider. |
| WHOIS / RDAP queries (WHOIS Lookup tool) | ▸ TO RDAP REGISTRIES | Domain registration queries are sent directly from your browser to public RDAP endpoints (Verisign for .com/.net, Google for .dev/.app, and other TLD-specific registries). The domain you query and your IP address are visible to the registry. Do not query sensitive internal hostnames. MYSYSAD servers are not involved. |
| AI-powered diagnosis and postmortem generation (AI Log Diagnosis, Incident Commander) | ▸ TO AI PROVIDERS (YOUR KEY) | These standalone tools use API keys you provide and store in your browser's localStorage. When you use AI features, your input data (logs, timeline events, scratchpad content) is sent directly from your browser to the AI provider you selected (Anthropic, OpenAI, Google Gemini, or Azure OpenAI). MYSYSAD servers never see your API keys or the data you submit. You control what you send and are responsible for any costs incurred. |
| User preferences and tool state | ▸ BROWSER LOCALSTORAGE | Theme preference, pinned tools, and per-tool session state are stored in your browser's localStorage. This data never leaves your device and you can clear it at any time through your browser settings. |
| Visit counts | ▸ TO VERCEL | The main pages use Vercel Web Analytics to count visits. It sets no cookies and stores nothing on your device. For each visit it records the page's address, the site that linked to it, your approximate location (country, region and city, worked out from your IP address), and your browser, operating system and type of device. Before anything is sent, the address is cut down to the page itself: everything after ? or # is removed, so shared links and anything you type into a tool are never included, and opening a tool isn't counted as a visit. Vercel tells repeat visits apart with a code made from the request, which it discards after 24 hours, and MYSYSAD sees only totals. See Vercel's privacy documentation for full details. |
| Fonts and code libraries | ▸ TO CDN PROVIDERS | The site loads fonts from Google Fonts and JavaScript libraries from cdnjs.cloudflare.com and cdn.jsdelivr.net. A few posts in the 2006–2014 blog archive also show images stored on Google's Blogger servers (blogger.googleusercontent.com). These providers receive your IP address and browser metadata when their resources load. MYSYSAD has no control over their data practices. |
| Visiting the site (every page request) | ▸ TO CLOUDFLARE & VERCEL | Like any website, mysysad.com is delivered through hosting and network providers (Cloudflare and Vercel). They see your IP address and standard request headers, and may keep standard access and security logs per their own policies. They never see the data you process inside the tools. |
| News: Reddit posts (News page and homepage news sidebar) | ▸ TO REDDIT | Your browser fetches posts directly from reddit.com/r/{subreddit}/top.json. Reddit receives your IP address and standard browser headers. No MYSYSAD server is involved. See Reddit Privacy Policy. |
| News: Hacker News stories (News page and homepage news sidebar) | ▸ TO MYSYSAD PROXY / TO ALGOLIA | On the News page, your browser asks the MYSYSAD /api/hackernews endpoint, which fetches the current top stories from the official Hacker News API server-side. The small news sidebar on the homepage fetches directly from hn.algolia.com/api/v1/search_by_date, so Algolia receives your IP address and query parameters. See Algolia Privacy Policy. |
| News: CVE alerts (News page) | ▸ TO MYSYSAD PROXY → CISA | Your browser asks the MYSYSAD /api/cves endpoint, which fetches public vulnerability data from CISA server-side. No personal information is sent. |
| News: Cloud provider status (News page) | ▸ TO MYSYSAD PROXY → STATUS PAGES | Your browser asks the MYSYSAD /api/status endpoint, which fetches public incident updates from cloud and service providers' status pages server-side. No personal information is sent. |
| News: RSS feeds from CISA, Krebs, LWN and other publishers (News page only) | ▸ TO MYSYSAD PROXY → FEED SOURCES | Your browser sends a request to the MYSYSAD /api/feeds endpoint, which server-side fetches RSS content from government agencies and publishers. The proxy does not log your queries, but the hosting provider (Vercel) may collect standard access logs per their policy. |
| Jobs: Remote sysadmin job listings (News page Jobs tab) | ▸ TO MYSYSAD PROXY → JOB SOURCES | Your browser sends a request to the MYSYSAD /api/jobs endpoint, which server-side fetches job listings from Hacker News (Algolia), Remotive, Jobicy, and We Work Remotely. No personal information is sent. Clicking a job link navigates directly to the third-party listing. |
Several advanced tools use the browser's File System Access API to read and write files directly on your local device. This includes:
File access is granted through your browser. In most browsers it ends when you close the tab, and you're asked again on your next visit; some browsers let you choose to allow access on every visit, which you can revoke in the browser's site settings.
MYSYSAD uses your browser's localStorage and IndexedDB to persist state between sessions. Specifically, the following may be stored locally on your device:
None of this data is synchronized to any server. It exists only in your browser on your device. You can clear it entirely by clearing your browser's site data for mysysad.com.
MYSYSAD.COM does not set any first-party cookies for tracking, advertising, or analytics purposes. No session cookies, authentication cookies, or persistent tracking identifiers are set by MYSYSAD.
Third-party resources (Google Fonts, Cloudflare CDN, Vercel) may set their own cookies as part of their service delivery. These are outside MYSYSAD's control. You can inspect and manage all cookies for this site through your browser's developer tools.
MYSYSAD is a professional technical platform intended for adult system administrators and IT professionals. It is not directed at children under the age of 13 and we do not knowingly collect any information from minors.
This privacy policy will be updated as the platform evolves. The "Last Updated" date at the top of this page reflects the most recent revision. Continued use of the site following any update constitutes acceptance of the revised policy. For material changes, a notice will be added to the site's main page.
Questions about this privacy policy or data handling practices can be directed to the site maintainer via the contact link in the footer.