OpsFort Tracker.

Privacy Policy

Last updated October 12, 2026

This policy explains what personal data Rodion Terentiev, an individual doing business as OpsFort (Florida, United States) ("OpsFort", "we") processes in OpsFort Tracker, why, for how long, and what rights you have. For account, billing and security data we are the controller. For personal data inside the Terraform state you connect we act as a processor for the customer that connected it, under the Data Processing Addendum. Questions: support@opsfort.com.

1. What we collect

  • Account: your email address, a salted hash of your password (never the password itself), whether your email is verified, and your display preferences.
  • Sign-in and security: for each signed-in session, the IP address, browser user agent and timestamps; short-lived rate-limit counters; the result of a bot check at sign-up and sign-in (Cloudflare Turnstile).
  • Workspaces: workspace names, members' email addresses and roles, and invitations you send (including the invitee's email address).
  • Customer Data: the Terraform state files you connect, stored encrypted, the resource inventory, change history and cost estimates derived from them, and the source configuration (AWS role ARN, region, bucket and object key, stored encrypted). State may contain personal data, for example names or email addresses in tags or settings.
  • Notifications and reports: your rules, and a delivery log of emails we sent (recipient address, status and time).
  • Billing: Stripe customer and subscription identifiers and subscription status. Card details are entered on Stripe's pages and never reach us.
  • Legal records: which version of these documents you accepted, when, and from which IP address and browser; and, when you connect a source, your acknowledgement about state contents.
  • Support: messages you send us.
  • Operational logs: technical request logs (including IP addresses) written by our servers.

2. Why we use it (legal bases)

  • To provide the Service you signed up for: account, workspaces, importing and analyzing state, notifications, reports and billing (performance of a contract).
  • To keep the Service and its users secure: preventing abuse, investigating incidents, enforcing our Terms (legitimate interests).
  • To understand and improve the Service using aggregated usage measurements that do not include state contents (legitimate interests).
  • To keep records required for tax, accounting and legal claims (legal obligation and legitimate interests).

We do not sell or rent personal data, and we do not use it for advertising.

3. Who we share it with

Only with service providers that process it for us under contract, and only as needed:

  • Amazon Web Services (United States): hosting, databases, storage, backups, content delivery and email delivery (Amazon SES).
  • Cloudflare (United States): bot protection on sign-up and sign-in (Turnstile).
  • Stripe (United States): subscription payments and invoices; Stripe is also an independent controller for payment data.
  • Atlassian (United States): our support desk (Jira Service Management) for problem reports and support requests you send us.

We may also disclose data when the law requires it, to protect rights and safety, or to a successor if the business is transferred (with these protections continuing). We will update this list before adding a provider that processes Customer Data.

4. International transfers

We are based in the United States and the Service is hosted there. If you are in the European Economic Area, the United Kingdom or Switzerland, transfers to us and our providers rely on the European Commission's Standard Contractual Clauses (incorporated in the Data Processing Addendum) or on the provider's certification under the EU-U.S. Data Privacy Framework.

5. How long we keep it

  • Account and workspace data: while the account or workspace exists.
  • Terraform state and derived data: while the source exists. Older raw state copies may be removed earlier under our storage retention settings. Deleted when the source, the workspace or the account that owns it is deleted.
  • Sessions: they expire after 7 days.
  • Email delivery log: while the workspace exists; your address is removed from it when you delete your account.
  • Backups: encrypted database backups are rotated automatically and kept for up to 90 days.
  • Operational logs: rotated automatically by size and overwritten; normally kept for days to a few weeks.
  • Legal records: after an account is deleted we keep, without IP address or browser, the record that the account accepted our documents, and a deletion record holding only the former account id, a one-way hash of the email address and the ids of deleted workspaces. We keep these for up to 6 years to establish or defend legal claims and to make sure a deletion is re-applied if a backup is ever restored.
  • Email suppression list: if an address bounced or complained, we keep it on a do-not-email list so we never email it again.
  • Billing records held by Stripe: as required by tax and accounting law.

6. Deleting your account

You can delete your account yourself in Account settings → Delete account. You will be asked for your password. Deletion is permanent and takes effect immediately:

  • your account, sessions, notification and report rules and workspace memberships are deleted;
  • workspaces where you are the only member are deleted with all their sources, stored state and history;
  • invitations you sent or received are deleted, and your address is removed from email delivery logs;
  • you are signed out and we send a confirmation to your email address.

To protect other people's data, deletion is not possible while you own a workspace that other members use (remove them first) or while a workspace has an active paid subscription (cancel it first).

Backups. Data that was in the database before deletion remains in our encrypted backups until they expire, within 90 days. Backups are not used for anything except recovery from a failure. If we ever restore one, we re-apply all recorded deletions before the Service is available again, so deleted accounts do not come back.

Full erasure. To have us erase every remaining record about you that we are able to erase, including support correspondence, your customer record at our payment processor (where tax law allows) and the other records listed in section 5, email support@opsfort.com from the address of the account with the subject "Full erasure request". We may ask you to confirm your identity. We complete the request within 30 days and confirm by email, and we tell you about anything we must keep by law (for example invoices) and why.

7. Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to the processing of your personal data, to receive it in a portable format, and to withdraw consent. Write to support@opsfort.com; we answer within 30 days. You can also complain to your data protection authority. If your request concerns state connected by a customer, we will pass it to that customer and help them answer.

California residents: we do not sell or share personal information for cross-context behavioral advertising, and we do not use sensitive personal information for purposes other than providing the Service.

8. Security

State files and source credentials are encrypted by the application before storage; connections use TLS; passwords are hashed; backups are encrypted; access to production systems is restricted to the operator of the Service. See the Data Processing Addendum for details.

9. Children

The Service is not directed to anyone under 18, and we do not knowingly collect their data.

10. Changes

We will post changes here with a new date. For material changes we notify you by email or in the Service and ask you to accept the new version.