This text describes how the software actually behaves and is provided as the operator's template; a deployment should have it reviewed by counsel for its jurisdiction before publishing.
What AICamera processes
Account data. Your name, email address, a salted Argon2id password hash (never the password), sign-in sessions, two-factor enrolment, and the organizations you belong to with your roles.
Camera configuration. Camera names, sites and locations, stream addresses and credentials. Credentials are encrypted at rest with a per-camera key bound to your organization and are never returned by the API or shown in the interface.
Recordings. Video from cameras you connect, stored in private object storage belonging to the deployment in ten-second files, for the retention period your package and camera settings define. Playback and downloads use short-lived signed links issued only to signed-in members of your organization.
Derived data. Detections, tracks, thumbnails, counting events, text and plate readings, appearance descriptors and search history produced from your recordings. They belong to your organization and are deleted with it.
Questions and searches. Search queries and assistant questions are stored in your organization’s history so you can revisit them; they are metered against your package.
Billing. Package, subscription and invoice records. Card details are entered on the payment provider’s pages and never reach AICamera servers.
Operational records. Request logs, audit events for security-relevant actions (sign-ins, role changes, camera changes, exports, administrative actions) and service health metrics.
How it is isolated
Every organization’s rows are protected by row-level security enforced by the database for every query, including those made by the platform’s own services. Platform administrators act through audited functions that re-verify their role and two-factor status in the database, and every such action is written to an immutable audit log visible to the affected organization.
Language-model providers
By default the assistant runs without any external model. If the deployment configures a provider, it receives only the text of your question, a pseudonymous identifier and the facts a tool returned — never video, thumbnails, credentials or data from other organizations. The provider, model and request identifiers are recorded with each answer.
Retention and deletion
- Recordings: the retention period set per camera, bounded by your package; expired recordings are deleted by leased jobs and their derived data with them.
- Organization deletion: requested by an owner, with an export window and a cancellation window, after which all organization data is purged. Audit history and minimum commercial records (invoices, payments) are retained as required by law.
- Sessions and tokens expire on schedule and can be revoked at any time from the Security page.
Your rights
Members can see and change their profile, sessions and two-factor settings. Owners can export and delete their organization. Requests about personal data held by the operator can be sent through the contact page.
Sub-processors
Object storage, email, SMS, push and payment delivery, and any language-model provider, are configured per deployment by the operator, who lists them here before publishing this page.