applye
Source: soon

Your data: where it lives and how to move it

Local-first is only a real promise if you can find, copy, and destroy your data yourself. Here is exactly where it is.

What is on disk

  • applye.db - one SQLite file holding your profile, jobs, applications, documents, and every cached AI result. It runs in WAL mode, so you may also see applye.db-wal and applye.db-shm next to it.
  • API keys - never in the database. They live in your operating system's keychain / credential manager, under the app identifier dev.applye.app.
  • Exported documents - wherever you chose to save them in the native dialog. Applye does not keep a second copy.

The database sits in the standard per-user app-data directory for your OS:

  • macOS - ~/Library/Application Support/dev.applye.app/
  • Windows - %APPDATA%\dev.applye.app\
  • Linux - ~/.local/share/dev.applye.app/ (or your $XDG_DATA_HOME equivalent)

Backing up and moving machines

  1. Quit Applye, so the write-ahead log is checkpointed cleanly.
  2. Copy the whole app-data folder, not just the .db file.
  3. On the new machine, install Applye, launch it once so the folder exists, quit, and put the copy in place.
  4. Re-enter your API key: keychain entries deliberately do not travel with a file copy.

That folder is also the whole answer to "what does a backup tool need to include". Any ordinary encrypted-backup setup covers Applye by covering that directory.

Deleting everything

Settings has a two-step Delete all data action: it wipes the local database and removes your keys from the keychain. Deleting your data here is deleting a file - there is no server copy to request, chase, or wait 30 days for. If you prefer, delete the app-data folder by hand; the result is identical.

What Applye cannot delete is data your AI provider retained on their side. That is governed by their terms, which is one reason bringing your own AI is a deliberate choice rather than a hidden default.