Protect the sign-in credentials
Choose a strong unique password rather than reusing one from another service. Store it in a password manager if you use one. Do not share a complete account login casually among a team. If you believe the password was exposed, change it through the controls available in your account and review recent activity. Recovery options should be based on what the service actually supports, not assumptions about email delivery.
Keep browser access private
Use a separate browser profile on a shared computer and avoid leaving the dashboard open when someone else can access the device. A browser session can allow account access even without the password being visible. Do not export session cookies or send them in support conversations. When finishing on a shared device, sign out and remove locally saved credentials using the browser’s available settings.
Handle codes and integration keys
An OTP is intended for the specific verification challenge that requested it. An API key can authorize requests from software. Neither belongs in a public repository, screenshot, or team chat. Keep integration credentials on the server side where possible and avoid exposing them in frontend code. If a diagnostic log includes a credential or live code, redact it before sharing the log and rotate exposed credentials where supported.
Check the account after unexpected activity
Review recent orders and balance activity if something looks unfamiliar. Distinguish a page refresh from a new purchase before making further requests. Preserve order identifiers and timestamps for a clear report while excluding secrets. For destination accounts linked to temporary numbers, maintain approved permanent recovery methods; securing the dashboard alone does not make a rental number a permanent account recovery channel.
Questions and answers
Is it safe to share browser cookies with support?
No. A session cookie can grant account access and should remain private.
Do screenshots need redaction?
Yes, when they include passwords, API keys, OTP values, or unnecessary personal data.
Using SMS Activation responsibly
Use numbers only for accounts, applications, and tests you are authorized to access. Follow the target platform’s terms and local law. Availability, prices, supported routes, and payment networks can change, so verify current details in the dashboard before paying.
See current countries, services, cryptocurrency deposits, activation prices, and rental periods after registration.