CamRA Data Processing Addendum
Between: G.I.S., Inc., doing business as VirtuWorks, of 3850 Bird Road, Suite 103, Miami, FL 33146 ("VirtuWorks", "Processor", "Service Provider", "we") and: the customer organisation identified in the CamRA account ("Controller", "Business", "Customer", "you").
Effective date: October 22, 2026 Contact for data protection matters: help@camra.ai
This Addendum forms part of the Terms of Service (the "Agreement") and governs our processing of Personal Information on your behalf.
1. Definitions
1.1 "CCPA" means the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act, and its regulations.
1.2 "Personal Information" has the meaning given by applicable United States state privacy law, and includes personal data and personal information as those terms are used in those laws.
1.3 "Customer Personal Information" means Personal Information within Customer Data that we process on your behalf under the Agreement. Annex A describes it.
1.4 "Business", "Service Provider", "Consumer", "Sell", "Share" and "Process" have the meanings given in the CCPA.
1.5 "Subprocessor" means a third party engaged by us to process Customer Personal Information.
1.6 "Security Incident" means a breach of our security leading to the accidental or unlawful destruction, loss, alteration, or unauthorised disclosure of or access to Customer Personal Information. It does not include an unsuccessful attempt or an event that does not compromise the security of Customer Personal Information.
2. Roles of the parties
2.1 You are the Business and Controller of Customer Personal Information. You decide where cameras point, what is recorded, who is granted access, how long recordings are kept, and what notice is given to the people recorded. We do not make those decisions and are not in a position to.
2.2 We are the Service Provider and Processor in respect of Customer Personal Information.
2.3 We are the Business and Controller in respect of the account, billing, support and service log data we collect for our own customer relationship. That processing is governed by our Privacy Policy, not by this Addendum.
2.4 Each party will comply with the privacy laws applicable to it.
2.5 You warrant that you have a lawful basis for the processing you instruct, that you have provided any required notice and obtained any required consent or authorisation, that camera placement is lawful, and that your use of licence plate recognition and person re-identification complies with applicable state law. See section 9 of the Privacy Policy.
3. Scope and instructions
3.1 We will process Customer Personal Information only on your documented instructions. The Agreement, this Addendum, and your use of the Service's features are your documented instructions.
3.2 We will not:
- retain, use or disclose Customer Personal Information for any purpose other than providing the Service, or as otherwise permitted by the CCPA for a Service Provider;
- Sell or Share Customer Personal Information;
- retain, use or disclose it outside the direct business relationship between us;
- combine it with Personal Information received from another source, except as the CCPA permits a Service Provider to do; or
- use it to train machine-learning models, whether our own or a third party's, except the feedback contributions of section 3.6.
3.3 We certify that we understand the restrictions in section 3.2 and will comply with them.
3.4 If we believe an instruction breaches applicable law, we will tell you promptly and may suspend that processing until it is resolved.
3.5 We will tell you if we can no longer meet our obligations under this Addendum. You may then take reasonable and appropriate steps to stop and remediate unauthorised use, including suspending processing or terminating under the Agreement.
3.6 Feedback contributions. While your organisation's setting "Help improve CamRA's models" is on (it is on by default, and an administrator can turn it off at any time in the Service), you instruct us to keep, when one of your Authorised Users marks a detection, an alert or an incident as right or wrong, the frame that feedback is about, its detection boxes and the verdicts, and to use them to train and evaluate CamRA's detection models. We keep them in our own storage, apart from your recordings, and process them on our own computers and on computers we rent from Vast.ai, Inc. (see the Subprocessor list), which may be outside the United States: there they are encrypted except on the rented computer while a job runs, and are wiped from it when the job ends. Only models that we run ourselves process them; no hosted AI service does. The record kept with each frame carries no names, identifiers of your organisation, sites, cameras or users, licence plates or exact times (only the hour of the day and the month); the frame itself is an image of what the camera saw and can show people, vehicles and their licence plates, and any date and time the camera prints on its picture. Turning the setting off stops new contributions; contributions already made are kept and are not removed by your retention settings or by the deletion functions of the Service.
3.7 Applications you connect. When you or your Authorised Users connect an integration with an API token, approve an application or AI assistant through OAuth or the Service's MCP server, or register a webhook receiver, you instruct us to send that application the data its token, grant or subscription allows. Such an application is not our Subprocessor, and what its operator does with the data is outside this Addendum.
4. Confidentiality
4.1 We will treat Customer Personal Information as confidential.
4.2 We will limit access to personnel who need it to provide or support the Service, will bind them to confidentiality, and will train them on their obligations.
5. Security measures
We maintain the technical and organisational measures described in Annex B. Annex B states what exists today, not what is planned. We will not materially reduce the overall level of security during the term.
6. Subprocessors
6.1 You give us general authorisation to engage Subprocessors. The current list, with what each one receives, is the Subprocessor list. It includes Apple Inc. (push notifications to the CamRA iOS app, and Sign in with Apple) and Google LLC (Google sign-in).
6.2 We will impose on each Subprocessor written obligations no less protective than this Addendum, and we remain responsible to you for its performance.
6.3 We will give you 30 days' notice before a new Subprocessor begins processing Customer Personal Information, by email to your account administrator and by updating the list. If you have a reasonable, documented objection on data protection grounds, tell us within those 30 days. We will work in good faith to offer an alternative; if we cannot, you may terminate the affected part of the Service. Prepaid balances are not refunded (Terms of Service, section 6.4).
7. Assistance with individual rights
7.1 If a Consumer contacts us with a request about footage or parking data at your site, we will not respond on the merits. We will direct them to you, or forward the request to your account administrator, unless the law requires otherwise.
7.2 We will provide reasonable assistance, at your cost where the effort is more than incidental, in responding to a request to know, access, correct, delete or port Customer Personal Information. The Service's own search, export, playback and delete functions are the primary means by which you fulfil such a request yourself.
7.3 We will assist you with a data protection impact assessment or a consultation with a regulator, so far as the information is within our control.
7.4 Practical limits you should know about. Deleting a specific individual from historical video is not technically possible: video is stored as whole clips and the people in a clip cannot be separated. Deleting the clip deletes everyone in it, including the requester. A vehicle record and its sighting history can be deleted individually. Person appearance vectors are held inside a recording's metadata and are deleted when that recording is deleted.
8. Security incidents
8.1 We will notify you without undue delay and in any case within 72 hours of becoming aware of a Security Incident affecting Customer Personal Information.
8.2 The notice will describe what is known: the nature of the incident, the categories and approximate volume of data, the likely consequences, and the measures taken or proposed.
8.3 We will cooperate reasonably with your investigation and remediation.
8.4 You are responsible for notifying affected individuals and regulators, as the Business. A notification by us is not an admission of fault.
9. Deletion and return
9.1 During the term, you may export and delete Customer Personal Information using the Service.
9.2 On termination, and on your written request to help@camra.ai, we will delete Customer Personal Information and confirm deletion in writing. Unless you request otherwise, we will retain it for 30 days after termination so you can export it, and will then delete it.
9.3 Deletion of an organisation and its data is done by us. An Authorised User can delete their own account in the Service (it is removed 7 days after they confirm), and an organisation can be deleted in the Service only when it is empty (no agents, cameras, other members or billing history). An organisation that holds data, and its storage account, are deleted by us. This is why section 9.2 requires a written request.
9.4 Backups and system logs may retain copies for a further period until they age out on their normal cycle. Those copies remain subject to this Addendum until deleted.
9.5 We may retain Customer Personal Information where the law requires it, for as long as required.
10. Audit and assurance
10.1 We do not hold a SOC 2 report, an ISO 27001 certificate, or any equivalent third-party audit report. We will say so rather than imply otherwise. We will tell you if that changes.
10.2 On reasonable written request, no more than once in any 12 months, we will complete a reasonable security questionnaire and provide the information reasonably necessary to demonstrate compliance with this Addendum.
10.3 An on-site audit is available only where a regulator requires it or following a confirmed Security Incident affecting you, on 30 days' written notice, during business hours, at your cost, subject to confidentiality, and without access to another customer's data or to our production environment in a way that risks it.
10.4 Where our infrastructure is operated by a Subprocessor, we will pass through that Subprocessor's published certifications and reports so far as we are permitted to.
11. International transfers
The Service is operated in the United States and Customer Personal Information is stored there. We do not offer data residency elsewhere. Some Subprocessors operate globally and may process limited data outside the United States, as the Subprocessor list states for each of them. This Addendum contains no cross-border transfer mechanism; if you become subject to a law that requires one, the parties will agree an amendment adding the appropriate mechanism.
12. Liability and precedence
12.1 Each party's liability under this Addendum is subject to the limitations and exclusions in the Agreement.
12.2 Order of precedence. In case of conflict: (a) a signed order form or master agreement, then (b) this Addendum, then (c) the Agreement, then (d) the Acceptable Use Policy and the EULA. This Addendum prevails over the Agreement only on the subject of data protection.
12.3 This Addendum terminates automatically when we stop processing Customer Personal Information, except for provisions that by their nature survive.
Annex A — Details of processing
Subject matter: provision of the CamRA video surveillance platform.
Duration: the term of the Agreement, plus the retention and deletion periods in section 9.
Nature and purpose: recording, storing, transmitting, analysing, indexing, searching and displaying video and derived data; managing parking, vehicles, guests and violations; sending notifications; and supporting and securing the Service.
Categories of data subject: anyone captured by your cameras, including employees, contractors, residents, tenants, customers, visitors, guests and passers-by; your Authorised Users; and people registered in your parking records.
Categories of Personal Information:
| Category | Examples |
|---|---|
| Video imagery | Recorded clips of monitored areas. Video only; CamRA records no audio. |
| Derived detections | Bounding boxes, object types, confidence scores, timestamps, best-shot crops |
| Scene captions | Machine-generated text descriptions of a clip |
| Person appearance vectors | Numerical OSNet re-identification embeddings for person detections, stored in recording metadata. Not face templates; CamRA performs no facial recognition. |
| Vehicle and licence plate data | Plate text, issuing region, vehicle type, make, model, colour, camera, timestamp, confidence |
| Vehicle owner records | Owner display name, owner email address, linked user account, unit, company, comments |
| Parking records | Parking lot and space assignments, occupancy, guest passes (user identifier, plate, region, validity window), vehicle ownership claims and their photographs |
| Violation records | Plate, vehicle status, violation type, free-text note, up to five photographs, the user who recorded it |
| AI outputs | Incident report titles, summaries, severity scores, search index entries, chat transcripts |
| Feedback contributions | Frames that Authorised Users' feedback is about (images that can show people, vehicles, licence plates and a time the camera prints), their detection boxes and the verdicts; the record kept with each frame carries no names, identifiers, licence plates or exact times (section 3.6) |
| Account and access data | Authorised User email addresses, Microsoft, Google and Apple account identifiers, permission assignments, permission change audit log, API token metadata, push device tokens |
Sensitive categories: none are collected deliberately. Whether the appearance vectors above constitute biometric information under Illinois, Texas or Washington law is a determination you must make for your own deployment; see section 9 of the Privacy Policy.
Annex B — Technical and organisational measures
These measures are in place today.
B.1 Encryption in transit. HTTPS throughout, with HTTP Strict Transport Security enabled outside development. The desktop viewer connects to the on-premises agent over TLS, checks the agent's certificate, issued by our own certificate authority and validated against a chain, and signs in to the agent with a session token the Service issues for that agent. Agents that fetch recordings from one another use mutual TLS with those certificates and a grant signed by the Service.
B.2 Encryption at rest. Recordings and metadata are held in Azure Storage, encrypted at rest by Azure Storage. The SQL database is hosted by Azure SQL. Recordings held on your own agent machine before upload are not encrypted by the Agent; securing that machine is your responsibility.
B.3 Tenant isolation. Each customer organisation gets its own Azure Storage account. Application-level isolation is enforced on every data access path in the application, not by a single global filter. The Azure AI Search index is shared between customers and every query is filtered to the requesting organisation, site and permitted cameras.
B.4 Access control. A permission model down to the individual camera. Camera-level grants surface in the interface but do not confer site-level operations. Permission changes are recorded in an audit log.
B.5 Authentication. Passwords stored as salted hashes by ASP.NET Core Identity. Email confirmation required before first sign-in. Minimum password length of 12 characters when a password is set or changed. An account is locked for 15 minutes after five failed sign-in attempts, on the browser sign-in and on the sign-in used by the desktop and iOS apps. Optional two-factor authentication with an authenticator app for sign-in with an email address and password. Optional sign-in with Microsoft, Google or Apple, which does not ask for CamRA's second factor and relies on that provider's own sign-in checks. Sessions revalidated against the user's security stamp every 5 minutes. API tokens stored only as a hash plus a short prefix, revoked immediately on request, limited to 25 active per account.
B.6 Least-privilege data access. Stored objects are never publicly readable. A viewer is given a file only through a short-lived signed URL, valid for 1 to 5 minutes depending on the asset. An on-premises agent receives a time-limited credential for its own organisation's storage only.
B.7 Privacy masks. Masks you configure are permanently burned into the video before upload. If burn-in fails, the recording is deleted rather than uploaded unmasked.
B.8 Payment data. Card details are captured directly by Stripe in the browser. We never receive, store or transmit a card number.
B.9 Telemetry minimisation. Agent log forwarding is off unless enabled, is time-windowed, and secrets are stripped from log properties and exception detail before transmission. The desktop and iOS viewers send no telemetry.
B.10 Access audit log. Sign-ins (successful, failed and locked out), two-factor authentication changes and challenges, the creation, revocation and first use of API tokens, the opening and downloading of recordings, the creation and use of share links to a recording or an incident (its text, pictures and every recording it gathers), and the export of incident reports are recorded in an audit log for your organisation. The log is visible only to your users who hold the audit-log permission for the organisation, and entries are kept for one year, independently of your recording retention policy.
B.11 Known gaps, stated plainly. An organisation that holds data cannot be deleted in the Service; we delete it, and its storage account, on written request (section 9). We will update this Annex as this changes, and we will not claim a control before it ships.