Rules for working with channels

1. Using the functionality of the website https://www.revicom.ltd/ (hereinafter referred to as the Site) or (and) software of the Revicom (the Contractor), you confirm your consent with this Rules for working with channels (including all the conditions of the technical requirements Operators contained in the Rules), hereinafter referred to as the "Rules". If you do not agree with the conditions set forth in the Rules, you must refuse to use the specified Site or (and) software, the consequences and procedure for such refusal are determined by the Agreement.

2. The terms and definitions contained in the Rules have the following meanings:

2.1. Contractor - Revicom LTD., a Cyprus company, located at Georgiou Katsounotou, 6, Limassol, 3036 Cyprus.

2.2. Customer, You - a person who has entered into an Agreement with the Contractor for the provision of Services.

2.3. Agreement - the Terms of service or a written agreement, including additional agreements and annexes thereto, concluded between the Contractor and the Customer, containing a link or indication of these Rules.

2.4. The meaning of terms and definitions that are not indicated in the Rules are determined in accordance with the provisions of the Agreement.

3. In all that is not regulated by the Rules, the Customer and the Contractor are guided by the terms of the Agreement (the Terms of service). In cases of conflict between the provisions of the Agreement (the Terms of service) and the Rules, the provisions of the Rules shall prevail.

If there are conflicts between these Rules and the rules of the Operator, located on the official website of the Operator, the rules of the Operator shall prevail.

In all other respects that are not regulated by the Rules, the Parties are guided by the terms of the Agreement (the Terms of service). In cases of conflict between the provisions of the Agreement (the Terms of service) of the Rules, the provisions of the Rules shall prevail.

4. The transfer of messages from the Customer to the Contractor takes place in the System via the Internet. The transport protocol for information transfer is agreed upon by the Parties additionally, possible protocols: HTTP, HTTPS (SSL), SMPP. If necessary, it is possible to set up a VPN tunnel.

5. In cases determined by the Contractor, access to the Contractor's System is carried out only from the agreed IP addresses of the Customer. At the same time, the Parties undertake to agree on the list of IP addresses from which the Customer will have access to the System prior to the commencement of the provision of the Services.

6. In the event of an accident or disconnection of the equipment or communication channels of the Contractor, the Customer is obliged to follow the instructions of the Contractor to limit the bandwidth of the connection of his equipment with the technical means of the Contractor in order to prevent their overload.

7. It is forbidden to send messages to telephone numbers of subscribers, where the numbers of subscribers in a numerical value for a certain period of time, sorted in ascending (or descending) order, are a sequence with an equal difference (step) between the nearest values.

8. The values of the speed of receiving and processing messages specified in the paragraphs "Bandwidth of communication channels between the Customer and the Contractor" are default values and, if necessary, are agreed upon by the Parties additionally.

SMS-MESSAGES

Definition of terms used in this section:

SMS-MESSAGE (MESSAGE) - a text message sent in the networks of GSM mobile operators. The size, length (number of symbols) and other technical requirements for SMS-Messages (Segments of an SMS-Message) are set by the Contractor in the Rules (taking into account the requirements of the Operator). The Contractor reserves the right to determine the format (encoding) of SMS-messages based on the current technical requirements of the Operator.

SEGMENTATION - splitting the original Message into several parts, each of which is a separate Message (SEGMENT). Segmentation is used to meet the requirements of communication standards for the size of the Message.

The meanings of other terms are determined in accordance with the provisions of the Agreement.

9. The Operator has set the following technical requirements for Messages:

9.1. Content requirements for Messages sent via SMPP and HTTPs protocols :

9.1.1. The maximum size of one Segment is 140 bytes (including UDH headers and/or other service information).

9.1.2. The maximum number of symbols (hereinafter, symbols are also understood as letters, unless otherwise indicated separately) in one segment (Message) for a one-part Message:

9.1.2.1. for Messages that contain Latin symbols specified in Table No. 1 below (hereinafter referred to as the TABLE) - 140 or 160 symbols (depending on the rules of the Operator through which the Message is transmitted);

9.1.2.2. for Messages containing symbols not specified in the Table - 70 symbols (provided that the size of each symbol is 2 bytes; if the size of the symbol is 3 or more bytes, the specified maximum number of symbol will be reduced).

9.1.3. Maximum number of symbols in one segment of a Message consisting of several segments:

9.1.3.1. for Messages that contain Latin symbols specified in the Table - 134 or 153 symbols (depending on the rules of the Operator through which the Message is transmitted);

9.1.3.2. for messages that contain symbols not listed in the Table - 67 symbols (provided that the size of each symbol is 2 bytes; if the size of the symbol is 3 or more bytes, the specified maximum number of symbol will be reduced).

9.1.4. Used encodings:

9.1.4.1. In cases of connection via the SMPP protocol:

- 0x00 – for Messages containing Latin symbols specified in the Table, one of the following encodings can be used (optional): GSM Default Alphabet , ASCII, ISO-8859-1;

- 0x08 - for Messages that contain non-Latin symbols, i.e. any symbols other than those specified in the Table are encoded in UCS-2 (ISO/IEC-10646).

9.1.4.2. In cases of connection via the HTTP, HTTPS(s) protocol:

- the applicable encoding is UTF-8.

9.1.5. The table of symbols, the use of which is allowed in the Messages (Segments) specified in clauses 9.1.2.1, 9.1.3.1 of Rules:

Table No. 1

Symbol	Name	Symbol	Name
0	Digit Zero	f	Latin Small Letter f
1	Digit One	G	Latin Capital Letter G
2	Digit Two	g	Latin Small Letter g
3	Digit Three	H	Latin Capital Letter H
4	Digit Four	h	Latin Small Letter h
5	Digit Five	I	Latin Capital Letter I
6	Digit Six	i	Latin Small Letter i
7	Digit Seven	J	Latin Capital Letter J
8	Digit Eight	j	Latin Small Letter j
9	Digit Nine	K	Latin Capital Letter K
'	Apostrophe	k	Latin Small Letter k
-	Hyphen-Minus	L	Latin Capital Letter L
!	Exclamation Mark	l	Latin Small Letter l
"	Quotation Mark	M	Latin Capital Letter M
#	Number Sign	m	Latin Small Letter m
$	Dollar Sign	N	Latin Capital Letter N
%	Percent Sign	n	Latin Small Letter n
&	Ampersand	O	Latin Capital Letter O
(	Left Parenthesis	o	Latin Small Letter o
)	Right Parenthesis	P	Latin Capital Letter P
*	Asterisk	p	Latin Small Letter p
,	Comma	Q	Latin Capital Letter Q
.	Dot	q	Latin Small Letter q
/	Solidus	R	Latin Capital Letter R
:	Colon	r	Latin Small Letter r
;	Semicolon	S	Latin Capital Letter S
?	Question Mark	s	Latin Small Letter s
@	Commercial At	T	Latin Capital Letter T
_	Low Line	t	Latin Small Letter t
+	Plus Sign	U	Latin Capital Letter U
<	Less-Than Sign	u	Latin Small Letter u
=	Equals Sign	V	Latin Capital Letter V
>	Greater-Than Sign	v	Latin Small Letter v
A	Latin Capital Letter A	W	Latin Capital Letter W
a	Latin Small Letter a	w	Latin Small Letter w
B	Latin Capital Letter B	X	Latin Capital Letter X
b	Latin Small Letter b	x	Latin Small Letter x
C	Latin Capital Letter C	Y	Latin Capital Letter Y
c	Latin Small Letter c	y	Latin Small Letter y
D	Latin Capital Letter D	Z	Latin Capital Letter Z
d	Latin Small Letter d	z	Latin Small Letter z
E	Latin Capital Letter E	CR	Carriage Return
e	Latin Small Letter e	LF	Line Feed
F	Latin Capital Letter F	SP	Space

9.1.6. The cost of the Services is determined depending on the number of Message Segments sent by the Contractor in accordance with the terms of the Agreement. At the same time, in the case of Segmentation, the cost of sending 1 (one) Message Segment is equal to the cost of sending 1 (one) Message.

9.1.7. The Customer undertakes to choose the applicable encoding of Messages, if the appropriate choice is provided for by the Rules, and to agree on its application with the Contractor.

The use of symbols not specified in the Table may result in the replacement/removal of differing symbols, or the use of UCS-2 or UTF-8 encoding (and appropriate Segmentation).

The Contractor shall not be liable if the Customer sends Messages in an encoding that is not agreed with the Contractor and (or) does not comply with the Rules (and/or the rules of the Operators), if this entailed the replacement / deletion of the above symbols and (or) the use of a different encoding and (or) Segmentation of Messages and (or) repeated or multiple payment for Messages. The Customer undertakes to fully pay for the Contractor's Services and reimburse the Contractor's expenses and (or) losses incurred in connection with Message Segmentation.

9. 2. Message text can be registered with the Operator as a Template. The tariffication of the message by the Operator depends on the type of the Template.

9.3. The minimum time interval between attempts to send two messages to one Subscriber with the same text and Sender's Name is 10 minutes.

9.4. Messages are sorted by the Contractor in terms of the Subscriber's belonging to a certain Operator in order to determine the correct route for its delivery to the Operator's Communication Center.

9.5. The SMS-Center of the Contractor must ensure the prioritization of SMS-traffic, according to the requirements of the Customer:

9.5.1. Messages related to high-priority traffic are sent by the Contractor with a bandwidth of 100 (one hundred) Messages per second via the HTTPs or SMPP protocol. The time of delivery of the Message to the Operator, provided that the Subscriber's phone is turned on, is in the network coverage area and is serviced by the Operator, is 15 (fifteen) seconds for 95% of the Messages. In this case, deviations within 1% are considered acceptable.

9.5.2. Messages related to normal traffic are sent by the Contractor with a bandwidth of 50 (fifty) Messages per second via the HTTPs or SMPP protocol. The time of delivery of the Message to the Operator, provided that the Subscriber's phone is turned on, is in the network coverage area and is serviced by the Operator, is 60 (sixty) seconds for 80% of the Messages. In this case, deviations within 5% are considered acceptable.

9.6. The bandwidth of the communication channels between the Customer and the Contractor must meet the following parameters:

9.6.1. Recommended waiting time for a response to a request to send messages (Customer -> Contractor):

- for messages sent via SMPP protocol – up to 5 seconds;

- for messages sent via the HTTPs protocol - up to 30 seconds.

9.6.2. The speed of receiving messages from the Customer to the Contractor and processing messages by the Contractor's platform for transmitting messages to subsequent networks is 100 messages/sec.

9.6.3. The maximum time for message delivery attempts is 24 hours;

9.6.4. The minimum time for message delivery attempts is 1 minute.