shield

TECHNICAL SPECIFICATION — v1.0.3 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)

v1.0.3 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

v1.0.3 Release Binary SHA-256 Checksums

VERIFIED PRODUCTION

EXE SHA-256 Checksum (Setup Installer) SniperAI_Pro_Setup_v1.0.3.exe

13FC53B77376D983CECB05678D574A08D938BA7BE268E84561F09832B2108BF2

ZIP SHA-256 Checksum (Portable Package) SniperAI_Pro_v1.0.3.zip

C8333590DD5A0AAE151BCB7BF71902D0394FCCC400FE5E65B011860CCFE73B05

Verify in PowerShell: Get-FileHash <file> -Algorithm SHA256

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.
Multi-Tenant Data Leakage: Unlike cloud CRM SaaS that shares database instances across multiple competing vendors, your opportunity ledger is an isolated local file store on your physical workstation disk.
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 →