shield
TECHNICAL SPECIFICATION — v2.0.2 SECURITY OVERVIEW Internal engineering/security architecture overview — not an independent certification or third-party security audit. This specification details internal architecture, host data boundaries, transport encryption, and cryptographic hash verification.
SECURITY ARCHITECTURE SPEC: RAM-SNIPER-SEC-v1.0.3 AUDITED BUILD: v1.0.3 (WIN-x64)

v2.0.2 Security Architecture & Data Boundary Overview

Sniper.AI Pro is designed with a defense-in-depth, local-first isolation model. Our engineering priority is simple: guarantee that your enterprise commercial lead intelligence never transits or persists on third-party cloud infrastructure.

laptop_windows

1. Host Process Isolation

The software executes strictly within user-space on the host Windows machine. No elevated kernel-mode drivers or administrative domain rights are required to install or run.

lock

2. Localhost IPC Loopback

The graphical cockpit and background intelligence workers communicate via loopback sockets bound strictly to 127.0.0.1:54321, blocking external network interfaces from probing desktop state.

storage

3. Encrypted Local Storage

Opportunity dossiers, buyer telephone contacts, and targeting criteria are stored locally on your workstation in %LOCALAPPDATA%\SniperAI_Pro, protected by Windows OS file ACLs and BitLocker.

cloud_off

4. Licensing Cloud Separation

Our licensing servers handle commercial activation tokens, version tags, and heartbeat pings only. Customer operational lead data is not uploaded to Sniper.AI's licensing cloud. Core lead processing and operational records remain local to your Windows workstation.

vpn_key

5. Modern Transport Encryption

All external licensing queries take place over encrypted HTTPS/TLS transport with certificate validation, protecting against adversary inspection or man-in-the-middle attacks.

fingerprint

6. Release Binary Integrity

Production binaries are built via deterministic packaging pipelines and published on GitHub Releases with cryptographically verifiable SHA-256 digests.

Cryptographic Release Attestation

v2.0.2 Release Binary SHA-256 Checksums

VERIFIED PRODUCTION
EXE SHA-256 Checksum (Setup Installer) SniperAI_Pro_Setup_v2.0.2.exe
10F0C8166DE314ED3F25807019D934B8D8799FED180E072162F16EEEC4874C2A
ZIP SHA-256 Checksum (Portable Package) SniperAI_Pro_v2.0.2.zip
CE0E81868840BB2EC4002AFD83043BAD39228B59C1BB74D43468E28349CE8240
PDF SHA-256 Checksum (Installation Guide) Client_Installation_Guide.pdf
070E1F3B6FF1139DBD9AA635ED061257F58EE3D42E81A031FD2DD7A6D0556AA2
Verify in PowerShell: Get-FileHash <file> -Algorithm SHA256 • SHA256.txt Manifest
Go to Download Section →

Threat Model & Operational Boundaries

Our security architecture is designed to address enterprise threat vectors common in revenue operations:

  • Cloud Breach Exposure: Because prospective buyer details and customer inquiries never leave your workstation, an external infrastructure compromise can never expose your proprietary pipeline data.
  • Data Isolation: Your opportunity ledger is an isolated local file store on your physical workstation disk, avoiding shared database infrastructure.
  • Credential Safety: Browser session cookies and authentication states remain within your local Windows user profile directory. No external proxy retains your operator credentials.

Vulnerability Reporting Policy

Ramaaya Technologies welcomes security research and responsible vulnerability disclosure. If you identify a potential security boundary issue or binary vulnerability, please report it directly to our security engineering team:

Email: hello@ramaaya.com
Please include reproduction steps, operating system build, and target binary version. We acknowledge reports within 48 business hours.
Related Documentation: Local Privacy Matrix · System Requirements · EULA
Back to Sniper.AI Pro Overview →