Privacy Policy

Privacy Policy

HYBERX PRIVACY POLICY


HyberX respects your privacy and is committed to protecting the information processed through our website, applications, software, artificial intelligence systems, and related services.

This Privacy Policy explains how HyberX (“HyberX,” “we,” “us,” or “our”) collects, accesses, processes, uses, protects, and, where applicable, retains information when you access or use HyberX.

HyberX is a real-time Software Guidance AI designed to assist developers, system administrators, IT support professionals, DevOps teams, cloud engineers, technical builders, managed service providers (“MSPs”), internal IT teams, and other users working with software and technical environments.

HyberX is designed to understand the user's permitted software and workflow context and provide relevant, step-by-step guidance in real time.

Unlike traditional AI systems that require users to manually upload screenshots, repeatedly copy error messages, or explain every stage of a technical problem, HyberX is designed to understand relevant context while the user is actively working.

Because context-aware artificial intelligence may interact with information visible within a software environment, privacy and data minimization are fundamental to the architecture of HyberX.

Our privacy model is built around a simple principle:

Information that does not need to be permanently stored should not be permanently stored.

HyberX is designed to process relevant workflow context temporarily, assist the user in real time, and terminate temporary contextual data when the applicable session ends.

1. SCOPE OF THIS PRIVACY POLICY

This Privacy Policy applies to information processed through:

  • the HyberX website, including hyberx.ai;

  • HyberX desktop applications;

  • HyberX browser-based experiences;

  • HyberX screen-aware functionality;

  • HyberX vision and contextual intelligence systems;

  • AI-powered software guidance functionality;

  • HyberX individual user accounts;

  • HyberX team and organizational workspaces;

  • enterprise deployments;

  • MSP and IT service deployments;

  • educational and technical training deployments;

  • HyberX pilot programs;

  • customer support interactions; and

  • any other HyberX products or services that expressly reference this Privacy Policy.

This Privacy Policy does not govern third-party websites, applications, infrastructure, platforms, or services that HyberX does not own or control.

2. WHAT HYBERX DOES

HyberX provides real-time contextual software guidance.

Depending on the functionality enabled by the user and the permissions provided to HyberX, the Service may temporarily interpret the user's permitted software or workflow context.

This may include context relating to:

  • a software application;

  • a technical dashboard;

  • a development environment;

  • a browser-based platform;

  • an error screen;

  • a terminal or console;

  • a deployment workflow;

  • a cloud environment;

  • a configuration workflow;

  • an IT support process;

  • a system administration task;

  • a selected screen or application area; or

  • the current stage of a technical task.

HyberX uses relevant context to understand where the user may require assistance and provide:

  • step-by-step software guidance;

  • contextual explanations;

  • troubleshooting instructions;

  • technical checkpoints;

  • next-step recommendations;

  • deployment guidance;

  • configuration assistance; and

  • workflow-specific support.

HyberX is designed to act as a contextual guidance layer between a user and the software with which the user is actively working.

HyberX is not designed as:

  • an employee surveillance platform;

  • a covert monitoring system;

  • a screen recording service;

  • a keylogging system;

  • an advertising surveillance platform;

  • an employee productivity scoring system; or

  • a behavioural profiling service.

HyberX does not use screen or workflow context to make decisions concerning employment, credit, insurance, housing, healthcare, immigration, or other legally or similarly significant decisions about individuals.

3. SCREEN AND WORKFLOW CONTEXT

HyberX is designed to reduce the need for users to manually upload screenshots, repeatedly copy technical errors, or continuously explain their current workflow to an AI assistant.

To provide real-time guidance, HyberX may temporarily process visual or technical context permitted by the user or enabled through applicable application permissions.

We refer to this information as “Screen and Workflow Context.”

Screen and Workflow Context may include information visible within the user's active software environment, such as:

  • software interfaces;

  • application names;

  • visible interface text;

  • error messages;

  • terminal output;

  • console output;

  • configuration information;

  • development information;

  • deployment status;

  • dashboard information;

  • technical logs visible on screen;

  • file names;

  • project names;

  • workflow status;

  • support tickets;

  • network information;

  • infrastructure information; and

  • other visible information relevant to the user's active technical task.

HyberX processes Screen and Workflow Context solely to understand the immediate task and provide relevant guidance.

Screen and Workflow Context is designed to be processed in real time and is not intended to become a permanent HyberX customer data record.

4. REAL-TIME AND MEMORY-BASED PROCESSING

HyberX uses a temporary, session-based processing architecture.

During an active HyberX session, relevant Screen and Workflow Context may be temporarily maintained within volatile system memory, including Random Access Memory (“RAM”), where required to process context and maintain continuity for the active guidance session.

RAM is used as a temporary processing environment.

It is not intended to function as permanent storage of user Screen and Workflow Context.

The temporary processing of information may allow HyberX to:

  • understand the current software state;

  • interpret a visible error;

  • understand previous steps within the active session;

  • maintain short-term task continuity;

  • provide a relevant next action; and

  • adapt guidance as the user's workflow changes.

When the applicable HyberX session or processing environment is terminated, the temporary Screen and Workflow Context associated with that active processing environment is designed to be deleted, released, or otherwise removed from active memory.

HyberX does not intentionally transfer Screen and Workflow Context from temporary session processing into a permanent historical screen archive.

HyberX does not maintain a permanent server-side repository of the user's Screen and Workflow Context.

HyberX does not maintain backup copies of Screen and Workflow Context after the applicable processing session has ended.

Where information remains locally on a user's own device, that information remains subject to the user's device, operating system, local application environment, and security configuration.

5. ZERO PERSISTENT STORAGE OF SCREEN AND WORKFLOW CONTEXT

HyberX is designed around a zero-persistent-storage model for private Screen and Workflow Context.

This means HyberX does not intentionally maintain a permanent copy of:

  • the user's screen;

  • screen frames processed for real-time guidance;

  • terminal activity visible during a session;

  • console output processed during a session;

  • visible technical workflows;

  • historical error screens;

  • visible customer information;

  • credentials appearing within screen context;

  • private project information processed during a session; or

  • other Screen and Workflow Context after the applicable session terminates.

HyberX does not maintain a historical screen database.

HyberX does not maintain a searchable archive of a user's previous screens.

HyberX does not maintain a video timeline of a user's activity.

HyberX does not provide users or workspace administrators with historical screen recordings because HyberX is not designed to permanently maintain such recordings.

The purpose of Screen and Workflow Context processing is to assist the user during the active interaction, not to create a permanent history of how the user works.

6. SENSITIVE INFORMATION AND SECRET PROTECTION

HyberX recognizes that technical users frequently work in environments where confidential or security-sensitive information may be visible.

Depending on the user's environment, visible information may include:

  • usernames;

  • passwords;

  • authentication credentials;

  • API keys;

  • access tokens;

  • session tokens;

  • private keys;

  • encryption keys;

  • connection strings;

  • cloud credentials;

  • infrastructure secrets;

  • account identifiers;

  • internal system information; and

  • other confidential information.

HyberX implements security controls specifically designed to reduce the risk of sensitive information being exposed or leaked through contextual processing.

Where sensitive information is identified within permitted screen context, HyberX's security architecture is designed to protect such information through security controls, including encryption and applicable sensitive-data protection mechanisms.

The objective of these controls is to minimize the unnecessary exposure of secrets while HyberX processes the surrounding technical context required to assist the user.

Sensitive information appearing within Screen and Workflow Context is not intentionally collected for the purpose of creating:

  • credential databases;

  • password repositories;

  • secret inventories;

  • advertising profiles;

  • user identity profiles; or

  • permanent customer records.

HyberX is not a password manager or secrets management platform.

Screen-visible passwords, authentication secrets, private keys, API keys, or access tokens processed as part of a temporary session are not intended to be permanently retained by HyberX.

Temporary Screen and Workflow Context containing such information is subject to the same real-time and session termination controls described in this Privacy Policy.

Users should nevertheless continue to follow appropriate cybersecurity practices and should avoid unnecessarily displaying or exposing highly sensitive information.

7. NO SCREEN RECORDING OR USER SURVEILLANCE

HyberX is not a screen recording service.

HyberX does not intentionally create permanent video recordings of a user's screen for later review.

HyberX does not maintain a historical timeline of everything viewed by the user.

HyberX does not build a historical database showing every application, command, webpage, or software interface used by an individual.

HyberX is not designed to secretly monitor employees on behalf of an employer.

HyberX is not designed to score employee productivity based on Screen and Workflow Context.

HyberX is not designed to provide employers or workspace administrators with retrospective access to a user's historical Screen and Workflow Context.

The processing of Screen and Workflow Context is designed for the limited purpose of providing immediate contextual software guidance.

8. INFORMATION WE COLLECT

The information HyberX processes depends on how the user interacts with the Service.

It is important to distinguish between:

  1. temporary Screen and Workflow Context, which is processed during active sessions and is not intentionally persistently stored; and

  2. limited Service Information, which may be required to operate accounts, subscriptions, analytics, security, and technical support.

8.1 Account and Profile Information

When a user creates or manages a HyberX account, we may collect limited account information such as:

  • name;

  • email address;

  • username;

  • account identifier;

  • organization or company name;

  • professional role or job function;

  • account preferences;

  • authentication information; and

  • account security information.

We use this information to identify authorized users, operate accounts, manage access, and provide the Service.

Passwords used to authenticate directly with HyberX are protected through applicable authentication and cryptographic security controls.

HyberX does not intend to store user passwords in readable plain text.

8.2 Screen and Workflow Context

When a user actively enables eligible HyberX guidance functionality, HyberX may temporarily process relevant Screen and Workflow Context.

This information is processed to:

  • identify the current software environment;

  • understand the active task;

  • identify visible technical issues;

  • interpret errors;

  • provide step-by-step guidance;

  • maintain temporary session continuity;

  • provide workflow-specific recommendations; and

  • adapt guidance to the user's current software state.

Screen and Workflow Context is processed in real time and is not intentionally retained as a permanent historical customer record after the session ends.

8.3 AI Interaction Information

During an active HyberX session, the Service may process:

  • user questions;

  • user instructions;

  • contextual requests;

  • selected actions;

  • active troubleshooting information;

  • AI-generated guidance;

  • session progression; and

  • feedback actively provided by the user.

Information required solely to maintain contextual guidance may be temporarily processed during the active session.

Private Screen and Workflow Context is not retained for artificial intelligence model training.

8.4 Minimal Device and Host Information

HyberX follows a data minimization approach to device information.

We do not seek to create a comprehensive profile of a user's device.

We may collect limited technical information reasonably necessary to:

  • identify an authorized host;

  • identify an active user session;

  • protect account access;

  • operate HyberX;

  • understand basic Service performance; and

  • diagnose technical problems.

Limited device or host information may include:

  • a device or host identifier;

  • operating system type;

  • HyberX application version;

  • general device category;

  • basic session information; and

  • limited technical information necessary to operate the Service.

HyberX does not intentionally collect an exhaustive inventory of software installed on a user's computer for behavioural profiling purposes.

HyberX does not intentionally collect personal files stored on a user's device.

HyberX does not intentionally collect unrelated browsing history for behavioural profiling.

HyberX does not use limited host information to monitor a user's unrelated device activity.

8.5 Product Analytics

We may collect limited product analytics necessary to understand how HyberX is performing.

This may include:

  • features accessed;

  • general feature usage;

  • session frequency;

  • session duration;

  • guidance completion events;

  • general product interactions;

  • application performance;

  • request latency;

  • failed product requests; and

  • aggregated usage statistics.

We use analytics to:

  • understand whether features function correctly;

  • identify product friction;

  • improve user experience;

  • improve product reliability;

  • understand general Service adoption; and

  • plan product improvements.

We do not use product analytics to reconstruct a user's private historical Screen and Workflow Context.

Where reasonably possible, analytics information may be aggregated or de-identified.

8.6 Crash Reports, Error Reports, and Bug Reports

HyberX may collect limited technical information relating to application errors, crashes, software defects, and reported bugs.

This may include:

  • crash events;

  • application error codes;

  • application version;

  • operating system type;

  • affected HyberX feature;

  • limited diagnostic events;

  • timestamps;

  • technical failure information; and

  • information voluntarily submitted in a bug report.

We use this information to:

  • identify software failures;

  • reproduce technical problems;

  • investigate crashes;

  • repair product defects;

  • improve Service stability; and

  • protect the reliability of HyberX.

HyberX seeks to minimize the personal information included in diagnostic and crash information.

Crash and diagnostic systems are not intended to create a historical archive of a user's Screen and Workflow Context.

Users should avoid intentionally including credentials, private keys, API secrets, or unrelated sensitive information in manually submitted bug reports.

8.7 Team and Organization Information

Where HyberX is provided through an employer, MSP, IT service company, educational institution, or other organization, we may process limited organizational information such as:

  • organization name;

  • workspace identifier;

  • team membership;

  • user role;

  • access permissions;

  • assigned access level;

  • license status;

  • security settings; and

  • organization-level configurations.

Authorized workspace administrators may manage:

  • user access;

  • workspace membership;

  • account permissions;

  • subscription allocation;

  • organization-level security settings; and

  • applicable product configurations.

HyberX does not provide workspace administrators with a permanent historical archive of user Screen and Workflow Context.

Organizations deploying HyberX are responsible for providing notices and obtaining permissions required under applicable privacy, employment, workplace monitoring, and labour laws.

8.8 Billing and Subscription Information

Where a user or organization purchases a HyberX subscription, license, or paid service, we may process:

  • customer name;

  • billing contact information;

  • billing address;

  • subscription plan;

  • transaction identifier;

  • invoice information;

  • payment status;

  • tax information; and

  • subscription history.

Payment information may be collected and processed directly by an authorized third-party payment processor.

HyberX may receive limited payment information such as:

  • payment status;

  • payment method type;

  • card expiration information; or

  • limited payment method identifiers.

HyberX does not intend to directly store complete payment card numbers unless such processing is expressly required and performed through an appropriately secured and compliant payment environment.

8.9 Customer Support Information

When a user communicates with HyberX, we may process:

  • name;

  • email address;

  • organization information;

  • support requests;

  • correspondence;

  • troubleshooting information;

  • voluntarily submitted attachments;

  • product feedback; and

  • information reasonably necessary to investigate the request.

Support information is separate from temporary Screen and Workflow Context.

Users should not intentionally send passwords, private keys, API keys, authentication tokens, or unnecessary sensitive personal information through ordinary support channels.

9. INFORMATION HYBERX DOES NOT INTENTIONALLY COLLECT FOR PROFILING

HyberX is not designed to intentionally collect the following information for advertising or behavioural profiling:

  • detailed personal browsing history;

  • unrelated personal files;

  • complete device content;

  • private communications unrelated to HyberX functionality;

  • detailed application inventories;

  • user keystroke histories;

  • personal password repositories;

  • credential databases;

  • biometric identity profiles;

  • advertising interest profiles; or

  • historical Screen and Workflow Context.

HyberX does not use screen context to determine a user's political beliefs, religious beliefs, health condition, sexual orientation, or other sensitive personal characteristics for profiling purposes.

10. HOW WE USE INFORMATION

We process information only for purposes reasonably connected to operating, protecting, and improving HyberX.

These purposes may include the following.

Providing Real-Time HyberX Guidance

We temporarily process relevant workflow context to understand what the user is currently working on and provide appropriate software or technical guidance.

Understanding Current Software Context

HyberX may interpret permitted visual or technical information to identify the software, interface, error, or technical workflow relevant to the user's active task.

Generating Contextual AI Guidance

Relevant temporary context may be processed to generate:

  • troubleshooting instructions;

  • configuration guidance;

  • technical explanations;

  • workflow checkpoints;

  • deployment instructions; and

  • next-step recommendations.

Maintaining Temporary Session Continuity

Relevant information may temporarily remain in active memory to enable HyberX to understand the progression of the user's current session.

Protecting Sensitive Information

HyberX may apply security and encryption controls designed to reduce the exposure of sensitive information appearing within contextual processing.

Managing Accounts

We use limited account information to:

  • authenticate users;

  • manage accounts;

  • administer access;

  • manage licenses; and

  • provide subscription functionality.

Securing HyberX

We may process limited technical information to:

  • detect unauthorized access;

  • identify suspicious activity;

  • prevent Service abuse;

  • investigate security incidents;

  • protect HyberX infrastructure; and

  • enforce applicable terms and policies.

Improving Product Reliability

We may use limited analytics, crash information, bug reports, and diagnostic data to:

  • identify product failures;

  • improve performance;

  • reduce latency;

  • resolve software defects; and

  • improve user experience.

Providing Customer Support

We use support information to respond to questions and investigate technical issues.

Processing Billing

We process billing and subscription information to provide paid services and manage transactions.

Communicating With Users

We may send:

  • account notifications;

  • Service notifications;

  • security alerts;

  • billing communications;

  • subscription information;

  • customer support responses;

  • important product updates; and

  • marketing communications where legally permitted.

Complying With Legal Requirements

We may process limited information where reasonably necessary to comply with:

  • applicable law;

  • valid legal process;

  • regulatory obligations;

  • enforceable government requests; or

  • the establishment, exercise, or defence of legal claims.

11. ARTIFICIAL INTELLIGENCE PROCESSING

HyberX uses artificial intelligence technology to understand permitted software context and generate contextual software guidance.

AI processing may be used to:

  • interpret relevant workflow state;

  • understand errors;

  • identify possible next actions;

  • adapt explanations to the active context; and

  • provide real-time guidance.

HyberX may use proprietary technology and authorized third-party artificial intelligence infrastructure to provide applicable functionality.

Where external infrastructure is used, HyberX seeks to transmit only information reasonably necessary to perform the applicable AI processing request.

12. NO AI TRAINING USING PRIVATE USER DATA

HyberX does not use private user Screen and Workflow Context to train artificial intelligence models.

HyberX does not use private session information to train general-purpose AI models.

HyberX does not use credentials, authentication secrets, visible private project data, or private technical workflows to create artificial intelligence training datasets.

HyberX does not sell or license private user information to third parties for AI model training.

HyberX does not intentionally contribute private Screen and Workflow Context to publicly available artificial intelligence training datasets.

Where third-party artificial intelligence infrastructure providers process information on behalf of HyberX, HyberX seeks to use contractual and technical arrangements that prohibit such providers from independently using private HyberX user content for model training.

HyberX may improve its product using:

  • aggregated product information;

  • de-identified information;

  • statistical information;

  • application performance information;

  • voluntarily submitted product feedback; and

  • technical data that does not reasonably reconstruct a user's private Screen and Workflow Context.

Private user Screen and Workflow Context is not retained for AI model training.

13. HYBERX IS AN ASSISTIVE GUIDANCE SYSTEM

HyberX provides AI-generated software and technical guidance.

Artificial intelligence systems may occasionally produce information that is:

  • incomplete;

  • inaccurate;

  • outdated;

  • technically inappropriate for a specific environment; or

  • different from an organization's internal procedures.

Users remain responsible for reviewing technical actions before implementing them.

Users should exercise particular care before performing actions involving:

  • production systems;

  • cloud infrastructure;

  • network configurations;

  • data deletion;

  • access control;

  • security controls;

  • database operations;

  • deployment environments; or

  • other critical technical systems.

HyberX is designed to assist users.

HyberX is not designed to replace professional judgment, internal security processes, organizational change controls, or technical authorization procedures.

14. OUR ROLE WHEN ORGANIZATIONS USE HYBERX

HyberX may process information in different legal capacities depending on the relevant product and customer relationship.

Information Managed Directly by HyberX

For information such as:

  • HyberX account information;

  • subscription information;

  • website information;

  • HyberX security information;

  • product analytics; and

  • direct communications with HyberX,

HyberX may determine the purposes and means of processing.

Customer-Controlled Information

When an employer, MSP, IT service provider, enterprise customer, school, or other organization provides HyberX to users and determines the purpose for which HyberX is used, the organization may be responsible for certain personal information processed within its environment.

In such circumstances, HyberX may act as a service provider or data processor acting on the organization's instructions.

Organizational customers are responsible for:

  • ensuring that they are authorized to use HyberX;

  • providing required privacy notices;

  • obtaining applicable permissions or consent;

  • managing user access;

  • configuring HyberX appropriately;

  • preventing unauthorized processing of third-party information; and

  • complying with applicable privacy and employment requirements.

Enterprise customers may enter into a Data Processing Agreement with HyberX where appropriate.

Privacy requests concerning customer-controlled information may need to be directed to the organization responsible for the relevant HyberX workspace.

15. DATA MINIMIZATION

HyberX follows a data minimization approach.

Our objective is to process the minimum information reasonably necessary to provide contextual software guidance and operate the Service.

We seek to:

  • limit Screen and Workflow Context to the active session;

  • minimize persistent storage;

  • use temporary memory-based processing for contextual data;

  • avoid maintaining historical screen archives;

  • protect sensitive information appearing within context;

  • collect minimal host and device information;

  • restrict information access;

  • reduce unnecessary data duplication;

  • limit provider access to required functions; and

  • delete information when it is no longer required for its defined purpose.

The fact that artificial intelligence technology may technically be capable of interpreting extensive context does not mean HyberX intends to permanently collect or retain that context.

16. DATA RETENTION

HyberX applies purpose-limited data retention practices.

Retention depends on the type of information involved.

Screen and Workflow Context

Screen and Workflow Context is processed during the active HyberX session.

HyberX does not intentionally persistently retain Screen and Workflow Context after the applicable session or temporary processing environment terminates.

Temporary session context maintained within RAM or another active temporary processing environment is designed to be deleted, released, or otherwise removed following session termination.

HyberX does not maintain permanent server-side backups of Screen and Workflow Context.

Sensitive Information Within Screen Context

Credentials, authentication secrets, API keys, passwords, private keys, or other security-sensitive information appearing within Screen and Workflow Context are not intentionally retained as permanent HyberX customer records.

Such information remains subject to the temporary session processing and deletion architecture applicable to Screen and Workflow Context.

AI Training Data

Private Screen and Workflow Context is not retained for artificial intelligence model training.

Product Analytics

Limited analytics may be retained for a reasonable period necessary to understand general product performance and usage.

HyberX does not use analytics retention to create a historical screen archive.

Crash, Error, and Diagnostic Information

Limited crash reports, application errors, bug reports, and diagnostic information may be retained for a reasonable period necessary to:

  • investigate software failures;

  • repair defects;

  • maintain Service reliability;

  • investigate security incidents; or

  • comply with applicable legal obligations.

Where reasonably possible, diagnostic information is minimized, aggregated, or de-identified.

Account Information

Account information may be retained while the user's account remains active and for a limited period after account closure where reasonably necessary for:

  • account administration;

  • security;

  • fraud prevention;

  • dispute resolution; or

  • legal compliance.

Billing Information

Billing and transaction records may be retained as required under applicable accounting, tax, financial, and legal requirements.

Support Records

Support records may be retained for a reasonable period necessary to resolve technical issues, maintain support history, investigate disputes, or protect the Service.

When information is no longer reasonably required, HyberX may delete, destroy, aggregate, or appropriately de-identify the information.

17. SECURITY

HyberX uses administrative, technical, and organizational safeguards designed to protect information against:

  • unauthorized access;

  • unauthorized disclosure;

  • accidental loss;

  • misuse;

  • alteration; and

  • destruction.

Depending on the applicable system and processing environment, safeguards may include:

  • encryption in transit;

  • encryption of applicable sensitive information;

  • sensitive-data protection controls;

  • access controls;

  • authentication controls;

  • temporary memory-based contextual processing;

  • limited data retention;

  • environment isolation;

  • infrastructure monitoring;

  • security logging;

  • least-privilege access practices;

  • vendor security management; and

  • security incident response procedures.

HyberX's security architecture is designed to reduce the amount of private contextual information available within persistent infrastructure.

Reducing unnecessary data retention is itself part of our security strategy.

No internet-connected system or security technology can guarantee absolute security.

Users are responsible for protecting their account credentials and should immediately notify HyberX if they believe their account has been compromised.

18. SECURITY INCIDENTS AND DATA BREACHES

If HyberX becomes aware of a security incident involving information under our control, we will investigate the matter and take reasonable steps to:

  • contain the incident;

  • assess the nature and scope of the incident;

  • mitigate applicable risks;

  • remediate security weaknesses; and

  • prevent similar incidents where reasonably possible.

Where required by applicable law, HyberX will notify affected individuals, organizational customers, privacy regulators, or other authorities.

Where HyberX processes information on behalf of an organizational customer, we will communicate relevant security incidents in accordance with applicable contractual and legal requirements.

HyberX may maintain legally required records relating to security incidents and privacy breaches.

19. WHEN WE DISCLOSE INFORMATION

HyberX does not indiscriminately disclose user information.

We may disclose limited information in the following circumstances.

Service Providers

We may engage service providers that assist with:

  • cloud infrastructure;

  • AI processing infrastructure;

  • authentication;

  • database services;

  • application monitoring;

  • security;

  • analytics;

  • customer support;

  • email delivery;

  • payment processing; and

  • subscription management.

Service providers are permitted to process information only as reasonably necessary to perform applicable services and subject to applicable contractual, security, and confidentiality requirements.

Organizational Customers

Where a user's account is provided through an organization, authorized administrators may have access to limited account and workspace administration information.

HyberX does not provide administrators with permanent historical Screen and Workflow Context because HyberX does not intentionally maintain such an archive.

Legal Requirements

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

  • comply with applicable law;

  • respond to valid legal process;

  • comply with an enforceable government request;

  • investigate fraud or abuse;

  • protect HyberX or its users;

  • address an immediate security threat; or

  • establish, exercise, or defend legal claims.

HyberX does not voluntarily provide governments or law enforcement agencies with unrestricted access to user information.

Business Transactions

Limited information may be transferred in connection with:

  • a merger;

  • acquisition;

  • financing transaction;

  • corporate restructuring;

  • asset sale; or

  • similar business transaction.

Where applicable, we will take reasonable steps to preserve appropriate privacy and confidentiality protections.

20. WE DO NOT SELL PERSONAL INFORMATION

HyberX does not sell personal information for monetary consideration.

HyberX does not sell Screen and Workflow Context.

HyberX does not sell credentials or technical workflow information.

HyberX does not sell private user information to data brokers.

HyberX does not use Screen and Workflow Context for cross-context behavioural advertising.

HyberX does not create advertising profiles based on:

  • terminal activity;

  • technical errors;

  • visible software activity;

  • support tickets;

  • deployment workflows; or

  • system administration activity.

Where applicable privacy laws define “sale” or “sharing” differently, HyberX does not intend to sell or share personal information for cross-context behavioural advertising.

21. SENSITIVE PERSONAL INFORMATION

HyberX does not require highly sensitive personal information for ordinary software guidance.

However, information visible within an active technical environment may incidentally include sensitive information.

Depending on applicable law, sensitive information may include:

  • passwords;

  • authentication credentials;

  • financial account information;

  • health information;

  • biometric information;

  • precise location information;

  • government identifiers;

  • racial or ethnic information;

  • religious information;

  • sexual orientation information; and

  • other legally protected information.

HyberX does not use such information to create sensitive characteristic profiles.

Where sensitive information incidentally appears within Screen and Workflow Context, it remains subject to HyberX's temporary contextual processing, security protection, and session termination architecture.

Users and organizations should minimize the unnecessary display of highly sensitive information during technical workflows.

22. INTERNATIONAL DATA PROCESSING

HyberX provides online services and may use authorized infrastructure providers operating in different jurisdictions.

Limited Service Information may therefore be processed in Canada, the United States, or other jurisdictions in which HyberX or its authorized providers maintain infrastructure.

Privacy and government access laws may differ between jurisdictions.

Where required under applicable law, HyberX uses appropriate contractual or legal mechanisms for international data processing and transfers.

For transfers governed by European data protection requirements, applicable mechanisms may include:

  • adequacy decisions;

  • Standard Contractual Clauses; or

  • other legally recognized transfer mechanisms.

HyberX's zero-persistent-storage model for Screen and Workflow Context is designed to reduce long-term retention of contextual information regardless of the applicable processing environment.

23. COOKIES AND SIMILAR TECHNOLOGIES

The HyberX website or web-based services may use cookies, local storage, and similar technologies to:

  • maintain user login sessions;

  • authenticate users;

  • protect account security;

  • remember user preferences;

  • understand website performance;

  • measure basic product usage; and

  • improve user experience.

Some technologies are necessary for HyberX to operate.

Where legally required, non-essential cookies or similar technologies will be subject to applicable consent controls.

Users may be able to restrict cookies through browser settings.

Disabling required cookies may affect Service functionality.

24. MARKETING COMMUNICATIONS

HyberX may send promotional or product-related communications where permitted by applicable law.

Users may opt out of promotional emails using the unsubscribe mechanism included in applicable communications.

HyberX may retain limited suppression information necessary to ensure that an unsubscribe request continues to be respected.

Opting out of marketing communications does not prevent HyberX from sending essential communications relating to:

  • account security;

  • billing;

  • subscriptions;

  • customer support;

  • Service operation; or

  • material product changes.

25. YOUR PRIVACY RIGHTS

Depending on the user's location and applicable law, individuals may have rights to:

  • request information about the processing of personal information;

  • access personal information held by HyberX;

  • request correction of inaccurate information;

  • request deletion of eligible personal information;

  • withdraw consent where processing is based on consent;

  • object to certain processing;

  • request restriction of eligible processing;

  • request portability of eligible information;

  • request information concerning categories of personal information processed;

  • request information concerning categories of recipients;

  • opt out of the sale or sharing of information where applicable; and

  • lodge a complaint with an applicable privacy or data protection authority.

Privacy rights are not absolute and may be subject to applicable legal exceptions.

To submit a privacy request, contact:

privacy@hyberx.ai

HyberX may need to verify the identity of the requester before providing access to, correcting, or deleting information.

HyberX will not unlawfully discriminate against a user for exercising an applicable privacy right.

Because HyberX does not intentionally permanently retain Screen and Workflow Context after session termination, HyberX may not possess historical Screen and Workflow Context in response to a later access request.

26. THIRD-PARTY AND CUSTOMER INFORMATION

Developers, system administrators, MSPs, IT support professionals, and technical teams may work with information relating to customers, employees, vendors, or other third parties.

Users must not intentionally use HyberX to process information that they are not legally or contractually authorized to access.

For example, an MSP or IT support provider should only expose customer information to an active HyberX workflow where that provider is authorized to process the information for the applicable technical support purpose.

Organizations are responsible for determining whether their use of HyberX is appropriate for a particular environment.

HyberX may restrict or suspend use of the Service where we reasonably believe the Service is being used to unlawfully access, expose, or process third-party information.

27. DATA REQUESTS RELATING TO SCREEN AND WORKFLOW CONTEXT

Because HyberX does not intentionally maintain a permanent historical Screen and Workflow Context archive, HyberX generally cannot retrieve previous screen context after the applicable session and temporary processing environment have terminated.

HyberX cannot provide a user with historical screen recordings that HyberX does not possess.

HyberX cannot restore deleted temporary session context where that context has been terminated in accordance with the architecture described in this Privacy Policy.

This zero-persistent-storage architecture is intentional and forms part of HyberX's security and privacy design.

28. CHANGES TO THIS PRIVACY POLICY

HyberX may update this Privacy Policy as:

  • our products evolve;

  • our technology changes;

  • our security architecture changes;

  • applicable legal requirements evolve; or

  • we introduce new functionality.

Where we make material changes, we may provide notice through:

  • the HyberX website;

  • the HyberX application;

  • email; or

  • another appropriate communication method.

The “Last Updated” date at the beginning of this Privacy Policy identifies the date of the most recent revision.

Where required by law, HyberX will obtain appropriate consent before materially changing the purpose for which previously collected personal information is used.

29. CONTACT HYBERX

Questions, privacy requests, complaints, or concerns regarding this Privacy Policy may be directed to:

HyberX Privacy Team
Email: privacy@hyberx.ai
Website: hyberx.ai

Legal Operating Entity: [INSERT HYBERX LEGAL ENTITY NAME]

Registered Business Address: [INSERT REGISTERED BUSINESS ADDRESS]

Please include “Privacy Request” in the subject line when contacting HyberX concerning personal information or privacy rights.

HyberX will review privacy concerns and respond in accordance with applicable legal requirements.

30. PRIVACY BY ARCHITECTURE

HyberX exists to help people work through complex software without constantly stopping, searching documentation, switching between AI tools, manually uploading screenshots, or repeatedly explaining what is happening within their software environment.

Understanding context is fundamental to that experience.

However, contextual understanding should not require permanent surveillance.

HyberX is therefore designed around:

  • real-time contextual processing;

  • temporary memory-based session handling;

  • RAM-based processing of active contextual information;

  • encryption and security controls for sensitive information;

  • protection of visible credentials and secrets;

  • zero persistent storage of Screen and Workflow Context after session termination;

  • no permanent server-side Screen and Workflow Context archive;

  • no backup copies of terminated Screen and Workflow Context;

  • no use of private user data for artificial intelligence model training;

  • minimal device and host information collection;

  • limited product analytics;

  • limited crash and diagnostic information;

  • purpose-specific data processing; and

  • data minimization.

HyberX's objective is not to create a historical record of how a user works.

Our objective is to understand the minimum context necessary to help the user during the active task.

The fact that an AI can understand more context does not mean it should permanently keep more context.

HyberX is designed to see what is necessary to help in the moment—not to remember everything a user has done.