01 · Data We Process
- Account data: username, registration email, account status, registration and recent sign-in timestamps; passwords are stored as hashes.
- Store and device data: Store Token hash/prefix, Client ID, device binding count, plugin versions, download records, source IP, and related timestamps.
- Plugin submission data: plugin packages, manifests, versions, descriptions, cover images, and submission/review status.
- Operational data: error logs, service status, request metrics, and technical information needed to investigate security events.
02 · How We Use Data
We use this data to provide account access, validate Store Tokens and device bindings, deliver plugins and updates, process licensing and payments, operate AI Cloud and Push Relay, detect abuse, troubleshoot issues, protect service security, and improve the product experience.
03 · AI Cloud & Training Data
When intelligent sampling, manual review, or manual image upload is enabled, AI Cloud may store snapshots, bounding boxes, object labels, confidence scores, camera/device identifiers, sample source, review results, dataset exports, training-job logs, model files, evaluation records, and deployment records. This data is used for review, training, model feedback loops, and deployment under your account. Do not upload content you are not authorized to process.
04 · Push Relay
Push Relay uses a separate Relay API Key. The service may retain the key hash/prefix, creation and last-used timestamps, delivery attempt/success/failure counts, and error codes. The design does not require persistent storage of full FCM Device Tokens or notification message bodies. Google/Firebase credentials are configured by administrators and used only for delivery.
05 · Payments & PayPal
When you use PayPal to purchase a paid plugin or service, we may retain order IDs, capture IDs, order status, amount, currency, payer ID, payer email, fees, and related timestamps. Sensitive payment credentials such as full card details are handled by PayPal.
08 · Retention & Deletion
Retention depends on feature needs, security auditing, order records, and your deletion actions. Where controls are available, you can delete images, datasets, models, Tokens, Relay Keys, or other resources. Minimal records may remain for a reasonable period for transactions, auditing, abuse prevention, backup rotation, or legal requirements.
09 · Security Measures
We use account authentication, password hashing, Store Token/Relay Key hashing, HTTPS, permission isolation, CSRF protections, controlled downloads, and server-side credential separation. No system can guarantee absolute security, so you should also use strong passwords, protect tokens/keys, and keep Securex Nvr and plugins up to date.
10 · Your Choices & Rights
You can disable real-time sync, delete or recreate Tokens/Relay Keys, clear device bindings, delete AI Cloud images/datasets/models, or stop using related services. Depending on applicable law in your region, you may also have rights to access, correct, delete, restrict processing, or obtain a copy of your data. Requests may require identity verification and can be limited by lawful retention obligations.
11 · Children’s Privacy
The services are intended for users capable of administering NVRs, plugins, and online services and are not specifically directed to children. If camera footage or uploaded content contains data relating to children, you are responsible for ensuring appropriate authorization and a lawful basis for processing.
12 · Changes to This Policy
We may update this Policy as features, laws, or security practices change and will update the “Last updated” date on this page. Material changes may be communicated through the site, release notes, or another reasonable method.