Use without business pairing
Dailer can be used without pairing to a business server. Contacts and Android call history are used on the phone for calling, caller identification, search, blocking and history management, subject to the default-phone role and Android permissions. Contact or history management can change the relevant device records when you request it.
The camera or selected QR image is processed on the phone for pairing. Optional voice search opens the speech-recognition service installed on the device, which handles speech under its own policy. History files you export go to your chosen destination.
Pairing and transmitted information
Business pairing is optional. A disclosure identifies the relevant HTTPS server and asks for approval before pairing. Pairing sends the temporary code, installation and request identifiers, device manufacturer/model, Android platform and app version. The server returns a phone identity and credential, business/store assignment and POS assignment where configured.
Call events send the other party’s number, direction, states such as ringing/answered/ended/missed/rejected and phone, call and event identifiers. The server records time and may derive duration or match the number to records held by the business. Business pairing does not upload contact names or photographs and does not upload call-audio recordings.
Pairing is optional. Call phone numbers and installation/device identifiers are sent to the business server for phone functionality and retained there; this is not merely transient on-device processing.
Background control and audio
While remote control is enabled, status requests can send availability, call state, number and call identifier. For an active call they may include speaker and microphone-mute state; these are control states rather than audio content.
Authorized workspace staff can request answer, reject, hangup, callback and supported speaker/mute controls. Command acknowledgments contain identifiers, outcome and reason. Enabled events and commands may be exchanged in the background. Conversation audio is handled by the phone system; Dailer does not record or upload call audio.
Local storage and cleanup limits
The pairing credential and temporary secret are protected with Android Keystore. Installation and replay-protection records are stored locally outside Android backup; the app excludes its databases, preferences and files from cloud backup and device transfer.
The local queue can retain numbers, states, times and destination identifiers for unacknowledged events. Acknowledged events are removed. Cleanup during enqueueing or synchronization caps the queue at 300 events, removes entries older than seven days and drops an event after twelve failed attempts. Cleanup occurs during app activity; on a powered-off or inactive phone, information may remain until the next cleanup activity.
Stopping, disconnecting and deletion
“Stop call control” pauses remote commands while event uploads can continue. “Remove pairing” removes the local credential and pairing attempt and stops new/queued uploads and commands. A request already in progress may finish. Removing pairing preserves the installation identity and does not immediately erase every local row or server history.
Clearing Android app data removes the app’s local information, but not Android’s system history, exported files or business-server records. Dailer does not create a human account; QR pairing identifies the installation and business. Email info@nursoft.al or contact the administrator about server information. We target acknowledgement and manual handling within seven calendar days. Actual erasure timing and applicable retention will be explained according to the information and responsible business.
Optional customer card and privacy choices
In versions that include the customer card, it starts disabled. Enabling it requires a separate notice and approval for the currently paired business. During an eligible call, the app sends the paired installation identifier, call identifier and full phone number to that business’s HTTPS server to request a matching customer record.
The business server may return the customer’s name and a summary of the latest eligible confirmed order: its reference, date, status, total, products and quantities, and the delivery address saved on that same order. Missing or ambiguous information is not replaced with another customer’s record. This information is used to help authorized staff recognize the customer and assist with the call; it is not sent to an advertising service.
The card is held in memory and hidden when the phone locks. It is cleared when the call ends or changes, the card is disabled, pairing changes or is removed, or the app’s process ends. The phone can request it again during an eligible call after unlocking. This does not delete the business’s underlying order or customer records, which follow that business’s retention and deletion rules.
Settings in supported versions let you separately enable or disable the customer card and the privacy controls for displaying names, photos and notes. Optional local call notes remain on the phone; enabling the customer card does not upload those notes, contact photos or the address book. You can turn off the card without stopping normal phone calls.
Repeating the latest order in Ordex
When you enable Repeat latest order and tap it for a compatible current call, the app opens the installed Ordex app with only the paired server origin and call/device identifiers. It does not pass connection credentials, phone numbers, names, products or addresses to that app. An authorized operator must review and explicitly confirm a draft in Ordex; this action does not automatically place an order. This option resets when pairing is replaced or removed.
Optional battery-status sharing
Battery-status sharing starts off. It requires the existing connection disclosure and a separate approval in Settings for the current paired credential. When the paired system supports and enables this feature, your separate approval and running call control allow existing status requests to include available battery percentage and charging state with the paired device ID. If the system does not confirm support, the app does not read or send battery measurements. Unknown values remain unknown. These readings help a compatible panel display the phone’s last reported condition. No extra permission or separate request is added, and the app keeps no local history of battery measurements. The setting and pairing-specific approval are stored locally. Turning this feature off stops new battery readings and measurements in later requests; an existing status request can report that sharing is disabled. Stopping call control stops polling and battery readings without sending an extra disabled-state request. Removing or replacing the pairing clears its approval. A request already in progress may complete. These actions do not request erasure of data already received by the server. No server alert threshold or retention period is promised.
Your choices and deletion
Connection is optional. Stop call control pauses remote commands, customer-card lookups and battery-status polling; call-event uploads can continue. Remove pairing stops new and queued call uploads, except a request already in progress, and removes the local pairing credential. It does not erase existing server history. The business operator retains server history for its operations. Contact that operator or info@nursoft.al for access or deletion requests, subject to applicable obligations. No fixed server deletion schedule is promised. Clearing Android app storage removes this app’s local data; it does not delete server history, Android’s call log or exported files.
Optional decline-and-SMS modes · version 8.0.18
Two independent Settings modes start off: manual decline with SMS and automatic decline with SMS. With manual mode on, pressing the red Decline button or using the rejection swipe on the incoming-call screen rejects an eligible call and requests the current saved SMS reply. With manual mode off, those gestures reject without SMS. There is no separate SMS call button. Ordinary rejection from a notification or paired POS panel never requests SMS.
With automatic mode on, the app itself rejects every eligible incoming call and requests the saved reply without a button press or a separate action for each call, including while locked. With both modes off, ordinary rejection sends no SMS and these modes do not reject calls automatically.
An SMS request requires this app to be the default phone app and the exact call to be ringing, confirmed incoming, outside a conference, with a visible usable telephone number and Android text-response support. For a hidden-number, SIP, unsupported or otherwise ineligible call, the red button or rejection swipe still rejects without SMS; automatic mode leaves that call ringing. If automatic handling and a manual action occur together, only the first claimed action can proceed; no second reply is requested. Missed calls, ending active calls, outgoing calls, reminders and number-blocking rules do not trigger these SMS modes.
The editable reply template is stored locally. The recipient number and reply text are passed to Android Telecom and the messaging service/carrier for the SIM associated with that call. Carrier charges may apply; longer replies may be split into several SMS messages and charged separately. Sending depends on Android, the installed messaging service, SIM and network availability. Ordex Dailer cannot confirm that the message was sent or delivered and does not automatically retry it.
Reply text is not sent to the paired business server. Existing manual quick replies and opening the messaging app remain separate actions. Any message history kept by the messaging service is separate from this app's local template.
Optional decline-and-SMS modes · version 8.0.19 (819)
Up to and including version 8.0.18 (818), rejection from an incoming-call notification or pop-up does not request SMS. The following behavior applies to version 8.0.19 (819), which is not yet published.
Two independent Settings modes start off: manual decline with SMS and automatic decline with SMS. With manual mode on, pressing Decline in the incoming-call notification or pop-up, pressing the red Decline button, or using the rejection swipe on the incoming-call screen rejects an eligible call and requests the current saved SMS reply. With manual mode off, those actions reject without SMS. There is no separate SMS call button. Rejection from a paired POS panel never requests SMS.
With automatic mode on, the app itself rejects every eligible incoming call and requests the saved reply without a button press or a separate action for each call, including while locked. With both modes off, ordinary rejection sends no SMS and these modes do not reject calls automatically.
An SMS request requires this app to be the default phone app and the exact call to be ringing, confirmed incoming, outside a conference, with a visible usable telephone number and Android text-response support. For a hidden-number, SIP, unsupported or otherwise ineligible call, manual rejection from the incoming-call notification, pop-up or full call screen still rejects without SMS; automatic mode leaves that call ringing. If automatic handling and a manual action occur together, only the first claimed action can proceed; no second reply is requested. Missed calls, ending active calls, outgoing calls, reminders and number-blocking rules do not trigger these SMS modes.
The editable reply template is stored locally. The recipient number and reply text are passed to Android Telecom and the messaging service/carrier for the SIM associated with that call. Carrier charges may apply; longer replies may be split into several SMS messages and charged separately. Sending depends on Android, the installed messaging service, SIM and network availability. Ordex Dailer cannot confirm that the message was sent or delivered and does not automatically retry it.
Reply text is not sent to the paired business server. Existing manual quick replies and opening the messaging app remain separate actions. Any message history kept by the messaging service is separate from this app's local template.
Automatic decline status on a linked POS · version 8.0.20 (820)
Version 8.0.20 retains the decline and SMS options described for version 8.0.19 and adds a status notice for linked business POS terminals. When the paired business server supports this notice, the app's authenticated device check-in includes an on/off value indicating whether automatic decline with SMS is active on the phone. The app checks the setting, access to calls and whether a usable reply is configured on the phone. The status report does not include SMS reply text.
The business server keeps the value in the latest status for the paired device and replaces it on the next check-in. Authorized users at the linked POS can see an active status and the phone's assigned name. The POS stops showing the notice when the status is off or the phone's check-in is no longer recent.
