Privacy Policy
Last updated: July 14, 2026
This Privacy Policy explains how OXU Guard handles information when users connect sources, monitor events, review detections, and use response actions.
OXU Guard is designed to support security monitoring while helping organizations keep access, event data, and response workflows controlled.
1. Information OXU Guard may process
OXU Guard may process information provided through connected sources and user activity inside the product.
This may include:
User account information, such as name, email address, role, and workspace access.
Source configuration information, such as source name, description, source ID, and integration status.
Security and activity events sent from connected systems.
Event fields, such as actor, source IP, location, device, event time, action, and result.
Detection rules, alerts, response actions, and related configuration.
Product activity logs, such as changes to sources, rules, alerts, or response actions.
OXU Guard may also process technical information required to operate the product, such as request metadata, error logs, and system performance data.
2. How information is used
OXU Guard uses information to provide security monitoring and response workflows.
This includes:
Receiving and processing events from connected sources.
Detecting event fields and schema changes.
Suggesting detection rules with AI assistance.
Generating alerts when active rules match incoming activity.
Displaying statistics, source health, and alert trends.
Running configured response actions, such as email notifications.
Supporting access control, troubleshooting, and product improvement.
OXU Guard does not use customer event data to create active detection rules without user review and approval.
3. AI-assisted features
OXU Guard may use AI-assisted features to help users understand event data, suggest detection rules, explain rule rationale, and identify potential security patterns.
AI-suggested rules are not automatically activated. Users are responsible for reviewing and accepting suggested rules before they become active.
AI output should be treated as decision support, not as a final security decision.
4. Data access and permissions
Access to OXU Guard is controlled by workspace permissions and user roles.
Depending on their role, users may be able to:
View sources, schemas, rules, alerts, response actions, and statistics.
Create or update data sources.
Review and activate detection rules.
Configure response actions.
View alert details and investigation context.
Organizations are responsible for assigning appropriate access to their users.
5. Credentials and integration secrets
OXU Guard may generate or store credentials such as API keys, client secrets, or integration tokens for connected sources.
These credentials are used to authenticate event ingestion or integration requests.
Users should keep credentials secure and avoid sharing them publicly. If a credential may have been exposed, it should be rotated or disabled.
6. Data protection
OXU Guard is designed to protect event data, configuration, and credentials using appropriate security controls.
These may include:
Secure transmission for event ingestion and product access.
Protected storage for sensitive integration information.
Role-based access control.
Activity tracking for important product changes.
Separation of access based on workspace or organization configuration.
7. Data retention
Event data, alerts, configuration, and activity history may be retained according to the organization’s product configuration, workspace settings, or applicable agreement.
Retention periods may vary based on product plan, storage quota, operational requirements, and legal or compliance needs.
8. Response actions and notifications
OXU Guard may send notifications based on configured response actions.
For example, when an alert is triggered, OXU Guard may send an email notification to a security admin, IT admin, or affected user, depending on the configured action.
Notification content may include alert details such as source, severity, rule name, event time, actor, and relevant event context.
9. User responsibilities
Users and organizations are responsible for:
Connecting only authorized data sources.
Ensuring event data is sent in accordance with internal policies and applicable laws.
Assigning appropriate user permissions.
Reviewing AI-suggested rules before activation.
Protecting integration credentials.
Configuring response actions responsibly.
10. Changes to this policy
This Privacy Policy may be updated from time to time to reflect product changes, legal requirements, or operational improvements.
When updates are made, the “Last updated” date will be revised.
11. Contact
For privacy-related questions, contact your organization administrator or the OXU Guard support team.