Privacy Policy

How NoeVault handles platform and user data.

NoeVault may collect account details, organization information, authentication metadata, session activity, IP address, browser/device information, audit logs, operational logs, uploaded files, support communications, community interactions, licensing activity, payment-related metadata, deployment records, and integration metadata needed to operate and secure the platform.

NoeVault uses collected information to provide authentication, access control, organization management, application onboarding, deployment operations, support workflows, licensing enforcement, payment processing support, security monitoring, audit tracking, troubleshooting, notifications, platform improvement, and operational governance.

NoeVault uses permission-based access, role-based controls, session validation, scoped organization and solution access, restricted administrative operations, audit logging, and authenticated API communication to help protect platform resources and organizational data.

NoeVault may work with third-party services such as payment processors, cloud hosting providers, identity providers, email services, monitoring tools, storage providers, deployment infrastructure, and external APIs. These providers may process limited data needed to perform their services.

NoeVault may retain audit records, operational logs, support tickets, deployment metadata, notification records, community content, uploaded files, and platform activity records for security, troubleshooting, compliance, operational continuity, and governance. Retention periods may vary by organization settings and platform requirements.

Organizations are responsible for managing their own users, permissions, uploaded content, application configurations, deployment decisions, compliance obligations, internal policies, and data handling requirements. NoeVault provides tools to support governance, but each organization remains responsible for how those tools are configured and used.

NoeVault is currently evolving through an early production and platform expansion phase. Features, integrations, policies, data handling practices, and operational safeguards may be refined as the platform matures. Updated privacy information may be published through platform notices, release notes, or policy pages.