Privacy Policy

Who we are

Fieldhand is operated by ABNER GABRIEL DE SOUZA LTDA, a company registered in Brazil (CNPJ 57.266.189/0001-86). For data about our customers' accounts (who signs in, billing, support) we are the controller. For data that comes from your devices or that your workspace puts in the Service, we process it on your behalf and following your instructions; your organization is the controller and should tell the people concerned. Contact for privacy matters, including our data protection officer (encarregado under Brazil's LGPD): support@fieldhand.dev.

What we collect

Account: your email address, the workspace name, your role and which devices you may access, sign-in records kept by our authentication provider, and the IP address of your requests.

Devices: the name, hostname, operating system, kernel and CPU architecture each agent reports; network interfaces and addresses; health metrics (CPU, memory, disk, temperature, load, uptime); connection times and public IP addresses; the state of services you choose to watch; an inventory (hardware vendor, model, serial number, installed packages and versions); and a hardware fingerprint (a one-way hash of machine identifiers) used to enforce free-plan limits.

Terminal sessions: who opened a session, on which device, from which IP address, when, for how long, and how many bytes went each way. We do not record what is typed or shown in the terminal; that traffic passes through the relay encrypted in transit and is not stored.

Fleet commands: the command, who ran or scheduled it, on which devices, and for each device its exit code, duration and the last 16 KB of its output.

Files, device web pages, logs, screenshots and remote view: who transferred which file (path and size), opened which address and port, read which log, captured or viewed the screen of a device, when, and from which IP address. File contents, screenshots, screen sessions, logs and web page traffic pass through the relay and are not stored.

Integrations: alert channel addresses you add (such as a Slack webhook URL) and API tokens, which we store only as hashes.

Billing: handled by Stripe. We store your Stripe customer and subscription identifiers, never your card details.

Why we use it, and on what basis

To provide the Service you signed up for (performance of the contract); to keep an audit trail, prevent abuse and fraud and secure the Service, including the sign-in bot check (legitimate interests and legal obligations); to bill paid plans and keep accounting records (contract and legal obligations); and to tell you about your account, security issues and changes to the Service (contract and legitimate interests).

We don't sell or share personal data for advertising, we don't use it to build advertising profiles, and we don't use your device data to train models.

Who processes it

Supabase (database and authentication, United States), DigitalOcean (hosting of the API and relay, United States), Cloudflare (DNS and bot protection), Resend (sign-in, invite and alert emails), Stripe (payments) and OSV.dev, run by Google (we send it package names and versions to look up known vulnerabilities, never anything that identifies you or a device). Alerts also go to the services you connect (Slack, Microsoft Teams, Discord, PagerDuty or your webhook), under their own policies. Each processor handles data only to provide its part of the Service.

We may disclose data when required by law or a valid order, to protect the rights, property or safety of our customers, ourselves or others, or as part of a merger or acquisition, in which case this policy continues to apply to it.

International transfers

Our infrastructure is in the United States, and we are based in Brazil. Data is therefore transferred across borders, relying on our providers' contractual safeguards (such as standard contractual clauses) and, where applicable, on transfers being necessary to perform our contract with you.

Cookies and similar technology

The dashboard keeps your sign-in session in your browser's local storage. Device web pages use one cookie, only on their own address, to know the page was opened from your dashboard. The sign-in page uses Cloudflare Turnstile to tell people from bots. We don't use advertising or third-party analytics cookies.

Retention

Metric history is kept for 7 days and connection history for 30 days. Device records, session and activity audit entries, and command results are kept while your workspace exists, so you have a history of access. When you ask us to delete your workspace, we delete its data within 30 days, except billing and tax records we must keep by law, and backups, which expire within 14 days.

Security

Connections use TLS. Device keys, enrollment tokens and API tokens are stored only as hashes. Every terminal session requires a single-use ticket that expires in 30 seconds, and every action on a device is checked against the person's role and device scope. Agent updates are signed. Access to production systems is limited and key-based. No system is perfectly secure; if a breach affects your personal data, we'll notify you and the authorities as the law requires.

Your rights

You can access, correct, export or delete your personal data, ask which processors received it, withdraw consent where we rely on it, or object to its use, by writing to support@fieldhand.dev. Depending on where you live (for example under Brazil's LGPD, the GDPR or US state laws such as the CCPA) you may have additional rights, and you can complain to your data protection authority (in Brazil, the ANPD). If you are a person whose data is in a customer's devices, we'll forward your request to that customer, who controls that data.

Children

The Service is for businesses and not directed to children; we don't knowingly collect data from anyone under 18.

Changes

We'll post updates here with a new effective date and email workspace owners about material changes.