Hexa DevKit · Privacy Policy
Privacy Policy
This policy explains how the Hexa DevKit macOS application handles developer data and separately describes this informational website.
Last updated: July 20, 2026
Local processing
Most Hexa DevKit tools process input entirely on your Mac. Formatting, conversion, encoding, decoding, hashing, inspection, text work, image work, and generation do not send developer-tool input to the developer or a remote service.
The three network tools
API Client, DNS Lookup, and WebSocket Client use the network only after an explicit action. API Client connects directly to the REST or GraphQL destination you enter. DNS Lookup uses the Mac system resolver for the host and record type you choose. WebSocket Client connects directly to the secure wss:// endpoint you specify. The developer does not receive or relay this traffic.
API history
Sanitized API request history is optional and remains in local Application Support. Request bodies are never stored. Authorization, cookies, token, secret, and key headers, along with sensitive query values, are removed before an entry is saved. You can disable history, choose limits and expiry, or clear it.
Files
Hexa DevKit opens only files you select or drop into a compatible tool. File contents are processed locally. They leave the Mac only if you intentionally place content into API Client and send a request.
Preferences and workspaces
Favorites, recents, exclusions, settings, shortcuts, saved workspaces, and session restoration data stay on the Mac. You can clear these local data groups independently from Privacy settings.
No collection by the application
Hexa DevKit has no accounts, analytics, advertising, tracking, subscriptions, trials, external checkout, or third-party SDKs. The developer does not collect behavioral or developer-tool data through the application.
Third parties and user-selected destinations
Hexa DevKit does not share app data with developer-selected third parties. Any future provider processing user data for the developer must provide the same or equal privacy protection described here and required by Apple. Endpoints you choose in API Client or WebSocket Client and the resolver configured on your Mac are independent services; their operators control their own privacy and retention practices.
Retention, deletion, and privacy choices
Working content normally remains in memory until you close its tab or quit the app. Sanitized API metadata, preferences, recents, workspaces, and session data remain locally until they expire under your selected history setting or you clear them in Settings. You can disable API history to stop future entries and clear each local data group independently. The developer has no app account or server-side app data to delete and no remote app-data consent to revoke.
Website hosting
This static website does not set analytics cookies, use a contact form, or add analytics scripts. Cloudflare may process IP addresses, request metadata, and security or infrastructure logs to host and protect the site under its own policies and retention controls. Hexa DevKit does not use those records for advertising, analytics, or profiling.
Contact
For privacy questions, email contact@anibalventura.com.