Privacy | Naradox

Controller and contact

Naradox is the service name used for naradox.com and the customer portal and is responsible for personal data processed through those services. The contracting legal entity, when applicable, is identified in the customer's quote, order, invoice, or separate agreement. Email privacy questions or rights requests directly to support@naradox.com with the subject "Privacy request".

Data Naradox processes

business contact and account data, including name, work email, customer organization, role, membership, password hashes and other authentication state, MFA state, invitations, and account-security activity; server-side portal session records contain an account reference and, only for customer sessions, a customer reference. They also contain a keyed SHA-256 digest of the opaque cookie identifier, the session-version and MFA-assurance state, and creation, last-activity, absolute-expiry, and revocation timestamps; Naradox does not store the raw session cookie identifier
public commercial, security-questionnaire, and migration intake data, including company, environment size, frameworks, review scope, platform, rollout constraints, timeline, and the description submitted by the requester
software and support entitlements, deployment labels, licensed-user capacity, downloads, release visibility, license issuances, and legal-policy acceptance evidence
billing and transaction records, including Stripe customer, Checkout, subscription, subscription-item, invoice, charge, refund, and dispute identifiers and their status; when the configured Stripe Tax mode is used, Stripe also collects and processes the billing contact name, billing address, and business tax identifier needed for tax calculation and invoicing; the Naradox portal database does not retain full payment-card or bank-account credentials, billing addresses, or tax identifiers
Requests, replies, status, environment, impact, timestamps, and customer-provided support attachments
private customer Documents, such as contracts, quotes, invoices, DPAs, order confirmations, and any file or metadata submitted for that vault
email and portal communications, including recipient, subject, message body, delivery status, attempts, error category, and related notification or renewal history
audit events, rate-limit records, keyed network-abuse signals, request identifiers, browser or user-agent metadata, and other operational information used to secure and troubleshoot the portal

Where data comes from

Most information is provided directly by the individual or the individual's organization through a form, account, Request, upload, or customer administrator. Naradox administrators add entitlement, document, support, and operational records; Stripe supplies payment and subscription events and identifiers; and the site generates security, audit, request, and delivery metadata when it is used.

Why the data is used

to assess public enquiries and follow up with the named business contact
to create accounts, sign users in, enforce account and MFA controls, manage members, and prevent misuse
to issue licenses, expose authorized downloads and Documents, and maintain release-delivery evidence
to create and administer subscriptions, tax calculation, invoices, refunds, disputes, renewals, and other billing actions through Stripe
to deliver transactional email and manage Requests, attachments, status updates, and follow-up communication
to keep evidence of accepted Terms, entitlement and billing changes, security events, and administrative actions
to investigate suspicious activity, service abuse, operational incidents, disputes, or legal requests

Legal bases

Depending on the context, Naradox processes personal data to take requested pre-contract steps, perform an agreement, meet accounting or other legal obligations, and protect legitimate security, fraud-prevention, service-operation, and dispute-resolution interests. Naradox relies on consent only where the specific processing requires consent; portal use and necessary transactional communication do not depend on marketing consent.

What stays local to Naradox

Naradox remains an offline-first product. Running deployments do not need a live connection to Naradox in order to validate already issued license materials.

the portal is not a runtime SaaS control plane
license verification happens inside the deployed product
customers decide what diagnostics, logs, screenshots, or configuration details they share during support

Naradox may provide only the data needed to service providers that operate hosting, private file storage, email delivery, payment, identity, monitoring, and security functions. Stripe handles Checkout, payment-method collection, subscriptions, tax-mode billing details, invoices, refunds, and disputes. Those providers process data under their own service terms and applicable data-protection commitments. Naradox does not sell personal data or share it for cross-context behavioural advertising.

International transfers

Naradox will use personal data in the regions where Naradox or its service providers operate. Where a transfer requires a legal safeguard, Naradox will rely on an applicable adequacy decision, approved contractual safeguards, or another transfer mechanism permitted by applicable privacy law.

Retention

Access is limited to people and providers that operate the service, secure it, administer billing, or serve the customer. Current portal defaults and criteria are:

rate-limit signals become eligible for routine deletion after 48 hours; ordinary audit events after 365 days; and bounded download-delivery audit copies after 2,555 days, subject to the configured cleanup process
terminal portal session records that are revoked or expired, expired or consumed one-time download-grant records, and used or expired password-reset and email-verification token records become eligible for deletion after 24 hours
an invitation email body containing its link is scrubbed after 8 days; other outgoing email bodies and last delivery errors are redacted after 90 days; terminal email records and accepted, revoked, or expired invitation records become eligible for deletion after 365 days
immutable release-download evidence, legal acceptances, entitlements, license issuances, orders, and invoice and transaction references are retained for the customer relationship and afterwards while needed for licensing, accounting, security, legal claims, or dispute evidence
Requests, Documents, and their attachments use purpose-based rather than fixed automatic retention: they remain while the customer relationship, open request, customer-visible record, or required evidence needs them. In the portal, an authorized customer user can delete only that user's eligible follow-up comments on an open Request. Requests to remove other Request content, attachments, Documents, or account data are handled through the privacy-request contact above and are carried out only to the extent the processing purpose has ended and licensing, security, accounting, legal-claim, dispute-evidence, or other applicable legal requirements permit deletion
customer agreements may define a stricter retention, deletion, export, or handling requirement; configured operational periods may also change when a binding requirement calls for it

Rights and choices

Individuals may request access, correction, deletion, export, objection, restriction, or withdrawal of a specific consent where applicable law provides those rights, and may complain to their competent data-protection authority. Send a request to support@naradox.com. Naradox may need to verify the requester and may retain records where licensing, security, accounting, legal-claim, or dispute obligations override deletion.

How Naradox handles website, portal, billing, and support data.