G.I.S., Inc., doing business as VirtuWorks ("VirtuWorks", "we") Effective date: November 18, 2026 Contact: help@camra.ai — 3850 Bird Road, Suite 103, Miami, FL 33146
This policy explains how we handle personal information in connection with CamRA, our video surveillance platform: the web application, the on-premises recording agent, the desktop viewer and the iOS viewer, and our website, camra.ai.
1. Two different roles#
Read this section first. It decides which of your rights apply and who you ask.
1.1 We are the business (controller) for our own customer relationship. Account records, billing records, support correspondence and our own service logs are ours. We decide what to collect and why, and this policy governs them.
1.2 We are a service provider (processor) for camera data. Video recordings, the detections and captions derived from them, licence plate reads, parking records and guest registrations are processed on behalf of the business customer ("Tenant") that installed the cameras. That Tenant decides what to film, where to point the camera, who may watch, how long to keep it and what signage to post. We act on their instructions under our Data Processing Addendum.
1.3 If you appear on camera at a site that uses CamRA, we are almost certainly not the right first contact. Contact the operator of that site — the name on the posted surveillance notice. If you cannot identify them, write to help@camra.ai and we will pass the request to the Tenant that controls those cameras. We will not disclose another organisation's footage to you on our own authority.
2. Information we collect#
2.1 Account information (we are the business)#
| Collected | Source |
|---|---|
| Email address, password (stored as a hash by ASP.NET Core Identity) | You, at sign-up |
| Microsoft account identifier, email, name and basic profile, if you sign in with Microsoft | Microsoft, at your direction |
| Google account identifier, email, name and whether Google has verified the email, if you sign in with Google | Google, at your direction |
| Apple account identifier, email (which may be an Apple private relay address), name, and an Apple refresh token kept encrypted so that we can revoke Sign in with Apple when you remove it or delete your account, if you sign in with Apple | Apple, at your direction |
| Email confirmation status — an unconfirmed account cannot sign in | Our system |
| Tenant, site and camera permission assignments, and an audit log of permission changes | Your administrator |
| Invitations you send or receive | You |
| API tokens you issue for the desktop app, the iOS app or the public API, and the applications you approve through OAuth | You |
| For each iPhone or iPad on which you turn on notifications in the CamRA app: its Apple push token, the device's name, the app version and when it was last seen | The CamRA iOS app, at your direction |
We do not collect a date of birth, a government identifier, or a payment card number.
Signing in with Microsoft, Google or Apple. When you choose one of them, your browser or app is sent to that provider, which signs you in under its own privacy policy and tells us your account identifier, your email address and your name. The provider learns that you are signing in to CamRA. We use what it sends to find or create your CamRA account and keep the link between the two; we do not receive your password for that provider, and we receive nothing else from your account there.
2.2 Billing information (we are the business)#
We store your Stripe customer identifier, your billing contact details, daily and monthly usage
totals, your prepaid balance and its ledger (every usage deduction, top-up, credit and adjustment),
the history of your card charges, receipts and statements, and the invoices issued before prepaid
billing. Card numbers never reach our servers. Card entry happens in a Stripe-hosted
element loaded directly from js.stripe.com in your browser; our server only ever sees a Stripe
identifier for the saved payment method.
2.3 Camera data (we are a service provider)#
Collected by the on-premises agent from the Tenant's own cameras and uploaded to the Tenant's dedicated Azure Storage account:
- Video recordings. Video only. The agent does not record, store or transmit audio. It requests both media types when it opens the RTSP connection, but it subscribes only to the video stream and the recorder writes a video-only file. There is no audio track in a CamRA recording.
- Object detections. Bounding boxes, timestamps, confidence scores and an object type, produced by YOLO models that run on the Tenant's own hardware.
- Best-shot images. Cropped stills of detected objects.
- Scene captions. Short natural-language descriptions of what a clip appears to show, produced by a small vision-language model running on the Tenant's own hardware.
- Person re-identification vectors. For person detections, the agent computes a numerical appearance vector (an OSNet embedding) and stores it inside the recording's metadata file. This vector describes overall appearance — clothing, shape, colour — and is used to follow the same person from frame to frame within that one recording. CamRA does not currently use it to link a person across different recordings. It is not a face template and CamRA performs no facial recognition of any kind. See section 9.
- Licence plate reads. Plate text, issuing region, and inferred vehicle type, make, model and colour, with the associated camera, timestamp and confidence.
2.4 Parking and access information (we are a service provider)#
Where a Tenant uses the parking features: registered vehicle records (plate, region, vehicle description, an owner display name, an owner email address, and a link to a unit or company), parking violation records (plate, vehicle status, a free-text note from the person recording it, an owner display name, and up to five photographs), vehicle ownership claims (including a supporting photograph) and guest passes.
Organisations using CamRA also keep records of people, with or without a CamRA account: a name, an email address, a phone number, a note, the companies and units the person is affiliated with and their role there, and whether their login to that organisation is disabled. When the person has a CamRA account, the organisation's record shows the account's name, email address and phone number. Phone numbers are stored for future SMS notifications; CamRA does not use them to send messages yet. You may leave an organisation from Account > Your organisations. Deleting your account removes the link to it and replaces your name with "Former member" in every organisation's record.
2.5 Guest registration (we are a service provider)#
When you scan a guest parking QR code you sign in with a Microsoft, Google or Apple account and register a licence plate. What is stored is: your user account identifier, the plate, the issuing region, the parking lot, and the validity window of the pass. Your name is displayed for confirmation but is not stored against the pass.
You may optionally photograph the plate instead of typing it. That photograph is sent to our automatic plate-reading provider, PlateRecognizer (ParkPow, Inc.), to extract the characters, the characters are placed in the form for you to check, and the photograph is not stored by us. If you would rather not have a photograph leave your phone, type the plate.
2.6 Device and log information#
Web server logs, application error logs, and connection records. The web application sends its own request, dependency and performance telemetry, and its warning and error log lines with personal details masked, to Microsoft Azure Application Insights. The on-premises agent keeps local logs on the Tenant's own machine. A Tenant's administrator can switch on telemetry forwarding from an agent to our monitoring system for a limited window, typically to diagnose a fault; that forwarding is off unless it is configured, and secrets are stripped before anything is sent.
The desktop and iOS apps send no telemetry or crash reports to us or to anyone else.
2.7 Push notifications on iPhone and iPad#
If you turn on notifications in the CamRA iOS app, the app registers the device's Apple push token with us, together with the device's name and the app version. We use it only to send you the alerts you chose to receive by push. Each notification is sent through the Apple Push Notification service (APNs), operated by Apple Inc., which receives the push token and the notification's content:
- for an event alert, its title (the alert number and the names of the alert rules) and a short line we write from the facts: the kinds of object detected, the camera's name and the time at the site (for example "Person, Vehicle on Loading dock, 8:52 PM EDT"). It is sent only to a person who may see that camera. A push never carries a picture, a licence plate or the AI-written summary;
- for a system alert (a camera or agent problem, billing, a system notice), its title and its sentence;
- identifiers that let the app open the right page: the notification, organisation, site, camera and incident identifiers and the page's address in CamRA.
Apple delivers the notification to the device and handles it under its own terms. You can turn push off for one alert subscription, for all of your devices ("Push to my phones" on your account page), or remove a device there; signing out of the app removes it too.
2.8 Cookies#
The CamRA application uses a small number of cookies and no advertising, analytics or tracking cookies. Because none of them are used for tracking or advertising, the application does not show a cookie banner.
| Cookie | Purpose | Type | Lifetime |
|---|---|---|---|
| ASP.NET Core Identity authentication cookie | Keeps you signed in | Strictly necessary | 14 days, sliding |
| Antiforgery cookie | Blocks cross-site request forgery on forms | Strictly necessary | Session |
| Sign-in correlation and nonce cookies (Microsoft, Google, Apple) | Protect the sign-in round trip with the provider you chose | Strictly necessary | Minutes, during sign-in only |
tenant |
Remembers which organisation you last viewed | Functional | 1 year |
site |
Remembers which site you last viewed | Functional | 1 year |
view |
Remembers whether you use the full or simplified interface | Functional | 1 year |
All of the above are first-party. tenant, site and view are set with SameSite=Strict, and
with the Secure flag whenever the page is served over HTTPS. You can delete or block them in your
browser; blocking the authentication or antiforgery cookie will prevent you from signing in.
Third-party resources that load in your browser may set their own cookies or storage under their own policies. In CamRA that is Stripe.js, on pages where a payment method is added, and the sign-in pages of Microsoft, Google or Apple when you choose to sign in with one of them. We do not receive analytics from them.
Our website, camra.ai. The website (not the CamRA application) uses Google Analytics 4 and
Microsoft Clarity, loaded through Google Tag Manager, to understand how visitors use its pages:
which pages are opened, how people move between them, the type of device and browser, and the
approximate area they visit from, derived from the IP address. Clarity also records how a page is
scrolled and clicked, so we can see where a page is unclear; it masks what you type. Google and
Microsoft set their own cookies for this, such as _ga and _ga_* (up to two years), _clck (one
year) and _clsk (one day). We use this only to improve the website: not for advertising, never sold,
and never combined with your CamRA account. Visitors from the European Economic Area, the United
Kingdom and Switzerland are asked first. The website tells where you are only from your browser's time
zone: when it is set to a European time zone, Google Tag Manager, and with it these tools, is not loaded
until you agree. Cookie settings
in the website footer changes the choice at any time. You can also block these cookies in your browser
or with Google's opt-out browser add-on (https://tools.google.com/dlpage/gaoptout); the website works the same
without them. We also use Google Search Console, which reports how the website appears in Google
Search; it adds nothing to the website and sets no cookies.
The desktop and iOS apps are not web browsers and set no cookies. The desktop app stores your server address and API token in a configuration file in your local application data folder; the iOS app stores them in the iOS Keychain.
2.9 Door access (we are a service provider)#
Where a Tenant connects its door access system to CamRA (for example 2N door stations or 2N Access Commander), CamRA keeps a log of what happens at its doors: each door opened, refused, forced or held open, when, how (card, PIN, mobile key, licence plate, exit button, or a remote open from CamRA), and, when the door system or CamRA knows it, who it was (the person's record in that organisation). When someone opens a door from CamRA, CamRA also records who asked and when. This log shows where a person was and when, so it is treated as personal data from the first event stored. It is kept for the Tenant's door event retention (90 days unless the Tenant sets another period, section 6), is in your personal-data download (section 8), and no longer names you once your account is deleted or the organisation deletes your record. Door system passwords and access tokens are stored encrypted and are never shown again; card numbers, PINs and codes typed at a door are not kept in this log.
3. How we use information#
- To provide, operate, secure and support the CamRA service.
- To authenticate you and enforce the permissions your administrator assigned.
- To meter usage and bill Tenants.
- To send transactional and notification email (alerts, invitations, password resets) through SendGrid; an alert email can carry the alert's picture unless the alert rule turns that off.
- To send the push notifications you turned on, through Apple (section 2.7).
- To detect, investigate and prevent abuse, security incidents and technical faults.
- To comply with law.
We process camera data, parking data and guest data only to provide the service to the Tenant and for the limited internal purposes a service provider is permitted, such as security, debugging and improving the service as described below. We do not use it to build advertising profiles.
Model training, and the one exception. The detection, caption and re-identification models are pre-trained and run unchanged, and we do not use Tenant camera data, captions, plates or embeddings to train machine-learning models, with one exception the Tenant controls. When a Tenant's user marks a detection, an alert or an incident as right or wrong, and the Tenant's setting "Help improve CamRA's models" is on (it is on by default; an administrator can turn it off at any time), we keep the frame that feedback is about, its detection boxes and the verdicts, to train and evaluate CamRA's detection models. The frame is an image of what the camera saw (the whole picture or the picture of one object), so it can show people, vehicles and their licence plates, and any date and time the camera prints on its picture. The record kept with it carries no names, no identifiers of the Tenant, site, camera or user, no licence plate and no exact time (only the hour of the day and the month): the person who gave the feedback is represented by a key that cannot be traced back to them without a secret only our server holds. These contributions are held in our own Microsoft Azure storage, apart from the Tenant's recordings, and are not removed by the Tenant's retention settings. We train and review the models on our own computers and on computers we rent from Vast.ai, Inc., which may be outside the United States: the contributions are copied there encrypted, decrypted only on the rented computer while the job runs, and wiped from it when the job ends. Only models that we run ourselves process them; no hosted AI service does. Turning the setting off stops new contributions; contributions already made are kept.
The AI features described in section 4 send data to Azure OpenAI Service. Under Microsoft's terms for that service, the data is not used to train Microsoft's or OpenAI's models.
4. Automated processing and AI features#
CamRA is an automated system and Tenants should treat it as one.
- On the Tenant's own hardware: object detection, person re-identification, and scene captioning.
- Sent to PlateRecognizer (ParkPow, Inc.): cropped vehicle images from recordings, for plate reading. Plate photographs taken by a guest, a resident or a parking officer are also sent here. The plate text and vehicle attributes come back and are stored.
- Sent to Azure OpenAI Service: scene captions, detected object types, plate text, camera name, site name, the local time, and the wording of the Tenant's alert rules and named areas, to generate an incident summary and severity score. Images are not sent. Where a Tenant uses the AI chat feature, the questions typed into it are also sent, together with the results of the look-ups the chat makes to answer them, which are limited to what the person asking may see in CamRA and never include images. The questions and answers are stored; the look-up results are not.
- Indexed in Azure AI Search: captions, plate text, camera and site names, and the incident summary, plus a numerical embedding of that summary, so incidents can be searched. All Tenants share one search index; every query is filtered to the requesting Tenant, site and permitted cameras before results are returned.
These outputs can be wrong. A detection, a caption, a severity score or a plate read is a machine guess. Nobody should be accused, fined, towed, excluded or disciplined on the strength of one without a human checking the underlying footage.
5. How we disclose information#
We disclose personal information only as follows:
- To subprocessors who host and operate parts of the service. The current list, with what each one receives, is in the Subprocessor list. It includes Apple, which delivers push notifications (section 2.7).
- To the sign-in provider you choose, Microsoft, Google or Apple, when you sign in with it (section 2.1). We tell Apple to revoke Sign in with Apple when you remove that sign-in or delete your account.
- To Google and Microsoft, which measure how our website, camra.ai, is used (section 2.8). This covers visits to the website only, not your use of the CamRA application. Google signals, ads personalisation and data sharing are turned off in Google Analytics, so this analytics data is not sold or shared for cross-context behavioural advertising.
- To the Tenant whose cameras or site the data came from, and to the users that Tenant has authorised.
- To applications a Tenant's users connect. A user can connect an integration with an API token, approve an application or AI assistant through OAuth or our MCP server, or register a webhook receiver. The Service then sends that application the data the token, grant or subscription allows, limited to what that user may see. That disclosure is directed by the Tenant and its user, and the application's operator handles the data under its own terms.
- To anyone holding a valid share link, if a Tenant user creates one. A share link for a recording or an incident (its text, pictures and every recording it gathers) is unauthenticated: anyone with the link can view and download that footage and, for an incident, read its summary, object captions and licence plate reads, including recordings that join the incident later, until the link expires (the creator chooses 1, 7, 14 or 30 days; expiry is enforced by our server) or is revoked.
- To professional advisers, an acquirer, or in a corporate transaction, subject to confidentiality.
- To law enforcement or in legal process, where legally required. Where a demand concerns a Tenant's camera data and we are lawfully able to, we will redirect the requester to the Tenant or notify the Tenant before responding.
We do not sell personal information and we do not share it for cross-context behavioural advertising. We have not done so in the preceding twelve months.
6. Retention#
| Data | Retained |
|---|---|
| Recordings, detections, best shots, captions, re-identification vectors, incident reports, search index entries | Per the Tenant's retention policy. The platform default is 90 days, which is also the shortest retention available. A Tenant may set a longer default, a per-camera override, or deliberately opt a camera or the whole organisation in to indefinite retention. |
| Licence plate history (vehicle records and sightings) | Indefinitely, until the Tenant deletes the vehicle record. Plate history deliberately survives the deletion of the recording it came from. |
| Vehicle images (a still image of the camera frame in which a vehicle was detected, kept for the vehicle record and for each of its sightings; the frame is not cropped, so it can show other vehicles and people) | Indefinitely, with the vehicle record, until the Tenant deletes that record. These images are not governed by the Tenant's retention policy and survive the deletion of the recording, and of the camera, they came from. |
| AI chat conversations | 7 days after the conversation was last used, then deleted automatically. |
| Door events and remote door opens (section 2.9) | 90 days, or the period the Tenant sets, then deleted automatically. |
| Feedback contributions used to train models (section 3) | Kept without a set end; not governed by the Tenant's retention policy. |
| Access audit log (sign-ins, failed sign-ins, lockouts, two-factor changes and challenges, API token events, recording playback and downloads, share links created and used, incident report exports) | 365 days, then deleted automatically. Kept independently of the recording retention policy, so an entry outlives the recording it refers to. |
| Parking violations, guest passes, vehicle claims and their photographs | Until the Tenant deletes them |
| Account records, and the link to a Microsoft, Google or Apple sign-in | Until the account is deleted, or the sign-in is removed from the account |
| Push devices (section 2.7) | Until you remove the device or sign out of the app, the app's sign-in is revoked, Apple reports the push token as no longer valid, or the account is deleted. When the app's sign-in ends on its own (after 90 days without use, or on its expiry date), no notification is sent to the device from then on, and the device and its push token are deleted with the sign-in 30 days later |
| API usage records (requests per token per hour) | 90 days |
| Billing and invoice records | As required by tax and accounting law |
| Local recordings on the Tenant's own agent machine | Controlled by the Tenant. The agent does not delete local files on a schedule. |
7. Security#
What actually exists today:
- HTTPS everywhere, with HTTP Strict Transport Security enabled outside development.
- Antiforgery protection on browser forms.
- Passwords stored as salted hashes by ASP.NET Core Identity; email confirmation required before first sign-in.
- Recordings held in an Azure Storage account dedicated to each Tenant, encrypted at rest by Azure Storage and never exposed for public anonymous access. Files are shown to a viewer only through short-lived signed URLs, valid for 1 to 5 minutes depending on what is being fetched.
- A permission model down to the individual camera, enforced on every repository call rather than by a global filter.
- API tokens stored only as a hash and a short prefix; revoking a token takes effect on the next request. A maximum of 25 active tokens per account.
- Encrypted connections between the desktop viewer and the on-premises agent: the viewer checks the agent's certificate, issued by our own certificate authority, 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.
- Privacy masks configured by the Tenant are permanently burned into the video before it is uploaded. If the burn-in fails, the recording is deleted rather than uploaded unmasked.
- Account lockout: after five failed sign-in attempts an account is locked for 15 minutes, on the browser sign-in form and on the sign-in used by the desktop and iOS apps.
- Optional two-factor authentication with an authenticator app. It applies to sign-in with an email address and password, on the web and in the apps; sign-in with Microsoft, Google or Apple does not ask for the second factor, and relies on that provider's own sign-in checks instead.
- A minimum password length of 12 characters when a password is set or changed. Passwords set before that minimum was introduced are not forced to change.
- An audit log of sign-ins and of who opened, downloaded or shared a recording, visible to the Tenant's users who hold the audit-log permission and kept for one year.
Choose a strong, unique password, and use an API token rather than sharing credentials.
No system is perfectly secure. We do not hold a SOC 2 report or an ISO 27001 certificate.
8. Your choices and rights#
- Access and portability. Signed-in users can download the personal data held in their account from Account > Personal data, including the door events that name them and the doors they opened from CamRA (section 2.9).
- Correction. Edit your account details in the same area, or ask your administrator.
- Deletion. You can delete your own account from Account > Delete account. You are signed out everywhere and your app sign-ins and connected applications are revoked straight away; the account is deleted 7 days later, and we email you a link to cancel before then. An account that is the only owner of an organisation that still holds cameras, agents, other members or billing history must hand that organisation over first, or ask us. Deletion of a Tenant organisation that holds data is handled by us on written request to help@camra.ai.
- Marketing. We do not send marketing email from the product. Notification email and push can be turned off per alert subscription, and push for all of your devices at once.
- Cookies. Manage them in your browser (section 2.8).
8.1 California residents#
Under the California Consumer Privacy Act, as amended, and where we act as the business:
Categories of personal information we have collected in the last 12 months: identifiers (name, email, account identifiers and the Microsoft, Google or Apple account identifiers of people who sign in with them, device push tokens, IP address, and the cookie IDs our website sets); commercial information (billing and usage records); internet or network activity (application logs, and the pages viewed and interactions on our website); approximate location derived from the IP address of website visitors; and, where a Tenant's site captures you, audio-visual information — video imagery, vehicle imagery, and the plate, appearance vector and caption data derived from it. We collect these from you, from your organisation's administrator, from Microsoft, Google or Apple when you sign in with one of them, and automatically from our systems, from Tenant cameras and from visits to our website.
Our website. The cookie IDs, website activity and approximate location above are collected on camra.ai to understand and improve the website. Google (Google Analytics) and Microsoft (Microsoft Clarity) process them as our service providers. They are not sold or shared for cross-context behavioural advertising.
Sources, purposes and disclosures are in sections 2, 3 and 5. Each category above is disclosed to subprocessors for a business purpose.
Sensitive personal information. We do not collect government identifiers, financial account numbers, precise geolocation, racial or ethnic origin, religious beliefs, health data, or biometric information for the purpose of uniquely identifying a person. Whether the appearance vectors in section 2.3 are "biometric information" under any given statute is a question we flag openly in section 9 rather than answer for you.
Do Not Sell or Share My Personal Information. We do not sell personal information and do not share it for cross-context behavioural advertising, so we do not provide a "Do Not Sell or Share" link. You can still turn off the website's analytics: choose Decline in the website's cookie banner or under Cookie settings in its footer, block cookies in your browser, or install Google's opt-out browser add-on (https://tools.google.com/dlpage/gaoptout).
Your rights are to know, access, correct, delete, obtain a portable copy, and not be discriminated against for exercising them. Exercise them at help@camra.ai. We will verify your request against the email on your account or, for a request about footage, by working with the Tenant that controls it. An authorised agent may submit a request with written proof of authority.
When we act as a service provider, we process camera and parking data only on the Tenant's documented instructions, we do not retain, use or disclose it for any other purpose, we do not combine it with data from other sources except as permitted, and we certify that we understand and will comply with these restrictions. Send a consumer request about a site's footage to that site's operator.
9. A note on biometric and plate-reading laws#
We would rather flag this than bury it.
Appearance vectors. For person detections, CamRA computes a numerical vector describing overall appearance, used to follow the same person within a single recording; it is not currently used to match people across recordings. CamRA does no facial recognition: it does not detect, crop, measure or match faces, and it stores no face template. Whether an appearance vector nonetheless falls inside a state biometric privacy statute — Illinois' Biometric Information Privacy Act, the Texas Capture or Use of Biometric Identifier Act, or Washington's biometric law — is a question of state law, and a Tenant operating in those states should take its own advice before enabling object detection on its cameras, which is what turns the appearance vectors on (there is no separate switch).
Licence plates. Several states regulate automatic licence plate recognition, including who may operate it, what it may be used for and how long plate data may be kept. CamRA keeps plate history indefinitely by default. A Tenant is responsible for confirming that this is lawful where its cameras are.
Audio. CamRA records no audio, which keeps it outside one-party and two-party consent recording statutes. If that ever changes we will update this policy before shipping it.
10. Children#
CamRA is a business product. It is not directed to children, and we do not knowingly collect personal information from anyone under 16 through our website or apps. A Tenant's cameras may of course capture a minor who walks past them; that footage is the Tenant's responsibility under section 1.2. If you believe we hold information collected directly from a child, write to help@camra.ai.
11. Where your information is held, and international transfers#
CamRA runs in the United States. Tenant recordings and metadata are stored in Microsoft Azure's East US region. We do not offer data residency outside the United States. Analytics for our website, camra.ai (section 2.8), is processed by Google (Google Analytics) and Microsoft (Microsoft Clarity) in the United States.
Some subprocessors operate globally and may process limited data outside the United States: Apple, when it delivers a push notification to a device wherever that device is; Microsoft, Google and Apple when you sign in with them; PlateRecognizer (ParkPow, Inc.), whose processing location is set by its own service; and Vast.ai, Inc., whose rented computers may process feedback contributions (section 3) wherever the computer we rent is. The Subprocessor list says what each one receives.
12. Changes#
We will post any updated policy here with a new effective date. For a material change we will notify Tenant administrators by email before it takes effect.
13. Contact#
G.I.S., Inc., doing business as VirtuWorks 3850 Bird Road, Suite 103, Miami, FL 33146 help@camra.ai