Privacy Policy

What Glintype does and does not do with your writing. Last updated 2 June 2026.

The short version

Glintype runs on your Mac. Your writing is processed on your Mac. Your writing is not sent to Glintype's servers because Glintype does not run servers that receive your writing. Optional cloud providers are strictly BYOK and only used if you opt in.

What we do not collect

The text you type. The suggestions the model produces. The apps you type in. The fields you type into. Screenshots. Clipboard contents. Any analytics event tied to your writing.

We do not run an analytics SDK in the app. There is no "anonymous improvement" opt-out because there is no collection in the first place.

What leaves your Mac

License activation: a request to the Glintype license service containing the license key and a coarse machine fingerprint. This happens on app launch and when you change a license state. We need it to verify the license and enforce the seat count.

Sparkle update checks: a request to the Glintype Sparkle feed to discover new versions. This is the same mechanism every Mac app uses for auto-updates.

That is the complete list of network calls that Glintype itself makes.

Local models and Apple Intelligence

When you use a local GGUF model, the model runs in-process via llama.cpp. All tokenization, prompt construction, sampling, and decoding happen on your Mac. Nothing is sent off-device for those suggestions.

When you use Apple Intelligence, suggestions are produced by the on-device FoundationModels runtime. Apple handles the FoundationModels privacy model; we do not see your prompts or the model's output.

Optional cloud providers (BYOK)

Glintype can route suggestions through third-party hosted models if you choose a Cloud or Hybrid mode. To do this you provide your own API key. The key is stored in macOS Keychain and is never transmitted to Glintype's servers.

When a cloud provider is active, the text immediately around your caret and any context you have enabled (clipboard, screen) is sent to that provider under their privacy and data retention terms. Glintype is not a party to that exchange. You can disable the cloud provider at any time and Glintype will fall back to local models.

Dictionary, memory, and accepted phrases

Your local dictionary entries, accepted-phrase memory, and per-app profiles are stored on your Mac. The dictionary store is encrypted with a key held in macOS Keychain. If you uninstall Glintype, this data remains on disk until you remove it through the menu bar app or by deleting the application support directory manually.

You can inspect, edit, and clear all of this data from inside the app.

Telemetry, crash reports, and "improvement" programs

There are no telemetry endpoints. There is no opt-in or opt-out for crash reporting because we do not collect crash reports. The macOS native crash reporter can be configured in System Settings → Privacy & Security → Analytics & Improvements; Glintype does not control that setting and does not receive data from it.

Children

Glintype is not directed at children under 13. We do not knowingly collect information from children. If you believe a child has provided information, contact [email protected] and we will delete the associated license.

Changes to this policy

If we change what the app does on the network, we will update this page. Material changes will be highlighted in the app on next launch.

Contact

Questions, requests, or concerns: [email protected]. We read every message and respond within a few business days.