Privacy Policy - SMS Business Card

Revision date: September 18, 2026.

Data controller / app owner: ABS SMS LLC (ООО «АБС СМС»).

Address: 170M Yantarnaya Street, Ufa, Russia.

Contact for data and account deletion requests: abssms@mail.ru.

This Policy describes data processing by the SMS Business Card mobile application (SMS-Business Card. Automation / СМС-Визитка), application ID com.smsvizitka.smsvizitka, and the controller's related services.

The App lets you configure replies to calls and messages, create templates, manage contacts and connect integrations. Rules determine the App's actions. Accessing data, recording history and sending a reply are separate operations: turning a reply off does not always stop receiving an event or storing its history. The conditions are explained below.

1. Data we process

1.1. Account and profile. The name, email address, phone number and business-card details you provide during registration, sign-in and profile setup; account, profile and device identifiers and authentication information. These data are used for sign-in, synchronization, licensing and support.

1.2. SMS. When permission to receive SMS is granted, the App receives the sender, text, arrival time and SIM information of incoming messages. Incoming SMS are recorded in a local journal, including before enabled actions are checked. A message can therefore be read and stored even when auto-reply is off or no matching rule exists. Text from some service senders is not stored in the journal.

The text is used to evaluate SMS chatbot conditions and prepare a reply; the number is used to match a contact, create a card and perform selected actions. The App also processes the recipient, text, time and delivery result of outgoing SMS sent by your rules, integration commands or manual actions. Server transfer conditions are in Section 5.

1.3. Calls. With the required access granted, the App processes phone numbers, call type, time and duration. These data support automation triggers, call history, contact cards, imports and reports. Use of call data is not limited to auto-replies.

1.4. Phone state and SIM. Call state, active SIM information, subscription ID, slot and carrier are used to determine call timing, select a SIM and apply sending settings.

1.5. Contacts. The App reads names and numbers to match events and apply filters. When the relevant features are used, it creates or updates phonebook entries and customer cards. App cards may be synchronized with the server; these are distinct from the system phonebook.

1.6. Messenger notifications. When system notification access is granted, the App processes the text, sender, phone number or conversation identifier, source app and event information available in notifications from supported messengers. Messenger call notifications are also used. See Section 4.

1.7. Accessibility access. The Accessibility service accesses messenger interface elements needed to send a message, including chat information, input fields, buttons and the operation's state. See Section 3.

1.8. Templates and attachments. Template text and the images, videos, audio and documents you select, their names and related metadata are processed to prepare, synchronize and send messages. Uploading a template attachment to the server transmits the file's contents, not just its name or path.

1.9. Technical data. App and device identifiers, model, OS and App versions, push tokens, usage events, error information and diagnostic logs are used for service operation, analytics and troubleshooting. Logs may contain information about processed events, contacts and messages. Servers and service providers also receive an IP address during network communication.

1.10. Purchases. The App processes purchase, subscription and license information. Google handles payments made through Google Play; the App does not receive your payment card details from Google Play.

The App does not request Android location permission.

2. How we use data

• Execute scenarios you configure and manual sending commands.
• Identify call types and incoming-message conditions and select replies.
• Maintain history, prevent duplicate actions and retry delivery.
• Create and synchronize profiles, cards, rules, templates and attachments.
• Operate connected CRM systems, spreadsheets, APIs and other integrations.
• Manage accounts, licenses, purchases and push notifications.
• Provide diagnostics, support and App usage analysis.

We do not sell personal data. Transfers for App operation, support and connected services are described in Section 5.

3. Accessibility Service

After you enable the service in Android settings, the App uses it to send messages in supported messengers according to your rules and commands. The service opens the selected chat, interacts with the message field, selected attachment and send button, and checks interface elements needed to complete the operation.

Interface access is used to automate sending. The recipient and message content are determined by your settings or sending command. The message and attachments themselves are delivered to the recipient through the selected messenger.

You can disable the service in Android accessibility settings. Sending operations that require it will stop working. Disabling Accessibility does not disable separately granted notification access or delete history. Incoming notification and diagnostic data processing are described separately below.

4. Notification access

When system notification access is enabled, the App receives notifications from supported messengers. Their data are used to identify messages and calls and work with cards, history and integrations. When the chatbot is enabled, the App evaluates rules and may reply using the notification reply mechanism.

Notification processing is not limited to enabled auto-replies. If a sender's number is identified and a profile and server contact card are available, incoming-message data may be transmitted to the controller's server, subject to the personal-contact filter. This flow does not require enabling the SMS-to-CRM action. Turning off a messenger reply rule alone does not stop this processing.

To stop the App receiving new notifications, disable its notification access in Android settings. This does not automatically delete data already stored or transmitted.

5. Data recipients and retention

5.1. The controller's servers

The App communicates with the controller's server at smsvizitka.com. Account, profile, device and license information, synchronized cards, rules, templates and attachments, event information and diagnostic data are transmitted when the corresponding App operations are used.

The conditions for transmitting message content differ:

• Incoming SMS: a message is queued for transfer to the controller when the send-to-CRM action is allowed at processing time and applicable plan restrictions and contact filters are satisfied. The number, text and event, profile and contact card information are transmitted. The queue supports retries after connection failures; disabling the action should not be taken as confirmation that a previously queued transfer has been cancelled.
• SMS auto-reply or adding a sender to contacts: these actions alone do not place the SMS text in that CRM queue. The local journal, card synchronization, separately configured integrations and diagnostic paths have their own processing conditions.
• Messenger messages: the sender, text and related card may be transmitted during notification processing under the conditions in Section 4. These conditions differ from those for SMS.
• Diagnostics: error reports and logs may be transmitted to the controller and diagnostic services. Logs can be sent from the App and in response to a server service command; sending is not limited to the user pressing a report button.

5.2. Selected recipients and integrations

When you send SMS, the mobile carrier and recipient receive the data; when you send through a messenger, the corresponding service and recipient receive it. This also applies to attachments.

If you connect a third-party integration, the App transmits the information specified by its settings to the configured address: for example, a number and name, message text, event source and time, and card information. Incoming SMS and messenger messages are subject to source settings, filters and feature availability under your plan. Third-party integrations are enabled separately from the primary CRM flow; disabling one does not disable the other. Consider the recipient's data practices when choosing an integration.

5.3. Service providers

The App uses these services:

Providers may process data in other countries. Their practices and retention periods are described in the Google Privacy Policy, Firebase data information and OneSignal Privacy Policy.

5.4. Retention and deletion

On your device. Entries in the local incoming-SMS journal older than 30 days are removed when cleanup runs during App operation. If the App has not been launched, cleanup may occur later. This period applies specifically to the incoming-SMS journal; it does not mean that every copy of message text in chats, sending history, cards, reports and server systems is deleted within 30 days.

Chat and sending history, settings and other local data may remain until they are cleared or App data are removed through Android. Turning off a rule does not delete previously stored history. Removing App data does not delete messages held by recipients, system phonebook entries or separately saved files.

On the controller's servers. Data are retained during account use to the extent needed to provide the features. When an account is deleted, its associated personal data are deleted from the controller's servers within 30 days. Section 6 explains how to request deletion.

With other recipients. Data already received by message recipients or CRM systems and messengers you select are also under those recipients' control. Deleting an App account does not automatically delete their accounts or conversations. Retention of technical data by providers in Section 5.3 follows their own policies; 30 days is not a universal deletion period for every external service. Contact the controller using Section 6 for questions about deleting data we have transferred to providers.

6. Your rights and account deletion

You can request information about your data, correction and deletion by contacting abssms@mail.ru.

In the App: open “Cabinet”, select “Delete account” and confirm. A network connection is needed to submit the request. If it fails, retry or contact us by email.

Without the App: email abssms@mail.ru with the subject “SMS Business Card - account deletion”. Include the account email address or profile identifier so we can locate your data. If you cannot find the identifier, explain this in the email. Do not send your password or sign-in codes. We may need to verify that the data belong to you to protect the account.

The request covers the account and related server data, including the profile, synchronized cards, templates, attachments and stored event information. The controller's deletion period is up to 30 days. Uninstalling the App from your phone is not a request to delete the account from the server.

You can change rules and disable integrations in the App and revoke SMS, phone, contacts, notification and Accessibility access in Android settings. Revoking the corresponding permission limits further access but does not delete stored data. Turning off auto-reply is not a substitute for revoking incoming-SMS or notification access.

7. Data security

The controller's primary API uses HTTPS. We apply access controls and data protection measures during processing. Protection of transfers to third-party integration addresses you select also depends on the recipient and connection used. No transmission or storage method provides absolute security.

8. Children

The App is intended for business use by adults and is not intended for persons under 18. If you believe that a child's data have been provided to us, contact abssms@mail.ru so we can review and delete those data.

9. Changes to this Policy

We publish changes on the policy page and update the revision date. When a processing change requires a separate notice or consent, updating this page alone does not replace that step.

10. Contact

ABS SMS LLC (ООО «АБС СМС»)

170M Yantarnaya Street, Ufa, Russia.

For privacy, data access and account deletion requests: abssms@mail.ru.