Node Vertex Privacy Policy

Information we process

• Account and contact information such as name, email, company, tenant slug, and support requests.
• Authentication and security data such as passkey registrations, hashed tokens, signed-link metadata, IP addresses, user agents, and audit events.
• Vertex metadata such as tenant slug, vertex key, type, access mode, lifecycle settings, timestamps, request counts, and policy configuration.
• Content that you intentionally store, upload, post, append, or expose through vertices, including files, forms, messages, app routing metadata, and workflow payloads.
• Operational telemetry such as errors, latency, request volume, abuse signals, and service health.

How we use information

We use information to provide Node Vertex, route requests, enforce policy, authenticate users, generate audit evidence, support customers, protect the service from abuse, troubleshoot incidents, and improve product reliability.

Data handling

Node Vertex is a governed communication fabric. Customers control what they store in vertices and should not place regulated or highly sensitive data in a vertex unless their tenant agreement, configuration, retention policy, and security controls support that use case.

Secrets and bearer tokens are stored as hashes where supported. Private keys and raw bearer tokens should never be sent to support or embedded in public content.

Sharing

We do not sell personal information. We may share information with infrastructure, email, analytics, security, and support providers that help operate Node Vertex, or when required by law, abuse response, security investigation, or a customer-directed integration.

Security, abuse, and contact

Report security issues, abuse, privacy requests, or support needs through the contact path on the Security and Trust page or through your account administrator.