Frequently Asked Questions
Answers to the questions eConnect hears most often from casinos, stadiums, and venues, covering facial recognition, POS Connect, license plate recognition, Red Light Green Light, privacy, and support. Search below or filter by topic.
189 questions
Yes. eConnect layers facial recognition and analytics over the cameras a venue already runs, with no camera replacement required. Results depend on placement rather than new hardware: dedicated, eye-level, choke-point cameras enroll far better than wide overview views, and cameras under about 720p are often not enough.
More than most properties realize. Operators report that manual surveillance catches only about 10 percent of people who return after a ban. After deploying facial recognition, the same operators report catching 8 times more at the lowest admitted figure, and up to 30 times more. One banned patron attempted re-entry 19 separate times before being caught at a side entrance.
In cooperative conditions - a good enrollment photo, decent lighting, and the subject facing the camera - eConnect reports match accuracy approaching 100 percent, and 99 percent or better overall in NIST-measured testing. Accuracy is driven by image quality, not luck: overhead cameras that capture hats instead of faces, backlit doorways, and poor enrollment photos are what cause misses. Camera-angle optimization alone moves typical properties from roughly 95 percent into the 99 percent range.
Retention is set by your property's data policy rather than a fixed product default. Enrollment records persist until they are removed, and detection history can be archived and purged at the server level through administrative data policy. Confirm the exact retention configured for your deployment with eConnect support.
Yes. eClear Access Control uses the face as the credential instead of a card or fob. Because a face cannot be cloned the way a low-frequency RFID badge can be copied with a cheap device such as a Flipper Zero, it removes the credential-cloning risk entirely, and access becomes contactless.
Indefinitely. An exported video stays available until you choose to delete it.
90 days by default. Longer retention can be configured for your deployment.
Yes. Contact support@econnect.tv and the support team will help configure an alternate export destination.
No. eConnect is read-only with respect to your POS. It receives transaction data and correlates it with video; it does not write back to or control the POS system.
Yes. Alerts can be delivered as on-screen popups inside your VMS, as push notifications to the eC Alerts mobile app on iOS and Android, and as email pushes where the network allows outbound mail. Alerts carry the enrollment photo, tags, and visit history so a responder has context immediately.
It measures the geometry of a face and compares it against a database of enrolled images. Where a person can reliably recognize around 1,500 faces, the system compares against thousands of records continuously and never stops paying attention.
Sub-one-second at entry points. Identity is confirmed in milliseconds, which is what makes it usable at a door without creating a queue.
No. The engine creates a uniquely differentiated face record even when the person is unknown, and alerts and history attach to that face. If a name is attached later, for example from a police BOLO, every prior unknown sighting retroactively resolves to that person. As one operator put it: I do not need to know your name, I just need to know your face.
Yes. That is one of the strongest arguments for face over document checks. Subjects using false identities are still recognized, because the face persists across aliases and across years.
Matches have been made against social-media photos that were decades old, and LinkedIn-quality images are good enough to enroll from.
Close, well-lit, cooperative, and front-facing. The rule is enroll from the best images, recognize from everywhere. Marginal enrollment shots pollute the database and cause bad matches, and bad matches are the single fastest way for operators to lose trust in the system.
Cage windows, TITO and sports-betting kiosks, and ID-scan podiums. Subjects have dwell time, consistent lighting, a fixed distance, and a reason to stand still, which produces the strongest enrollments - stronger still when tied to the transaction data.
Employees first, since they are the most frequent visitors and face matching beats hand scanners on both speed and accuracy. Then VIPs through loyalty enrollment. Then everyone previously ejected. When importing historical cases, do the highest-impact ones first - you only get one chance to start the database right.
Yes. The platform supports bulk enrollment of third-party images and watchlists, and operators routinely import historical cases from systems such as iTrack. Prioritize the highest-impact cases first.
Both. Search by face works across live feeds and recorded video, and you can search by uploading an image or capturing a frame.
Effectively immediate. A police-supplied photo can be loaded and checked against recent presence in roughly 20 seconds, and investigations that previously took hours collapse to minutes once a decent face shot exists.
It maps the network of people who repeatedly appear alongside a subject, turning one identified face into a web of known associates. It surfaces individuals seen within 5 seconds before or 90 seconds after the subject on at least 3 separate occasions, and the strength of each connection is shown by the weight of the line between profiles.
Yes. The parameters are adjustable, including expanding to multiple degrees of separation - two or three hops out from the original subject.
No. It works on uniquely differentiated faces, so associates can be mapped even when none of their names are known.
A $240,000 VIP safe robbery was proven to be an inside job when the supposed victim's face was run against history and found associating with the two perpetrators - and getting out of the getaway car - roughly two weeks earlier.
Partially. Recognition algorithms focus on the area around the eyes, which vendors optimized during mask mandates. Properties that need reliable capture typically require masks to be lowered at the door so every face is captured.
Yes. Deployments have flagged edge cases including identical twins and fraudulent IDs in real time.
Duplicate face records can be merged into a single identity from within the facial recognition tools.
Yes. Faces can be searched by image, by name or description, by tag, and through the Cameras tab.
Yes. Subject activity can be viewed by date, and detection records include the detector name, timestamp, time zone, match confidence, and the detection photograph.
Collections answer who this person is - Employees, VIPs, Watch Lists, Regular Customers. Tags describe the person's current state on top of that grouping. Collection membership also controls which individuals are visible to downstream systems such as Live Monitor filters, Face Verify kiosks, and pub/sub publishers.
Yes, and it is one of the most-cited reasons operators buy it. Never miss a VIP is one of eConnect's five core benefits, and the same recognition that flags a banned patron lets a host greet a high-value guest at the door.
Yes. The technology can recognize celebrities, athletes, and social-media influencers with 60,000 or more followers - a single positive post can organically reach an audience equivalent to three T-Mobile Arenas.
Launderers avoid player cards and keep transactions under alert thresholds, so they are invisible to card-based monitoring. Correlating transactions to faces identifies uncarded players, flags suspicious TITO ticket activity, and surfaces offset betting at sports kiosks.
Yes. The platform supports Title 31 reporting obligations such as bill-stuffing detection, and eConnect is building an integration to forward case details to a leading compliance-reporting system so compliance staff can file the required reports.
Yes. Organized rings advertise on social media to sign up new-member cards, share a pre-agreed PIN, and harvest 90 days of new-customer free-play offers using many cards and IDs against a single face. Face recognition removes the fraud because the face is the constant.
Yes. Flagging people who damage machines or structures - a single iDeck can run about $1,500 - lets a property identify and recover thousands when those individuals return.
Yes, and employees are the highest-value enrollment group because they are the most frequent visitors. Combined with POS data, face recognition ties register exceptions to the specific person who caused them, and it has caught cases as unusual as an employee secretly living in break rooms for weeks.
Investigators have succeeded with very little. In one case a masked robber was identified from a distinctive printed t-shirt: the team found the shirt's artwork online, cropped and enrolled the face printed on it, and located unmasked frames of the same person.
eConnect processes more than 10,000 live camera channels, is connected to over 300,000 cameras across its customer base, and matches millions of faces every month.
A self-service face verification kiosk that runs in a browser on any device with no installer. A guest looks at the camera and sees a full-screen colored overlay telling them to proceed or check in with security. It is available live at faceverify.econnect.ai.
Green means welcome - recognized and in good standing. Yellow is a soft prompt to check in at the security podium, typically for first-time visitors or routine confirmations. Red is the same instruction with a firmer visual signal for staff awareness. The colors and messages are fully customizable.
No. On-screen text stays neutral and helpful, and the guest is never shown a reason for their result. Only the operator sees the underlying detail.
None beyond a device with a browser and a camera. It runs on a phone, a tablet - a wall-mounted iPad or Android tablet is the most common deployment - or a PC or kiosk in browser kiosk mode. An optional Fully Kiosk Browser integration supports locked-down Android.
Yes. Live Monitor runs as a locked-down full-screen dashboard: hide the application menu, disable the settings gear, disable pause and play, disable inline person editing, and hide person and detector names on public-facing screens. The whole configuration is encoded into a shareable URL for fleet deployment.
The Live Monitor configuration string is compressed, not encrypted - anyone with the URL can reproduce that dashboard configuration, so store it securely. Face Verify's shareable URL is encrypted and deliberately excludes the Identity server credentials.
Adjust the detection confidence thresholds, refine tag configuration, update the subject database with better images, and consider location-based filtering. The general guidance is to start conservatively, test during low-activity periods, and adjust from experience.
Verify the eConnect connection status, confirm the alert preferences are configured, and check that the user's permissions include alert access. If alerts are missing for specific people, verify their subject tags and review camera positioning and image quality.
No. Alerts should be timely, actionable, and routed only to the team that needs them. Sensitive investigations can be kept in a private bucket visible only to a small surveillance team, so a subject can be tracked daily without any all-staff notification.
They should. Alerts are configured to expire based on expected dwell time - a moving subject at an entrance expires faster than someone transacting at the cage.
Yes, and that is a deliberate design point. Alerts use snapshots - the enrollment photo, the tag, and visit history - so the alert can travel to a host or a manager even where raw surveillance video is not permitted to leave the surveillance room.
One tribal property handling thousands of guests per weekend reports roughly 15 to 20 alerts on a Friday or Saturday.
No. Acknowledging an alert closes it on all other machines, and Auto Acknowledge coordinates responses automatically across a multi-operator room so work is not duplicated.
An alert option that automatically opens a subject-specific tab on the primary monitor and keeps it updated in real time as that person moves through the property and triggers further alerts.
Trafficking is typically one degree separated from other crimes, so it surfaces during other investigations. Suspected individuals are flagged into a private investigative bucket, the team reviews daily who is on property and who they arrived with, and association mapping exposes the wider network. Missing-person photos supplied by police can be checked against recent presence in about 20 seconds.
There is a real tension here. Entrance signage serves as attestation and matters legally, particularly under Illinois BIPA. But operators who work trafficking and organized crime cases keep the specific capability close to the chest, because publicizing it invites evasion - the same pattern already seen with license plate recognition.
It correlates point-of-sale transaction data with camera video, so a register exception is not just a line in a report - it is an event you can watch. Every void, discount, refund, and no-sale is tied to the footage that captured it.
Sixteen defined event types: Void, No Sale, Discount, Refund, Comp, Employee Meal, Check Transfer, Check Merge, Manual Price Entry, High Check Total, Low Check Total, Excessive Quantity, Split Tender, Tip Adjustment, Rounding or Change Discrepancy, and Time Outside Operating Hours. Each carries a numeric identifier so investigators can filter on it.
Short ringing - ringing up a cheaper item or nothing and pocketing the difference. Floating receipts - reusing an old check on a later similar transaction to steal the full amount. Line item voids - deleting rung items to lower the total. Discounts - applying a discount on a cash sale and keeping the difference. No Sale - popping the drawer without a sale, often paired with short ringing.
Yes. Manager voids are a recognized theft method, and managers who leave their POS swipe card or password with trusted employees enable further theft. Manager activity warrants the same scrutiny as line staff.
As it happens. Transaction data is available immediately for exception monitoring and alerting, so suspicious activity is surfaced in real time rather than discovered in a later audit.
Through a secure REST API with JWT authentication. POS vendors and system integrators push transaction data into the platform, where it powers real-time analytics, exception monitoring, and loss-prevention insight.
Yes. Developers validate integrations against a live server through the Dev Center at devcenter.econnect.tv, without needing the eConnect team involved. Developer support is at dev@econnect.tv.
Cameras are associated to POS terminals within the platform, which is what links each transaction to the footage of the lane where it happened.
Position it to capture the patron's face, the transaction, and the terminal screen in a single field of view - typically behind the cash register. Avoid high overhead mounts, which capture the tops of heads instead of faces.
Yes. POS Connect supports investigating a single employee's shift and tracking that employee across multiple terminals or revenue centers.
Yes. The Query Builder supports advanced queries, multi-item searches, saved queries that can be edited later, and an aggregation tool for rolling data up.
Yes. POS Connect supports searching directly by check number.
A POS Connect report that surfaces patterns in employee transaction behavior over time, rather than showing individual exceptions in isolation.
Flags mark suspicious transactions so they can be grouped, reviewed, and followed up rather than getting lost in transaction volume.
Yes, and that is the point of running POS Connect alongside facial recognition. Transactions are linked to the person actually at the terminal, which defeats shared logins and borrowed swipe cards.
Yes. The platform integrates with TITO, cage, and kiosk systems, and AML forensics ties facial recognition to TITO and cage transactions.
Yes. At least one deployment links ATM monitoring to individual guests alongside cage transaction verification by face.
Export from a saved case. The exported file is fully self-contained - it includes an offline Windows player, so recipients need no eConnect software to view it, and transaction overlays and facial recognition tags travel with the video.
Yes. All exported video is digitally watermarked to protect the integrity of the footage and help prevent tampering, which supports its use as case evidence.
Yes. Cases support attachments, saved video, multiple incident types, and an activity log that tracks incident progress over time.
Yes. Face profile reports can be exported as PDF.
Dashboards are user-built and customizable. You can create and customize dashboards, add a facial recognition live feed, adjust grid columns, change graph colors, and enable auto-refresh for wall displays.
eConnect's frictionless entry system. It combines an ID scan with facial recognition for returning guests, so identity is confirmed at the door in milliseconds. The principle is simple: green means go, red means check.
No - it means you stop checking the same ID repeatedly. One New York casino is legally required to scan every guest's ID; facial recognition lets returning guests skip the repeat check while the property stays fully compliant. In the operator's words: we needed to check every ID, but we did not need to do it every time.
One government-owned New York casino processes up to 10,000 guests a day through a single-door entry system using Red Light Green Light.
No. The system automatically detects banned individuals and self-excluded patrons and flags edge cases such as identical twins and fraudulent IDs in real time, while operating inside New York's strict surveillance and data privacy regulations. The framing used by the operator who deployed it: this is not about spying, it is about simplifying.
Yes. Marketing kiosks with facial recognition let guests claim promotional items without presenting an ID or a wallet.
Yes. That is the frictionless VIP entry use case - recognizing the people who matter the instant they arrive so hosts can greet or route them without adding a checkpoint.
No. It runs on the cameras a venue already operates. No separate entry hardware is required for identification.
The entrance is the key touchpoint where excluded patrons can be intercepted before they reach the floor. Pairing license plate recognition with ID scanning at that point helps staff distinguish VIPs from excluded players before anyone gets inside.
Yes. At least one deployment covers workforce compliance and contractor tracking with automatic badge printing.
Because RFID badges can be cloned. Cheap, widely available devices such as the Flipper Zero copy low-frequency RFID cards in seconds, giving an attacker the same access as a trusted employee. A face cannot be cloned or emulated, and access becomes contactless at the same time.
Yes. Face matching is faster and more accurate than hand scanners, and some venues retired their hand scanners after COVID in favor of it.
Yes. eClear covers face management for access control and time and attendance, and is available from the Cloud Portal.
Plate Connect reads plates from existing LPR hardware. As with faces, results depend on dedicating and positioning the camera properly rather than on buying a new one.
Yes. Advanced LPR ties plate reads to the people driving the vehicles, so a plate read is not an isolated event - it links to a known person through facial recognition.
A real-time view of the parking lot that pairs plate recognition with facial recognition, so venue teams know who is arriving before guests reach the door.
Yes. Plate Connect supports fuzzy similarity search on plates.
Yes. Plates can be added to monitoring and hot lists, and matching reads generate real-time alerts through the same alerting system as faces.
Through the Events Bridge API using your own external ID. There are calls to monitor a plate, unmonitor it, check whether a given externalId is currently monitored, and retrieve every plate you have under monitoring.
It records plate details and identifies banned vehicles before entry, giving staff warning at the lot rather than at the door.
Yes. Capturing vehicle details supports fast response to vandalism and theft cases that would otherwise have no starting point.
Yes. LPR events, hot list integration, and vehicle tracking are part of every eConnect VMS integration, with alerts surfacing natively in the VMS interface.
Yes, which is why operators keep detection capabilities confidential. Evasion following public awareness is a pattern already observed with license plate recognition, and it informs how properties talk about facial recognition.
Five certified VMS platforms: Mirasys, Genetec Security Center, Dallmeier Hemisphere, Synectics, and Intellicene. Every integration delivers face recognition, license plate recognition, real-time alerts, and native embedding of eConnect tools inside the existing VMS interface.
Genetec Security Center versions 5.10 through 5.13, via a certified integration covering face recognition, LPR, and POS data overlay.
Yes. eConnect completed official Genetec Security Center certification, announced April 2025, confirming interoperability with Genetec's unified security platform.
No, that is the point of native UI embedding. eConnect tools appear inside the VMS your operators already use - alerts arrive in the Genetec tray by priority, or through the eConnect icon in the Mirasys toolbar.
Real-time facial recognition delivered over MQTT, with a native eConnect UI embedded in SeMSy 5.
Casino management systems, player tracking and loyalty systems, POS systems, TITO, cage and kiosks, ID and passport scanners, sports-betting kiosks, and Omnigo or CIP reporting systems. Alerts and profile data can also flow onto the venue message bus for hosts, marketing, and operations.
Yes. Both on-premise and cloud deployments are supported. Cloud deployments use a customer-specific address at customername.econnectcloud.com; on-premise deployments run against your own server host on port 5009.
Yes. On-premises deployment keeps all traffic on the private network, self-signed certificates are supported for private deployments, and IP whitelisting is available for webhook endpoints.
JWT bearer tokens. A client logs in once at the auth endpoint to obtain a token, sends it on every protected call, and renews it before expiry. Every endpoint enforces its own minimum permission on top of that.
Face images and biometric data are encrypted in transit, all communications require HTTPS, external IDs are isolated per partner, and webhook payloads are secured with partner-specific authentication.
The intermediary service between partner systems and eConnect backends. It accepts monitoring requests using the partner's own external IDs, handles enrollment and matching against the Identities API for faces and eConnect Core for plates, manages webhook callbacks on detection, and maintains the mapping between partner IDs and internal identities.
Yes. Events Bridge maps your externalId to the internal person ID or plate record, so you keep your proprietary identifier scheme without compromising system integrity.
As HTTP POST requests to your configured endpoint. Authentication supports Basic Auth or Bearer Token, retry logic uses configurable attempts with exponential backoff, and the payload carries your original externalId plus additional fields.
Events Bridge maintains monitoring state through backend outages. Detection events are queued and processed when the system recovers, and webhook delivery retries against failed partner endpoints.
No. A single API call propagates to all connected endpoints. Face systems are distributed across multiple Identities API instances and LPR across multiple eConnect Core instances, with Events Bridge handling connection management and synchronization.
Publish is fire-and-forget: it returns 200 OK with an empty body and feeds the recognition engine. PublishWithResponse is the synchronous counterpart and returns the detected faces immediately, with largestFaceOnly and allowDoubleDetection options. Both require the Face Publishing permission.
Two GET endpoints, one keyed by personId and one by faceId. Both support paging with skip and take, time bounds with epochStartMs and epochEndMs, and sort order via dateAscending. Each result carries confidence, UTC timestamp, IANA time zone, detector name, and the detection image. Requires the Read Detections permission.
Yes. Enrollment photos are retrieved by faceId and detection photos by faceId and detectionId, both returned as JPEG to any authenticated caller. File documents can be uploaded and downloaded with the Add and Read Identity Files permissions.
Yes. Publishing points and subscriptions are first-class features with their own permission categories, and collection membership controls which identities the pub/sub publishers can see.
Yes. The eConnect MCP Server connects assistants such as Claude, ChatGPT, and VS Code Copilot directly to an installation, exposing 62 tools across 7 categories at mcp.econnect.ai. You query live data and run reports in natural language without opening the portal.
Four modules: face recognition including enrolled subjects, detections, and watch lists; LPR events, hot lists, and detector status; POS transactions, exceptions, and register status; and casino operations covering sessions, player profiles, cage transactions, and Title 31 compliance.
Tokens are encrypted with AES-256-GCM. A token is valid for 7 days by default, configurable up to 30 days, and is reusable across sessions until it expires.
Yes. Cloud deployment is recommended for internet-accessible installations, and an on-premises deployment keeps all MCP traffic on the private network for closed environments.
The central dashboard at econnectcloud.com for launching every eConnect cloud application you are permitted to use. It provides single sign-on, an app launcher, and user access management. Identities, eClear, and Face Rec are the highlighted applications.
The Windows application used in surveillance rooms as the central command interface. Operators search by face, monitor live face and LPR detection streams filtered by location, tag, and category, manage and acknowledge alerts, configure thresholds and escalation, generate reports, export detection logs, and manage subject profiles.
Chrome, Edge, Firefox, and Safari.
Very. The system is strictly permission-driven and menus differ per user based on role. Categories include Identities, Live Monitoring, Users and Roles administration, Tags, Identity Entity Fields, Publishing Points, Subscriptions, Audit Logs, and Administration. A user with no module permission sees no menu items at all.
A System Administrator at your site, through System Administration then Users and Roles.
Yes. The audit log records identity creation, updates, and deletion, tag changes, face enrollment and removal, alias, address and notes edits, custom field updates, document changes, and user or role changes. Each entry captures who, what changed with before and after values, when, and the target identity.
No. It is append-only and cannot be edited from the UI. Entries are added by operator actions only, and can be archived or purged solely through administrative data policy at the server level.
Yes. The Person Editor includes an Audit History section scoped to that individual, while the site-wide Audit page handles broader queries and can be filtered by date range, user, identity, and event type.
Yes. The eC Alerts app delivers real-time alerts on iOS and Android, and there is an eCU Mobile App for management. Enabling a user requires Mobile Alerts Enabled on their account plus membership in the Mobile Alerts logical group and alert-bridge permission in eConnect Cloud.
It is increasingly a liability. Air-gapped surveillance systems never receive patch updates and become vulnerable within a few years. Modern deployments depend on cooperation between progressive IT and surveillance teams, balancing cloud services against on-premise AI, with API bridges to CMS and marketing platforms designed carefully.
Most are not. They are typically un-networked serial or USB devices meant to check age and detect altered IDs. Networking them is a physical-layer lift, but once on the message bus they eliminate repeated ID checks at the door, hotel desk, and cage, and they feed high-quality images into enrollment.
Probably less. Online flows increasingly do photo plus face match, and standalone physical license scanning is expected to fade as a result.
Yes, and it is in use across the industry, but the obligations vary by jurisdiction. Entrance signage constitutes attestation, which matters under Illinois BIPA. California requires an opt-out and removal capability. Recommended language belongs in loyalty terms and conditions and in employee handbooks. Confirm your own state's requirements with counsel.
The distinction that matters is between privacy and anonymity. There is no privacy in a public space; what facial recognition removes is anonymity. The technology can even keep a subject anonymous to floor staff while retaining the data electronically for Title 31 filing.
California requires an opt-out and removal capability, and identity deletion is a supported, audited operation. Confirm the removal process that applies in your jurisdiction with eConnect and your counsel.
At the entrance. Entrance signage constitutes attestation. Supporting language should also appear in loyalty program terms and conditions and in employee handbooks.
A responsible-gaming program in which individuals voluntarily bar themselves from gaming venues to help manage problem gambling. Venues are expected to help enforce those commitments by keeping enrolled individuals from gambling on the premises.
Because human recognition does not scale. A person can maintain about 150 close relationships and reliably recognize roughly 1,500 faces. A venue's exclusion list, checked against thousands of arriving guests, exceeds what memory can do.
Yes. Several gaming control boards expose their self-exclusion list via API, and eConnect can integrate so barred individuals are flagged automatically rather than only at ID-scan entrances. The platform also supports state exclusion lists and bulk watchlist enrollment.
Regulatory fines from state and regional gaming boards reaching into the thousands of dollars, plus negative publicity and reputational damage when violations become public.
Yes. Selfie onboarding supports remote pre-registration and self-exclusion enrollment.
Increasingly so. Operators report regulators are coming on board, summed up as: no one wants to go back to tape.
Responsible AI is a standing pillar of eConnect's public platform framing, presented alongside Who We Protect, Platform, Partners, and Results.
That is a policy decision the technology forces you to make rather than one it makes for you. With new knowledge comes new responsibility: whether past behavior predicts future conduct, and how to balance safety against inclusivity, is the core tension operators now face.
Publicly available mug shots can be imported into facial recognition databases. Nevada alone has 7,386 registered sex offenders, with about 4,500 residing near the Las Vegas Strip.
Enrollments and approvals should pass through an owner with authority to reject bad or bad-intentioned entries before they go live - especially before any watchlist is shared between properties.
Yes. Suspected individuals can be flagged into a private bucket visible only to a small surveillance team, so daily review happens without any property-wide alert.
Yes. Live Monitor has explicit Hide Person Name and Hide Detector Name settings for exactly this, alongside the other kiosk lockdown controls.
Yes. External IDs are isolated per partner, and webhook payloads are secured with partner-specific authentication.
Confirm with eConnect for your specific contract and deployment. This is not addressed in the current published documentation.
It depends on your deployment. On-premise installations keep data on your own servers; cloud installations run under your customer-specific econnectcloud.com instance. Confirm the region and hosting arrangement for your contract with eConnect.
Confirm current certifications directly with eConnect. The published documentation covers encryption in transit, JWT authentication, and per-partner isolation, but does not list formal audit certifications.
eConnect provides lifetime support, training, and updates, with 24/7/365 US-based live support. Lifetime IT support is a stated core benefit of the platform.
eConnect reports a Net Promoter Score of 98 percent, with customer satisfaction at 98.67 percent happy and 1.33 percent neutral. It won the 2024 Industry Excellence Award for Customer Support from Gaming and Leisure Magazine.
Four stated pillars: immediate response times to minimize downtime, expert technical guidance across software, cameras, and servers, seamless system integration assistance, and long-standing industry partnership.
Email support@econnect.tv or call (702) 523-8786. Developer questions go to dev@econnect.tv.
Yes. eConnect University is a free certification program offering interactive training, digital badges, and certification tracks. Lifetime training is included with the platform.
Go to the eConnect University registration page, create a learner profile, verify your email to activate the account, then browse the available courses and certification tracks.
Not required, but it helps. Operators report the up-front work of importing known profiles and prioritizing high-impact cases pays dividends, and that a dedicated data analyst accelerates it considerably.
Create the user in the desktop application and in eConnect Cloud with alert-bridge permission. Then under Setup, Users, User List, enable Mobile Alerts Enabled and save. Add the user to the Mobile Alerts logical group. The user then signs into the desktop app, connects their Cloud credentials under Setup, Home, and signs into eC Alerts with the same credentials.
New devices ship with a default PIN that is not published publicly. Request it from eConnect support at 702-523-8786 or support@econnect.tv, then set your own PIN under General.
Yes, settings save to browser local storage and survive reloads and power cycles. But they are specific to that browser and device, and clearing site data, using private mode, or uninstalling the browser erases them. Use the encrypted shareable URL as your backup and fleet deployment method.
Yes. Sample and test candidate locations before committing to them. Whether an existing camera works depends on its age, resolution, height, and distance, and 720p is often not enough.
Start conservatively and adjust from experience. Test alert preferences during low-activity periods, train every operator on the response procedure, establish clear communication protocols between staff, and document and review alert effectiveness regularly.
A Las Vegas-based software company providing AI facial-recognition and behavioral-analytics software for casinos, stadiums, and hospitality venues. Its mission is to turn passive surveillance into proactive intelligence.
Founded January 4, 2009 by Henry Valentino - around 15 years in business. The company originated in casino surveillance and grew into the category leader for gaming protection software.
More than 400 clients protected, deployed across 100 or more casinos and venues.
Henry Valentino is President and CEO, George DiGrandi is COO, Guido Arias is CFO, Travis Whidden is CTO, Malcolm Rutherford is EVP of Strategic Operations, and Matthew Carrier is VP of Sales.
In the United States. eConnect is headquartered in Las Vegas and its software is US-developed and US-supported.
Yes. eConnect is licensed for gaming jurisdictions.
By deployment share, yes. The 4th Annual International Casino Surveillance Survey put eConnect at 33 percent of casino facial recognition deployments, roughly 1.5 times the next vendor - Oosto/Anyvision at 22 percent, SAFR/Vision Labs and Briefcam at 6 percent each, and Clearview at 2 percent.
The 2021 G&L Gaming and Hospitality Platinum Award for identity management, voted by a roundtable of gaming and hospitality executives, and the 2024 Gaming and Leisure Industry Excellence Award for Customer Support.
Its recognition engine is ranked among the most accurate in NIST testing.
It is built specifically for casinos rather than adapted to them, backed by a team drawn from casino surveillance, with integrations into gaming-specific systems - TITO, cage, player tracking, Title 31 reporting - that general-purpose vendors do not carry.
Gaming venues and casinos, stadiums and arenas, and hospitality, retail, and restaurants.
Facial Recognition, Red Light Green Light, POS Connect, Plate Connect for LPR, eClear Access Control, eClear I.D. Scanner, RatingsConnect, Baccarat Analyzer, TITO Connect, the eC Alerts App, and the eCU Mobile App.
Pricing is quoted per deployment. For scale, operators describe the cost as often less than a single security guard while covering surveillance, operations, compliance, and marketing. Contact eConnect at (702) 523-8786 for a quote.
Spread it across departments. The system serves surveillance, operations, compliance, and marketing simultaneously, and sharing the cost across those budgets speeds approval. Some customers assign a dollar value per tag, such as felony ejections, to quantify return directly.
It comes from several directions at once: recovering property damage costs, eliminating promotional and ratings fraud, catching ban evaders that manual surveillance misses roughly 90 percent of, reducing investigation time from hours to minutes, and improving VIP recognition. eConnect frames it as turning the existing camera investment from a cost center into a profit center.
No. The core positioning is upgrade, do not overhaul - the software integrates into any legacy video security system and layers onto the cameras and VMS already in place.
Request a demo through econnect.ai, or call (702) 523-8786.
