Getting Started
This guide will help you set up your account, understand the core functionality, and get started with API access and Product Configurations.
Accessing the Portal
- Navigate to your portal URL: https://mylink2.linkmobility.com/
- Log in with your assigned credentials.
- If it’s your first time, follow the activation link sent via email.
🔐 Two-factor authentication (2FA) may be required depending on your organization’s security policy.
Key Features
- Manage accounts, users, permissions, and 2FA
- Monitor activity, dashboard, and logs
- Generate and manage API credentials
- Configure security settings
- Access support and documentation
- Access and manage MyLINK Products
Regional Availability
The MyLINK Portal is available in several global regions to provide optimal performance, scalability, and compliance with data regulations.
Available Regions
| Region | Services Available |
|---|---|
| Norway | SMS, WhatsApp, Email, RCS, MyLINK Marketing Platform, MyLINK Connect, MyLINK Engage, MyLINK Studio |
| Denmark | SMS, WhatsApp, Email, RCS, MyLINK Marketing Platform, MyLINK Connect, MyLINK Engage |
| Finland | SMS, WhatsApp, Email, RCS, MyLINK Marketing Platform, MyLINK Connect, MyLINK Engage |
| Sweden | SMS, WhatsApp, Email, RCS, MyLINK Marketing Platform, MyLINK Connect, MyLINK Engage, MyLINK Studio |
| Spain | WhatsApp, MyLINK Connect |
| France | WhatsApp, RCS, MyLINK Connect |
| Italy | |
| UK | WhatsApp, RCS, MyLINK Studio, MyLINK Marketing Platform |
| Portugal | |
| Mexico | |
| Germany | WhatsApp, RCS, MyLINK Engage |
| Austria | WhatsApp, MyLINK Engage |
| Colombia | |
| Romania | RCS |
| Switzerland | MyLINK Engage |
Data Residency and Compliance
All data is processed and stored within the selected region, in accordance with regulations like GDPR, CCPA, and local telecommunications requirements.
✅ Each region is isolated — data never crosses regional boundaries without explicit routing.
Security
The MyLINK Portal is built with a security-first mindset. From login to message transmission, every interaction is encrypted, authenticated, and audited.
Authentication
All API access requires a Bearer token:
Tokens can be managed in the API Credentials section of the portal.
🔄 Login method can be changed, but this affects all users and subaccounts globally.
Two-Factor Authentication (2FA)
2FA is supported and can be enforced per account. Supported methods:
- SMS-based codes
- Federated login/SOO (Azure AD and Google Identity)
Admins can configure 2FA and SOO under Account Settings → General Settings → Login Method.
Audit Logs & Dashboard
- Dashboard metrics are retained for 90 days.
- Logs (via Logs Explorer) are retained for 90 days.
- Message search API data follows a 90-day TTL per index.
- Reporting API raw data is stored indefinitely.
Personal Data Processing
| Personal Data | Purpose | Flow IDs | Protection |
|---|---|---|---|
| Login & notifications | F1, F2 | TLS 1.3 | |
| Mobile Number | 2FA validation | F1–F4 | TLS 1.3 |
Data Flows Summary
All internal and external flows use TLS 1.3 and are segmented by ID. See full list under Flow IDs F1–F15 (Authentication, Logs, Storage, Reporting, etc.).
Data Repositories
| Repo | Description | Type | Retention |
|---|---|---|---|
| R1 | Internal DB (non-personal) | MySQL | Internal use only |
| R2 | Import/export file storage | Local | 7 days |
| R3 | Static HTML/CSS (Azure-hosted) | SPA | — |
| R4 | Azure Blob URLs for rendering | MySQL | 14 days |