Перейти до вмісту
Редагування збережень сюжетного режиму GTA 6 на PS5 вже доступне.
Legal & Security

Security & Vulnerability Disclosure Policy

How NinjaSaves protects accounts, desktop sessions and console save operations, the strict boundaries prohibiting unauthorized testing or scraping, and how to report an inadvertent security observation.

Останнє оновлення: 2026-11-18

1. Purpose and binding scope

This Security & Vulnerability Disclosure Policy applies to ninjasaves.com, the NinjaSaves Desktop application (Windows, Linux, and macOS), all NinjaSaves APIs, Workers, edge caches, media buckets, console transfer coordinators, and associated save-processing and support systems (collectively, the Service). It forms part of and supplements our Terms of Service.

Machine-readable security contact metadata is published at /.well-known/security.txt in accordance with RFC 9116. Publishing this policy or security.txt is solely to provide a lawful reporting channel for inadvertent observations and to state clear authorization boundaries.

2. No public bug bounty and no implied authorization

NinjaSaves does not operate a public bug bounty program, offers no monetary or account rewards for unsolicited vulnerability reports, and grants no general or implied authorization to test, probe, scan, attack, or reverse-engineer any part of the Service.

Any active security testing, penetration testing, red-teaming, automated scanning, or adversarial research against NinjaSaves requires a prior written engagement signed by an authorized officer of NinjaSaves specifying the exact targets, source IP addresses, and testing window. Without prior signed authorization, active probing is unauthorized access under applicable computer-misuse and anti-circumvention laws.

3. Strictly prohibited conduct (zero safe harbor)

You must never engage in, instruct an automated tool or AI/LLM agent to perform, or assist any third party in performing any of the following against the Service:

  • Decoy, canary, and internal endpoint probing: accessing, querying, or submitting payloads to any path under /api/internal/*, any endpoint referenced in the X-NinjaSaves-Security response header, or any path disallowed in /robots.txt. Those routes include active intrusion-detection tripwires and honeypots. Synthetic prompts, schema hints, or attestation challenges returned by decoy endpoints are deception controls to identify unauthorized automation—they never grant permission, privileges, a contract, or safe harbor.
  • Automated scanning, fuzzing, and agentic attacks: running vulnerability scanners, directory/parameter brute-forcers, GraphQL/RPC enumerators, headless scrapers, LLM/AI autonomous pentest or exploit agents, credential-stuffing tools, OTP or token brute-forcers, or rate-limit bypass tools.
  • Client, binary, and protocol tampering: decompiling, disassembling, unpacking, patching, hooking, debugging to bypass checks, intercepting via MITM proxies, forging device or session signatures, replaying API calls, spoofing console identifiers, or extracting keys, tokens, savepatches, or proprietary save codecs from NinjaSaves Desktop or console transfer sessions (except to the narrow extent mandatory statutory law expressly permits and cannot be waived by contract).
  • Cross-account or unauthorized data access: attempting to view, enumerate, modify, download, or delete any account, session, save file, original backup, private share link, support attachment, or billing record that you do not personally own, including testing “proof of concept” access beyond the minimum needed to recognize an issue existed.
  • Availability, scraping, and social attacks: denial-of-service, volumetric or concurrency exhaustion, automated harvesting of game/cheat catalogues or save listings (including for AI training or competing services), or phishing, impersonating, or pretexting NinjaSaves users, contributors, Discord moderators, or staff.

4. Reporting an inadvertent observation responsibly

If, during ordinary, lawful personal use of NinjaSaves on your own account and devices, you inadvertently observe behavior that appears to be a security or privacy vulnerability:

  • Stop immediately: do not exploit the condition, escalate privileges, modify server state, test against other accounts, download data that is not yours, or run automated scripts to map the behavior.
  • Submit confidentially via our legal intake: file a report through our legal & security contact form (category: Other legal concern, subject prefixed with [Security]), listing the affected URL or app version, timestamp (UTC), and clear textual steps describing what occurred. Do not upload exploit binaries, third-party personal data, or credentials.
  • Maintain confidentiality: allow us a reasonable time to investigate and remediate before publicly discussing the observation, and destroy any incidental diagnostic artifacts containing non-public information once reported.

Where an individual submits a passive, good-faith report of an inadvertent observation in strict compliance with every condition above (without having engaged in any conduct in Section 3), NinjaSaves will not initiate legal action against that individual solely for having observed and reported the issue. This non-enforcement statement applies only to NinjaSaves’ own claims for that compliant report; it is not an authorization for further testing, does not bind third parties, and waives no rights or remedies where Section 3 or our Terms of Service were breached.

5. How NinjaSaves protects the Service

  • Transport and session protection: HTTPS/TLS across web and API traffic, HttpOnly / SameSite=Lax web session cookies, same-origin CSRF enforcement on state-changing routes, Cloudflare Turnstile and multi-tier IP/account rate limits, and OS-protected desktop credential storage (Windows DPAPI, Linux Secret Service, and macOS Keychain—never plaintext password files).
  • Scoped save and backup handling: temporary working saves are scoped to authenticated ownership and expire from active availability (normally around 24 hours). Optional original backups are stored as opaque packages in private storage with per-account quotas and no public media URLs.
  • Payment isolation: card numbers and payment credentials are collected directly by Stripe’s PCI-DSS-compliant payment interface; NinjaSaves never stores full card numbers or CVV codes.
  • Abuse Monitoring & Network Defense: automated intrusion tripwires, server-side deterministic replay checks on NinjaSaves Arcade, console-sharing anomaly detection, and immediate IP, CIDR, ASN, or account blocks for hostile traffic.

6. Customer security responsibilities and enforcement

Download NinjaSaves Desktop exclusively from our official Downloads page, keep your operating system and app updated, use a unique password, and keep private save-share links confidential (anyone with a private share link fragment secret may be able to import that shared snapshot while the link remains active). Contact us immediately via Contact or revoke sessions in Account settings if you suspect unauthorized account access.

Violations of this Policy may result in immediate session revocation, permanent account termination without refund of abused periods to the extent permitted by law, network/ASN blocking, civil claims for damages and injunctive relief, and preservation and referral of logs to competent law-enforcement and computer-crime authorities.