Version 0.12.0

Someone who knew your account ID could keep you out by trying wrong passwords. A device you have used before can now get past that lock, but your password and, if enabled, your second factor are still required. In exchange, the lock no longer limits attempts made from that device. You can remove this access by changing or resetting your password, recovering your account, signing out every device, or changing your passkeys or second factor.

Until now, only people who had to accept a new version heard about it. If you had nothing to accept, nothing in the app told you. From now on you get a quiet in-app notification each time it changes. It does not wake your device, and you can read the Statement again in Settings, under Privacy & Data.

On an Android phone with Google Play, you can install WIGGWIGG from Google Play and receive updates there. No more detour through Settings to allow your browser to install a file. The preview build remains available from wiggwigg.ca; it may have bugs, and its look or features may change during Early Access. On iPhone, the web app works in your browser while the App Store version is on the way.

When a WIGGWIGG announcement is set up with its regular link and a French link, its button now opens the one that matches your language, in the banner and in your notifications.

For an account that still had to accept version 2026.09.10.11, the acceptance screen for version 2026.09.19.12 summarized only its IP address correction. It now presents one combined summary of the changes to communications and keys, residence and taxes, and IP addresses before asking you to confirm that version. If you had already accepted version 2026.09.10.11, you are not asked for another acceptance.

Several account pages, including billing, the vault, notifications and the shop, could stay blank for a moment when you were signed out, especially in French. They now take you straight to sign-in in the right language, then return to the page you intended to open. That blank screen exposed no account information.

Opening billing from a Credits Running Low notification could leave every page after it blank until you reloaded. Two redirects lost your language along the way. They now keep it, so billing and the rest of your visit display normally.

The Security Alerts setting promised an alert for sign-ins from a new device, but that alert was not being sent. It now describes the alerts it actually covers: sign-in locks, recovery attempts and other security events handled by this setting. The sign-in lock alert is new in this version; recovery alerts already existed.

In several parts of the web app, for example when you add a payment method, verify a phone number or request a refund, an error or an important warning can appear in a red box. The red text in that box was hard to make out against its background, especially in dark mode. It is now darker in light mode and paler in dark mode, so it is much easier to read in both.

Voicemail and MMS offers now open your number add-ons screen instead of the website. The cart no longer links to a missing page for topping up credits. In the Android app installed from Google Play, a number you just released stays held for a few minutes and can no longer be taken back from the app during that time.

On several buttons that open the web app to finish a purchase or manage your billing, a note on screen or the screen reader's announcement said mobile checkout was coming soon. We removed that promise. On those buttons, screen readers now announce that the button opens WIGGWIGG in your browser.

When you paid for a plan change by card, your card paid the full amount unless you chose an amount of credits yourself. By default, the amount now comes out of your credit balance first, and your card pays the rest. At least $0.50 is always left for the card, because our payment provider cannot charge a card for less. You can still enter a different amount or choose “Use none”.

In some browsers, a leftover from an older session made every new sign-in fail after your password or second factor. The app wrongly treated it as a newer session. Your sign-in now goes through even when that leftover is still present; your password, code and security key were not the problem.

At sign-in, when you reached the two-factor code field, a screen reader announced a technical name instead of telling you how many digits you had entered. It now tells you. On the “Upgrading your vault encryption” screen, the “Stuck? Get help” link also showed a technical name instead of those words. It now shows them. Both problems are fixed in French and in English.

When you signed in without two-factor verification and your password was accepted but your account then failed to load, the sign-in page showed “An unexpected error occurred” or “Network error”. It now asks you to reload the page before trying again, as it already did with two-factor verification.

On the web and in the mobile app, the support form gave the category covering calls, texts, and voicemail a technical name: “VoIP” or “VoIP & Calls”, depending on where you opened it. In that form, the category is now called “Calls & Texts”.

With WIGGWIGG in French, a screen reader announced the number of digits entered in a code, such as your two-factor code, always in the plural, for example “1 chiffres sur 6 saisis”. It now says “1 chiffre saisi sur 6”, in the singular for zero and one digit, on the web and in the app. The English wording was already correct.

The sign-in page now distinguishes two failures that used to say only to reload: encrypted data that will not unlock and another WIGGWIGG tab blocking the session. It now tells you to sign in again or close the other tabs, depending on the case, and explains what support can help with. A device that cannot finish a security upgrade can also let you in with your current protection; the upgrade can finish later from another browser or computer.

If you had enabled telemetry, error reports could contain identifiers the setting promised to exclude, including an account ID, phone number or overly specific page address. Those addresses are now reduced to their general form and error text no longer contains your account ID. Your sharing choice and the recent-request list are also cleared at sign-out.

After a subscription or trial ends, your number stays held for 30 days. If no payment method is saved, your credits can now pay for the per-unit plan or a new subscription to keep that number. The per-unit plan then keeps renewing with credits while the balance is enough. If a payment method is saved, that flow is unchanged; if your credits are short, the app clearly explains why.

Some refunds paid as account credit, the ones titled "Refund: Payment" in Credits History, could not be used in part. That includes, for example, the refund for a phone number that could not be activated, or a refund requested from an invoice. When a renewal, a purchase or an invoice payment needed only part of one of these credits, the payment failed: the purchase did not go through, or the invoice stayed unpaid. These credits now pay what is owed, and the rest stays on your account. In Credits History, a refund used in part shows on separate lines: the part used, dated the day of the refund, and the rest, dated the day the credit was used. Other credits, such as those titled "Refund: Subscription cancellation", could already be used in part.

Paying a past-due subscription invoice with credits marked the invoice paid but could leave the service past due and the number silent. Service is now restored when the invoice is settled, provided the subscription is not already suspended or cancelled. A daily check retries cases where the first restoration fails.

A bitcoin payment now marks an invoice paid only when it covers the amount still owed and both the invoice and its subscription can still be settled. A payment reported before suspension can wait up to 48 hours for confirmation without the subscription being suspended. If it arrives too late or falls short, the invoice stays open instead of showing a false success. If it belongs to an invoice already settled, that invoice's status does not change. A properly confirmed payment no longer goes back to pending; if your payment does not appear in your account, contact support.

When you ask for a refund on a unit pack from its invoice, you get back the share of the price you paid that matches the units left in that pack, tax included. Units you have already used are not refunded, and a depleted pack cannot be refunded. The same rule applies to international balance top-ups and to older minutes or texts packs. The refunded units come out of the pack the moment you confirm. If the number of units left in that pack changes between seeing the amount and confirming, nothing is refunded: we tell you so, and you can ask again for the new amount. If the refund fails when you confirm, the units go back into the pack. Refunding the pack that started your monthly refill also stops that refill. And when you ask for a refund from an invoice paid by card, the refund to your card is now pre-selected, with credits still available.

When you go over your number of identities, the ones you choose become read-only, and the app tells you that deleting one frees a slot. Deleting freed nothing: only adding a phone plan or adding identities reopened an identity. Now, deleting an active identity frees a slot, and the identity that has been read-only the longest becomes editable again, one per freed slot. If unlocking does not succeed the first time, your next deletion or addition does it again.

When a subscription is cancelled for non-payment, the credits applied to each of its unpaid invoices now come back to you. Before, the credits on at most one of those invoices came back to you.

After a subscription is cancelled, we hold your number for 30 days, then release it. The notifications sent seven days and one day before the release offered to reactivate the subscription at $3 a month to keep the number. That price was out of date: keeping a number costs $7 a month, and that is what we charge when you reactivate. Both notifications now say $7 a month, including the ones already in your notifications list.

After a subscription is cancelled, you can keep your number by paying for the per-unit plan. Once kept, though, it could stay in Do Not Disturb mode for up to a day, until our daily check put it back in service. Your number now works again as soon as you keep it. If a technical problem stops that from happening, our daily check takes care of it, as before.

When you used WIGGWIGG in French, the category filter for your support tickets and a ticket’s page showed the category and priority in English. They now appear in French.

Several links from the FAQ into the app led to a missing page or the wrong one: the links to read and send your messages, manage your blocked numbers, contact support, see your active sessions, add or update your payment method and start the free trial. They now lead to the right page, and the app opens in the language of the FAQ you are reading, even when your browser is set to the other language. The answer about the password manager, which had no link into the app in French, now takes you to your vault in both languages.

If you have cancelled the Advanced Routing add-on, your schedule rules and date overrides no longer apply. They are kept, and they apply again if you add Advanced Routing back.

After a 911 call, emergency services may need to call you back. For the next hour, the number you dialled 911 from rings for the first calls it receives, three at most. They ring even if your schedule or your default setting would otherwise turn them away, and even while your number is being held. A per-contact rule set to “Block silently” could still turn those calls away. It no longer does. Texts no longer count toward those three calls. They now go through the spam filter like any other text. Each new 911 call already restarted the hour. It now restarts the count too. Numbers you have blocked stay blocked, and their calls do not count toward the three. However, the call does not ring if your schedule, your default setting or a per-contact rule sends it straight to voicemail or answers the caller with an automatic text. That is the case, for example, with “Block with text reply” or “Send a text reply to blocked callers”. If our system cannot confirm your recent 911 call, your usual settings apply.

With WIGGWIGG in French, some priorities on your support requests appeared in the masculine form: “Urgent”, plus “Moyen” and “Élevé” in the mobile app. They now agree with the feminine word “priorité”: “Urgente”, “Moyenne” and “Élevée”. On the web, a request's page also shows “Créée le” before its date instead of “Créé le”, and the priority choices read more naturally, for example “Faible : ce serait un plus”. The English wording was already correct.

In your support tickets, the category for appealing a decision was called “Trust Appeal”. It is now called “Appeal”, on the web and in the app.

The usage packs page still said that once overage charges reached $5, your phone could no longer call or text. On your pay-per-unit numbers, that's not how it works: when your units run out, your spending limit takes over, and it's $0 by default. Other messages also said you always receive calls, even without units. In fact, once the limit is reached, outgoing calls and texts wait for your next unit purchase. Incoming calls go to your voicemail if it is on; otherwise they are declined. Texts you receive are delivered as soon as you add units. Calls to 911 are not blocked by units or your spending limit. The usage packs page, the explanation under your spending limit, and the one under your usage now say so clearly. So does the "No units for now" choice when you buy a number, on the web and in the mobile app. When you use WIGGWIGG in French, the page title in your browser tab is now in French too.

When you cancelled a subscription, the app did not say that 911 calls still work from the held number. It now says so, alongside the reminder that the number is held free for 30 days. The messages shown when you detach a number from an identity now simply say it goes into Do Not Disturb mode. The app also said that what you had already used reduced the refund, whatever your plan. It now says so only for plans that include minutes or texts, the only ones where that is true. When you keep your number after a cancellation, the confirmation now says it works again as soon as you keep it. And when you refund a subscription from its invoice, the window now tells you before you confirm that the refund also cancels the subscription and, for a number, what happens to that number. The refund method you pick in that window no longer changes on its own before you confirm. If our payment provider has not confirmed the refund yet, the window tells you the subscription was not cancelled.

Performance measurements are off by default. If you had enabled them, they could be sent with your sign-in cookies, browser name and a full address containing an identifier or phone number. They now send only the site and page, replace sensitive details with a placeholder, and include neither cookies nor the browser name. They also pause while your session is locked or unlocking and after sign-out. Older reports expire on the same schedule as the rest.

Since July, a WIGGWIGG announcement received in your notifications showed only its time and its button, with no title or message. It now shows its text in your language, including announcements you already received.

Saved routing data could crash your dashboard when you reopened it. We fixed that issue. Expired routing information is no longer presented as current while it refreshes.

When a new WIGGWIGG phone number was being set up, an error prevented its automatic verification from processing the confirmation text sent by our phone carrier. We fixed that error.

WIGGWIGG recorded a fingerprint of the network address you connected from. We have stopped recording them, and this update erases the ones already in our databases. Our backups still hold some, until they age out or we delete them. A temporary fingerprint of your address is still used to limit the number of requests, and it is not kept. Our cloud provider's firewall also counts requests per address and blocks the ones that go over its limits. Your active sessions list no longer shows an address row, and your data export now says "Not stored" or "No longer collected, awaiting erasure" instead of a fingerprint.

Every new version of the Privacy Statement was put to you for acceptance, even when it changed nothing about what you had agreed to. Acceptance is now judged from the most recent version that genuinely required fresh consent, so a wording correction no longer interrupts you.

When signing in failed after your password was accepted, or your account was suspended, the message told you to reload the page or contact support, without saying how. A “Stuck? Get help” link now appears under those messages. It opens our contact page in a new tab, because before sign-in the app's help form cannot work. The text of this page's error messages is also a little darker, so it reads better on the pale red background.

Sharing performance measurements is off by default. If you turn it on, each page load now reports the time spent before the request (redirects, the background service starting up), on the network, and until the page's real content is on screen, as well as the time between opening the page and your session unlocking automatically. These stay durations, counts and broad categories: no text, no identifiers and nothing about your security settings. A load that goes through the lock screen sends no start-up measurement, and a browser that rounds its clocks sends nothing. They tell us what slows the app down and let us measure the improvements to come.

When a page opened, the app loaded some data twice, opened a calling channel even when no number could ring in the browser, and loaded every notification list just to show a counter. It now waits for a real reconnection, opens the channel only when useful, and loads notification lists when needed. The counter includes usage alerts too. The bell has learned to count without opening every drawer.

Calling and texting abroad are not available yet. We now post updates, and the date of the next one, on a single status page with an RSS feed. The site and the app link to it instead of repeating a date that could pass.

Repeated attempts with a wrong two-factor authentication code now open a 30-minute lock, then a 2-hour and a 24-hour lock. A code that was already used is refused too. During password sign-in, a nonexistent account, a locked account and a wrong password now return the same response, which no longer reveals which case applies.

The codes we send to verify a personal number for call forwarding go to Canadian numbers only. Any other number, such as a US or toll-free number, is refused when you request the code, with a message saying so. This protects the service against a kind of fraud that gets us to send codes to expensive foreign numbers. A number you already verified keeps working as before, including for reaching your voicemail when you call your WIGGWIGG number.

In WIGGWIGG, date exceptions are rules that change how your calls behave on specific dates, such as during a vacation or holiday. Anyone else signed in to WIGGWIGG could view the date exceptions of one of your numbers if they knew that number's technical identifier. That identifier is a code of letters and digits that WIGGWIGG assigns to each number, not the phone number itself. They could see each exception's details, including its dates and times, what happened to your calls during those times, and its name and notes, if it had any. For exceptions imported from your calendar, they could see your events' dates, times and time zone, and the identifier your calendar gives each event, but not their titles. They could also create an exception aimed at your number, but it stayed tied to their own account: it did not appear in yours and did not change how your calls were routed. Another account was already unable to change or delete your exceptions. We do not know whether anyone used this flaw, because our logs do not cover the whole time it was possible. WIGGWIGG now checks that the number is yours before showing its exceptions or adding one, and refuses the request if it is not.

The Privacy Statement wrongly said our security records kept a one-way fingerprint of your IP address for seven years, never the address itself. The named record never held those fingerprints, some older fingerprints could be reversed, and our provider audit trail instead keeps some addresses themselves for seven years. Version 2026.09.19.12 and the whitepaper now describe those facts.

The FAQ wrongly said a cancelled number stayed active until the end of the paid period. It now explains that the subscription ends immediately, the unused portion is refunded through the available option you choose, and any portion paid with credits returns as credits. The number stays held free for 30 days so you can take it back with a new plan, and 911 calls keep working. The links now open the correct Subscriptions page.

The FAQ said that after a failed payment, we retried your card over the following days, and that updating your payment method was enough to restore service. That was not the case: those retries never charged your card, and updating your payment method does not pay the invoice. The FAQ now explains what happens: we notify you in the app, and the invoice stays due. In the meantime, the number cannot send texts or make calls, and incoming calls are refused, with no voicemail. 911 calls still work, even without an active plan. If you cannot settle the invoice, write to support. The FAQ also suggested you could keep your number past the 30 days it is held free; it now says you need to resume that number's line before it is released.

These notes announced Privacy Statement version 2026.09.19.12, which corrected how we described IP addresses, along with an acceptance screen summarizing its changes. Our site showed that version as current from September 19 to October 31, 2026, but it was never activated in the app: version 2026.09.10.11 stayed in place there. The acceptance screen described above never appeared, and the Privacy Statement notification was not sent for that version. On October 31, 2026, we published version 2026.10.29.24. Its summary of changes includes the IP address correction.