Know exactly what leaves your computer.
SmartBlur runs its core media detection and blurring on your supported Windows 10/11 PC or macOS 14+ Apple silicon M1鈥揗5 Mac. Network access is limited to clearly defined product services, including licensing, updates, payments, and feedback you choose to send.
- Core media processing
- Local
- Network access
- Defined services
- Detection issue images
- Explicit consent
Normal media workflows stay on the device.
The detection models ship with the desktop application. SmartBlur does not need to upload source media to a cloud AI service to find and blur faces, heads, bodies, plates, or manual regions.
- Source photos, videos, and camera frames in normal workflows
- Blurred exports and processed recordings
- Detection coordinates and manual blur regions
- Pro identity-matching face lists created on the device
Local work and network services are kept distinct.
This is the practical boundary an organization can use during privacy, security, or vendor review.
No source media is sent to SmartBlur for AI blurring.
Detection, manual redaction, and export run in the desktop app.
Camera frames and processed output are not sent to SmartBlur.
Live preview, recording, and supported camera output run locally.
A salted device identifier, device label, app version, and license or plan context.
Activation, entitlement checks, device limits, and service protection.
The current app version and normal request information.
Check for, deliver, and verify available application updates.
Account, order, transaction status, and license fulfillment information.
Complete payment, issue licenses, support refunds, and reconcile orders.
The message, contact details, and app or license context you submit.
Investigate an issue and respond to your request.
The selected original image, only after you explicitly approve the upload.
Review that specific detection result. The file is re-encoded to remove embedded metadata and deleted within 12 months.
Security practices around connected services.
These controls apply to SmartBlur-operated services. Payment and email providers also apply their own security and privacy practices.
Encrypted connections
SmartBlur website, account, license, feedback, and update services use TLS while data is in transit.
Protected device identifiers
Device fingerprints used by licensing services are stored as salted hashes rather than raw hardware identifiers.
Separated private feedback storage
Consented detection-report images are stored separately from public media and removed by an automated retention process.
Controlled access
Access to customer, license, transaction, and submitted feedback data is limited to authorized operational use.
Submitted service data is stored on our infrastructure in Singapore.
Detection feedback images are deleted within 12 months. Other customer, license, transaction, and validation records are retained according to operational, accounting, fraud-prevention, and legal needs. Privacy requests are handled through the contact below.
Need facts for an internal vendor review?
Send your privacy or security questions to the SmartBlur team. We will answer based on the current product architecture and data handling shown here.
Scope note:SmartBlur supports privacy and redaction workflows, but software alone does not determine whether an organization鈥檚 use is legally compliant. Customers remain responsible for lawful use, access controls, configuration, and review of final outputs. Last reviewed: August 22, 2026.