Privacy notice

The short version

IntegrateKit's tools run in your browser. The JSON, XML, tokens and other payloads you paste or open are processed on your device and are not sent to our servers, not stored by us, and not shared with anyone.

What runs in your browser

Formatting, validation, comparison, data masking, JWT decoding, encoding utilities and report generation all run locally in your browser, in a background worker. Files you open are read locally. Downloads and copies are created on your device.

By default, nothing you paste is kept after you close the page. If a tool offers to remember your input on this device, it is off by default, the data stays in your browser's local storage only, and you can clear it at any time.

What we collect

• Anonymous usage events to understand which tools are useful, for example "JSON formatter: beautify used", with an approximate input size range and duration range. These events never include payload contents, field names or values. We use cookieless analytics.
• Technical error reports containing the error type and where it happened in our code. Error messages that could contain fragments of your input are removed before sending.
• Standard web server logs kept by our hosting provider, such as IP address, browser type and requested page, for security and reliability.

What we never collect

• The contents of payloads you format, validate, compare or mask.
• Tokens you decode.
• Original values of fields you mask.

Accounts (when available)

Accounts are not available yet. When they are, signing in with GitHub or Google will share your email address, name and avatar with us. If you choose to save comparison or masking profiles, we will store the settings in them, such as field names, JSON paths and rules, but never payload values. The app will tell you clearly whenever something is about to be stored in your account. You will be able to export or delete your data.

Payments (when available)

Paid plans are not available yet. When they are, payments will be handled by a payment provider. We will store your subscription status, not your card details.

Important limitations

Data masking helps reduce accidental exposure of common sensitive fields, but it cannot guarantee that every sensitive value is found. It is not a substitute for your organisation's data-handling policies or for any regulatory compliance process. Always review output before sharing it.

Contact

Contact details for privacy questions will be published here before the public launch.