Local accounting data
The core bookkeeping workflow is built around a local Mac administration. Mekazu does not need a cloud mirror of the administration for invoices, purchases, VAT, reports, bank activity, and exports.
Privacy and data security
Local-first accounting needs clear data boundaries.
Mekazu is designed around local administrations on Mac. This page explains what that means for accounting data, AI model access, cookies, newsletter preferences, MCP, REST API access, backups, and the responsibilities that remain with the user.
Short answer
Mekazu keeps the core accounting administration local on the Mac. External AI providers are used only when the user connects them with their own account and API key.
AI provider boundaries
Mekazu does not include paid access to OpenAI, Claude, Mistral, or other external model providers. If you connect an external provider, you do that with your own account and API key. Local models can be used through Ollama where supported.
Cookies and newsletter preferences
Google Analytics is loaded only after analytics cookies are accepted. Newsletter preferences are stored separately from cookie consent in the local website database until a production email provider is connected.
MCP and REST API access
MCP and REST API access can expose accounting context to tools, scripts, or compatible AI clients. These workflows require a license after the 14-day AI trial and should be enabled only for trusted local workflows.
User responsibilities
Users remain responsible for Mac security, backups, operating system updates, provider accounts, API keys, and deciding which data may be sent to connected model providers.
Checklist
Security checklist
- Protect the Mac account and disk with strong credentials
- Keep backups of accounting files
- Store model provider API keys carefully
- Review which AI provider receives data
- Enable MCP and REST API access only when needed
- Use the preference center to manage analytics and newsletter choices
Related