Privacy

Reference evidence review stays in your browser

At /review, the ZIP and separate trust JSON you select are read in this browser tab to run the checks. They are not uploaded to Nikxius or stored by the website. Clear the review or close the tab to discard the page’s in-memory review state. Reports you choose to download are saved to your device.

The payment evidence reviewer requires no account and runs no analytics. The payment sandbox console also runs no analytics. Its displayed records are demonstration data. These remain separate reference examples from Nikxius Runtime.

Opening these pages and loading their application assets still makes requests to our hosting service. The host receives standard HTTP request information, including IP address, request time, path and browser information, to serve and operate the website. Local file review does not mean that visiting the website involves no network requests.

The public demonstration

The assurance demo replays fixed synthetic loan-servicing results. Review choices select synthetic sample reports; they do not create a real approval. The public demo does not call an external model, connect to your infrastructure or accept uploaded evidence. Historical Runtime and payment examples remain separate reference tools.

The current public website does not enable the legacy payment certificate issuer or private execution APIs. The separate payment reviewer and sandbox remain historical reference pages.

Optional website analytics

Public marketing and research pages use Google Analytics 4 only after you select Allow analytics. Before that choice, or when you decline, these pages do not load Google analytics tags. Analytics is not used on the evidence reviewer or sandbox console.

When enabled, Google Analytics receives fixed page and event labels, coarse device class, validated campaign labels and the selected current-solution category when you choose to provide it. We also retain the same consented events in a first-party store so we can inspect the funnel. This store uses random visitor and session identifiers, not fingerprinting. The visitor identifier expires after 90 days. We do not send email addresses, companies, free-text form answers, evidence files, sample labels, full query strings or confidential infrastructure content to analytics.

To keep the source of an enquiry through navigation, this tab retains validated campaign labels, the landing-page path and referring hostname for a 30-minute session. Referrer paths and query strings are discarded. Form submissions retain that attribution even if optional analytics is declined. Campaign labels should never contain personal information. Counts cover received, consented events and can miss visitors who decline analytics or block requests.

Your analytics choice is stored locally in this browser for 180 days. You can change it using Analytics settings on marketing pages. Declining analytics does not prevent you from using the website.

Evaluation enquiries and historical forms

The evaluation form stores your work email, organization and role, optional system/review/current-process categories, source attribution, consent and receipt in the private website store. We use these to understand and respond to your enquiry. An answer that your current process works well is retained as negative evidence; a submission does not establish demand, budget or a purchase commitment.

When you submit a form, we store your email, optional waitlist details or required action-enquiry answers, source attribution, receipt and timestamp in our private website store. We use them to assess the workflow, respond to an enquiry or tell waitlist members about availability as requested. A waitlist signup is an expression of interest, not a reservation, a verified identity or a customer relationship. We do not verify ownership of email addresses in this flow.

The public waitlist number, when enabled, counts unique persisted email entries that are not tests or unsubscribed. It exposes no emails, companies or answers. A technical-session request records intent; it is not a confirmed booking. Nothing in these forms grants access to your infrastructure or authorizes a payment.

Please provide a nonconfidential summary. Do not submit passwords, API keys, customer records, manifests or other secrets. We use server validation, duplicate suppression, a hidden spam field and per-IP request limits. Rate-limit addresses remain in process memory and are not stored in demand or analytics records.

Ask founder@nikxius.com to leave the list or request access, correction or deletion. We retain enquiries while they are relevant to follow-up, with periodic review of inactive records; there is no automated deletion schedule today. Analytics settings controls future analytics collection, not removal of an enquiry you explicitly submitted.

Contact and retention

If you email us, your message passes through email providers and reaches our business inbox. We use your contact details and message to respond, understand the enquiry, and assess a potential technical evaluation. An email enquiry does not subscribe you to a newsletter.

Retention of correspondence and operational records depends on the purpose for which they are needed and applicable requirements. Do not email credentials, customer records, production manifests or private evidence.

To ask about your information, or request access, correction or deletion, contact Nikxius at the address below. Applicable rights and any limits depend on the law and the circumstances of the request.