All articles

Who sees the SMS, what gets stored, and for how long: answers for your security team before you buy numbers

Before a client's first purchase of numbers, their security team usually sends us the same list of questions. Who physically receives the SMS? What stays in the system after an order? How long is it kept, and who can it be shared with? Below are our answers, exactly as we give them in writing. Your security team won't like some of them, but it's better to find that out before the purchase is approved than after.

Who receives and sees the SMS

SimAggregator is a marketplace. The numbers belong to suppliers. They are real SIM cards in the suppliers' GoIP gateways, SIM banks, or ordinary phones. The code from a service is received by the SIM card in the supplier's device. The text then passes through the platform and appears in the order details in your dashboard. For a business, this is the key fact about the security of SMS data on virtual numbers: the message passes through someone else's hardware and through our systems. That's why we never write "only you can see the SMS content."

On top of that, the supplier sees orders on their numbers in their sales history: the service, the status, the buyer type (individual or B2B), and the buyer's name. Keep this in mind when you decide who registers the account and under what name. Only verification codes should go through these numbers. Passwords, customer data, and work conversations should never end up on a temporary number.

Do you need an account, and what gets stored

There's no anonymous purchase. You can check prices and availability for each supplier without signing in, but you can only buy a number from an account. The account keeps your order history, searchable by number, and a feed of balance activity: payments, refunds, and top-ups.

The privacy policy allows data retention for up to 5 years and disclosure in response to a lawful request. If your internal rules require a shorter retention period, compare them with the policy text in advance. The legally binding version of the agreement and the policy is the Russian one, so your lawyers need to read that version, not a translation.

What the service can be used for

The service is intended only for receiving verification codes, within the law and the platforms' rules, and you must be 18 or older to use it. Getting around bans, limits, and identity checks is not part of that, and we won't help with it.

One more point for your lawyers: receiving an SMS doesn't guarantee a successful sign-up on a third-party service. That decision is up to the platform itself. If the code doesn't arrive before a one-time activation expires, the money goes back to your internal balance automatically. You have to cancel a rental with no code yourself within the first hour after purchase, before any SMS or call arrives: after that it is paid even if the code never arrives. Refunds are not sent to a card or wallet, and once the SMS is received, the service is considered delivered.

The number is temporary, and that's a security issue too

An activation currently lasts one hour (the catalog sets it per service). A rental lasts 1, 3, or 7 days. When the term ends, the SIM card stays with the supplier. Once the resale cooldown is over, another buyer can purchase the same number for the same service, and from then on they will be the one receiving that service's codes. You can buy an expired number again as long as the SIM is still online. If it has gone offline, all you can do is ask the supplier to bring it back into service.

The takeaway for your security team: don't link a number like this to accounts the company will need access to after the rental ends, and don't make it the only way to recover an account.

What to do on your side

Items 3 to 6 are about API keys. Before you start an integration, check with support whether the API itself is available on the new platform.

  1. Turn on two-factor authentication (TOTP). You set it up on the secure sign-in page.
  2. Give dashboard access to one or two people in charge, not the whole department. If an employee with access leaves or a laptop goes missing, change the password and end the sessions on other devices.
  3. Issue a separate named key for each environment and script: production, the test environment, a one-off data export. If a key leaks, you revoke just that key and the others keep working.
  4. Save the key to a secrets manager right after you issue it. The key string is shown only once, and we keep only its fingerprint. A lost key can't be recovered: it gets revoked and a new one is issued.
  5. Check the last-used date of your keys regularly. If a script was stopped long ago but its key shows a recent date, revoke the key and find out who was using it.
  6. Don't put keys in a repository or in configs that get shared with contractors. The dashboard doesn't currently offer an IP allowlist for keys, so you are the only one controlling access to a key.

Before the purchase is approved, open the agreement and the privacy policy on sim-aggregator.com and attach them to the request for your security team. Then turn on two-factor authentication in your account's security settings, while the account still has no balance and no API keys.

Your first number in a minute

Signing up takes a minute, topping up a couple more, and the code arrives in 20 seconds.

Buy a number
No subscription feeCancel with a refund in the first hour