After a suspension, a notice explains what happened to your trial
If your account was suspended when your free trial ended and you had chosen a plan, a notice tells you what happened to that plan and to your number once the suspension is lifted.
November 10, 2026 · 109 changes
This release makes incoming calls more reliable and brings back the breached-password check on the web. Notifications are back on Android with Google Play, with no update needed, and suspension notices explain more clearly how to appeal and reach 911. In the mobile app, the other changes come with version 0.14.0.
Read the blog post about version 0.14.0
These notes describe WIGGWIGG as it was when this version came out. Some changes apply only to the web app or only to the mobile apps, and mobile changes arrive with the matching app update. Prices and plans may have changed since. See current pricing
If your account was suspended when your free trial ended and you had chosen a plan, a notice tells you what happened to that plan and to your number once the suspension is lifted.
On an identity’s page, the list of your verified personal numbers now lets you remove a number. Once you confirm, the number is removed from all your identities right away, and your WIGGWIGG numbers no longer forward calls to it. To use it again, you’ll need to verify it once more. If your account hasn’t used its free phone trial, another account will also be able to verify that number. Otherwise, the removed number remains reserved to your account until your account is permanently deleted. When free phone trials are paused, the page for buying a number now says so and offers the paid plan, instead of showing the trial button. Finally, on the web, the error messages in the steps for verifying a number now tell you what to do.
For now, new phone trials are paused. On the web, and in the mobile app starting with version 0.14.0, the page for buying a number says so and offers the paid plan. Trials already underway keep their end date. When trials are offered, an account’s first eligible number includes a 14-day trial and 100 units, with no credit card. At present, the trial asks for a verified Canadian personal number, mobile or landline, on the identity that will receive the calls. Internet-based numbers, toll-free numbers, and numbers whose line type we cannot confirm are not accepted, and a verified number can be used by only one account at a time. If your number is refused, you can verify another one, take the WIGGWIGG number you chose with a paid plan, or write to support. We may limit or stop new trials in case of abuse or if costs become too high. The trial never turns into a paid plan on its own. If you choose a plan, the first month is charged when the trial ends, or right away if you choose to start now.
On the website, when saving an emergency address failed, the window always showed the same message, whatever the cause. In three situations, it now tells you what to do: check the fields if the address could not be confirmed, refresh the page if an address is already saved for this number, or try again in a few minutes if our telephony provider could not save it.
Since mid-August, when we added credits to your account with a reason, the notification showed an incomplete sentence, without the amount or the reason. The credits themselves were added to your balance. The notification now shows the amount and the reason. In the mobile app, they show starting with version 0.14.0. Most notifications received between mid-August and this fix only say that a credit was added; the amount and the reason are still shown in your credits history.
After your vault’s automatic encryption upgrade, a browser could keep reusing an old copy of your contact list, which could leave some contacts missing from the list in the web app. Each browser now reloads the full list once. If contacts are still missing after that, contact support.
When setting up something you paid for fails on the first attempt, an automatic task tries again in the background. That task was missing a permission it needed, so a purchase could stay paid without being set up, and every retry failed. The task now has the permission it needs and can finish the setup.
When you search for a number by city, the search now recognizes common ways of writing a name, like “ste-therese” or “saint-therese” for Sainte-Thérèse, and looks for numbers in that town first. A one-letter typo can also be corrected; a message then shows the town searched and what you typed. If no numbers are found in that town, the message above the suggested numbers names the area code searched. In the mobile app, the correction and these messages need version 0.14.0.
On Android, refreshing your phone’s connection no longer interrupts an incoming call.
Once a call has ended, a new call can now ring normally, even if the previous call’s screen was still showing.
On iPhone, WIGGWIGG keeps the existing call connection in place until its background refresh is ready.
On iPhone, WIGGWIGG now preserves your lock-screen call choice when it wakes in the background. If your choice allows the call to ring, startup no longer interrupts it.
WIGGWIGG now keeps sending incoming calls to your phone even if you turn off message and activity alerts. On Android, notifications still need to be allowed for the incoming-call screen to appear while the app is in the background or the phone is locked.
On Android, when you answered a call from the lock screen, the person on the other end could hear only fragments of your sentences. One possible cause: Android could slow down WIGGWIGG’s microphone once the screen was locked, because it did not know a call was in progress. From the moment you answer until the call ends, the app now tells Android, with a quiet ongoing-call notification. Calls you place are not covered by this change. On the Google Play version, WIGGWIGG may also offer to open Android’s battery settings so you can turn off battery optimization for the app. On some phones, that optimization can make incoming calls ring late or be missed. This change comes with version 0.14.0 of the Android app.
When the connection your calls use drops without warning, the app now notices sooner when you dial, tells you clearly that the call couldn’t go through, and starts reconnecting so you can dial again. On Android, it also renews an idle connection when you answer, instead of getting stuck on the call screen. This change comes with version 0.14.0 of the app.
When WIGGWIGG is already connected on the phone selected to receive the call, a temporary notification problem no longer shortens the time you have to answer.
If your account already held an unused record for the number you were buying, activation failed on every automatic retry and your paid line never arrived. WIGGWIGG now reuses that record to deliver your line, with a single subscription. Nothing is reused when the number is linked to another account, already belongs to a billed line, or was released; we handle those cases by hand.
When a trial line’s activation failed on every automatic attempt up to the set limit, WIGGWIGG could not close it: it stayed pending, with no notice at all. It is now closed and you get a notice in the app. If you have not yet used the one replacement your trial allows, the notice invites you to choose another number. Otherwise, it tells you that replacement has already been used. In rare cases, it points you to support instead.
In the web app, some label names that had stopped showing because they were saved with an earlier key for your account can now be restored. When you sign in with your password, if your browser can read some of these names again, the app lists them and you choose which ones to restore. No name is replaced without your approval. Names that stay unreadable are now flagged in the list. You can rename those labels, and their colours and assignments stay the same.
On iPhone, WIGGWIGG now retries the call alert if the first attempt takes too long or runs into a temporary problem.
On iPhone, a brief connection interruption is now less likely to make you miss a call that’s still ringing.
After accepting the current Privacy Statement, signing in, and unlocking your data on a device, WIGGWIGG automatically prepares that browser or mobile device for calls to active numbers set to ring there. The All Devices setting includes the current device; with Custom, only the devices you selected are set up. A number bought on the web can then ring the current browser without requiring you to visit settings first, as long as WIGGWIGG stays open, unlocked, online, and connected. A clear status tells you whether this device is set up, what happens to calls under your routing settings, and what you can do next.
On some phones, an incoming call rang once and then cut off, and the caller reached voicemail or was hung up on. It happened when the app had restarted in the background, for example after a missed call, because it then refused calls until it had finished registering with our servers again. The app now keeps its ability to receive calls when it restarts in the background, for as long as you are signed in, and closes it when you sign out or your session expires.
A number you buy now uses the language you bought it in for its system messages, instead of English, including the short notice that tells callers you aren’t available. Adding the voicemail add-on no longer switches it back to English. The “System Voice” setting also shows in the web app’s Voicemail tab even without the voicemail add-on, so you can choose the language for that number and for your existing numbers.
On iPhone, when the app itself found a call still waiting for you as you opened it, for example because the call notification had not reached it, it only showed a banner inside the app, with no system ringtone and no call screen on the lock screen. It now shows the iPhone’s usual call screen in that case, and you answer as you would any call.
When none of your devices was set up to receive the call, for example with no phone signed in to the app and the web app not open in a browser, the call still rang for 20 seconds before applying your “If you don’t answer” choice. The caller heard ringing, then reached your voicemail or was hung up on. In that case, your choice now applies as soon as the call arrives. Nothing changes when a device is set up to ring, even if it is off or offline, or when 911 calls you back.
On the web, after you picked a region, searching for a word could show “no numbers” even when some numbers contained that word. On the web and in the mobile app, each new word you search for is now looked for anywhere in the number. When you enter a city, numbers found in that city come first, and the rest follow under “Other cities”. A “Cities found” row also lets you show only one city’s numbers. City names are easier to read, for example “Sainte-Thérèse” instead of “STE-THERESE”. On the web, the examples in the search field also match the regions on offer.
The number in your browser tab now matches the unread badges you see in the app. If some of your notifications can’t load, the bell and the Notifications page say so and offer to try again, instead of showing an empty list. “Mark all read” no longer touches lists that couldn’t load.
If your account is suspended or locked and you have not yet opened calling on your trial number, 911 stays available in the app. Until the line is ready, the app sends you to your phone’s own calling app.
If calling setup fails for a trial number, it is tried again the first time you open calling, usually in a few seconds. When lines free up, paying customers are served first. For 911, use your phone’s own calling app until the line is ready.
When an account is suspended, its trial number can give back its calling connection to serve other customers. Giving back that connection does not release the number, and 911 stays free and is never blocked. If the connection was given back, the line gets ready again the first time you open calling, which usually takes a few seconds. For as long as the suspension lasts, that line then serves 911 only. While it gets ready, or if that fails, WIGGWIGG tells you to call 911 from your device’s own calling app. On a device that can place calls, the WIGGWIGG mobile app opens that calling app with 911 for you if the line is slow or down. Once the suspension is lifted, all calling gets ready the first time you open it.
While an account is suspended, its trial number can also give back its calling connection when devices are set up for its calls: their access is removed, and in-app 911 uses access reserved for 911. If the suspension is lifted, your devices get their access back the first time you open calling.
While an account is suspended, its numbers no longer forward incoming calls or ring them in the app. Calls go to voicemail, or are declined when it is off. Auto-replies to calls and texts are no longer sent. If 911 calls you back within the hour after your call, that call-back still goes through as before.
The suspension notice used to say that 911 calls still worked. It now says you can still call 911 from WIGGWIGG and, if the call doesn’t go through, to use your device’s own calling app or another phone. In the mobile app, this text needs version 0.14.0.
Our November 1, 2026 Terms of Service prohibit opening several accounts to get more than one free trial. They also prohibit lending or reselling a number so other people can receive other services’ verification codes on it. If your account is suspended for one of these reasons, the app tells you why and you have at least 10 days to appeal. During that period and, if you appeal, until the decision, your numbers are kept, and 911 stays free and is never blocked. If the line needs to get ready when you open calling, or if that fails, WIGGWIGG tells you to call 911 from your device’s own calling app. If you don’t appeal or the suspension is upheld, a number obtained with a free trial can then be released and cannot be recovered. No paid number is released for these reasons.
If unlocking fails in the web app, the message now shows in your language. Trying again after a temporary failure no longer signs you out automatically. If unlocking still fails, the message asks you to sign out and sign in again.
When you unlock your data in the web app, the vault now shows up in the menu and in search on the first try. You no longer need to lock and unlock again to make it appear.
If your account is suspended for a use against our rules, the notice on the web and in the app now links to our Responsible Use page, which lists the prohibited uses, and reminds you that you can appeal the decision: a person will review your account. If your account still has a WIGGWIGG line, every suspension notice also explains that while your account is suspended, your lines can call only 911, and calls to one of your numbers ring in WIGGWIGG only for about an hour after a 911 call from that number, so emergency services can call you back. While an appeal of a suspension for a use against our rules waits for a decision, we keep the trial numbers you still have.
In a web browser, the Community now opens in a new tab, and WIGGWIGG stays open in the tab you came from. After you save your forum settings, a link lets you open the Community. If you added WIGGWIGG to the home screen of your iPhone or iPad, the Community still opens in the same window. The Join the community page also shows when your profile is loading, when it couldn’t load, and when a sign-in link is incomplete.
When a purchase totals $0, for example because your credits cover everything, you can no longer pay in bitcoin. The bitcoin option explains that it needs an amount above zero, and the selection moves to another payment method.
When the voice list can’t load, the picker says so instead of saying there are no voices, and offers to try again. This applies on the web and in the mobile app, for voicemail and call screening.
The window showing a test call’s result appeared in English even when WIGGWIGG was set to French. It now shows in your language. If the test fails, it asks you to try again in a moment and to check your call routing, instead of showing a technical message.
During account recovery, password strength hints showed in English on the French page. They now show in your language, as they do at sign-up.
In the vault on the web, the username and email fields of a new password entry now line up, even when a label wraps. On a small screen, the button that generates a username moves below the label instead of squeezing it.
When you cancel an add-on in the Android app, a window now tells you how you’re refunded: to your original payment method, as credits, or partly both, with the amounts. If the refund is still being confirmed, it says so. If it failed, it asks you to write to support. Before, the app showed no result at all.
Achievement celebrations now have a visible close button, and on Android the back button closes them too. They no longer close by themselves while a screen reader is on, so you have time to hear them. Tapping the banner no longer closes it.
In the mobile app’s lists of choices, screen readers now read every detail of each option, such as its description and extra text, and that extra text is easier to read in dark mode.
In the mobile app’s Contacts and Vault lists, if a label used as a filter was deleted or no longer assigned to any item, the hidden filter could leave the list empty. The filter is now cleared automatically, and the list’s content returns.
In the web app, before you export your data, delete your account or take some other sensitive actions, WIGGWIGG may ask for your password. If you closed that window while your password was being checked, the action could still go through. You can no longer close the window during that check. You can still close it before you confirm your password.
When you got a new number, texting could sometimes fail to switch on right away, without anyone knowing: calls worked, but texts sent to that number never arrived. We now retry switching it on automatically within minutes, then regularly for a week, and if a number is still waiting, we can see it as soon as we look at your account. If you got your number before this update and texts are not reaching it, write to us through in-product support and we will take care of it.
When a notice about the end of your prepaid subscription was waiting for you, it kept your account notifications from loading. In the mobile app, the notifications page showed an error. In the web app, those notifications were missing from the list, including that notice. Your account notifications now load again. On the web and on Android, the expiry notice appears among your other notifications.
In the web app, on a vault entry’s page, a breach that we cannot place before or after your current password showed a technical code instead of its explanation. This affected imported entries and passwords with no known set date. The warning now explains what we do not know and suggests changing the password. The severity and colour shown for each breach do not change.
In the mobile app, some purchase, trial, activation and usage notifications left a gap where the number should be, for example “Successfully purchased with…”. On the web, while your numbers were loading, some put “your number” into a sentence that could not hold it, for example “The phone number your number is no longer available…”. They now read as complete sentences, and on the web, the number still appears once it is found among your numbers. In the mobile app, the confirmation for a number purchase now also names the credits used, if any.
Notifications confirming a purchase opened with awkward wording, and a purchase paid in full with your credits showed an amount of $0.00. They now simply say what you bought, then, as applicable, what your credits covered and what you paid. A purchase fully covered by your credits says so clearly, with no zero amount.
In the web app, opening a deleted vault entry showed “Share link not found”, as if you had followed a share link. The page now says the entry cannot be found and may have been deleted, with a button back to the vault. If the entry just cannot be shown right now, the page says that too, without claiming it no longer exists, and offers to try again.
During the 30-day grace period before your account is permanently deleted, you get reminders. They said all your data would be erased. That was not accurate. They now say your personal data will be deleted, apart from the records the law or the security of the service requires us to keep. Our Privacy Statement gives the full list. During those 30 days, you can still change your mind: sign back in, then choose Cancel Deletion.
In the web app, a vault share link could refuse the right password when the password started or ended with spaces, for example after copying and pasting it. The mobile app already removed those spaces when it created a link, but the web page where the link opens did not. Spaces at the start and end of the password are now ignored for links created in the mobile app and for every new link created in the web app. Spaces inside the password still count, and a password that opened a link before still opens it. The “Weak password” notice also leaves those spaces out when it rates the password.
After several tries in a short time, the web page for a vault share link showed “Incorrect password, or this link is invalid.” even when the password was right. The page now says there have been too many attempts, that this does not mean the password is wrong, and to wait up to an hour before trying again.
At purchase, WIGGWIGG asks our telephony provider for the access that lets you place and take calls from the app and the browser. When the provider refused that request, the number was still announced as ready, nobody knew, and calls, incoming and outgoing, did not work in the app or the browser. A regular check now asks for that access again automatically, within minutes, then every hour for a week if the provider still refuses. We are also warned within the hour when a number ends up in that situation, and each purchase no longer sends its provider requests twice.
When the server answered that a number did not yet have its calling access, the app asked again every few seconds for as long as the screen stayed open, which wasted battery for nothing. It now asks once, shows the line as unavailable with the Reconnect button, and asks again when you press it, when you switch numbers, or when you come back to the app.
On the maintenance page, the French sentence saying the service is unavailable was missing part of its negation. It now uses the complete written form.
When WIGGWIGG is temporarily unavailable during an update, the maintenance page now checks whether service is back and automatically returns you to the app. The Try again button runs the same check. The expected return time clearly shows your browser’s time zone, and the page displays the message for the current maintenance window.
A number you get with the free trial now takes the language you use WIGGWIGG in for its system messages, including the short notice that tells callers you aren’t available. Until now, it was always English. In the mobile app, this needs version 0.14.0: if you start the trial from an older version, the number still gets English. You can change this language at any time with the “System Voice” setting in the web app’s Voicemail tab.
The vulnerability disclosure policy still used the outdated wording that WIGGWIGG was invitation-only. That wording has been removed, without changing how to report a security issue.
The fallback maintenance page is now published and verified with the WIGGWIGG version being deployed. It no longer stays on an older version during an outage.
The 0.12.0 release notes announced an acceptance screen for Privacy Statement 2026.09.19.12. 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 screen never appeared, and the Privacy Statement notification was not sent for that version. A dated correction now appears below those notes, without changing their original text. Version 2026.10.29.24, published on October 31, 2026, includes the IP address correction.
This page showed an effective date for version 2026.09.19.12, although that version was never activated in the app. It now says the version was published on the site from September 19 to October 31, 2026, was never activated in the app, and is carried into version 2026.10.29.24. The text of the version and its address are unchanged.
If you use WIGGWIGG with Google Play, your notifications stopped arriving on October 28 while the app was closed or in the background, including those for incoming calls. A change on our side had cut our server’s access to the Google service that delivers them. In those cases, the app did not ring for your calls. Your forwarding number still rang, as did your selected devices that do not use WIGGWIGG with Google Play. If no one answered, the call followed your no-answer setting. Your notifications arrive again, and you do not need to update the app. If they do not come back, open WIGGWIGG once. WIGGWIGG without Google was not affected.
Some text on the site and in the app suggested that a passkey opens the app on its own or always stays on one device. That text now says a passkey confirms it’s you after your password, and that, depending on the service that keeps it, it stays on one device or syncs to your other devices. The app also said the key never reached our servers. That is true for a passkey kept by another service: we receive only its public part. A passkey kept by WIGGWIGG is saved in your vault, encrypted on your device before it reaches us.
On Android, when you add a passkey to your WIGGWIGG account and your phone has no passkey service other than WIGGWIGG turned on, the app now tells you so, and that you can turn one on in Android settings, instead of showing an error. On Android 13 and earlier, it says passkeys in the app need Android 14 or later, instead of offering a button that can’t work.
When a text you sent doesn’t get through, WIGGWIGG now shows the reason under the message when we know it, for example that the number opted out of your texts or doesn’t receive texts. The button under the message now matches that reason too: it no longer appears when sending again couldn’t get through. Before this fix, the reason was lost on the way, and each of these texts showed the same general notice, with a button that put your wording back in the message box. Texts that failed before this fix keep the general notice, because their reason was never saved.
When you view a support request with new replies, the app marks them as read. If that failed, the app kept trying until you left the screen, and your other actions could be slowed down or refused in the meantime. It now tries only once per new reply. This fix arrives with version 0.14.0 of the mobile app.
You can now complete the recovery-key update form without another required step blocking it. For some people returning after a long absence, both steps could appear at the same time. They now appear one at a time, and support remains available if you need help.
When you finish account recovery, your new password and recovery key are now saved together. If a step fails, you can retry without keeping an incomplete update. WIGGWIGG also confirms that everything is complete before letting you continue.
Since mid-October, an add-on bought on its own through the cart, for a number you already had, could fail to be added to the number. It is now added as intended.
In English, the credit notification and two support notifications capitalized the main words of their title and button, for example “Credits Added to Your Account”. They now follow the same rule as the rest of the app, with a capital letter only at the start. In the mobile app, this change comes with version 0.14.0. French is unchanged.
When you release a number, WIGGWIGG now reminds you to replace it in any account that sends you sign-in or two-factor authentication codes. A released number may later go to someone else, who would then receive calls and texts meant for you.
When your “If you don’t answer” choice is “Hang up”, or it is “Send to voicemail” while your voicemail is not enabled, the caller heard ringing and then the line dropped, or the call was refused without a word. They now hear a short notice saying you are not available right now, and then the call ends. The notice is read in the language chosen under “System Voice”, in your number’s Voicemail tab on the web, even without the voicemail add-on. It also plays when that choice applies because none of your devices is set up to ring. The description of that choice in the web app now says this.
During a free trial, each number reserves a calling connection with our telephony provider, and the number of those connections is limited. Accounts created in bulk reserved them without ever calling. We now free the connection of a number still on trial three days after its activation, if calling was never opened for it in the app or on the web and it forwards its calls. Your call forwarding and your texts keep working in the meantime. The first time you then open calling on that number, even after choosing a paid plan, its connection is created again: the screen says the line is getting ready, which usually takes a few seconds. If preparation fails, a message explains why and you can try again. Until the line is ready, dial 911 from your phone’s own calling app. Numbers whose calling was already opened, numbers that ring in the app and numbers no longer on trial keep their connection.
Until now, when your line could not be prepared, the web app’s dialer only said it was not connected. While your line is getting ready, it now says so and retries on its own for about twenty seconds. If preparation fails, a message explains why, including when the cause is a limit on our side, with a “Try again” button. While the line is not connected, the screen reminds you to dial 911 from your phone’s calling app. Screen readers announce these states and the moment the line is ready.
Until now, a 911 call in the app always waited for your WIGGWIGG line. When that line is down, offline, reconnecting or takes more than five seconds to connect, dialing 911 now opens your device’s calling app, which may ask you to confirm. The call then shows your device’s number and the location your carrier provides, not the address registered for your WIGGWIGG number. If your device cannot place calls, such as an iPad, the call waits in the app for your WIGGWIGG line to connect; if the line is down or offline, the screen tells you to dial 911 from another phone. 933, the 911 test number, always stays in the app, as does 911 when you still have to choose which line to call from. If your line could not be prepared, a message explains why with a “Try again” button. When connecting takes a while, a “Stop connecting” button appears. Screen readers announce when the line is ready.
On the web and in the app, the suspension notice now shows the reason for the suspension and how long it lasts. If an account is suspended for using trial numbers to receive other services’ codes, the notice also gives the deadline to appeal. It says we keep the number at least until that date and, if there is an appeal, until our decision. Until then, the number can’t be used in WIGGWIGG to call, text, or check messages and voicemail, but calls to 911 still work. Unless an appeal is upheld, the account may be closed after that date and deleted 30 days later.
When you use an identity’s page to cancel a subscription that includes a number, the confirmation now shows the date your number is held until, in your account’s time zone. If that date isn’t available, the message says your number is held for a limited time.
The account deletion window is simpler: the 30-day grace period, and how to cancel by signing back in, are explained once instead of twice.
In a custom section of an identity or a contact, the edit and delete buttons now sit level with the field they belong to, even when its value wraps onto two lines. They are easier to tap on a phone, and a screen reader names the field they act on.
At checkout and renewal, the group of fields asking for your country and province had no name for screen readers. It is now announced as “Where you live”. Nothing changes on screen.
When you close the keep-your-number window without doing anything, keyboard navigation picks up at the button that opened it, instead of starting over from the top of the page.
In the mobile app’s notification settings, a screen reader read the same sentence twice for most switches. It now reads it once.
In Android and iOS autofill, a saved password is no longer called a “login”. When WIGGWIGG hasn’t verified that an app is connected to an entry, the window now asks “Use this password here?” On Android, the messages for verifying it’s you, filling a password, or remembering your choice are clearer too.
In the mobile app, the messages shown when you go over your identity limit no longer talk about a “slot” or a “spot” to free up. They now talk about your identity limit.
The notice about an attempt to recover your account and the reminder of your vault security plan were rewritten in simpler sentences.
When a notice shows at the top of the mobile app, for example the announcement of a maintenance pause, the text was cut after two lines and the Details button did not show the whole sentence. You can now tap the notice text to expand it and read all of it. As soon as you tap elsewhere, open the details, or leave the app, the notice goes back to its usual size.
When you remove a verified number, the confirmation window now says that a free trial already underway continues. Calls stop being forwarded to that number, though.
The button to request moving a number to another carrier is no longer on every number’s card. It now sits at the end of the number’s details page, with an explanation, and a request already open shows there too. This move is still free, through in-product support. In the mobile app, this change comes with version 0.14.0.
When we suspend an account because it is part of a series of accounts used to receive other services’ verification codes on trial numbers, the suspension screen now says so clearly, on the web and in the app, and the person can appeal the decision. Once the appeal deadline has passed and no appeal is pending, we can also release the trial numbers of a suspended account, so those numbers no longer receive codes.
When verification is required for the free trial, we ask our telephony provider for the personal number’s line type: it must be a mobile number or a landline, not an internet-based or toll-free number. Until now, a number the provider did not place in any of these types was accepted. Such a number now gets the same answer as an internet-based number: you can verify another personal number, take the WIGGWIGG number with a paid plan, or contact support if you think this is a mistake.
Accounts created in bulk were sending dozens of verification codes a day to strangers. On top of the hourly limits, each number and each account can now receive or request a limited number of codes over 24 hours, and an account can try a small number of different numbers a day. We also no longer send a code to a number whose format cannot exist in Canada. A person verifying their own number, even asking for a new code once or twice, should not reach these limits.
The website no longer keeps campaign parameters or the previous page to pass them into registration, and the server no longer stores them when an older app version sends them. The admin pages that showed this information by person have also been removed. Older values already stored, including those of deleted accounts, have been out of our live database since November 2, 2026. Copies may remain in our encrypted backups until they are deleted.
WIGGWIGG now refuses a vault field too long to save safely and tells you which one to shorten, instead of saving something that could disrupt autofill on your devices. When you import, entries with a field that is too long are skipped, and the preview tells you how many.
When a site asks WIGGWIGG to create a passkey with a site name or username too long to save safely, WIGGWIGG now declines instead of saving an entry that could disrupt autofill on your devices.
On Android, WIGGWIGG now asks for your fingerprint or screen lock before creating or using a passkey it keeps for you. Outside your browser, it offers that passkey to an app only if the site recognizes the app. A new passkey stays on your phone until it is added to your vault. On Android and iPhone, WIGGWIGG now refuses to keep a passkey for your own WIGGWIGG account. The ones you already have keep working, and a notice in the app’s Settings explains their limits and suggests adding another method.
Since version 0.10.0, when your anti-phishing security marker was on, the WIGGWIGG windows that fill and save your passwords and passkeys in other Android apps never showed your marker, creating a passkey in WIGGWIGG failed for every site, and saving a password could fail too, sometimes with unreadable names in the identity list. These windows now show your phrase, colours, and avatar, and you can create passkeys and save passwords in them. Your audio signature doesn’t play in these windows; it still plays at sign-in.
To add an authenticator app or remove a two-factor method, you now confirm with a method you already have, or with your password if none of your methods can. On the web, adding a passkey takes two steps: first you confirm it’s you, then you create the passkey. On the web, or in the mobile app starting with version 0.14.0, you can remove an authenticator app with a passkey, or a passkey with a code from your authenticator app. Some passkeys can’t confirm these changes, including those added with version 0.12 or 0.13 of the mobile app and those already on an account that had an authenticator app. Your security settings show which ones. If your security notifications are on, an in-app notification can tell you when a method is added or removed.
A passkey’s name can now be changed only from the account it belongs to. Before this fix, WIGGWIGG didn’t check which account a passkey belonged to before changing its name. A signed-in person who knew the random code that internally identifies another account’s passkey could therefore rename it. Renaming a passkey didn’t let anyone see its name, use it or remove it.
From October 30 until this fix, a safeguard in our database restored information it should have allowed to be erased. When an account was deleted, the old advertising campaign tags recorded at sign-up stayed stored. When someone unsubscribed from the newsletter, the encrypted email address kept with their subscription stayed stored. Deleting an account now erases those tags. Unsubscribing erases the email address kept with the subscription, the page of origin and the old campaign tags. Tags left on accounts deleted since October 30 have been out of our live database since November 2, 2026. The encrypted email addresses left after an unsubscribe since October 30 are still stored.
Since April, on the web, the check that compares your account password against known data breaches had stopped working, and no password was flagged. It works again on the web, at sign-up and when you change your password, and the mobile app also runs it at sign-up, starting with its version 0.14.0. A password found in a known breach is refused, and you choose another one. The check runs once, when you create your account or confirm your new password. For this check, only the first five characters of a fingerprint of your password leave your device. If the check cannot run, we tell you, and you can continue without it.
The free trial questions, on the trial page and in the FAQ, now say that a number whose line type cannot be confirmed as mobile or landline is not eligible, and what to do in that case. A new question explains that if you have not opened calling in the app or on the web after three days of trial, your number still receives calls and texts, app calling usually gets ready in a few seconds the first time you open it, and you should use your phone’s own calling app for 911 until it is ready.
The page that presents a business phone number to freelancers and the self-employed did not say what the free trial asks for. A short note under the buttons at the top of the page and in the pricing section now explains that, when verification is required, you first verify a personal Canadian mobile or landline number by text or call, and which numbers are not eligible. It adds that a verified number serves only one account at a time, and that this phone is also the one that rings when your WIGGWIGG numbers forward a call. The guide on which number to publish when you work for yourself now says so too, beside its link to the trial.
Each version’s release notes, until now readable only in the web app after signing in, are now also published on our website, so you can read and share them without an account.