Send SMS to Kosovo: Complete Compliance Guide & API Integration 2025

How to Send SMS to Kosovo: Market Overview & Mobile Operators

Sending SMS messages to Kosovo requires understanding the market structure, mobile operators, and regulatory landscape. Kosovo has two main mobile operators – Vala (Kosovo Telecom, ~50% market share) and IPKO (~47% market share). Here's what you need to know before launching your SMS campaigns in Kosovo.

Market Conditions: When you send SMS in Kosovo, you'll work with a competitive telecommunications market. As of Q2 2024, Kosovo had 1.91 million mobile users with a penetration rate of 103.4%. Both operators have deployed 5G networks as of mid-2024, with Vala launching 5G services and IPKO completing 5G testing in July 2023 achieving speeds over 1.2Gbps. SMS messaging in Kosovo remains a reliable communication channel for business-to-consumer communications, authentication services, and transactional messaging. According to ARKEP's Q1 2024 data, mobile penetration reached 104.2% of the population with coverage spanning 100% of inhabited zones and 94% of Kosovo's territory. While OTT messaging apps like WhatsApp and Viber are popular in urban areas, SMS delivery rates remain consistently high across both feature phones and smartphones, typically exceeding 95% when proper formatting and compliance practices are followed.

SMS Features and Capabilities for Kosovo Messaging

When you send SMS to Kosovo, you'll have access to several key features. Kosovo supports standard SMS capabilities including concatenated messages and alphanumeric sender IDs, though two-way SMS functionality is limited.

Two-way SMS Support in Kosovo

Two-way SMS is not currently supported in Kosovo through major SMS providers. You cannot receive replies to your messages through standard SMS channels. For interactive communication, consider implementing alternative solutions such as web-based forms, WhatsApp Business API integration, or voice IVR systems that can be referenced in your SMS messages.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported for messages exceeding standard length limits.

Message length rules: Standard SMS length is 160 characters for GSM-7 encoding, 70 characters for UCS-2 encoding.

Concatenation billing example: A 320-character message in GSM-7 encoding splits into 3 segments (each segment 153 characters to accommodate concatenation headers). You are billed for 3 SMS messages. For UCS-2 encoding, a 140-character message splits into 3 segments (67 characters each), resulting in charges for 3 messages. Always account for concatenation when budgeting SMS campaigns.

Encoding considerations: Both GSM-7 and UCS-2 encodings are supported, though support may vary by sender ID type.

MMS Support

MMS messages are not directly supported in Kosovo. Instead, MMS content is automatically converted to SMS with an embedded URL link where recipients can view the multimedia content. User experience: Recipients receive a standard SMS containing a shortened URL. They must click the link to view images, videos, or other multimedia in their mobile browser. This method works across all device types but requires data connectivity to view content. Consider file size limits (typically 1-5MB) and hosting duration (usually 30 days) when using MMS-to-SMS conversion services.

Recipient Phone Number Compatibility

Number Portability in Kosovo

Number portability is available in Kosovo as of December 2023. ARKEP authorized the PXS&Botek consortium to provide number portability services for both mobile and fixed-line subscribers. This allows users to switch between Vala and IPKO while keeping their existing phone numbers. Businesses sending SMS should integrate with real-time number portability databases to ensure accurate message routing. Without proper integration, messages may be routed to the wrong carrier, causing delivery delays or failures. Most major SMS API providers handle number portability lookups automatically.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Kosovo. Attempts to send SMS to landline numbers will result in failed delivery and an error response (400 error code 21614 for Twilio API), with no charges applied to your account.

SMS Compliance Requirements in Kosovo: GDPR & Law 06/L-082

Kosovo has implemented Law No. 06/L-082 on Protection of Personal Data (effective February 13, 2019), which transposes the EU's GDPR. This law governs all marketing communications, including SMS. The Information and Privacy Agency (IPA) enforces compliance, with fines ranging from €400 to €40,000 for violations. Article 82 of Law 06/L-082 specifically addresses direct marketing violations, imposing fines between €2,000 and €4,000 for minor infringements and up to 2-4% of annual turnover for serious breaches. ARKEP (Regulatory Authority of Electronic and Postal Communications) oversees telecommunications services and technical compliance.

SMS Marketing Consent Requirements in Kosovo

Explicit Consent Requirements:

• Obtain written consent that is "clearly distinguishable from other matters"
• Use "intelligible and easily accessible" forms with "clear and plain language"
• Maintain records of how and when consent was obtained
• Include clear terms of service and privacy policy during opt-in
• Specify the types of messages users will receive and approximate frequency
• For direct marketing, you may collect limited personal data: name, address, telephone number, email, and fax number

Consent form checklist (based on Law 06/L-082 requirements):

• ☑ Clear statement of purpose: "I consent to receive promotional SMS messages from [Company Name]"
• ☑ Specify message types: "You will receive offers, promotions, and updates"
• ☑ Frequency disclosure: "Approximately 4-8 messages per month"
• ☑ Opt-out instructions: "Reply STOP to unsubscribe at any time"
• ☑ Data processing notice: Link to privacy policy explaining data handling
• ☑ Timestamp and method of consent collection for compliance records

HELP/STOP and Other Commands

• All SMS campaigns must support standard HELP and STOP commands
• Commands should be recognized in both Albanian and Serbian
• Common keywords to support:
  • STOP, NDALO (Albanian), PRESTANI (Serbian)
  • HELP, NDIHME (Albanian), POMOĆ (Serbian)
• Process opt-out requests within 8 days (as required by Law 06/L-082)

Implementation example for processing opt-out commands:

const OPT_OUT_KEYWORDS = ['STOP', 'NDALO', 'PRESTANI', 'UNSUBSCRIBE', 'END'];

async function processInboundSMS(from: string, body: string): Promise<void> {
  const normalizedBody = body.trim().toUpperCase();

  if (OPT_OUT_KEYWORDS.includes(normalizedBody)) {
    await addToSuppressionList(from);
    await sendConfirmation(from, 'You have been unsubscribed. No further messages will be sent.');
    await logOptOut(from, new Date(), 'SMS_KEYWORD');
  }
}

Do Not Call / Do Not Disturb Registries

Kosovo does not maintain an official Do Not Call registry. However, Law 06/L-082 requires that:

• Data subjects can object in writing at any time to use of personal data for direct marketing
• You must stop using data within 8 days of receiving the objection
• Maintain suppression lists with opted-out numbers for at least 12 months
• Regularly clean contact lists to remove inactive or opted-out numbers

Time Zone Sensitivity

Kosovo follows Central European Time (CET, UTC+1) in winter and Central European Summer Time (CEST, UTC+2) in summer. Daylight saving time transitions occur on:

• Last Sunday in March at 2:00 AM CET → 3:00 AM CEST (clocks forward 1 hour)
• Last Sunday in October at 3:00 AM CEST → 2:00 AM CET (clocks back 1 hour)

For 2025, the transitions are March 30 and October 26.

Best practices include:

• Send messages between 9:00 AM and 8:00 PM local time
• Avoid sending during religious holidays and national celebrations
• Only send outside these hours for urgent notifications or critical updates
• Account for DST transitions when scheduling campaigns in advance

Kosovo SMS Sender ID Options: Alphanumeric, Long Codes & Short Codes

Alphanumeric Sender IDs for Kosovo (No Registration Required)

Operator network capability: Supported

Registration requirements: No pre-registration required – dynamic usage allowed

Sender ID preservation: Yes, sender IDs are preserved and displayed as sent

Character limitations: Maximum 11 characters, alphanumeric (A-Z, a-z, 0-9), no spaces or special characters except hyphens. Examples: "BankAlert", "ShopKS", "MyCompany"

Best practices: Use recognizable brand names, maintain consistency across campaigns, avoid generic terms that could be flagged as spam.

Long Codes for Kosovo Messaging

Domestic vs. International: International long codes supported – domestic long codes not available

Sender ID preservation: Yes, original sender ID is preserved

Provisioning time: Typically 1–2 business days

Use cases: Ideal for transactional messages, alerts, and two-factor authentication

Pricing: International long code pricing varies by provider, typically €0.03-0.14 per SMS segment. Check with your SMS provider for Kosovo-specific rates (MCC 221).

Short Codes

Support: Not currently supported in Kosovo

Provisioning time: N/A

Use cases: N/A

Kosovo SMS Content Restrictions: What You Can't Send

Restricted Industries and Content:

• Gambling and betting services (regulated by Kosovo Gaming Authority)
• Adult content or services
• Cryptocurrency promotions (unregulated financial services)
• Political campaign messages without proper authorization
• Pharmaceutical promotions (requires health authority compliance)

Content violations and consequences (under Law 06/L-082):

• Unsolicited marketing: Fines €2,000-€4,000 per violation (Article 82)
• Data processing without consent: Fines up to €40,000 or 2-4% annual turnover
• Failure to honor opt-outs within 8 days: Additional penalties and enforcement actions
• Fraudulent or deceptive content: Potential criminal prosecution under Kosovo's consumer protection laws

Kosovo SMS Content Filtering

Known Carrier Filtering Rules:

• Messages containing keywords related to restricted industries (gambling, crypto, adult)
• URLs from suspicious or blacklisted domains
• Messages with excessive punctuation (!!!, ???) or all-caps text
• Phishing indicators: fake banking URLs, urgent security warnings with suspicious links

Specific keyword categories that may trigger filtering:

• Gambling: "casino", "bet", "jackpot", "lottery", "win money"
• Financial fraud: "confirm account", "verify identity now", "urgent security"
• Adult content: explicit language, dating service keywords

Tips to Avoid SMS Blocking:

• Avoid URL shorteners in messages (use branded short domains instead)
• Use clear, professional language
• Limit special characters and emoji usage
• Include company name in message content
• Test messages with carrier spam filters before large campaigns
• Register sender IDs with your SMS provider for reputation tracking

Best Practices for SMS Marketing in Kosovo

Messaging Strategy

• Keep messages under 160 characters when possible to avoid concatenation charges
• Include a clear call-to-action with specific instructions
• Use personalization tokens (customer name, account details) to increase engagement
• Maintain consistent sender ID across campaigns for brand recognition
• Front-load important information (first 50 characters) as some devices show previews

Industry-specific examples:

• Retail: "Hi [Name], 20% off this weekend at [Store]! Show this SMS at checkout. Valid until Sunday. Shop now: [link]"
• Banking: "VALA BANK: Transaction alert. €150.00 withdrawn from account x1234 on 15/10/2025 at 14:23. Call 080012345 if unauthorized."
• Healthcare: "Reminder: Dr. [Name] appointment tomorrow 10:00 AM at [Clinic]. Reply Y to confirm or call 038012345 to reschedule."

Sending Frequency and Timing

• Limit marketing messages to 4–5 per month per recipient
• Space messages at least 24 hours apart to avoid fatigue
• Avoid sending during major holidays:
  • Independence Day (February 17)
  • New Year's Day (January 1-2)
  • Religious holidays: Eid al-Fitr, Eid al-Adha (Muslim calendar)
  • Christmas (December 25 for Catholics, January 7 for Orthodox Christians)
  • Easter (varies annually for both Catholic and Orthodox observances)

Frequency recommendations are based on industry benchmarks showing opt-out rates increase significantly above 5 messages/month for promotional content. Transactional messages (order confirmations, security alerts) are exempt from these limits.

Localization

Kosovo is a multilingual society with Albanian and Serbian as official languages. Support both Albanian and Serbian languages for maximum reach:

• Albanian (majority): Use Latin alphabet, avoid diacritics if possible for compatibility
• Serbian: Use Latin script (more universally supported) rather than Cyrillic for SMS
• Include language preference in your opt-in process
• Offer bilingual opt-out instructions: "Reply STOP/NDALO/PRESTANI to unsubscribe"

Script considerations: While Cyrillic (Serbian) is technically supported via UCS-2 encoding, Latin script ensures better compatibility across all devices and reduces message length issues. Most Kosovo Serbs can read Latin script.

Opt-Out Management

• Process opt-outs within 8 days (as required by Law 06/L-082)
• Send confirmation message for opt-out requests within 24 hours
• Maintain separate opt-out lists for different types of messages (marketing vs. transactional)
• Regularly audit your opt-out processing system (monthly compliance checks)
• Store opt-out records for at least 12 months for regulatory compliance

Testing and Monitoring

• Test messages across both Vala and IPKO networks before launching campaigns
• Monitor delivery rates by carrier (target >95% delivery rate)
• Track opt-out rates and patterns (>2% opt-out rate indicates problems)
• Regularly test HELP/STOP functionality (weekly automated tests recommended)
• Monitor for carrier filtering changes (subscribe to ARKEP announcements)

Kosovo-specific KPIs and benchmarks:

• Delivery rate: 95-98% (properly formatted messages)
• Open rate: 95-98% within 3 minutes of delivery
• Click-through rate: 8-15% for promotional SMS with links
• Opt-out rate: <2% for well-targeted campaigns
• Response rate: 15-25% for transactional SMS requiring action

Send SMS to Kosovo: API Integration Guide (Twilio, Sinch, MessageBird, Plivo)

How to Send SMS to Kosovo with Twilio

Twilio provides robust SMS API support for sending messages to Kosovo mobile numbers. Here's how to implement Twilio SMS for Kosovo:

import { Twilio } from 'twilio';

// Initialize Twilio client with your credentials
const client = new Twilio(
  process.env.TWILIO_ACCOUNT_SID,
  process.env.TWILIO_AUTH_TOKEN
);

// Function to send SMS to Kosovo
async function sendSMSToKosovo(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    // Ensure proper formatting for Kosovo numbers (+383)
    const formattedNumber = to.startsWith('+383') ? to : `+383${to}`;

    const response = await client.messages.create({
      body: message,
      from: senderId, // Alphanumeric sender ID or phone number
      to: formattedNumber,
    });

    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
    // Handle Kosovo-specific errors
    if (error.code === 21614) {
      console.error('Invalid Kosovo phone number or landline attempted');
    } else if (error.code === 30003) {
      console.error('Rate limit exceeded - implement backoff');
    }
    throw error;
  }
}

Send SMS to Kosovo Using Sinch API

Sinch offers reliable SMS delivery to Kosovo with straightforward integration and competitive pricing:

import { SinchClient } from '@sinch/sdk-core';

// Initialize Sinch client
const sinchClient = new SinchClient({
  projectId: process.env.SINCH_PROJECT_ID,
  apiToken: process.env.SINCH_API_TOKEN
});

// Function to send SMS using Sinch
async function sendSinchSMS(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    const response = await sinchClient.sms.batches.send({
      to: [to],
      from: senderId,
      body: message,
      delivery_report: 'summary' // Enable delivery reporting
    });

    console.log(`Batch ID: ${response.id}`);
  } catch (error) {
    console.error('Sinch SMS Error:', error);
    throw error;
  }
}

Kosovo SMS Integration with MessageBird

MessageBird provides comprehensive SMS capabilities for Kosovo messaging campaigns:

import messagebird from 'messagebird';

// Initialize MessageBird client
const mbClient = messagebird(process.env.MESSAGEBIRD_API_KEY);

// Function to send SMS via MessageBird
function sendMessageBirdSMS(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  return new Promise((resolve, reject) => {
    mbClient.messages.create({
      originator: senderId,
      recipients: [to],
      body: message,
      datacoding: 'auto' // Automatic encoding detection
    }, (err, response) => {
      if (err) {
        reject(err);
        return;
      }
      console.log('MessageBird Response:', response);
      resolve();
    });
  });
}

Plivo SMS API for Kosovo

Plivo offers reliable SMS delivery to Kosovo numbers with detailed delivery tracking and reporting:

import plivo from 'plivo';

// Initialize Plivo client
const plivoClient = new plivo.Client(
  process.env.PLIVO_AUTH_ID,
  process.env.PLIVO_AUTH_TOKEN
);

// Function to send SMS via Plivo
async function sendPlivoSMS(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    const response = await plivoClient.messages.create({
      src: senderId,
      dst: to,
      text: message,
      url_strip_query_params: false // Preserve URL parameters in tracking
    });

    console.log('Message UUID:', response.messageUuid);
  } catch (error) {
    console.error('Plivo Error:', error);
    throw error;
  }
}

API Rate Limits and Throughput

• Twilio: 100 messages per second
• Sinch: 30 messages per second
• MessageBird: 60 messages per second
• Plivo: 50 messages per second

Strategies for Large-Scale Sending:

• Implement queue systems using Redis or RabbitMQ for buffering
• Use batch APIs when available (Sinch batch API supports up to 1,000 recipients)
• Implement exponential backoff for rate limit handling (start with 1s delay, double on each retry)
• Monitor delivery rates and adjust sending speed accordingly
• Distribute load across multiple provider accounts for redundancy

Rate limit handling example:

async function sendWithBackoff(sendFunction: () => Promise<void>, maxRetries = 5): Promise<void> {
  for (let i = 0; i < maxRetries; i++) {
    try {
      await sendFunction();
      return;
    } catch (error) {
      if (error.code === 30003 || error.status === 429) {
        const delay = Math.pow(2, i) * 1000; // Exponential backoff
        await new Promise(resolve => setTimeout(resolve, delay));
      } else {
        throw error;
      }
    }
  }
  throw new Error('Max retries exceeded');
}

Error Handling and Reporting

// Comprehensive error handling for Kosovo SMS
interface SMSError extends Error {
  code?: string;
  status?: number;
}

// Kosovo-specific error codes
const KOSOVO_ERROR_HANDLERS = {
  '21614': 'Invalid number format or landline attempted',
  '21408': 'Kosovo number portability lookup failed',
  '30003': 'Rate limit exceeded',
  '30007': 'Message filtered by carrier (content violation)',
  '30008': 'Unknown destination number (invalid Kosovo prefix)',
};

async function handleSMSError(error: SMSError, recipient: string): Promise<void> {
  // Log error details with Kosovo context
  console.error({
    code: error.code,
    status: error.status,
    message: error.message,
    recipient: recipient,
    country: 'Kosovo (+383)',
    timestamp: new Date().toISOString()
  });

  // Handle specific error codes
  switch (error.code) {
    case '21614': // Invalid number
      await markNumberAsInvalid(recipient);
      await notifyAdmin(`Invalid Kosovo number: ${recipient}`);
      break;
    case '21408': // Number portability issue
      await retryWithPortabilityCheck(recipient);
      break;
    case '30003': // Rate limit exceeded
      await queueForRetry(recipient, 60000); // Retry after 60 seconds
      break;
    case '30007': // Content filtered
      await flagContentForReview(recipient);
      await notifyCompliance('Message blocked by Kosovo carrier filters');
      break;
    case '30008': // Invalid Kosovo prefix
      await validateKosovoNumberFormat(recipient);
      break;
    default:
      await logGenericError(error);
  }
}

// Helper function to validate Kosovo number format
function validateKosovoNumberFormat(number: string): boolean {
  // Kosovo: +383 followed by 8 digits
  // Valid prefixes: 44, 45, 46, 49 (Vala), 43, 48 (IPKO)
  const kosovoPattern = /^\+383[4][3-9]\d{6}$/;
  return kosovoPattern.test(number);
}

Frequently Asked Questions: Sending SMS to Kosovo

What are the SMS regulations and compliance requirements in Kosovo?

Kosovo follows Law No. 06/L-082 on Protection of Personal Data (effective February 13, 2019), which transposes the EU's GDPR. This law requires written consent for SMS marketing, processing opt-outs within 8 days, and maintaining proper records. The Information and Privacy Agency (IPA) enforces compliance with fines ranging from €400 to €40,000. Article 82 specifically addresses direct marketing violations with fines between €2,000 and €4,000 for minor infringements.

Which mobile carriers and operators support SMS messaging in Kosovo?

Kosovo has two main mobile operators: Vala (Kosovo Telecom) with approximately 50% market share and IPKO with 47% market share. Both operators support SMS messaging and have deployed 5G networks as of mid-2024. As of Q2 2024, Kosovo had 1.91 million mobile users with 103.4% penetration rate.

Do I need to register alphanumeric sender IDs to send SMS in Kosovo?

No, Kosovo does not require pre-registration for alphanumeric sender IDs. You can use dynamic sender IDs, and they will be preserved and displayed as sent to recipients on both Vala and IPKO networks. Sender IDs are limited to 11 alphanumeric characters (A-Z, 0-9, hyphens allowed).

Is number portability available in Kosovo?

Yes, number portability is available in Kosovo since December 2023. ARKEP authorized the PXS&Botek consortium to provide number portability services, allowing users to switch between operators while keeping their phone numbers. Integrate with real-time number portability databases for accurate message routing.

What is the correct phone number format for sending SMS to Kosovo?

Kosovo uses the international dialing code +383. Phone numbers follow the ITU-T E.164 format: +383 followed by an 8-digit National Significant Number.

Valid formats:

• International: +383 44 123 456
• E.164 (API): +38344123456

Mobile prefixes:

• Vala: 44, 45, 46, 49
• IPKO: 43, 48

Common formatting errors to avoid:

• Missing country code: "44123456" (invalid)
• Wrong country code: "+381 44123456" (Serbia, not Kosovo)
• Incorrect digit count: "+383 4412345" (only 7 digits)
• Landline attempted: "+383 38123456" (landlines use prefix 38)

How long does it take to get opt-out compliance in Kosovo?

Under Law 06/L-082, you must process opt-out requests and stop using personal data within 8 days of receiving a written objection from the data subject. Best practice is to process opt-outs immediately and send confirmation within 24 hours.

Can I send text messages to landline numbers in Kosovo?

No, sending SMS to landline numbers is not supported in Kosovo. Attempts will result in failed delivery with error responses (such as Twilio error code 21614), and you will not be charged for these failed attempts. Kosovo landlines use prefix 38 (e.g., +383 38 XXX XXX).

What SMS message length limits apply in Kosovo?

Standard SMS length is 160 characters for GSM-7 encoding and 70 characters for UCS-2 encoding. Concatenated messages are supported for longer content. For GSM-7 concatenation, each segment holds 153 characters; for UCS-2, each segment holds 67 characters. Message costs multiply by the number of segments.

Recap and Additional Resources

Sending SMS in Kosovo requires compliance with Law 06/L-082 on Protection of Personal Data, understanding the two main mobile operators (Vala and IPKO), and following best practices for message delivery and consent management. This comprehensive guide covers everything from regulatory requirements to API integration for successful Kosovo SMS campaigns.

Key Takeaways

1. Compliance Priorities:

   • Obtain written consent as required by Law 06/L-082 (effective February 13, 2019)
   • Support HELP/STOP commands in Albanian and Serbian
   • Process opt-outs within 8 days
   • Respect time zone restrictions (CET/CEST, 9:00 AM – 8:00 PM)

2. Technical Considerations:

   • Use proper phone number formatting (+383 followed by 8 digits)
   • Integrate with number portability databases (available since December 2023)
   • Implement proper error handling for Kosovo-specific error codes
   • Monitor delivery rates across Vala and IPKO networks (target >95%)

3. Best Practices:

   • Test thoroughly across both major carriers before large campaigns
   • Maintain clean contact lists with proper suppression management
   • Monitor API rate limits and implement exponential backoff
   • Support bilingual messaging (Albanian and Serbian, both in Latin script)

Next Steps for Kosovo SMS Implementation

1. Review ARKEP telecommunications regulations for the latest updates on licensing, spectrum allocation, and consumer protection rules
2. Familiarize yourself with Law 06/L-082 on Protection of Personal Data requirements, particularly Articles 73-82 on direct marketing
3. Implement opt-out handling system with 8-day processing requirement and automated confirmation
4. Set up monitoring and reporting systems for both Vala and IPKO delivery rates by carrier
5. Test your SMS integration with both operators before launching campaigns (send test messages to +383 44/45/46/49 for Vala and +383 43/48 for IPKO)
6. Register with the Information and Privacy Agency (IPA) if processing significant volumes of personal data
7. Establish data processing agreements with your SMS provider compliant with GDPR/Law 06/L-082

Additional Resources

• ARKEP (Regulatory Authority of Electronic and Postal Communications): arkep-rks.org – telecommunications regulations, licensing, spectrum management, and consumer protection guidelines
• Information and Privacy Agency (IPA): aip.rks-gov.net – Data protection compliance, enforcement actions, and guidance on Law 06/L-082 implementation
• Kosovo Official Gazette: gzk.rks-gov.net – legal publications, regulations, administrative instructions, and official government announcements
• ITU Kosovo Numbering Plan: ITU-T E.164 Kosovo – Official numbering plan and technical specifications for +383 country code
• Law 06/L-082 Full Text: DataGuidance – Complete legislation on personal data protection with direct marketing provisions