Privacy Policy

AimeFlux does not collect, store, sell, or share personal data, audio recordings, transcripts, prompts, or usage history.

We do not have access to your recordings, transcripts, prompts, API keys, or local application history.

AimeFlux optionally supports integrations with third-party AI providers configured directly by you.

If you enable these integrations, transcript text or prompts may be transmitted directly to the provider you selected for processing.

These providers operate independently from AimeFlux and are governed by their own privacy policies and terms.

You are solely responsible for reviewing and understanding the policies of any third-party provider you choose to use.

AimeFlux can expose local history and automation tools through its MCP server when you enable and connect it to an MCP client.

MCP responses are local product data surfaces. They can include transcript text, prompts, collection metadata, summaries, snippets, and processing metadata when requested by your connected client.

Private modes and private collections are hidden from MCP-visible transcript, collection, suggestion, semantic search, and related-history tools.

Semantic MCP search returns short snippets and metadata for visible results instead of full raw or processed transcript bodies.

MCP access is controlled by the local client configuration you choose. AimeFlux does not receive copies of those MCP responses.

Purchases, licensing, and payment processing are handled by third-party providers.

AimeFlux does not directly store payment card information.

Application settings, vocabulary entries, replacement rules, prompts, transcript history, collections, semantic index data, downloaded models, caches, and credentials are stored locally on your device.

Transcript history saved by AimeFlux is encrypted at rest with a local database key stored in macOS Keychain.

Local configuration files, installed community package state, license snapshots, and trial snapshots are encrypted locally.

License keys, local encryption keys, and supported provider API credentials are stored using secure platform-provided storage such as macOS Keychain.

Explicit config exports, collection exports, and community package exports are portable files by design. They may contain mode names, prompts, collection names, collection rules, summaries, replacement rules, provider settings without secrets, app bindings, and folder paths you configured.

Exports, clipboard contents, local backups, and files you move outside AimeFlux are user-managed copies and may not be encrypted by AimeFlux.

Uninstalling AimeFlux may not automatically remove locally stored application data, configuration files, transcript history, downloaded models, or caches.

You are responsible for maintaining the security of your own device, backups, exports, and third-party accounts.

Depending on your jurisdiction, you may have rights under applicable privacy laws, including rights related to access, deletion, correction, restriction, portability, and objection to processing.

Because AimeFlux does not collect or centrally store your local application data, most data can be deleted directly through AimeFlux history controls, by uninstalling the application, or by manually removing local files.

This Privacy Policy may be updated periodically to reflect legal, operational, or product changes.

Updated versions will be published with a revised "Last updated" date.

For privacy-related inquiries:

[email protected]