KIYA Communications
Products Coverage Developers Pricing Contact
Get in touch
Products Coverage Developers Pricing Contact Get in touch
Legal · Privacy

Privacy Policy

This policy explains how KIYA Communications collects, uses, stores, and protects information when you visit our website, register an account, or send messages through our SMS gateway.

Last updated · 02 September 2024

On this page

  1. Who we are
  2. Scope of this policy
  3. Data we collect
  4. How we use data
  5. Legal bases (GDPR)
  6. Message content & metadata
  7. One-time passwords
  8. Sharing & sub-processors
  9. International transfers
  10. Retention
  11. Security
  12. Your rights
  13. Cookies
  14. Children
  15. Changes to this policy
  16. Contact us

1. Who we are

KIYA Communications (“KIYA”, “we”, “us”) is a company registered in the Republic of Seychelles, with its registered office in Victoria, Mahé. We operate a global SMS gateway used by businesses to send marketing campaigns, transactional notifications, and one-time passwords (OTPs) to their end users. For the purposes of EU/UK data protection law, KIYA generally acts as a data processor on behalf of the business that uses our platform (our “customer”), and as a data controller for information we collect directly from website visitors and account holders.

You can reach our team at [email protected].

2. Scope of this policy

This policy applies to:

  • Visitors to kiyasms.com and related marketing pages.
  • Customers who register an account, view documentation, or contact our sales team.
  • End users of our customers, whose phone numbers and message content are processed through our gateway.

If you are an end user receiving an SMS sent through KIYA, the business that contacted you is the data controller. Please refer to their privacy notice for details about how they obtained your number and what they do with your data. We process that information only on their instructions.

3. Data we collect

3.1 Account & billing information

  • Company name, business address, VAT or tax identifier.
  • Account holder name, work email, work phone number.
  • Authentication data (hashed passwords, API keys, 2FA settings).
  • Billing details processed through our payment provider (we do not store full card numbers).

3.2 Usage & technical data

  • Log data such as IP address, browser, device type, and timestamps.
  • API request metadata (endpoint, status, latency, error codes).
  • Dashboard activity (logins, settings changes, campaign events).

3.3 Messaging traffic

  • Sender ID (alphanumeric or numeric).
  • Recipient mobile number (MSISDN) supplied by the customer.
  • Message body, encoding, segments, and any media identifiers.
  • Delivery metadata: route, country, operator, status, timestamps, and error codes returned by carriers.

4. How we use data

  • To deliver, route, and monitor SMS traffic across our global carrier network.
  • To authenticate API requests and protect customer accounts.
  • To detect fraud, SIM-farms, SMS pumping, and abusive traffic patterns.
  • To produce delivery reports, analytics, and aggregated insights for the customer.
  • To bill customers and reconcile carrier costs.
  • To respond to customer support, sales, and compliance enquiries.
  • To comply with legal obligations and lawful requests from regulators.

5. Legal bases (GDPR)

Where the EU/UK GDPR applies, we rely on the following legal bases:

  • Contract — to provide the gateway service to our customers and operate their account.
  • Legitimate interests — to secure the platform, prevent fraud, improve performance, and conduct limited B2B marketing to existing customers.
  • Legal obligation — to retain billing records, respond to lawful authority requests, and comply with telecom regulations.
  • Consent — for optional cookies and any direct marketing where consent is required.

6. Message content & metadata

Message bodies and recipient numbers submitted through our API are processed strictly to deliver each message and to produce delivery receipts. We do not read message content for advertising purposes and we do not sell message content or recipient numbers.

Carriers and downstream operators may also process message metadata in order to deliver the SMS over their network; this is unavoidable for any SMS service worldwide and is governed by their own terms.

7. One-time passwords (OTPs)

OTP traffic receives the same confidentiality controls as any other message. By default we minimise persistence of OTP message bodies in long-term storage, and they are not exposed in customer-facing logs after the configured retention window. Customers can configure shorter retention or content-redaction on a per-route basis.

8. Sharing & sub-processors

We share data only with parties strictly necessary to operate the service:

  • Mobile network operators (MNOs) and SMS aggregators who terminate traffic in destination countries.
  • Cloud infrastructure providers hosting our platform and databases.
  • Payment processors for billing.
  • Compliance, anti-fraud, and analytics providers bound by confidentiality.
  • Authorities where we are legally required to disclose information.

A current list of sub-processors is available on request from [email protected].

9. International transfers

SMS is inherently global: a message sent to a recipient abroad must be transmitted to operators in that country. Where personal data leaves the EEA or UK, we rely on appropriate safeguards such as Standard Contractual Clauses (SCCs), the UK International Data Transfer Addendum, or adequacy decisions where available.

10. Retention

  • Message content — retained for up to 30 days by default, then deleted or irreversibly redacted. Customers can shorten this period.
  • Delivery metadata — retained for up to 13 months for analytics, dispute resolution, and carrier reconciliation.
  • Account & billing records — retained for as long as the account is active and for up to 10 years after closure where required by tax or telecom law.
  • Security & access logs — retained for up to 24 months.

11. Security

We protect data using a layered approach: TLS 1.2+ in transit, encryption at rest, isolated production environments, role-based access controls, mandatory 2FA for staff, key rotation, and continuous monitoring. We follow recognised industry frameworks for SMS aggregators and review our controls regularly. No system is perfectly secure, but we work hard to minimise risk and to notify customers promptly of incidents that affect them.

12. Your rights

Subject to local law, individuals have rights to access, correct, delete, restrict, or object to the processing of their personal data, and to data portability. Where we act as a processor for one of our customers, we will refer your request to that customer and assist them in responding. Where we act as a controller, please email [email protected] and we will respond within applicable statutory timeframes.

If you are in the EEA or UK, you may also lodge a complaint with your local data protection authority.

13. Cookies

Our marketing site uses a small number of strictly necessary cookies and, where you consent, simple analytics cookies that help us understand which pages are useful. We do not run third-party advertising trackers.

14. Children

KIYA is a B2B service intended for businesses and their authorised personnel. Our website is not directed at children, and we do not knowingly collect personal data from anyone under the age of 16.

15. Changes to this policy

We may update this policy from time to time. When we make material changes, we will update the “Last updated” date above and, where appropriate, notify customers through the dashboard or by email.

16. Contact us

Questions about this policy or how we handle your data?

  • Registered office: KIYA Communications, Victoria, Mahé, Republic of Seychelles
  • Email: [email protected]
  • Phone: +90 532 487 21 06
© 2026 KIYA Communications. All rights reserved.
Home Privacy Terms