OwlTerm Privacy Policy

Last Updated: August 1, 2026

OWLTERM TECHNOLOGIES INC., a Delaware corporation (“OwlTerm,” “we,” “us,” or “our”), operates the OwlTerm desktop application, websites, cloud services, user portal, and related services collectively referred to as the “Service.”

This Privacy Policy explains how we collect, use, disclose, retain, and protect personal information when you use the Service.

This Privacy Policy is a notice about our data practices. Our Terms of Service separately govern your use of the Service.

1. Overview

OwlTerm is an AI-powered terminal and operations workspace that includes a desktop application, cloud backend, web portal, and integrations with third-party service providers.

OwlTerm may process information when you:

create or access an account;
use AI-assisted features;
connect to local or remote systems;
create or run Jobs;
use account, credit, or billing features;
contact support;
visit our websites.

We seek to limit collection to information reasonably necessary to provide, operate, secure, support, and improve the Service.

We do not sell or rent personal information.

We do not share personal information with third parties for their independent advertising purposes.

2. Information We Collect

2.1 Account Information

When you create or use an OwlTerm account, we may collect:

your email address;
account identifier;
account status;
verification and authentication records;
plan or beta eligibility;
credit balance and usage;
subscription or billing status, if applicable;
account creation and last-login information;
settings associated with your cloud account.

OwlTerm uses passwordless or token-based authentication. We may process temporary login codes, session tokens, device-related authentication records, and related security information.

We do not store authentication codes in readable form longer than needed for their intended purpose.

2.2 Device and Application Information

When you use the desktop application, we may process information such as:

application version;
operating-system type and version;
system architecture;
general device or installation information;
application configuration relevant to compatibility;
feature availability;
error status;
connection status;
technical diagnostics.

We do not use this information to continuously monitor unrelated activity on your device.

2.3 Website and Network Information

When you access our websites, portal, authentication services, or cloud APIs, we or our infrastructure providers may automatically process:

IP address;
request date and time;
browser type;
operating system;
requested URL or API route;
response status;
account or session identifier;
referring page, where available;
security and fraud-prevention signals;
approximate geographic region inferred from an IP address;
network and server logs.

This information may be used to operate the Service, authenticate users, diagnose errors, enforce limits, investigate abuse, and protect accounts and infrastructure.

2.4 Local Terminal Sessions

OwlTerm allows you to create and interact with terminal sessions, including local shell, SSH, SFTP, PowerShell, and WinRM sessions.

OwlTerm does not continuously upload the entire terminal session merely because a terminal is open.

Terminal display contents and ordinary terminal interaction generally remain on the device unless you invoke a feature that requires selected information to be processed through OwlTerm’s cloud services or a third-party provider.

For example, terminal information may be transmitted when you:

invoke an AI feature;
request analysis or command generation;
ask OwlTerm to interact with a terminal;
create a report using terminal results;
submit diagnostic information for support;
use another cloud-dependent feature.

2.5 AI and LLM Interaction Data

When you invoke an AI feature, OwlTerm sends the prompt and context reasonably necessary to fulfill the request.

Depending on the feature, this context may include:

recent terminal output;
commands;
working-directory information;
operating-system or shell information;
connection or target identifiers;
Job definitions and results;
error messages;
file content deliberately included in the request.

OwlTerm does not continuously upload the entire terminal session merely because a terminal is open.

AI requests are transmitted through OwlTerm’s cloud infrastructure and may be sent to third-party AI providers, currently including the OpenAI API, for processing.

Under normal operation, OwlTerm does not persist the full contents of AI prompts or responses in its cloud account database.

AI conversation history is normally stored locally on the user’s device. Users may delete locally stored conversation history through the desktop application.

OwlTerm may temporarily process prompt and response content while delivering an AI request. Content may also be processed or retained in limited circumstances when:

you deliberately submit it in a support request;
you enable or provide diagnostic information;
access is necessary to diagnose a reported problem;
access is necessary to investigate abuse or a security incident;
retention is required by law;
a third-party AI provider processes it under its applicable policies.

Deleting local AI history does not delete request metadata retained for billing, security, fraud prevention, or legal purposes, and does not control information temporarily processed by third-party providers.

2.6 AI Request and Billing Metadata

For metering, billing, credit management, reliability, service limits, and abuse prevention, OwlTerm may store metadata about AI requests.

This metadata may include:

account or user identifier;
request date and time;
selected feature or task category;
selected AI model;
input token count;
output token count;
request length;
request duration;
credits charged;
success or failure status;
error category;
request, task, or transaction identifier.

This metadata does not ordinarily contain the full prompt or full AI response.

We may use this metadata to:

calculate credit usage;
display account usage;
enforce account and plan limits;
investigate billing errors;
diagnose performance problems;
detect unusual or abusive usage;
analyze aggregate Service reliability.

2.7 Jobs and Automation Information

When you use OwlTerm Jobs or related automation features, OwlTerm may process information such as:

Job definitions;
Job names and identifiers;
actions and scripts;
variables;
target identifiers;
selected hosts or groups;
concurrency and error settings;
execution status;
results and error messages;
exports or generated reports.

The amount of Job information transmitted to cloud or AI services depends on the feature you invoke.

Jobs and related configurations stored locally remain on your device unless you use a cloud feature that transmits or synchronizes them.

2.8 Files and File Content

OwlTerm may access local or remote files when you deliberately request actions such as:

opening a file;
editing a file;
transferring a file;
asking an AI feature to analyze or modify a file;
generating a report from file content;
attaching a file to a support request.

File content is not automatically uploaded merely because a file is visible in the application.

When you ask an AI feature to process a file, the relevant file content or selected portions may be transmitted through OwlTerm’s cloud infrastructure and to the applicable AI provider.

2.9 Connection Credentials and Private Keys

Saved connection passwords, private keys, and related authentication information are stored locally using operating-system credential facilities, such as macOS Keychain or the corresponding credential facility available on Windows.

OwlTerm does not intentionally store saved SSH passwords, private keys, or remote-system passwords in its cloud services.

Depending on your configuration, OwlTerm may locally store:

a private key;
a reference or path to a private-key file;
a private-key passphrase;
a connection password;
other connection authentication information.

You are responsible for securing your device, operating-system account, local files, keyring, and credential store.

Credentials may be used locally by OwlTerm to establish connections requested by you.

2.10 Secrets and Sensitive Information

Terminal output, commands, files, and AI prompts may contain sensitive information, including:

passwords;
access tokens;
private keys;
authorization headers;
session cookies;
environment variables;
hostnames;
usernames;
IP addresses;
file paths;
source code;
confidential business information;
customer data;
personal information.

OwlTerm does not guarantee that all secrets, hostnames, personal information, or other sensitive content will be automatically detected or removed before information is processed by an AI provider.

You should review the context you provide and avoid submitting secrets or confidential information unless doing so is necessary, authorized, and appropriate for the applicable feature.

A secret displayed in terminal output may be transmitted when that output is included as context for an AI request, even though OwlTerm does not intentionally store the underlying connection credential in its cloud services.

2.11 Support and Feedback Information

When you contact OwlTerm for support or provide feedback, we may collect:

your email address;
support messages;
screenshots;
logs;
terminal output you choose to provide;
AI prompts or responses you choose to provide;
system and application information;
files or other attachments;
correspondence with support personnel;
bug reports and feature requests.

Please remove passwords, private keys, tokens, and unrelated sensitive information before submitting support materials.

Authorized OwlTerm personnel may inspect submitted information where reasonably necessary to:

respond to your request;
diagnose a reported malfunction;
reproduce a problem;
investigate a security issue;
investigate abuse;
comply with law.

Access is limited to personnel or service providers with a business need.

2.12 Payment and Transaction Information

When paid services are available, payment processing may be handled by third-party payment providers such as Stripe.

OwlTerm does not store full payment-card numbers or card security codes.

We may receive limited billing information from the payment provider, such as:

customer identifier;
transaction identifier;
payment status;
subscription status;
billing country;
card brand and partial card details;
purchase amount;
invoice information;
refund or dispute status.

Payment providers process payment information under their own privacy policies and legal obligations.

2.13 Communications

We may collect information when we send or receive:

account-verification messages;
login messages;
security notifications;
service announcements;
policy notices;
support communications;
billing communications;
optional product updates.

Transactional messages may be necessary to operate your account.

Where permitted by law, we may send optional product or marketing communications. You may unsubscribe from optional marketing communications using the method provided in the message.

Unsubscribing from marketing does not prevent us from sending necessary security, account, billing, or legal notices.

3. Sources of Information

We collect information from the following sources:

3.1 Directly From You

For example, when you:

create an account;
enter a prompt;
use an AI feature;
submit a Job;
contact support;
provide feedback;
purchase a service.

3.2 Automatically From the Service

For example:

request logs;
device information;
application version;
token counts;
usage records;
error status;
security events;
login history.

3.3 From Your Organization

If an employer, administrator, or other organization provides or manages your access, we may receive information from that organization.

3.4 From Service Providers

We may receive limited information from providers involved in:

cloud hosting;
authentication;
email delivery;
AI processing;
billing;
fraud prevention;
security;
technical support.

4. How We Use Information

We may use information to:

provide and operate the Service;
authenticate users;
maintain user sessions;
process AI requests;
provide terminal, file, Job, and reporting features;
calculate credits and usage;
process payments and subscriptions;
enforce plan and account limits;
diagnose errors and performance problems;
provide customer support;
respond to security reports;
detect, prevent, and investigate fraud, abuse, and unauthorized access;
maintain the security and reliability of the Service;
analyze aggregate usage and operational performance;
communicate account, security, product, and policy information;
comply with law and legal process;
enforce our Terms of Service;
establish, exercise, or defend legal claims;
protect OwlTerm, users, and third parties.

5. AI Providers and Model Training

OwlTerm currently uses the OpenAI API to provide AI features.

OpenAI states that content submitted through its API is not used to train or improve OpenAI’s general-purpose models by default unless the API customer affirmatively opts in to data sharing.

OwlTerm does not currently opt in to using customer API content for OpenAI model training.

OwlTerm has not represented that it has a Zero Data Retention arrangement with OpenAI.

Depending on the endpoint, account configuration, and applicable provider policies, OpenAI may retain or process certain request or response data for purposes such as abuse monitoring, safety, legal compliance, or service operation.

Provider retention and processing practices may change. Current information about OpenAI’s data practices is available through OpenAI’s official business and API documentation.

OwlTerm does not currently use the content of customer prompts, terminal context, files, or AI responses to train OwlTerm models or general-purpose AI models.

OwlTerm may use non-content operational metadata, such as:

token counts;
request duration;
error categories;
model selection;
feature usage;
success or failure rates;

to operate, secure, bill for, evaluate, and improve the Service.

If OwlTerm proposes to use customer content for a materially different purpose, such as model training, we will update this Policy and provide any notice or obtain any consent required by applicable law before applying the new purpose to previously collected content.

6. Local Data and Cloud Data

OwlTerm stores certain information locally on your device. Depending on your use and configuration, local information may include:

AI conversation history;
saved host configurations;
Job definitions;
application settings;
connection information;
locally cached content;
credentials stored through the operating-system keyring;
local logs.

Cloud information may include:

account information;
authentication and session records;
credit balances;
AI request metadata;
billing records;
login and security history;
support correspondence;
cloud service logs.

Deleting information from the desktop application does not necessarily delete related cloud metadata.

Deleting cloud account information does not automatically delete locally stored information from your devices.

Uninstalling the application may not remove all local files or credentials stored by the operating system.

7. How We Disclose Information

We may disclose information in the following circumstances.

7.1 Service Providers

We may disclose information to service providers that perform services on our behalf, including providers of:

cloud hosting and infrastructure;
AI processing;
email delivery;
authentication;
billing and payment processing;
security and abuse prevention;
technical support;
professional services.

These providers may process information only for the applicable service, subject to their contractual obligations, applicable law, and their own responsibilities.

Current provider categories may include:

Amazon Web Services for cloud infrastructure;
OpenAI for AI model processing;
Stripe for billing and payment processing;
email and authentication infrastructure providers.

A provider may process information in countries different from the country where you live.

7.2 Legal Compliance and Protection

We may disclose information when we reasonably believe disclosure is necessary to:

comply with law, regulation, court order, subpoena, or legal process;
respond to lawful government requests;
enforce our Terms of Service;
detect or investigate fraud or abuse;
protect the security of the Service;
protect the rights, safety, and property of OwlTerm, users, or others;
establish, exercise, or defend legal claims.

Where legally permitted and reasonably practicable, we may provide notice before disclosing information in response to legal process.

7.3 Corporate Transactions

Information may be disclosed or transferred in connection with:

a merger;
financing;
acquisition;
reorganization;
bankruptcy;
sale of assets;
due diligence for a proposed transaction.

Any successor receiving personal information will be subject to applicable privacy laws and the commitments applicable to the information.

7.4 With Your Direction or Consent

We may disclose information when you direct us to do so, authorize an integration, submit information to another service, or otherwise provide consent.

8. No Sale or Advertising Sharing

OwlTerm does not sell personal information for money.

OwlTerm does not currently share personal information for cross-context behavioral advertising or targeted advertising.

OwlTerm does not provide AI prompt or terminal content to advertisers.

If these practices change, we will update this Policy and provide rights or choices required by applicable law.

9. Hosting and International Data Transfers

OwlTerm’s primary cloud infrastructure is currently hosted using Amazon Web Services in Singapore.

Information may also be processed in other countries, including the United States, when it is transmitted to providers such as OpenAI, Stripe, email providers, or other service providers.

The laws of countries where information is processed may differ from the laws of your country.

Where required by applicable law, we will use appropriate safeguards for international data transfers, such as:

contractual protections;
approved data-transfer clauses;
provider security commitments;
other lawful transfer mechanisms.

We may change hosting locations or cloud regions as the Service evolves. Where required, we will provide appropriate notice regarding a material change in data location or transfer practices.

10. Legal Bases for EEA and UK Processing

Where the European Economic Area or United Kingdom data-protection laws apply, we process personal information under one or more of the following legal bases.

10.1 Performance of a Contract

We process information where necessary to:

create and manage your account;
authenticate you;
provide requested AI features;
provide cloud functionality;
administer credits and billing;
respond to support requests.

10.2 Legitimate Interests

We may process information for legitimate interests such as:

protecting accounts;
securing our systems;
preventing abuse and fraud;
diagnosing failures;
maintaining Service reliability;
improving non-content operational performance;
enforcing our agreements;
protecting legal rights.

We consider the effect of this processing on users and do not rely on legitimate interests where those interests are overridden by applicable rights.

10.3 Consent

We may rely on consent where required, such as for certain optional communications or optional data collection.

You may withdraw consent where processing is based on consent. Withdrawal does not affect processing that occurred before withdrawal.

10.4 Legal Obligations

We may process information to comply with:

tax and accounting requirements;
court orders;
regulatory obligations;
lawful government requests;
security and incident-reporting requirements.

11. Data Retention

We retain personal information for as long as reasonably necessary for the purposes described in this Policy.

Retention depends on factors such as:

whether your account remains active;
the type of information;
the reason it was collected;
security and fraud-prevention needs;
support requirements;
contractual obligations;
accounting and tax requirements;
legal limitation periods;
applicable law.

Our current retention approach includes the following.

11.1 Account Information

Account information is generally retained while the account remains active.

After an account-deletion request, eligible information may be deleted, de-identified, or restricted after verification and completion of applicable administrative processes.

11.2 Local AI Conversation History

AI conversation history stored locally remains on the device until:

the user deletes it;
the application removes it according to its local settings;
the application data is removed from the device.

OwlTerm cannot delete local history from a device to which it no longer has access.

11.3 AI Prompt and Response Content

Under normal operation, OwlTerm does not persist full AI prompt and response content in its cloud account database.

Content may be processed transiently to complete requests.

Content deliberately submitted for support or debugging may be retained with the corresponding support case for as long as reasonably necessary to resolve the issue, maintain support records, protect security, or comply with law.

Third-party AI providers may apply their own retention periods under their applicable policies and account configurations.

11.4 Request and Billing Metadata

AI request, token, credit, transaction, and billing metadata may be retained as reasonably necessary to:

operate accounts;
display or verify usage;
investigate billing disputes;
prevent abuse;
maintain accounting records;
meet tax or legal obligations.

11.5 Login and Security Records

Login history, security events, IP records, and abuse-prevention information may be retained for a reasonable security period based on the type of event and ongoing risk.

Records associated with fraud, abuse, a security incident, or a legal dispute may be retained longer.

11.6 Payment Records

Billing, payment, invoice, tax, refund, and dispute information may be retained for the period required by accounting, tax, financial, fraud-prevention, and legal obligations.

11.7 Support Records

Support correspondence and voluntarily submitted diagnostic information may be retained for as long as reasonably necessary to:

resolve the request;
identify recurring issues;
protect account security;
maintain business records;
comply with law.

11.8 Logs and Backups

Information may remain temporarily in:

infrastructure logs;
security logs;
database backups;
encrypted backups;
disaster-recovery systems;
provider systems.

Backup copies are generally removed or overwritten according to applicable backup and lifecycle schedules.

Information retained in backups may not be immediately removed when active data is deleted but will not be restored for ordinary use unless needed for recovery, security, or legal purposes.

12. Account Deletion and Data Requests

OwlTerm does not currently provide an automated self-service account-deletion or cloud data-export feature.

You may request access, correction, or deletion of eligible personal information by contacting:

support@owlterm.com

We may require verification that you control the applicable account or email address before fulfilling a request.

When processing an account-deletion request, we may:

revoke active sessions;
disable account access;
delete or de-identify eligible account information;
retain records required for billing, fraud prevention, security, tax, dispute resolution, or legal compliance.

Deleting an OwlTerm account does not automatically delete:

local application data;
local AI history;
locally saved Jobs;
credentials stored in the operating-system keyring;
files stored on your device;
files stored on remote systems;
information retained by third-party providers under their policies.

Users are responsible for removing locally stored data and credentials from their devices where desired.

13. Your Privacy Rights

Depending on your location and applicable law, you may have rights concerning your personal information.

These may include the right to:

request access to personal information;
obtain a copy of certain information;
request correction;
request deletion;
restrict certain processing;
object to certain processing;
request portability;
withdraw consent;
opt out of certain sales, sharing, or targeted advertising;
appeal a denied privacy request;
complain to a data-protection authority;
receive equal service without unlawful discrimination for exercising a privacy right.

These rights may be subject to exceptions. For example, we may retain information needed to:

complete a transaction;
provide the Service;
protect security;
prevent fraud;
maintain legal claims;
comply with tax, accounting, or legal obligations;
exercise freedom of expression or other legal rights.

To submit a request, contact:

support@owlterm.com

Please include enough information for us to identify the relevant account and understand the request.

We may ask you to verify your identity. We will use verification information only to process and protect the request.

Where required by law, an authorized agent may submit a request on your behalf. We may request evidence of authorization and may separately verify your identity.

We will respond within the period required by applicable law.

Where applicable, instructions for appealing a denied request will be included in our response.

14. EEA and UK Rights

Where EEA or UK data-protection law applies, you may have rights to:

access personal information;
correct inaccurate information;
erase information;
restrict processing;
object to processing based on legitimate interests;
object to direct marketing;
receive portable information;
withdraw consent;
lodge a complaint with a supervisory authority.

You may contact your local data-protection authority if you believe our processing violates applicable law.

15. California and Other U.S. State Privacy Rights

Certain U.S. state privacy laws provide eligible residents with rights to:

know or access categories and specific pieces of personal information;
correct inaccurate information;
delete eligible information;
obtain portable information;
opt out of sale, targeted advertising, or certain sharing;
limit certain uses of sensitive personal information;
appeal a denied request;
receive protection from unlawful discrimination.

OwlTerm does not currently sell personal information or share personal information for cross-context behavioral advertising.

Whether a particular state privacy law applies to OwlTerm or a specific request depends on factors such as the user’s residence, the nature of the processing, and statutory applicability thresholds.

We may voluntarily honor reasonable privacy requests even where a particular law does not require us to do so.

16. Organization-Managed Accounts

If you use OwlTerm through an employer or other organization:

the organization may control your account or access;
an administrator may manage account eligibility;
the organization may establish policies governing your use;
the organization may request access to information associated with its account, subject to applicable law and product functionality;
your use may also be governed by the organization’s own privacy notices and policies.

Questions about your organization’s handling of information should be directed to that organization.

17. Cookies and Similar Technologies

Our websites and portal may use cookies and similar technologies that are necessary to:

maintain authenticated sessions;
protect against cross-site request forgery;
preserve security state;
support login and OAuth flows;
remember limited settings;
prevent automated abuse;
maintain website operation.

Third-party services involved in payment, authentication, security, or abuse prevention may also set or access cookies or similar identifiers.

Disabling cookies may prevent authentication, account access, payment, or other website features from functioning correctly.

We do not currently use cookies for cross-context behavioral advertising.

18. Analytics and Crash Reporting

OwlTerm does not currently operate a broad cloud collection system for full terminal content or command history analytics.

We may analyze non-content operational information such as:

token counts;
feature category;
request duration;
success or failure;
application version;
operating system;
error category;
credit usage.

If we introduce additional analytics or automated crash-reporting services, we will update this Policy where the change materially affects our collection or disclosure practices.

Diagnostic logs or screenshots may be collected when you deliberately provide them to support.

19. Security

We use administrative, technical, and organizational safeguards designed to protect personal information.

Depending on the system and information, these safeguards may include:

encryption in transit;
access controls;
account authentication;
credential isolation;
operating-system keyrings;
network security controls;
security logging;
least-privilege access;
backups;
monitoring and incident investigation.

No application, network, cloud service, transmission, storage system, or security measure is completely secure.

We cannot guarantee that information will never be:

accessed without authorization;
intercepted;
altered;
lost;
corrupted;
disclosed;
unavailable.

You are responsible for:

securing your device;
maintaining operating-system security;
installing security updates;
protecting your email account;
protecting local credentials;
limiting access to your OwlTerm account;
using appropriate safeguards for systems connected through OwlTerm.

If you believe your account or information has been compromised, contact:

support@owlterm.com

20. Children’s Privacy

The Service is not directed to individuals under 18 years of age, and individuals under 18 may not create OwlTerm accounts.

We do not knowingly permit children under 18 to register for the Service.

If we learn that we collected personal information from a child in violation of applicable law, we will take reasonable steps to delete or otherwise handle the information as required.

A parent or guardian who believes a child has provided personal information may contact:

support@owlterm.com

21. Do Not Track and Global Privacy Control

Some browsers provide “Do Not Track” signals. There is not currently a universally accepted standard for responding to all such signals.

Because OwlTerm does not currently sell personal information or use it for cross-context behavioral advertising, a browser opt-out signal does not change those practices.

Where applicable law requires recognition of an opt-out preference signal, such as Global Privacy Control, we will process the signal as required for the browser or device from which it is received.

22. Changes to This Privacy Policy

We may update this Privacy Policy as the Service, providers, laws, and data practices evolve.

When we update the Policy, we will:

publish the revised version;
update the “Last Updated” date;
provide additional notice when required by law.

For material changes, notice may be provided through:

email;
the desktop application;
the user portal;
our website.

Where required by law, we will obtain consent before using previously collected information for a materially different purpose.

We will not rely solely on continued use of the Service where applicable law requires affirmative consent.

23. Contact Us

For privacy questions, requests, complaints, or security reports, contact:

OWLTERM TECHNOLOGIES INC.

Email: support@owlterm.com
Website: https://www.owlterm.com