Alias Privacy

Alias stores snippets, aliases, collections, tags, rich text, app-specific rules, import labels, usage counts, and related library metadata in a local SQLite database. By default, that database is at ~/Library/Application Support/Alias/Alias.sqlite.

Local usage history may record which snippet was copied or inserted, the action and time, and the frontmost app's bundle identifier when that option is enabled. You can turn off new app attribution and clear existing usage history in Alias Settings.

Direct-distribution builds store the local trial start date and an activated license in the macOS Keychain. A signed license contains the purchase email, license plan, issue date, and included-updates date. Alias verifies that license on your Mac using a bundled public key; activation does not contact the fulfillment service.

Alias can import CSV, Raycast JSON, and TextExpander plist files that you choose. The app previews the import first and writes selected items to the local library only after you approve the import.

Alias requests Accessibility permission to insert expansions into other apps and Input Monitoring permission to detect aliases typed globally. It keeps a short in-memory typing buffer for matching and resets that buffer after matches and navigation keys. Alias does not intentionally save every keystroke.

Launch at Login is optional and can be changed in Settings. Alias does not request broader access to files or accounts to perform text expansion.

Copy and insertion features use the macOS pasteboard. During an insertion, Alias temporarily writes the rendered snippet to the pasteboard, performs the paste, and restores the prior pasteboard contents. Selected-text wrapping temporarily copies the selection and restores the prior contents after reading it.

Alias writes an expansion diagnostics log at ~/Library/Application Support/Alias/ExpansionDiagnostics.log. It may contain timestamps, permission and event-tap state, app names or bundle identifiers, snippet identifiers, and redacted per-run alias fingerprints.

The current app does not intentionally log exact alias triggers, typed text, clipboard contents, rendered expansions, snippet bodies, license keys, or imported file contents. The log is reset when the expansion engine starts, and you can clear it in Settings.

Alias has no account system, cloud snippet sync, advertising, third-party analytics SDK, or crash-reporting SDK. It does not send snippets, aliases, imports, usage history, diagnostics, clipboard contents, selected text, or app rules to SideQuest.

Direct-distribution builds may use Sparkle to request the SideQuest-hosted Alias update feed and download an update. The infrastructure serving those files may process standard request information such as an IP address, client details, requested URL, and timestamp to deliver and protect the service. Development builds omit the update feed.

Stripe hosts Alias checkout, and the separate Alias fulfillment service handles the minimum order information needed to deliver and recover a license. Alias itself does not receive full card details or retrieve your order from that service. The general SideQuest Privacy Policy explains purchase, fulfillment, transactional email, and support handling.

If you voluntarily send logs, screenshots, snippets, or other details through support, SideQuest uses that information to answer the request. Share only what is needed, and do not send card details or a license key through the support form.

Alias keeps local library data until you change or delete it. Removing the app bundle does not necessarily remove its Application Support folder or Keychain records. You can clear usage history and diagnostics in Settings. To remove the remaining local library, quit Alias and delete its Application Support folder.

Purchase and support records are separate from the app's local data and may need to be retained for refunds, fraud prevention, accounting, tax, dispute handling, or other legal obligations. Use the SideQuest support page for a privacy question or request.

If Alias's data practices change, this notice will be updated before the changed version is released. A published revision will include a new effective date.