Privacy & NDA Compliance
Official declaration — NCR Quality Tracker v4.0.0
Official NDA Compliance Declaration
This document certifies that NCR Quality Tracker v4.0.0 processes and stores all project data exclusively on the user's local device. No project data is transmitted to, stored on, or accessible by any external server, cloud service, or third party.
Technical Architecture — How Data Stays Local
NCR Quality Tracker is a Static Single Page Application (SPA) built with React. Once the application is loaded in the browser, it operates entirely on the client device. The architecture guarantees data locality through the following mechanisms:
Local Storage Only
All imported data (Issues, Benchmark, Checklist, NCR) is stored exclusively in the browser's localStorage — a sandboxed storage area that never leaves the device.
No Network Calls
After the initial page load, the application makes zero network requests. All data processing (import, filter, export) happens in the browser's JavaScript engine.
No Authentication Required
No user accounts, no login tokens, no session cookies tied to project data. Data access is controlled solely by physical access to the device.
NDA Compliance Checklist
How to Independently Verify — Step-by-Step
Any team member or IT auditor can verify these claims in under 2 minutes using built-in Chrome tools:
Open Chrome DevTools
Press F12 (or Ctrl+Shift+I on Chromebook). This opens the browser's built-in developer tools — no installation required.
Monitor Network Activity
Click the 'Network' tab. Import an Excel file and apply filters. Observe: the only network requests are for static app files (HTML/CSS/JS) loaded once at startup. Zero data requests are sent to any server.
Inspect Local Storage
Click the 'Application' tab → 'Local Storage' → select the app URL. All your project data is visible here, stored locally under the key 'ncr-tracker-v4'. No external database connection exists.
Test Offline Mode
Enable airplane mode or disconnect from Wi-Fi. Reload the page. The application loads and all data remains accessible — proving no server dependency for data storage or retrieval.
Data Lifecycle & User Control
Users retain full and exclusive control over their project data at all times:
| Action | Where it happens | Data leaves device? |
|---|---|---|
| Import Excel file | Browser memory (RAM) | No — file is read locally |
| View / Filter data | Browser localStorage | No |
| Export CSV | Browser Blob API | No — downloaded to device |
| Export PDF | Chrome print engine | No — printed/saved locally |
| Backup (JSON export) | Browser Blob API | No — downloaded to device |
| Restore (JSON import) | Browser memory (RAM) | No — file is read locally |
| Clear all data | localStorage.clear() | N/A — deleted from device |
Recommended Security Practices
- Export a JSON backup after each weekly import and store it on your company's secure Google Drive or SharePoint — this is your NDA-compliant archive.
- Use Chrome's built-in password protection or Chromebook's user account lock to prevent unauthorized physical access to the device.
- Do not use the 'Share' feature of Chrome to share the tab — share only the exported PDF reports, not the live application with loaded data.
- When decommissioning a device, use the 'Clear All Data' button in Settings → Data Management to permanently delete all project data from localStorage.
- For multi-user environments, each team member should import data on their own device — data is not shared between users by design.
NCR Quality Tracker v4.0.0 — Privacy & NDA Compliance Declaration
Issued March 2, 2026 · Developed by Serge NDUDI / SAM · All project data processed locally on user device
This document can be printed or saved as PDF using the button above for audit purposes.