Local Privacy & Data Processing Matrix
Enterprise revenue and trade operations require absolute confidentiality. Sniper.AI Pro is engineered around a local-first operational paradigm. Unlike multi-tenant cloud SaaS tools that ingest and warehouse your prospect data on external servers, Sniper.AI Pro processes inquiries within your Windows machine.
Workstation Local Boundary
Prospective buyer records, commercial specifications, phone numbers, contact names, and outreach messages reside inside your machine's private local storage (%LOCALAPPDATA%\SniperAI_Pro).
- ✓ Raw leads & RFQs stay on local disk
- ✓ Targeting rules & exclusions evaluated locally
- ✓ Local data store exportable anytime to XLSX
- ✓ Browser automation executes under local user profile
Licensing Cloud Separation
The external cloud infrastructure exists strictly to validate commercial subscription entitlement, enforce single-seat node-locks, and process cryptographic licensing handshakes over encrypted HTTPS/TLS connections.
- ✓ Cryptographic license token verification
- ✓ Hashed machine hardware ID (node-lock)
- ✓ Client version string verification
- ✗ Customer operational lead data is not uploaded
Field-Level Data Processing Matrix
swipe Swipe horizontally to inspect full matrix →
| Data Category | Processing Boundary | Uploaded to Cloud? | Storage & Retention | Operator Control |
|---|---|---|---|---|
| Buyer Leads & RFQs Inquiry title, product name, quantity, commercial specs | Local Workstation Only | LOCAL ONLY (Not Uploaded) | Local storage (%LOCALAPPDATA%\SniperAI_Pro\opportunities_pipeline.json). Retained until deleted by operator. |
Full. Operator can delete, purge, or export to Excel anytime. |
| Buyer Contact Details Phone numbers, contact names, company records | Local Workstation Only | LOCAL ONLY (Not Uploaded) | Local storage (%LOCALAPPDATA%\SniperAI_Pro\indiamart_captured_leads.xlsx). Never uploaded. |
Exportable to local spreadsheet (.xlsx). |
| Targeting Matrix & Rules Positive keywords, negative exclusions, geo corridors | Local Workstation Only | LOCAL ONLY (Not Uploaded) | Local configuration file on disk (%LOCALAPPDATA%\SniperAI_Pro\config_indiamart.json). |
Operator creates, edits, and backs up rules locally. |
| Outreach Templates & Proposals Draft pitch text, pricing models, quote terms | Local Workstation Only | LOCAL ONLY (Not Uploaded) | Local storage on workstation disk (%LOCALAPPDATA%\SniperAI_Pro\config_indiamart.json). |
Fully editable inside the local UI cockpit. |
| Browser Sessions & Cookies Local operator browser profiles & active session cookies | Local Workstation Only | LOCAL ONLY (Not Uploaded) | Workstation user profile directory (%LOCALAPPDATA%\SniperAI_IndiaMart_Session). Subject to OS file ACLs. |
Operator maintains standard browser controls and credentials. |
| License Key & Token Commercial key string, activation status, subscription tier | Client ↔ Licensing API | YES (HTTPS/TLS Encrypted) | Stored in licensing cloud for entitlement verification. Signed cache kept locally on disk. | Operator views subscription expiry inside client. |
| Hardware Device Identifier One-way SHA-256 hash of host installation identifier | Client ↔ Licensing API | YES (One-Way Hash) | Used solely to enforce single-seat node-lock per license. Transmitted as formatted hash string. | Transferable to new hardware upon support request. |
| Licensing Heartbeat Periodic timestamp check ensuring active commercial validity | Client ↔ Licensing API | YES (HTTPS/TLS Encrypted) | Audit log for licensing concurrency on server. Offline grace period supported locally. | Automatic periodic check; zero operational impact. |
| Application Version Tag Client build version string (v1.0.3) sent with licensing handshakes | Client ↔ Licensing API | YES (Version String) | Sent as payload field during activation and heartbeat calls. | Updates are downloaded manually by the operator from official release channels. |
| Error / Crash Diagnostics Application stack traces and unhandled exceptions | Local Workstation Only | Implementation-dependent — not independently verified | Logged locally on disk (%LOCALAPPDATA%\SniperAI_Pro\license_audit.log). No automated remote telemetry transmission configured. |
Operator can inspect or clear local logs anytime. |
Localhost Loopback IPC (127.0.0.1)
Sniper.AI Pro's native desktop UI and core processing engines communicate via local inter-process communication (IPC) bound strictly to the loopback interface (127.0.0.1:54321).
This port is inaccessible from external networks and does not accept remote connections, providing strict memory-level and socket-level isolation within your workstation.
Enterprise IT & Data Residency Compliance
Because Sniper.AI Pro retains all commercial data on local storage, enterprise organizations operating under stringent data residency or confidentiality regulations (such as NDA commitments, GDPR client protections, and internal trade secret protocols) do not incur third-party cloud data processor liability.
Your organization maintains full administrative sovereignty over disk encryption (BitLocker), file access control lists (ACLs), and automated backup schedules.
Questions Regarding Data Governance?
Enterprise security officers requesting an Architecture Review or customized Data Processing Addendum (DPA) may contact our engineering security office: