MYWATCHTOWER SUB-PROCESSOR LIST
Version 1.11 • Effective Date: October 18, 2026
This MyWatchtower Sub-processor List (this “List”) names the third parties that JEKA Software, Inc. (“JEKA”) engages to process Community Personal Data on JEKA’s behalf in connection with the Services (each, a “Sub-processor”). This List does not name vendors that process only JEKA’s own business records.
1. Definitions; Related Documents
1.1 Defined Terms. Capitalized terms used in this List have the meanings given in the MyWatchtower Data Processing Addendum (the “DPA”), and capitalized terms not defined in the DPA have the meanings given in the MyWatchtower Community Services Agreement (the “CSA”) or the Brivo Integration Addendum, as applicable, and “Reselling Integrator” has the meaning given in the MyWatchtower Terms of Service & End User License Agreement.
1.2 Related Documents. This List is the list referred to in DPA Section 7.3, in Section 4 of the MyWatchtower Platform Privacy Notice, and in Section B.2a of the MyWatchtower Terms of Service.
2. Publication; Record
2.1 Posting. JEKA posts this List at https://portal.jekasoftware.com/policies/subprocessors/ for informational purposes, and this List does not require acceptance by any person.
2.2 Record of Sub-processors. The List posted at that address is the current record of JEKA’s approved Sub-processors, and Annex C of a Community’s DPA reflects the entries that applied to that Community on the effective date of its DPA.
2.3 Earlier Versions. Published versions of this List are not edited after publication, and a copy of an earlier version is available on written request to legal@jekasoftware.com.
3. Changes to this List
3.1 New Sub-processors. JEKA adds a new Sub-processor to this List before that Sub-processor processes any Community Personal Data and, where practicable, at least 30 days in advance.
3.2 Urgent Replacements. Notwithstanding Section 3.1, JEKA may engage a replacement Sub-processor immediately for data security, business continuity or emergency reasons, in which case JEKA adds the replacement to this List and gives notice as soon as practicable.
3.3 Change Notices. A Community may subscribe to notices of changes to this List by email to legal@jekasoftware.com with the subject line “Subscribe: Sub-processor List”. Each version of this List states its version number and effective date.
3.4 Objections. A Community’s right to object to a new Sub-processor, and the procedure and remedies that apply following an objection, are as set out in DPA Section 7.3.
4. Current Sub-processors
4.1 Form of Entry. Each entry in this Section 4 states the Sub-processor’s function, the Community Personal Data it processes, its location and its status.
4.2 Voxtelesys, LLC. Function: telephone lines and telephone numbers for the telephone service JEKA provides to a Community under its Telephone and Internet Service Schedule on a hosted telephone system; voice and SMS delivery for Kiosk voice calls and notifications over those lines. Data: telephone numbers; call audio and message content in transit; call and delivery metadata. Location: United States. Status: current, for the Communities whose telephone service runs on a hosted telephone system.
4.3 3CX. Function, Data and Status: the same as for Voxtelesys, LLC in Section 4.2, for the hosted telephone system those lines use. Location: United States, with U.S. headquarters in Tampa, Florida.
4.4 Twilio Inc. Function: SMS notification delivery; MWT Connect entry-request voice and video calls to residents and to a telephone number the Community designates for an Access Point, such as its gatehouse telephone. MWT Connect is not a telephone service and is not connected to 911 (CSA Section 5.1). Data: telephone numbers; message content; call and session metadata. Location: United States. Status: current. A Community MWT Connect number that reaches the Platform, answered by an automated assistant, is a planned feature and is not yet built. JEKA adds any provider for it to this List before it processes Community Personal Data.
4.5 Apple Inc. (Apple Push Notification service). Function: push notification delivery to the MyWatchtower application on iOS devices. Data: device tokens; notification content in transit. Location: United States. Status: current.
4.6 Google LLC (Firebase Cloud Messaging). Function: push notification delivery to the MyWatchtower application on Android devices. Data: device tokens; notification content in transit. Location: United States. Status: current.
4.7 The Servicing Integrator Named on a Community’s Order Form or Service Order. Function: servicing work for the Community’s account. It is the party JEKA schedules for warranty visits and the Community’s first contact for on-site matters (CSA Sections 2.5 and 4.4; where the Community’s Reselling Integrator bills the Community, Integrator Partner Agreement Sections 5.4 and 5.6). On-site work outside the warranty is not a Service; the Community arranges it with the Servicing Integrator or another licensed contractor of its choice. Data: the Community’s site configuration, equipment status and service history, and the Community Personal Data it can access in that role. It is bound by a written agreement that meets the requirements of DPA Section 4.3. Location: United States. Status: current. Approval: under the CSA, the Order Form naming it is the Community’s notice and approval (CSA Section 2.6).
4.8 HID Global Corporation. Function: orders, warranty service and support for the HID products JEKA supplies. Data: the Community’s name, site and contact details; equipment serial numbers; troubleshooting information. Location: United States; HID and its subcontractors may handle the information in other countries. Status: a Sub-processor only where a Community’s site uses HID products bought from an integrator partner of JEKA.
4.9 Microsoft Corporation (Microsoft Clarity). Function: web usage analytics for the MyWatchtower application. Data: device and usage data; session interaction data. Location: United States. Status: current. Where the application asks for the user’s consent to analytics, Microsoft Clarity collects no data until the user consents.
4.10 Google LLC (Google Analytics 4). Function: web usage analytics for the MyWatchtower application. Data: device and usage data; online identifiers. Location: United States. Status: current. Where the application asks for the user’s consent to analytics, Google Analytics 4 collects no data until the user consents.
4.11 Cloudflare, Inc. (Cloudflare Turnstile). Function: human-verification challenges and content delivery for web forms. Data: IP address; user agent; browser characteristics. Location: United States. Status: current.
4.12 Brivo Systems LLC. Function: cloud access-control software platform. Data: access credentials; access events. Location: United States. Status: a Sub-processor only under the Direct form of the Brivo Integration Addendum, where JEKA holds the Brivo Account.
4.13 Microsoft Corporation (Microsoft Azure). Function: hosting; production cloud computing for the Platform’s application programming interface and background services; email delivery through Azure Communication Services. Data: each category of Community Personal Data the Services process. Location: United States. Status: current.
4.14 Supabase, Inc. Function: hosting; production database, authentication and file storage for the Platform. Data: each category of Community Personal Data the Services store, including user account and credential data. Location: United States. Status: current.
4.15 Netlify, Inc. Function: hosting; delivery of the MyWatchtower web application (application files and edge network). Data: IP addresses and device and browser data of application users. Location: United States. Status: current.
4.16 Radar Labs, Inc. Function: maps in the MyWatchtower application, including the Community Log map and the map an Administrator uses to draw a door’s opening area. Data: the area a map shows; a location a user places on a map and the map image saved with a Community Log entry; IP addresses and device and browser data of users viewing a map. Location: United States. Status: current.
4.17 Pushy LLC. Function: push notification delivery to installations of the MyWatchtower application that have not yet moved to Apple or Google push. Data: device tokens; notification content in transit. Location: as Pushy LLC’s published terms state; JEKA is confirming it with the vendor and will state it here. Status: retiring. JEKA removes this entry when the last such installation updates.
4.18 Environmental Systems Research Institute, Inc. (Esri, ArcGIS). Function: satellite imagery and address search for door maps in the MyWatchtower application. Data: the area a map shows; an address an Administrator searches for. Location: United States. Status: current.
4.19 Network Concern, Inc. Function: administers the hosted telephone system and supplies internet access at the Communities where JEKA provides them under its Telephone and Internet Service Schedule. Data: telephone numbers; call metadata; the site’s telephone and network configuration. Location: United States. Status: current.
5. Parties That Are Not Sub-processors
5.1 Third-Party Platforms a Community Chooses. Third-Party Platforms a Community chooses, such as Eagle Eye Networks video services and Brivo under the Channel form of the Brivo Integration Addendum, are not Sub-processors in that role. Under the Channel form, the Integrator or the Community holds the Brivo Account. Each Third-Party Platform processes data under its own agreements and privacy policy.
5.2 Sign-in Providers. Facebook, Google and Apple are not Sub-processors when a user elects to sign in through them, and in that role each acts under its own terms.
6. Questions
6.1 Contact. Questions about this List may be directed to legal@jekasoftware.com, through the support portal at support.jekasoftware.com, or by mail to JEKA Software, Inc., 16703 Early Riser Avenue, Suite 533, Land O’ Lakes, FL 34638.