Repository navigation
Privacy and Data
Tepegoz is local-first. In the current product shape, there is no required account, no managed cloud backend, and no server receiving browsing telemetry.
User data lives under the platform user-data directory:
| OS | Path |
|---|---|
| Windows | %APPDATA%\tepegoz |
| macOS | ~/Library/Application Support/tepegoz |
| Linux | ~/.config/tepegoz |
The profile contains SQLite data, preferences, quarantined downloads, local models, dictionaries, extension data, and helper/provider configuration.
Sensitive secrets are encrypted through the OS keychain:
- AI provider API keys.
- Stored website login credentials.
- WireGuard private keys.
Encrypted values generally do not travel to another machine by copying the profile folder. That is the protection working, but it means migration needs export/import flows where available.
Current export coverage includes:
- Bookmarks as Netscape HTML.
- Stored logins as Google-compatible CSV.
- Browsing history as CSV.
- Downloads list as CSV.
- Preferences as re-importable JSON.
- Macros as re-importable JSON.
- Scheduled task configuration as re-importable JSON.
- Trust profiles as re-importable JSON.
- Individual agent chats or diagnostic bundles.
Agent memory and skills do not yet have a supported export path. In the current build, those stores are effectively inert, so the gap is mostly future-facing.
Cloud model prompts and page content go directly from the user's machine to the selected provider using the user's own key. Tepegoz does not currently proxy those calls through a managed service.
Close the app before copying the profile folder. SQLite uses WAL side files, so copying only the main database while the app is open can miss recent writes.
docs/data-and-backup.mddocs/ai-transparency.mddocs/website/privacy.md