Data governance
Privacy Policy
Last updated: September 20, 2026
1. Data we collect
Google sign-in provides a name, email address, and sign-in identifier. The private host also stores camera settings, recordings, event images, statistics, sessions, and notification settings.
2. How data is used
- Authenticate the designated administrator and provide NVR functions.
- Create event recordings, direction statistics, and Telegram notifications.
- Retain human labels, original DVR-mail images, clear frames, and event clips for model training, compatibility diagnosis, and quality validation.
- After explicit consent, store only a non-administrator's name, email, and consent time for SlimNVR development updates.
- Public page visits record the time, page path, IP address, browser category and approximate country/city to understand product interest and notify the designated private administrator Telegram chat. Statistics are not publicly displayed. Admin pages, APIs, static files and recognizable bots are excluded; query strings, full User-Agent values and sign-in cookies are not retained in analytics.
- Individual visit records expire after 48 hours and are removed in bounded batches; identity-free daily and lifetime page-view totals remain. IP-location cache entries last at most 24 hours. Page views are not unique people, and an IP-derived city is not a precise location.
3. Storage and retention
Camera content normally remains on the user's self-managed host. Continuous recordings and unlabelled event images, clips, and HD-generation sources expire after 24 hours and are cleaned in bounded batches. Human-labelled events and related shared-clip material are retained for training, including false positives. Event text records, labels, and statistics remain; expired jobs cannot recreate deleted media. Active work is temporarily protected. Local cleanup does not delete copies already sent to Telegram or held in backups. Subscription data remains until its purpose ends or deletion is requested.
Retention rollout
Expired unlabelled event media currently moves to a recoverable local quarantine and is not physically deleted, so it still consumes disk space. Indexed continuous recordings continue to be deleted under the 24-hour policy. Cached homepages use a same-origin background request to record visible page views. When Cloudflare is enabled, validated visitor IP and approximate country, region, city, postal code, coordinates and timezone may be reported to ip.zuola.com to improve its location database; both providers' results go to the private administrator Telegram chat. Reports exclude cookies, full User-Agent, Referrer and browsing URLs.
4. Third-party services
Sign-in uses Google OAuth. When notifications are enabled, the first DVR-mail image is sent to the selected Telegram chat for human labeling, followed by the completed event video. Website visitor IPs are sent to the Zola-operated ip.zuola.com location service; approximate locations, browser categories and page details are sent to the designated private administrator Telegram chat, using summaries at higher traffic levels. Local retention does not delete Telegram or backup copies. Those providers process data under their own privacy policies.
Weather comparison
When nearby weather comparison is enabled, the system sends administrator-configured area coordinates to Open-Meteo for numerical weather data, but never sends camera images. Hourly weather values, locally computed image features, and daily summaries are retained for future comparisons; sampling does not retain an additional image copy. Nearby weather models are not on-site measurements.
5. Security
The system uses HTTPS, sign-in protection, and avoids directly publishing camera ports. No networked service can guarantee absolute security, so users should keep the host updated and use secure camera passwords.
6. Your choices
You may stop using Google sign-in, disable Telegram notifications, or contact Zola Technology Co., Ltd. to request access, correction, or deletion of subscription data.