Privacy
Privacy Notice
Effective: September 20, 2026
Scope and roles
This notice explains how TraceTerm handles information across the public website, authenticated Portal, Backend, support channels, and authorized Windows Terminal CLI installations.
TraceTerm acts as controller for account, authentication, subscription, security, and direct-support information. For operational content submitted to a customer-controlled Workspace, TraceTerm generally processes that content to provide the service on the customer's instructions. A separate enterprise agreement may define these roles in greater detail.
Information processed
- Identity and account data, such as name, email address, authentication provider, browser sessions, preferences, and security events.
- Workspace, Team, role, membership, invitation, subscription, invoice-reference, and measured product-usage information.
- Terminal CLI installation identifiers, authorization state, version, platform, device label, and last-seen information.
- Work Session and Operational Trace content, including commands, command outputs, timestamps, notes, device names, IP addresses, circuit references, configurations, and other context supplied during network work.
- Derived artifacts, topology relationships, exports, AI-run metadata, support correspondence, service logs, and diagnostic information.
TraceTerm does not receive or store full payment-card numbers. Stripe processes payment credentials on its hosted surfaces.
Purposes and legal bases
We process information to provide and secure the service, authenticate users, authorize installations, synchronize operational work, preserve canonical evidence, create requested artifacts and exports, administer Teams and subscriptions, deliver service communications, support users, prevent abuse, and comply with legal obligations.
Depending on the context and applicable law, processing is based on performance of a contract, steps requested before entering a contract, compliance with legal obligations, legitimate interests in operating and protecting the service, and consent where it is specifically required.
Service providers and sharing
TraceTerm uses service providers only as needed to operate the product. Current core providers include AWS for hosting and storage, Stripe for billing, Resend for authentication email and operational notifications, and Zoho for correspondence. These providers process information under their own security, privacy, and regional-processing terms.
We may also disclose information when instructed by an authorized Workspace user, required by law, needed to protect rights or safety, or involved in a corporate transaction subject to appropriate safeguards. TraceTerm does not sell personal information.
BYOK AI processing
AI derivation is optional and starts only when an authorized user requests it. The relevant frozen trace projection, selected context, and TraceTerm system instructions may then be sent to the AI provider configured by the user. The resulting artifact and provider metadata may be stored with the Workspace.
The selected provider's terms, retention controls, regional processing, and usage charges apply. Users are responsible for deciding whether the operational content may be submitted to that provider. Provider API credentials are intended only for user-requested product functions and are stored using application encryption controls.
International processing
TraceTerm and its providers may process information in countries other than the user's country. Where required, TraceTerm relies on contractual, organizational, and technical safeguards appropriate to the service and the applicable legal framework.
Retention, deletion, and redaction
Account, subscription, security, and support records are retained while needed to provide the service, maintain legal and financial records, resolve disputes, and protect the service. Operational content is retained while its Workspace remains active or as otherwise controlled by the customer and applicable plan or agreement.
Deletion or redaction may preserve non-content audit metadata such as identifiers, timestamps, hashes, and status history. Deleted data may remain in encrypted backups until the applicable backup lifecycle completes. TraceTerm may retain information longer when required by law, a dispute, a security investigation, or an enterprise agreement.
Security and customer responsibilities
TraceTerm uses technical and organizational controls designed to protect information, including authenticated Workspace boundaries, revocable installation authorization, encrypted transport, restricted infrastructure access, credential protection, monitoring, and backups. No system can guarantee absolute security.
Customers must have authority to access managed devices and process operational content. Users should avoid entering secrets unnecessarily, review data before AI processing or export, use available redaction controls, protect their sign-in methods and API keys, and revoke installations or sessions that are no longer trusted.
Your choices and rights
Subject to applicable law and the customer's control of a Team Workspace, individuals may request access, correction, confirmation of processing, deletion, portability, information about sharing, or review of a privacy concern. Some requests may be limited by security, audit-integrity, contractual, or legal-retention requirements.
You may manage active browser sessions, authorized installations, Team memberships, billing, AI credentials, and selected content through the product. Privacy requests can be sent to the contact below; identity verification may be required before a request is completed.
Website and session technology
The public website and Portal may use essential browser storage and cookies for authentication, security, Workspace continuity, preferences, and service operation. TraceTerm does not use optional analytics for advertising or cross-site tracking.
The public website offers optional Google Analytics measurement to understand visits, plan interest, and Terminal installer link clicks. Analytics is not loaded until the visitor accepts it, advertising storage and personalization remain disabled, and TraceTerm does not send account identity or operational content to Google Analytics.
Separately, TraceTerm records a daily aggregate count of requests made through its installer download links, whether or not optional analytics is accepted. This count contains no account, IP address, or device identifier. A download request does not prove that the installer transfer or installation completed.
Visitors may reject optional analytics or change their choice using Cookie preferences in the website footer. The preference itself is stored locally so the website can respect that decision.
Children and changes
TraceTerm is a professional network-operations service and is not directed to children. We may update this notice as the service, providers, or legal requirements change. The effective date above identifies the current version, and material changes will be communicated through an appropriate service channel.
Contact
Privacy questions and rights requests can be sent to support@traceterm.com. Contracting and payment records identify the applicable TraceTerm service operator for a purchased subscription.