Privacy policy
Last updated: 23 September 2026
This policy explains the categories of information L2S Proximity may process, why they are used and the choices available to users and customer organisations. Exact processing depends on the features, integrations and mobile permissions enabled for a tenant. This policy applies to the L2S Proximity website, service and Android application with package name com.beamclientside101.
1. Who we are
L2S Proximity is published on Google Play under the developer name UniDL Technologies. The L2S Proximity product and service are owned and operated by FrontL Hawk Limited. Together, these identifiers describe the application, publisher and service provider associated with this policy. We provide communications, CRM, sales productivity, automation, AI-assisted, WhatsApp, reporting and mobile field-operation tools to organisations worldwide.
2. Our customer’s role
A customer organisation controls how its workspace is configured, which employees receive access and what business information is submitted. The organisation is responsible for giving required notices, establishing an appropriate lawful basis and complying with employment, communications and data-protection laws that apply where it operates.
3. Information we may handle
- Account information: names, email addresses, phone numbers, roles, membership and verification state.
- Business records: leads, customers, deals, sales, payments, inventory, notes, documents, tasks and reminders.
- Business communication activity: phone numbers, contact or CRM record identifiers, call direction, time, duration, outcome notes, follow-up steps and user-confirmed messaging activity associated with a lead or customer.
- Assistant interactions: messages, requested actions, confirmations, approvals and resulting activity involving Sophia.
- Field activity: work check-ins, check-outs, visits, location names, timestamps and GPS coordinates where enabled and permitted.
- Device contacts and call history: when permission is granted, contact names and phone numbers and device call-log entries used locally to provide the phone book, caller identification and Recents.
- Technical information: device, application instance, push-notification token, browser, network, security, diagnostic, analytics and service-usage information needed to operate, secure and improve the platform. Firebase Analytics may process an app instance identifier, Android advertising identifier where available, masked-IP-derived approximate location, and application lifecycle or screen-interaction events. These are used for analytics and reliability, not behavioural advertising by L2S Proximity.
4. Mobile GPS and distance information
With foreground location permission, L2S Proximity can record the GPS point and time associated with an agent’s explicit office check-in, office check-out or field-activity check-in. The Android app does not request background location permission and does not use these check-ins for continuous background location tracking.
Location information is intended for legitimate attendance, visit and field-operation records. It is sent only when the user starts the relevant action and the permission has been granted. It should not be used for undisclosed or disproportionate surveillance.
5. Device contacts, calls and messaging
L2S Dialer requests contact access to display and search the user’s on-device phone book and identify callers. The app does not upload the user’s complete device address book. When a user intentionally creates a business lead or customer, the details entered for that business record are sent to the organisation’s L2S workspace.
Call-log access is requested only after the user selects L2S Dialer as the device’s default phone application and separately approves the Android runtime permission. Device call history is used to show Recents and to match phone numbers locally. Private call history is not uploaded. For calls linked to an assigned business lead or customer, L2S may sync the number, business record, direction, start time, duration and user-entered report or next step to the organisation’s secure workspace for audit, follow-up and reporting.
The Android application does not request permission to read, receive, write or send SMS or MMS messages and does not read SMS content or device message history. A user may choose to open the device’s messaging application from L2S. If the user then confirms that a business message was sent, L2S may store the recipient business record and time of that user-confirmed activity; it does not collect the SMS body.
If a user deliberately starts an audio note during a call, microphone permission is requested at that moment. The resulting microphone recording is kept in the app’s private storage on that device and is not uploaded automatically. The feature may not capture the other caller’s audio. Users are responsible for obtaining any consent required by law.
6. How information is used
- Provide the service and connect activity to the correct tenant, user and record.
- Support sales workflows, follow-ups, field operations, reporting and coaching.
- Authenticate users, enforce access controls and investigate suspected misuse.
- Operate Sophia and supported automation requested by authorised users.
- Maintain, troubleshoot and improve service reliability and usability.
- Meet legal obligations and protect the rights and safety of customers and users.
We do not sell personal information, call logs or contact information, and we do not use call-log, contacts or location data for advertising.
7. Permissions and user choices
Mobile operating systems ask for permissions before protected device capabilities are available. L2S asks incrementally when a feature needs contacts, phone, call history, microphone, notifications or foreground location. A user can decline a request or later change access in Android settings. Call-log access is used only while L2S remains the default phone handler; L2S does not request SMS permissions. Denying a permission disables or limits only the related feature. Users should also contact their employer or company administrator about organisational monitoring policy.
8. Access, sharing and retention
Information is made available to authorised users in the relevant tenant according to role and responsibility. We use service providers where necessary for hosting, secure API delivery, Firebase analytics and push notifications, communications, security and support. They may process only the information needed to provide those services under applicable contractual and security obligations. We do not share device contacts or private call history with advertisers. Business records are retained according to customer, operational, security and legal requirements and are removed or anonymised when no longer required. On-device contacts, call history and audio notes remain subject to the user’s device controls; locally saved audio notes can be deleted in L2S Dialer.
9. Security
We use layered controls including encrypted connections, tenant-aware access, role-based permissions, protected sessions and accountable activity. No service can guarantee the elimination of every risk. Learn more on the Security and trust page.
10. Access, correction and deletion requests
Depending on applicable law and the organisation’s legitimate record obligations, users may request access to or correction or deletion of personal information. Employees should normally begin with their company administrator; other enquiries can be directed to us.
11. Contact and app identity
App: L2S Proximity (com.beamclientside101). Google Play developer: UniDL Technologies. Product and service operator: FrontL Hawk Limited. Privacy, access or deletion requests can be sent to info@l2s-proximity.co.ke or made by calling +254 700 112 042 / +254 106 139 320.