openTARS

Privacy & security

openTARS runs on your computer. This page lists everything that can leave it, what stays, and how openTARS keeps risky actions under your control.

What stays on your computer

  • The AI models run locally on the llama.cpp engine (or on Ollama, if you pick it in the developer settings). What you type, say and show is processed on your machine, including your voice.
  • No account, no telemetry and no analytics.
  • Your chats, memory and settings are files in your home folder. Settings → Memory & privacy shows what openTARS remembers, forgets items one by one and erases everything.
  • The log (~/.tars_log) records the actions taken, in a private folder. It keeps only the length of text typed on your behalf, not the text itself.
  • Text actions read the text you selected only when you press the shortcut, and Replace puts back what you had copied. openTARS never reads the clipboard in the background, and the selected text is treated as material, never as instructions.
  • Edited photos are saved as a new copy without the location and device data the camera wrote; the original is not changed.
  • The suggestion based on the program you are using is on by default: every 4 seconds it looks only at the name and title of the active window, saves and sends nothing, and you can turn it off in Settings → Assistant.

What can leave it

  • The update check. When the window opens and every 6 hours while it stays open, read-only requests to GitHub (api.github.com, raw.githubusercontent.com, github.com) to see if there is a new package. Nothing about you is sent besides the request itself. TARS_SEM_AVISO_VERSAO=1 turns it off.
  • The model check. When the window opens and every 6 hours, openTARS asks Ollama's registry (registry.ollama.ai) for the description of the published Gargantua, to tell you when yours is older. Nothing is downloaded until you click Update.
  • The cloud, only if you turn it on. The text you write and the screenshots you ask about go to the provider you chose, with your own key or account. The key is stored only on this computer, never shown, never written to the log and never passed to the commands the AI runs. A cloud model is never picked automatically, and the window warns you when your text goes to a provider.
  • Model downloads. The first time it opens, openTARS downloads the llama.cpp engine from GitHub (github.com) and Gargantua 2.5 from Hugging Face (huggingface.co), plus four small photo models, each one checked against a fixed SHA-256 before it is used. Models you add from the store come from Ollama's library.
  • Searching the model store. When you type in the store's search and ask it to look online, the words go to ollama.com to find models.
  • Calendar, notes and e-mail, only if you turn them on. A calendar link is downloaded when you ask about your schedule, at most every 15 minutes. E-mail connects to your own mail server with a certificate check; the password stays in your system's keyring, and nothing is sent without your yes.
  • Missions in a virtual machine. The VM sees none of your files. If you leave its internet on, its web traffic goes through a small proxy that lists every site it visited, and the files it makes only reach your computer if you pick them.
  • Websites you ask for. When you ask openTARS to open or search a site, your browser visits it as usual.

How it stays in your control

  • Commands that delete data or change the system (rm -r, rm with wildcards, find -exec rm, dd, mkfs, git reset --hard, curl | sh, ssh, shutting down) wait for your Allow. These are fixed rules, not AI.
  • Commands that ask for a password with sudo do not hang: they stop and show you the command to run yourself.
  • Scheduled routines only delete, send or install if you allowed that when you created them. Anything else makes them stop and tell you.
  • Closing a program is like clicking its X: if it asks to save, openTARS does not force it.

This website

This site is a static page hosted on GitHub Pages. It sets no cookies, has no analytics, and loads its fonts, images and video from this same site. GitHub, as the host, may log visits under the GitHub Privacy Statement.

Report a security issue

Write to projectopentars@gmail.com before opening a public issue. Include the openTARS version (opentars --version), your system (Linux distro, Windows or macOS version), what you did and what happened. Reports are answered as soon as possible, and fixes ship as a new package that installed copies pick up on their own.