CamRA Subprocessors
G.I.S., Inc., doing business as VirtuWorks ("VirtuWorks", "we") Last updated: October 22, 2026 Contact: help@camra.ai
This page lists the third parties that process personal information on our behalf to deliver CamRA. It is incorporated into the Data Processing Addendum and referenced by the Privacy Policy.
To be notified when this list changes, email help@camra.ai and ask to join the subprocessor notice list. We will give 30 days' notice before a new subprocessor begins processing Customer Data.
1. Infrastructure and platform
| Subprocessor | Service used | Data it processes | Location |
|---|---|---|---|
| Microsoft Corporation (Azure) | Blob Storage — one storage account per customer organisation | Video recordings, recording metadata (detections, best-shot images, scene captions, person appearance vectors), thumbnails, parking and violation photographs | United States (East US; replication Standard LRS) |
| Microsoft Corporation (Azure) | Blob Storage — our own training data store | Feedback contributions: the frame a user's feedback on a detection is about (an image that can show people, vehicles, licence plates and a time the camera prints), its detection boxes and the verdicts, with a record that carries no names, identifiers, licence plates or exact times, while the organisation's "Help improve CamRA's models" setting is on | United States |
| Vast.ai, Inc. | Rented GPU computers on which we train, evaluate and review CamRA's own detection models (open-weights models that we run ourselves; no hosted AI service) | The feedback contributions above, copied in encrypted form for a job; decrypted only on the rented computer while the job runs and wiped from it when the job ends | Depends on the computer rented; may be outside the United States |
| Microsoft Corporation (Azure) | SQL Database | Accounts, permissions, camera and site configuration, licence plate and vehicle records, parking, guest passes, violations, notifications, push devices, billing records, AI incident reports and chat transcripts | United States |
| Microsoft Corporation (Azure) | App Service | The CamRA web application and API, which handle all of the above in transit | United States |
| Microsoft Corporation (Azure) | IoT Hub | Agent control messages, device twin state, camera connection status | United States |
| Microsoft Corporation (Azure) | Event Hubs | Agent event stream | United States |
| Microsoft Corporation (Azure) | Application Insights / Azure Monitor | The web application's own request, dependency and performance telemetry and its warning and error log lines, with personal details masked. On-premises agent logs, when an administrator enables forwarding: these may include camera names, site names, file paths and licence plate text; secrets are stripped before transmission; off by default. | United States |
| Microsoft Corporation (Azure) | Azure OpenAI Service | Scene captions, detected object types, licence plate text, camera and site names, local times, the wording of alert rules and named areas, AI chat questions and the text results of the look-ups the chat makes. No images are sent. Deployments in use: gpt-5-mini for reports and chat, text-embedding-3-small for embeddings. Under Microsoft's terms the data is not used to train Microsoft's or OpenAI's models. |
United States |
| Microsoft Corporation (Azure) | AI Search | One shared index containing captions, licence plate text, camera and site names, incident titles and summaries, and an embedding of each summary. Queries are filtered by organisation, site and permitted cameras. | United States |
| Microsoft Corporation | Microsoft identity platform (OAuth sign-in) | Email address, name, basic profile and account identifier, where a user chooses to sign in with Microsoft | Global |
2. Application services
| Subprocessor | Service used | Data it processes | Location |
|---|---|---|---|
| Apple Inc. | Apple Push Notification service (APNs) | For each iPhone or iPad on which a user turned on notifications in the CamRA iOS app: the device's push token, and the content of each notification sent to it: an alert's title (the alert number and the alert rule names), a short line naming the kinds of object detected, the camera and the time at the site, or a system alert's title and sentence, and the identifiers the app needs to open the right page. Never a picture, a licence plate or AI-written text. | United States; Apple delivers notifications to devices worldwide |
| Apple Inc. | Sign in with Apple | Where a user chooses to sign in with Apple: the sign-in request, and our request to revoke the sign-in when the user removes it or deletes their account. Apple tells us the user's Apple account identifier, email address (which may be a private relay address) and name. | United States; Apple operates the service globally |
| Google LLC | Google sign-in (OAuth) | Where a user chooses to sign in with Google: the sign-in request. Google tells us the user's Google account identifier, email address, whether the email is verified, and name. | United States; Google operates the service globally |
| Stripe, Inc. | Payment processing and card storage | Billing contact name and email, organisation name, card details entered directly into Stripe in the browser, payment method identifiers, invoice and charge records. Card numbers never reach our servers. | United States; Stripe operates globally |
| Twilio Inc. (SendGrid) | Transactional email delivery | Recipient email address, name where included, and the content of notification, alert, invitation, email-confirmation and password-reset messages, including an alert's picture unless the alert rule turns it off | United States |
| ParkPow, Inc. (PlateRecognizer) | Automatic licence plate recognition, api.platerecognizer.com |
Cropped vehicle images from recordings; photographs uploaded by a guest, a resident or a parking officer to read a plate. Returns plate text, region and inferred vehicle attributes. ParkPow's own terms govern how long it keeps the images it receives. | Set by ParkPow's service; may be outside the United States |
3. Content delivered to the end user's browser
These are not subprocessors of Customer Data, but resources the browser loads from a third party when a user opens the CamRA web application. They may receive the user's IP address and set their own cookies under their own policies.
| Provider | What loads | When |
|---|---|---|
| Stripe, Inc. | js.stripe.com — Stripe.js and Stripe Elements |
On pages where a payment method is added |
| Microsoft, Google, Apple | Their own sign-in pages | When a user chooses to sign in with one of them |
There are no analytics, advertising or session-replay scripts in the CamRA web application. No Google Analytics, no Google Tag Manager, no Meta pixel, no Hotjar, no browser-side Application Insights.
The CamRA Desktop and iOS viewers load no third-party content and send no telemetry.
4. Applications a customer connects
An integration a customer's user connects with an API token, an application or AI assistant the user approves through OAuth or CamRA's MCP server, and a webhook receiver the customer registers are not our subprocessors. The customer chooses them, and the Service sends each one the data its token, grant or subscription allows, on the customer's instruction. Their operators handle that data under their own terms.
5. Not used
For the avoidance of doubt, CamRA uses no facial recognition service, no data broker, no advertising network, and no third-party model-training service (on the computers we rent from Vast.ai we run the training ourselves). Customer Data is not used to train machine-learning models, by us or by any subprocessor, except the feedback contributions described in section 3 of the Privacy Policy, which we use for CamRA's own detection models.