Skip to content
Nexscope

SECURITY

Protecting accounts, data and ecommerce workflows.

Nexscope uses technical and organizational safeguards designed to protect the personal information it processes. This page summarizes published practices and explains how to report a potential security issue privately.

Published security practices

Nexscope's Privacy Policy identifies the following safeguards. Their implementation and scope may evolve with the service.

Encryption

Encryption of data in transit and at rest.

Assessment

Regular security assessments and penetration testing.

Access controls

Access controls and authentication mechanisms.

People and process

Employee training on data protection.

No absolute-security claim

No internet transmission or storage system can be guaranteed to be completely secure. The Privacy Policy is the source of truth for Nexscope's current published data-security statement.

Protect credentials when using Nexscope

  • Enter API keys only in the intended Nexscope product or documented client configuration. Do not paste them into public issues, discussions, screenshots or articles.
  • Redact bearer tokens, cookies, authorization headers, payment details and private customer data before sharing a request or error example.
  • Treat a key as compromised if it was exposed. Revoke or rotate it through the appropriate account controls before continuing.
  • Connected selling-partner authorization uses the supported authorization flow; Nexscope does not request or store a selling partner's Seller Central username or password.

Report a potential vulnerability

Email service@nexscope.ai with the subject “Nexscope security report.” Do not disclose an unpatched issue in a public GitHub issue or community discussion.

Include enough information to reproduce the issue

  1. The affected Nexscope domain, page, API endpoint or feature.
  2. Clear reproduction steps and the observed security impact.
  3. Relevant timestamps, request identifiers and redacted evidence.
  4. A safe way for the Nexscope team to contact you.

Keep the report safe

Do not include passwords, live API keys, session tokens, payment data, unnecessary personal information or another user's private data. If sensitive evidence is required, first ask the team to arrange an appropriate transfer method.

Scope of this page

This is a public security overview, not a certification report, penetration-test result, bug-bounty promise or service-level agreement. Nexscope does not claim a security certification here unless an official current document is linked explicitly.