Privacy Policy
Последна редакция / Last updated: 14.11.2026
1. Controller and contact
For personal data processed in providing Fetcher, the responsible provider is Bozhidar Hristov, an individual. For GDPR requests use the contact form. Roles concerning data in user projects depend on the specific context.
2. Data categories
Depending on the features used, data may include account and virtual-session information, agent identifiers, files, commands and results. Fetcher's database stores technical session and request logs, including session identifiers, timestamps, IP addresses, User-Agent strings, paths or URLs, status codes and execution metadata. Metadata about virtual sessions and agent requests is also stored. MariaDB access may involve connection parameters, database and table names, schemas, SQL queries and results that may contain personal data. Users enter connection credentials and set MariaDB account privileges. MariaDB credentials are stored in an encrypted file on the user's computer, are used only by the local agent to connect to the MariaDB server, and are not sent to the Fetcher backend.
3. Purposes and legal bases
Processing supports requested features, access and session management, security, diagnostics and responses to inquiries. Depending on the circumstances, legal bases may include contract performance, legitimate interests, legal obligations or consent.
4. Transfers and recipients
Data and results may pass through the agent, backend and the AI platform used, depending on the operation. Not all information necessarily stays on the user's device. Access by infrastructure and other providers depends on services actually used.
5. Security and retention
Access controls, permissions and additional SQL validation are used for the read-only MariaDB feature. Users control MariaDB account privileges. MariaDB credentials are stored locally in an encrypted file on the user's device and used only by the agent; they are not sent to the backend. Technical logs and session metadata are stored in Fetcher's database. Technical web-session and request logs (fetcher_log_sessions, fetch_log_local and fetch_log_url) are subject to an automated daily cleanup of records older than 90 days. Cleanup runs in limited batches, so a backlog may take multiple daily runs to clear. Expired OAuth authorizations are cleaned up separately; valid authorizations and active virtual sessions are managed according to their lifecycle. Account deletion requires confirmation and password verification and is blocked while the account owns projects or connections. When deletion succeeds, account records, associated virtual sessions, OAuth authorizations and related records are removed. Session logs are deleted where their identifiers are exclusive to the account; records associated with shared identifiers may remain. Agent identities (ASIDs) are retained independently of user accounts, while direct references to the deleted user in agent identity records are cleared. Other records are retained according to their operational or security purpose and applicable legal obligations; a request to exercise data-protection rights can be made through the contact form.
6. Your rights
Subject to GDPR, you may request access, rectification, erasure, restriction, portability and object to processing where applicable. You may withdraw consent where it is the legal basis and complain to the Bulgarian Commission for Personal Data Protection.
7. Changes
Material changes will be reflected in an updated policy. For inquiries use the contact form.