Privacy Policy

Nexoxa ("we", "us", "our") operates the NexoxaBridge website (asteron.nexoxa.com and related domains), account services, and the NexoxaBridge Database & Server Studio desktop application ("Software").

We provide developer platform software — desktop workbench with optional cloud subscriptions for platform features (not ai tokens). Nexoxa is established in India. For the purposes of the EU General Data Protection Regulation ("GDPR"), UK GDPR, India's Digital Personal Data Protection Act, 2023 ("DPDP Act"), and similar laws, Nexoxa is the data controller / Data Fiduciary for personal data processed through our website and account platform.

This policy applies to visitors of our website, registered account holders, and signed-in users of the Software when it communicates with our platform (authentication, billing, and tier-gated features). It does not govern third-party sites you connect to through the Software — those systems have their own policies.

Stored on NexoxaBridge servers (account & platform only)

• First name and last name
• Email address (used as your account identifier)
• Password (stored as a one-way cryptographic hash — we never store plaintext passwords)
• Subscription tier (Free, Pro, Enterprise) and account status
• Authentication session tokens and session expiry
• Workspace membership, invites, roles, and activity summaries for Pro collaboration
• End-to-end encrypted connection blobs and encryption key material for Pro workspace sharing (ciphertext and public keys only — see section 7)
• Account creation date and last activity timestamps
• Support emails and correspondence you send us voluntarily
• Billing status (payment card details are handled by our payment processor — we do not store full card numbers)

Never stored on NexoxaBridge servers in readable (plaintext) form

• Database connection URLs, passwords, ports, or full connection strings — except inside end-to-end encrypted blobs that we cannot decrypt (Pro workspace sharing only; see section 7)
• SSH private keys, SFTP/FTP credentials, or saved-connection secrets from your local vault
• S3 access keys, secret keys, or bucket credentials in plaintext
• SMTP mail credentials or message content
• SQL queries, query results, schema files, or migration scripts (except optional Pro team-pulse metrics and truncated activity metadata — see section 7)
• Copilot conversation history, prompts, or AI context from your databases (Pro/Enterprise; processed via your BYOK key or Enterprise-hosted Copilot — not stored on our platform)
• Knowledge-graph snapshots or FK graph data from your databases (unless you explicitly enable Pro cloud sync)
• File transfer queues, audit logs, or server dashboard telemetry from your infrastructure
• Web analytics and speed-insights events from sites where you install @nexoxa/analytics or @nexoxa/speed-insights — those stay on your server in .nexoxa/ JSONL files (see section 8)
• Contents of your local workspace, saved queries, or UI layout preferences
• RSA private keys used for workspace encryption — these remain on your device only

The NexoxaBridge desktop application is local-first by design. When you save a connection, the Software encrypts the connection string and stores it in your operating system's secure credential vault — not in our cloud.

Account required: You must create an NexoxaBridge account (Free, Pro, or Enterprise) and sign in to use the Software and Platform. There is no anonymous or login-free mode — every tier requires registration and authentication to open the studio, enforce plan limits, and access Copilot and connection features.

What remains local-first: after you sign in, your saved database connection URLs, SSH keys, and local workspace data stay on your device, encrypted in your OS credential vault — not in readable form on our servers. Sign-in verifies your account; it does not upload your production secrets unless you explicitly use Pro collaboration features described in section 7.

Uninstalling the Software removes NexoxaBridge-managed entries from your local credential store. We cannot uninstall or wipe data on your device remotely because we never had your connection data in the first place.

We process personal data only where we have a valid legal basis:

We do not rely on consent as the sole basis for processing that is required to use core account features. Where we ask for consent (e.g. non-essential cookies), you can refuse without losing access to paid features you have already purchased, except where a feature inherently requires that processing.

When you register at asteron.nexoxa.com — required for Free, Pro, and Enterprise — we process:

We use this information solely to authenticate you, enforce plan limits, process payments, provide support, and comply with law. We do not use your email for unrelated advertising without consent.

Free tier: Requires sign-in. After authentication, the studio runs locally. Copilot can use your own API key stored locally. No schema or connection data is uploaded to NexoxaBridge servers.

Pro/Enterprise: Also requires sign-in. May include platform-hosted Copilot (OpenRouter) and knowledge-graph features. In these cases:

• Only data required for the feature is transmitted — e.g. schema metadata or graph summaries you trigger, not your raw connection strings
• Passwords, SSH private keys, and S3/SMTP credentials are never sent to AI providers
• Transmission uses TLS 1.2+ encryption in transit
• You can disconnect from the platform and continue using local-only features

Pro and Enterprise workspaces may invite teammates and optionally share database access or live database metrics. This section describes exactly what is uploaded, what stays encrypted, and what we can and cannot read.

End-to-end encryption model

What we store for collaboration (platform database)

• Workspace name, membership, roles, and invite status
• Collaboration activity log entries you generate (e.g. "connection shared", schema actions synced by teammates)
• Editor change proposals — encrypted JSON (cell edits, SQL, CSV rows, DDL specs). Readable metadata (schema/table names, change type) is stored separately for review UI.
• Encrypted connection blobs (encrypted_payload) — ciphertext only; no readable hostname, username, password, or URL
• RSA public keys and per-member wrapped workspace keys (required for E2E key distribution)

In-app disclosure & consent

Before you create or join a workspace, the Software shows a collaboration data disclosure describing encrypted vs. readable sync. You must accept the disclosure and agree to these Terms and this Privacy Policy (including this section) before collaboration features activate on that device. Consent is stored locally per account; we may ask you to re-accept if the disclosure changes materially.

Team pulse (optional live metrics)

If a connected workspace member publishes team pulse, we may store non-secret metadata in readable form to show teammates a live dashboard:

• Database engine type (e.g. PostgreSQL)
• Database label or name (not your password)
• Hostname or IP address of the connected server (not the full connection URL)
• Aggregate metrics (database size, connection count, table counts, cache hit ratio)
• Optional session snapshots (e.g. active query text, database user name) — only what the publisher's connected session exposes; you control this by staying connected and using live sync

Team pulse does not include your connection password or full connection string. To avoid publishing hostname or query snippets, do not enable live sync or disconnect before teammates view pulse data.

If our platform were breached

An attacker with access only to our database would obtain ciphertext, public keys, and wrapped keys — not usable connection URLs or passwords without also compromising a workspace member's device and unlocking their local private key. This is materially stronger than storing connection strings in plaintext, but no system is risk-free: protect your device, use strong passwords, and rotate credentials if you suspect compromise.

Your controls

• Sharing is opt-in — only workspace owners/editors who choose "Share" upload encrypted blobs
• Remove a shared connection or leave a workspace to stop future access for teammates
• Rotate database passwords at the source if a teammate's device may be compromised
• Free tier does not use workspace connection sharing or team pulse

Platform API & website logs

Our servers may temporarily log:

• IP address and approximate region (derived from IP)
• Browser user agent and request path
• Timestamp and HTTP status code
• Authentication success/failure (without logging your password)

Logs are used for security monitoring, debugging outages, and abuse prevention — not for advertising profiles. Retention is limited (typically 30–90 days unless needed for an incident investigation).

Cookies & local storage

• Strictly necessary: Session tokens for account login and admin authentication
• Functional: Preferences you set on the website (e.g. theme), stored in localStorage on your browser
• We do not use third-party advertising cookies or sell data to brokers

Under the GDPR and ePrivacy rules, strictly necessary cookies do not require consent. For any non-essential cookies we may add in the future, we will request consent via a clear banner before setting them.

@nexoxa/analytics & @nexoxa/speed-insights (self-hosted SDK)

NexoxaBridge ships optional npm packages — @nexoxa/analytics and @nexoxa/speed-insights — that you may install on any website or app you operate — for every SSH deployment in Bridge where that SDK is integrated. This is the default, production-ready integration model:

What the SDK may collect (on your server)

What Nexoxa does not do with SDK data

• We do not receive SDK events on Nexoxa platform servers or any Nexoxa-hosted analytics pipeline
• We do not sell visitor data or share it with ad networks
• We do not fingerprint visitors across unrelated sites
• Bridge does not upload your .nexoxa/ files to our platform by default

Your responsibilities if you install the SDK

If you operate a public website with our SDK, you are typically the data controller for visitor analytics on that site. You should:

• Disclose analytics in your own privacy policy (what you collect, why, retention, and rights)
• Use requireConsent and setAnalyticsConsent() / setSpeedInsightsConsent() with your cookie banner where EU/UK ePrivacy consent is required
• Avoid sending personal data in custom events or URLs (e.g. email in query strings) — paths are sanitized but you control what you pass to track()
• Optionally set NEXOXA_COLLECT_SECRET on your server to reject unsigned POST abuse
• Mount NEXOXA_DATA_DIR in Docker so data survives restarts and Bridge SSH can read it

NexoxaBridge desktop (local dev only)

When developing with Bridge locally, collect routes may also exist on 127.0.0.1:47821 for testing. Production sites should use the SDK + @nexoxa/*/node routes on your deployment, not the developer laptop.

We use trusted service providers ("processors" under GDPR) who process data only on our instructions and under contractual safeguards:

• Cloud hosting and database providers (account data storage)
• Payment processors (billing)
• Email delivery (support and transactional messages)
• AI inference providers for Pro Copilot (prompt/response handling — not your connection vault)

If personal data is transferred outside the European Economic Area (EEA) or UK, we rely on appropriate safeguards such as Standard Contractual Clauses (SCCs), adequacy decisions, or equivalent mechanisms required by GDPR Chapter V.

You may request a list of key subprocessors by emailing [email protected].

If you are in the EEA, UK, or Switzerland (or another jurisdiction with similar laws), you have the following rights regarding your personal data:

• Right of access — obtain a copy of personal data we hold about you
• Right to rectification — correct inaccurate name or email
• Right to erasure ("right to be forgotten") — request deletion of your account data, subject to legal retention obligations
• Right to restriction — ask us to limit processing in certain circumstances
• Right to data portability — receive account data in a structured, machine-readable format
• Right to object — object to processing based on legitimate interests
• Right to withdraw consent — where processing is consent-based, without affecting prior lawful processing
• Right to lodge a complaint with your local supervisory authority (e.g. your national Data Protection Authority in the EU, or the ICO in the UK)

Note: We cannot export or delete data that exists only on your device (connection vault, local queries) because we do not possess it. You control that data through the Software and your OS.

Nexoxa operates from India and serves users worldwide, including Data Principals in India. Where the DPDP Act applies, Nexoxa acts as a Data Fiduciary for account and platform personal data described in this policy (name, email, billing metadata, session tokens, workspace membership, and related records). We do not act as Data Fiduciary for personal data inside databases, servers, mailboxes, or files you access through the Software — you remain responsible for lawful processing of that data.

Lawful processing & consent

We process personal data for specified purposes: providing accounts, authentication, billing, collaboration features you enable, security, and support. Where consent is required, we obtain it through sign-up, checkout, or explicit in-product choices. You may withdraw consent for optional processing by contacting us or deleting your account; withdrawal does not affect prior lawful processing.

Rights of Data Principals (India)

Subject to the DPDP Act and applicable rules, you may have the right to:

• Access information about personal data we process about you and how to exercise your rights
• Correction and completion of inaccurate or incomplete personal data
• Erasure when retention is no longer necessary for the stated purpose or when you withdraw consent (subject to legal retention for tax and billing)
• Grievance redressal — raise concerns about our processing (see below)
• Nominate another individual to exercise your rights in the event of death or incapacity (contact us to register a nominee)

Children

Our services are intended for developers and IT professionals. We do not knowingly process personal data of children in a manner that requires verifiable parental consent under the DPDP Act. If you believe a child has provided us data without appropriate consent, contact [email protected] and we will delete it promptly.

Cross-border transfers

Where personal data is transferred outside India, we implement safeguards required by applicable law, including contractual clauses with processors and limiting transfers to what is necessary to provide the service.

We implement technical and organizational measures appropriate to the risk, including:

• TLS encryption for data in transit to our platform
• Password hashing (scrypt) — passwords are never stored in plaintext
• Access controls and least-privilege for production systems
• Session tokens with expiry for admin and user authentication
• Local AES-256-GCM encryption for credentials in the desktop app
• End-to-end encryption (AES-256-GCM + RSA-OAEP) for Pro workspace shared connections — platform stores ciphertext only
• Regular dependency updates and security monitoring on platform infrastructure

No method of transmission or storage is 100% secure. If you believe your account has been compromised, contact [email protected] immediately. For compromise of your local machine, rotate database passwords and SSH keys at the source — NexoxaBridge cannot do that on your behalf.

Our services are intended for developers and IT professionals aged 16 and over. We do not knowingly collect personal data from children under 16. If you believe a child has provided us data, contact [email protected] and we will delete it promptly.

We do not use automated decision-making or profiling that produces legal or similarly significant effects on you within the meaning of GDPR Article 22. Copilot suggestions in the Software are assistive tools — you decide whether to run any query or migration.

We may update this Privacy Policy to reflect product changes or legal requirements. Material changes will be posted on this page with a revised "Last updated" date. For significant changes affecting existing users, we will provide notice by email or in-app where appropriate. Continued use after the effective date constitutes acknowledgment; if you disagree, you may delete your account.

Privacy and data protection inquiries: [email protected]

See also our Terms of Use for the contractual rules governing the Software and website.