Privacy policy

Scope and roles

This Policy applies when AuraOne processes personal information as a controller for websites, documentation, marketing, recruiting, and business operations, and as a processor when providing Services on behalf of enterprise customers.

Customer organizations control the personal data processed in their AuraOne environments. Customer agreements and applicable data-processing terms govern that relationship.

Information we collect

The information collected depends on the product, relationship, customer configuration, and way a person interacts with AuraOne.

• Account and contact information, including name, email, company, job title, and authentication information.
• Usage and telemetry information, including feature events, performance information, and error records.
• Support information, including ticket content, communications, and troubleshooting records.
• Technical information, including IP address, browser, device, and security logs.
• Billing contact and transaction information processed with payment providers.

How we use information

• Provide and operate the websites, products, and services.
• Secure accounts, systems, and workflows and investigate suspected misuse.
• Support users and diagnose product or deployment issues.
• Improve products and understand aggregate usage.
• Meet legal, contractual, accounting, and administrative obligations.
• Send service and marketing communications where permitted.

Legal bases where GDPR applies

• Contractual necessity where processing is needed to provide the Service.
• Legitimate interests such as security, service improvement, fraud prevention, and administration.
• Legal obligations including tax, accounting, and data-protection duties.
• Consent where the applicable law or processing activity requires it.

Open product and local project boundaries

Open product behavior depends on the current application, edition, user configuration, providers, telemetry settings, and explicit export actions. Documentation alone does not establish that a local, browser, desktop, package, or hosted behavior is available.

Users should review the current product and release record for storage, telemetry, crash reporting, provider keys, exports, and connected services.

Sharing and service providers

AuraOne may share information with service providers, professional advisers, affiliates, authorities where required, and parties involved in a corporate transaction, subject to applicable law and contractual duties.

Customer-specific subprocessors, regions, and transfer terms are handled through the applicable service and procurement review.

Security and retention

AuraOne uses technical and organizational measures designed to protect information. Specific controls, configurations, retention periods, deletion paths, and recovery practices vary by product and deployment.

Open the security page for the current public control boundary.

AI model training and analytics

AuraOne does not use customer data to train general foundation models without express consent. Product analytics and safety research should use the minimum necessary information and the applicable customer, user, and legal permissions.

Customer organizations retain their rights in Customer Data as provided by the governing agreement.

Choices and privacy rights

Depending on location and relationship, individuals may have rights to access, correct, delete, restrict, object, port, or withdraw consent. AuraOne may need to verify identity and may direct a request to the customer that controls the relevant data.

Marketing choices can be changed through the unsubscribe link in the communication or by contacting AuraOne.

Privacy contact

Use the contact form for privacy questions or rights requests. Do not include sensitive identification documents or private customer data until a secure path is established.

Contact the privacy team

Change history