Changelog

Changes that affect what you pay, what you are owed, or what you are allowed to do. Internal work does not appear here — this is a record of commitments, not a release feed.

  1. POLICY

    Acceptable use: what applies to banks, payment services and government services

    The acceptable use page, the terms and the pricing page used to say that numbers for banking, payment processors and government identity verification are not sold and are refused at checkout. That was not what the catalogue did. The pages now say what the rule is: a number may be used with such a service only for an account in your own name, never to pass an identity check as someone else. Impersonation, evading a suspension, bulk registration and fraud remain prohibited.

  2. POLICY

    The terms now cover the iPhone app

    The terms were written before the iPhone app existed. They now say how it works there: credit is bought in packs through Apple’s In-App Purchase and paid to Apple; credits do not expire; when no code arrives the credit returns automatically, and an order can be cancelled once two minutes have passed; a delivered code is not refunded. A refund of the purchase itself is Apple’s to give, and when Apple refunds one the credit it added is taken back, which can leave the balance below zero. Deleting the account gives up any credit left on it. Two sentences were corrected: the one about keeping a password to yourself now also fits people who sign in with Apple, and the promise to return a remaining balance when an account is closed for abuse now says that credit bought through Apple can only be refunded by Apple.

  3. POLICY

    The privacy policy now covers notifications and account deletion in the iPhone app

    The privacy policy now says what the iPhone app’s notifications involve: if you allow them, the notification token for your iPhone is stored with your account and your alert choices; alerts are sent through Apple’s push notification service; and unless you switch that off in the app, the alert contains the verification code. It also says that each order keeps the number and the text of the message that arrived, describes deleting the account inside the app — confirmed with Apple — next to the website’s path, and lists everything that stays after a deletion: payment references, abuse signals with the account removed, delivery records and, for at most 30 days, the analytics record of a website top-up. It now says what each way of signing in gives us: with Google sign-in on the website, Google also passes your name and the address of your profile picture, which we do not use. The 3 October version said in-app purchase records were passed to an outside sales-reporting service. That is not switched on and nothing is sent, so the sentence was removed.

  4. POLICY

    The privacy policy now covers the iPhone app

    In the iPhone app you sign in with Apple, which gives us an identifier and an email address that can be a private relay address. Credit added in the app is paid to Apple, which sends us a signed record of each purchase and any refund; card details never reach us.

  5. POLICY

    Analytics now records the steps of an order — still nothing that identifies you

    Until today analytics only counted page views, so we could not see where people gave up. It now also records the steps: opening a service, pressing Buy, signing up or in, starting and completing a wallet top-up, renting a number, a code arriving and how long it took, and refunds or failed orders with their reason. Your email, account id, the number you rented, the code and the supplier are never sent — events carrying anything outside a fixed list are dropped in code. A completed top-up is now counted when the payment provider confirms it to our server; for that, and only if analytics was on when you started the payment, Google’s random visitor id is kept next to a one-way fingerprint of the payment, with its amount, currency and provider reference, for up to 30 days. The consent rules have not changed, advertising features stay off, and the privacy policy lists all of this, including one new two-minute cookie.

  6. SERVICE

    Premium · Non-VoIP purchases were failing — fixed

    From launch until today, buying a Premium · Non-VoIP number did not work. The number was reserved with the supplier, but a fault on our side stopped it from being attached to the order, so no number was ever shown. Every affected order was refunded in full — but the balance stayed locked for up to fifteen minutes first, which is not acceptable. The fault is fixed. If a number ever cannot be handed over again, the refund now normally happens in the same moment, and the safety net that returns money from stuck orders runs after five minutes instead of fifteen.

  7. POLICY

    Google Analytics added — with your consent in the UK, EEA and Switzerland

    The site now runs Google Analytics 4 to count visits and see which pages and services are used. In the UK, EEA and Switzerland no analytics cookie is set unless you accept the banner; declining sends only cookieless, aggregate signals. Advertising features are switched off. The privacy policy has a new “Analytics and cookies” section that lists every cookie the site can set and a switch to opt out at any time.

  8. POLICY

    Delivery percentages are now a single 24-hour figure

    The site used to blend four time windows into one composite number. Measured across 398 options, the thirty-day window read higher than the last day 61% of the time and gave a non-zero rate to 109 options that had delivered nothing for three days. The percentage is now the supplier's rate for the last 24 hours and nothing else — a figure you can check rather than a composite you cannot. The cost is stated on the measurement page: a route that died in the last few hours can still show yesterday's number.

  9. POLICY

    Delivery percentages are now attributed to their source

    The pages said these rates were measured here. They are not: each percentage is reported by the wholesale source supplying that option, from its own orders. Only one of the sources reports rates at all, so options from the others read “measuring” permanently rather than carrying an invented figure. We publish no delivery measurement of our own and do not plan to.

  10. CATALOGUE

    Every option in a country is now visible, ranked by evidence

    Service pages showed one option per country and hid the rest — in the United Kingdom that meant one row where nine exist. You now pick a country, then see all of its lines. Ranking leads with a guaranteed physical line, then reported delivery from high to low, then price. An option whose pool is only partly physical no longer outranks one with a reported delivery rate.

  11. PRICING

    Card and crypto payments opened

    The site now takes real payments. Card details are entered on the payment provider's page and never reach our servers. Buy-now-pay-later options are deliberately switched off: they are not designed for instantly-consumed credit, and their dispute windows do not fit it.

  12. POLICY

    Terms, privacy and acceptable use published

    First versions of the three policy documents. The privacy text describes actual system behaviour rather than boilerplate, including what survives account deletion and why. None of the three has been reviewed by a lawyer yet, and the operating entity is still a placeholder — both stated openly on the pages themselves.

  13. POLICY

    Delivery measurement method published

    The method behind every percentage on the site is written out in full, including the time-window weighting, why a rate can read “measuring”, and the cases where the measurement is misleading.

  14. PRICING

    Refund rules fixed at the database level

    Two rules became structural rather than procedural: an order that never received a code is refunded automatically, and an order that did receive one is never refundable. Both are enforced inside the function that moves the money, so no request path can bypass either.

This service is new, so the record starts here rather than reaching back years. Live operational readings are on the status page.