Privacy Policy for Jace

Effective date: September 20, 2026

Jace is a macOS JSON editor developed by Andy Liang. This policy explains how Jace handles information when you use the app.

JSON files and local app data

Jace processes JSON documents locally on your Mac. Jace does not intentionally upload the contents of your JSON files.

The app stores the following information locally to provide its features:

JSON files you choose to open, edit, or save
Temporary draft copies used for crash recovery
Recent-file security bookmarks, file size, and last-opened date
Short draft snippets shown in the Recent panel
Editor preferences such as font size and indentation width
Text you paste or files you choose for a comparison, held only while the comparison is open

This information remains on your device and is not collected by Jace as remote service data. You can remove recent entries from the Recent panel. Saving or closing a draft removes its recovery copy during the normal document workflow.

Crash, diagnostic, and usage information

Jace uses Firebase Crashlytics, Firebase Analytics, and supporting Firebase services provided by Google to help diagnose crashes, improve reliability, and understand which features are used. When reporting is available, these services may automatically collect:

Crash stack traces and relevant application state
App version and bundle identifier
Device model, hardware characteristics, operating-system version, and available memory or disk information
Random installation and session identifiers used to group and deduplicate reports
Limited SDK transport and diagnostic metadata

Jace also records feature-usage events, such as when a document is opened, formatted, edited in the tree, or compared, or when a setting changes. These events carry only coarse details like the action taken, whether it succeeded, the editor mode, counts (for example, the number of differences found), and a rough file-size range.

Jace never includes file names, file paths, or JSON document contents in crash reports or usage events, and does not attach account information or custom user IDs. Jace has no user accounts. Diagnostic and usage data is not used for advertising or cross-app tracking and is not sold.

The App Store privacy disclosures for Jace classify this information as Usage Data, Crash Data, and Other Diagnostic Data, used for App Functionality and Analytics, not linked to identity, and not used for tracking.

Google processes this information as a service provider. Firebase currently documents that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal. For more information, see:

Accounts, advertising, and tracking

Jace does not require an account. It does not contain advertising, use advertising identifiers, create advertising profiles, or track activity across other companies’ apps or websites.

File access

Jace uses the macOS App Sandbox. It can read or write a document only after you select or open it through macOS, and it stores app-scoped security bookmarks so selected recent files can be reopened.

Children

Jace is a general-purpose developer tool and is not directed specifically to children. It does not knowingly collect personal information from children.

Your choices

You control which files Jace can access. You can remove recent-file entries in the app and delete local documents or drafts using normal macOS file and app-management controls.

Because Jace has no accounts and diagnostic records are not linked to an account identity, Jace does not maintain a user profile to access or delete. For privacy questions or a request concerning diagnostic information, contact the developer using the address below. Some requests may require information sufficient to locate the relevant diagnostic record.

Changes to this policy

This policy may be updated when Jace or its service providers change. The effective date at the top of this page will be revised when changes are made.

Contact

Andy Liang
Email: jace@andylia.ng