Terms of Service

1. Acceptance of Terms

By creating an account, authenticating through NSGO, or utilizing any services provided across the NS ecosystem (including go.naborajs.me and associated developer utilities), you agree to be bound by these Terms of Service. If you do not agree with any part of these terms, you must not access or use the platform.

2. Central Account Identity & Handles

NSGO serves as your unified central identity. Each user is assigned a stable public identifier (NSGO ID) and may select a unique public handle.

• Handles are registered on a first-come, first-served basis, subject to system reservation policies.
• Impersonation of real individuals, organizations, or official NS administration is strictly prohibited and subject to immediate account revocation.
• Handle changes are rate-limited to maintain cryptographic integrity and cross-service security (7-day database cooldown).

3. Data Protection & Zero-Trust Token Isolation

We implement strict isolation between authentication credentials and external applications. The NSGO IP Logger and any third-party developer integrations maintain entirely distinct, segregated database schemas. Your authentication tokens, passwords, and sensitive credentials are never accessible by external telemetry tools. For details regarding data collection and cryptographic safeguards, see our Privacy Policy.

4. Acceptable Use & Account Lifecycle

You retain full ownership of your user profile and developer metadata. You may deactivate your account temporarily or request complete, irreversible deletion through your account settings.

Any intentional exploitation of NS APIs, DDoS attempts, unauthorized automated scraping, or security evasion will result in immediate suspension without prior notice.

5. Developer & OAuth Client Responsibilities

Developers integrating NSGO Single Sign-On into third-party services must adhere to OAuth 2.1 specifications:

• Confidential client secrets must never be embedded in public client code or mobile applications.
• All callback endpoints must utilize exact registered redirect URIs and enforce HTTPS in production.
• Applications must only request scopes necessary to support verified application features.
• Developers must respect user token revocation and purge associated local session data when notified.