Clear about
your data.

Processing on your Mac

Dev Workbench is a native macOS developer utility designed to process developer data locally. The app does not require an account and does not include advertising, tracking, analytics, or an app-operated telemetry or crash-report upload service.

KeLoc is the public name used for Dev Workbench. The Dev Workbench operator does not receive workbench input, output, or in-app usage telemetry. Network connections occur only through the explicit workflows described below or through Apple’s App Store services.

Text conversions, JSON and YAML transformations, JSON queries, token and key inspection, regular expressions, timestamps, identifiers, colors, subnet calculations, image-to-data-URI conversion, text comparison, and local data and log analysis run on your Mac.

Files are opened only through workflows you choose. Clipboard content is read or written when you use a paste or copy action. Content placed on the system clipboard is then managed by macOS and may be available to other applications or clipboard features you use.

Information stored on your Mac

Retention varies by workbench:

• Dev Workbench stores non-sensitive preferences such as the selected workbench, formatting choices, layout settings, and entitlement status.
• JSON Tools may restore source input up to 200,000 UTF-8 bytes. Larger JSON input is not restored.
• Epoch Time Converter stores its configured timestamp, duration, difference, timezone, and display values. Color Picker and Converter stores configured colors, favorites, and saved palettes.
• Local Data imports are materialized into app-managed DuckDB sessions. Saved sessions contain the imported snapshot, schema and session metadata, and—when applicable—a security-scoped reference to the source file. They are kept in the app’s local cache storage until explicitly deleted or removed by macOS.
• Log Analyzer file imports can create saved DuckDB sessions in the app’s Application Support storage. A saved session may include the imported log snapshot, derived fields, session metadata, and a security-scoped reference to the original source file.

JWT tokens, decoded claims, secrets, public or private keys, and pasted JWK or JWKS data are session-only. Within the app, cURL source, generated code, standard input, captured responses, and execution output are session-only. Authored cURL file-output options can write response bodies, headers, cookies, traces, HSTS or ETag state, generated libcurl source, or other files inside the user-selected Execution Folder. Those files remain until you delete them.

Image to Data URI does not persist image bytes, data URI input, or generated output. Text Diff does not persist compared source text or generated differences. Other workbenches may retain preferences while leaving their input and output session-only.

Files you export or download are stored at the destination you select and are not managed as app-session data.

Explicit network actions

Most workbench actions do not connect to a remote conversion or analysis service. The following actions intentionally use the network:

• Run Curl: After you explicitly run a request, the configured request is sent directly to its destination. It can include the URL, query parameters, headers, authentication values, request bodies, and content from local files inside the user-selected Execution Folder or from a separately selected Standard Input file. The destination’s privacy and retention practices apply. Dev Workbench does not operate an intermediary server and does not receive the request or response.
• Web Preview: After you explicitly open a preview, WebKit loads the chosen URL and its page resources. The destination can receive the URL, query parameters, IP address, browser information, and ordinary web requests. The preview uses a non-persistent WebKit data store, but that does not make the request anonymous or control what the destination retains.
• Open in Browser: The app hands the selected destination to an external application. That application’s behavior and privacy settings then apply.

Parsing a URL, generating code from cURL, and all other ordinary transformations are separate from these explicit network actions. Avoid placing credentials in a web preview URL unless you intend to send them to that destination.

App Store purchases

Dev Workbench Pro is a non-consumable App Store purchase. Dev Workbench uses Apple’s StoreKit services to obtain Pro product information, process purchases, restore purchases, and verify entitlements. Apple may process purchase, account, device, and transaction information under its own policies. Dev Workbench stores entitlement state locally so it can determine which features are unlocked.

Workbench input and output are not included in StoreKit product, purchase, restore, or entitlement requests. Read Apple’s App Store privacy information for Apple’s handling of App Store data.

Retention and deletion

The Clear action removes the current workbench content according to that workbench’s behavior. Clear does not necessarily remove preferences, saved Local Data or Log Analyzer sessions, exported files, system clipboard content, native undo history, or copies included in Mac backups.

• Use Session Manager’s explicit Delete action to remove saved Local Data or Log Analyzer sessions. Deleting an app-managed session does not delete the original source file.
• Remove saved Color favorites and palettes using their workbench controls.
• Delete exported or downloaded files from their selected destinations using Finder or another file-management tool.
• Delete files created by authored cURL file-output options from the selected Execution Folder using Finder or another file-management tool.
• Clear sensitive session-only content before leaving the workbench when other people can access the same Mac account.

For help identifying or removing remaining app-managed local data, contact hello.keloc@gmail.com. Dev Workbench cannot delete data held by destination websites, external applications, Apple, clipboard managers, or backup services; use the controls provided by those services.

Website and external services

The Dev Workbench website does not include site-operated analytics, advertising pixels, newsletter forms, or tracking cookies. Its own styles, scripts, fonts, screenshots, and video poster images are served with the site.

Cloudflare Pages processes requests for this website as the hosting provider and may receive technical request information under Cloudflare’s Privacy Policy. Cloudflare Web Analytics and optional request logging are not currently enabled.

Optional YouTube demonstrations

Where a YouTube demonstration is available, the website initially displays a locally hosted poster. A YouTube player loads only after you choose to load the video. Loading or opening a YouTube video connects to Google and YouTube, which may receive your IP address, browser information, and playback activity. See Google’s Privacy Policy.

Support and policy changes

The current support address is hello.keloc@gmail.com. If you contact it, KeLoc and its email provider receive the email address, message, and attachments you provide. This information is used to investigate and respond to your request. Do not include passwords, tokens, private keys, or unrelated private file content in a support request.

Support messages are kept only as long as reasonably needed to respond, investigate related issues, and maintain necessary support records. You may request deletion by emailing the same address. Deletion applies to copies controlled by KeLoc and cannot control the email provider’s operational backups or information that must be retained for security or legal reasons.

This policy identifies KeLoc as the public operator name, uses the confirmed support address, and is effective September 16, 2026. Future changes to Dev Workbench data handling or relevant dependencies will be reflected on this page and, when required, in the app’s App Store privacy information. The support page includes guidance for preparing a useful problem report.