<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article How secure is RCS for Business? in RCS</title>
    <link>https://community.sinch.com/t5/RCS/How-secure-is-RCS-for-Business/ta-p/16545</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;At a high level, RCS offers a branded, &lt;A href="https://sinch.com/blog/rcs-verified-senders/" target="_self"&gt;verified&lt;/A&gt;, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://sinch.com/blog/rcs-vs-sms/" target="_blank" rel="noreferrer noopener"&gt;richer messaging experience than SMS&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;– and this includes its more robust security.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Messages are encrypted in transit, which includes between the user’s end device (both iOS and Android) and Google and between Google and a messaging partner like Sinch. Messages on Google’s servers are encrypted at rest as well. Messages are not encrypted on the user’s device, and there are times when messages are unencrypted for policy, security, and spam reasons.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;RCS for Business helps establish more trust between businesses and consumers and protects against the uncertainty and threats of fraud and SMS&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://sinch.com/blog/what-is-smishing/" target="_blank" rel="noreferrer noopener"&gt;phishing&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;attacks.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;For more information about RCS for Business security, read this &lt;A href="https://sinch.com/blog/rcs-security/" target="_blank" rel="noopener"&gt;Sinch Blog article&lt;/A&gt;.&lt;/EM&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Thu, 19 Jun 2025 14:53:40 GMT</pubDate>
    <dc:creator>Shahzad_Ismail</dc:creator>
    <dc:date>2025-06-19T14:53:40Z</dc:date>
    <item>
      <title>How secure is RCS for Business?</title>
      <link>https://community.sinch.com/t5/RCS/How-secure-is-RCS-for-Business/ta-p/16545</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;At a high level, RCS offers a branded, &lt;A href="https://sinch.com/blog/rcs-verified-senders/" target="_self"&gt;verified&lt;/A&gt;, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://sinch.com/blog/rcs-vs-sms/" target="_blank" rel="noreferrer noopener"&gt;richer messaging experience than SMS&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;– and this includes its more robust security.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Messages are encrypted in transit, which includes between the user’s end device (both iOS and Android) and Google and between Google and a messaging partner like Sinch. Messages on Google’s servers are encrypted at rest as well. Messages are not encrypted on the user’s device, and there are times when messages are unencrypted for policy, security, and spam reasons.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;RCS for Business helps establish more trust between businesses and consumers and protects against the uncertainty and threats of fraud and SMS&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://sinch.com/blog/what-is-smishing/" target="_blank" rel="noreferrer noopener"&gt;phishing&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;attacks.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;For more information about RCS for Business security, read this &lt;A href="https://sinch.com/blog/rcs-security/" target="_blank" rel="noopener"&gt;Sinch Blog article&lt;/A&gt;.&lt;/EM&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 19 Jun 2025 14:53:40 GMT</pubDate>
      <guid>https://community.sinch.com/t5/RCS/How-secure-is-RCS-for-Business/ta-p/16545</guid>
      <dc:creator>Shahzad_Ismail</dc:creator>
      <dc:date>2025-06-19T14:53:40Z</dc:date>
    </item>
  </channel>
</rss>

