Version 0.13.0

In the iPhone and iPad app, you can request account deletion and track its progress while we prepare to close your service. As soon as the request is accepted, renewals and automatic payments stop. Service you already paid for stays available until its end date, or until an earlier verified shutdown. If your account still has a phone number or active service, the app walks you through it. If an invoice is still payable on a past-due or suspended subscription, you will need to cancel that subscription first.

When you edit an entry, you can now check “This account has no password”, handy for sites that sign you in with a link by email or with another account. Before, such entries showed “No password saved”, which suggested one was missing. They now show “None, this account doesn't use a password”, without the “Not confirmed on site” warning. The old password goes into the entry's history, which keeps up to 3 previous passwords for 30 days: after that, it is no longer there. The choice is available on the web and in the mobile app.

A calling device without a name now gets one in the mobile app that shows the phone and the WIGGWIGG app, for example “Pixel 8 · WIGGWIGG without Google”. The name is encrypted on your device, like a name you choose. On Android, if the device still carries another WIGGWIGG app's automatic name for this phone model, that name is updated: the app only replaces a name that matches one of those automatic names character for character. Also on Android, when an older device carries one of those automatic names, the app offers to remove that older device, once this phone is ready to receive calls for the same numbers.

The “Passkeys” screen, now called “Passkeys and devices”, now has a “Sign out of all devices” button. It ends all your sessions, including on the device you're using. Your other devices stop ringing and alerting you to new messages until you sign back in on them. Each of your other devices finishes signing out the next time its app reaches WIGGWIGG. Until then, what's already on the device stays there. This doesn't change your password, and you'll need it to sign back in. Your vault and your data stay intact. On iPhone and iPad, searching Settings for “sessions” or “devices” now leads to this section. The app doesn't show a list of your sessions and doesn't let you choose a single session to end.

On Android, the banner at the top of the web app now offers to install the Android app from Google Play, instead of a home screen shortcut. The variant without Google downloads from the Mobile Apps page. On iPhone and iPad, the banner now leads to the App Store.

On blocking screens in the web and mobile apps, emergency-call actions are smaller and separated from the main actions. They appear only when your account has at least one number eligible to call 911, including without an active plan or a saved emergency address. A confirmation explains the calling route before starting the call or opening your device’s calling app.

During a call, the app works out how much time you have left from your units and your spending limit, then hangs up when that time runs out. This also applied to 911: with no units and a $0 spending limit (the default), the app could end a 911 call that was already connected. It no longer ends a 911 call for these reasons, nor an incoming call marked “Possibly a 911 callback”. During these calls, it no longer plays a countdown or shows a usage warning. One exception remains in the mobile app: such a call can still be ended for these reasons if you answer it with “End & answer”, or if the label appears after you answer.

When you called another WIGGWIGG number and reached its voicemail, your usage statement showed 0:00, but units were still counted, including for the time the line stayed open after your message. These calls no longer count against your units, and a WIGGWIGG number's voicemail now hangs up on its own once the recording is done. Also, a text or picture the carrier could not deliver now returns its unit to you. That refund, announced in version 0.10.0, was failing on our side.

The cart and checkout now refuse an add-on that is already active on the number, even one added to a plan change, and nothing is charged. On the web, a message explains why. If such a purchase still goes through and was paid only with WIGGWIGG credits or in bitcoin, its amount, taxes included, comes back to your credits automatically. If any part of it was paid by card, support is alerted and refunds you: the part paid by card goes back to your card, and the rest comes back as credits.

When you cancelled a number's plan chosen during the trial, the prorated refund was calculated from the trial end date, even months later. It could therefore be too high or too low. It is now always calculated from the start of your current paid period. Refunds already paid are not taken back. If you think yours was too low, write to support. Also, a $0 invoice for a plan that started as a trial is no longer presented as a trial invoice once the trial is over, whether in the invoice list, on the invoice page or in the PDF.

When a payment doesn't go through, your number now keeps working for 10 days, on the units you have left. Before, incoming calls were refused and outgoing calls and texts were blocked from the first day, earlier than our terms of service allow. Without payment, the subscription is then suspended, as before. 911 calls are never blocked. If your number was already paused when this update arrived, it comes back as soon as the invoice is paid. In version 0.13.0 of the mobile app, you can also make calls and send texts during those 10 days, as on the web.

During the 10-day grace period to settle a late payment, your number works with your remaining units, and your spending limit counts as $0. Your limit resumes once the invoice is paid, and the setting you chose does not change. If your units run out in the meantime, new outgoing calls and texts are blocked. Incoming calls go to your voicemail if it is on; otherwise they are declined. A call already under way is not cut off. To keep going, you can add units. 911 calls are never blocked.

For one hour after you call 911 from the app, calls to that number ring even when your units are used up and your spending limit is reached, and they are not billed. That way, emergency services can call you back. Before, that hour opened only for a number without an active phone plan or on a Number Only plan. It now also opens for a number with an active plan, including during a trial or while a payment is late. On a number with an active plan, the hour can open at most six times in a 24-hour period, and a 911 call made again within five minutes of the one that opened it does not count again. This limit applies only to the callback hour, not to your 911 calls, and the 911 call itself is never billed. If the hour does not open, for example because the limit is reached or WIGGWIGG is not notified of your 911 call, incoming calls follow your usual settings and billing. As was already the case for other numbers, the first three calls of that hour ring even if your schedule, your default setting or a per-contact rule would turn them away. Numbers you have blocked stay blocked, and a call your settings send to voicemail or answer with an automatic text does not ring.

In the web app, a “Call 911” button is now offered on the required-consent screen, on the session lock screen, during the password change that follows an account recovery, and when your account is suspended. In the mobile app, it is offered on the lock, required-consent, vault-check, security-upgrade and account-suspension screens. On the mobile app's required-update and maintenance screens, the button is also offered and goes through your device's calling app. If your account is suspended, you can still call 911 from your WIGGWIGG numbers, and a 911 callback can still reach you in the app. Other outgoing calls stay blocked during the suspension. In the web app, when the session is locked, the button calls from your WIGGWIGG number if the web app was already ready to call in that tab before the lock; otherwise, it offers your device's calling app. During the password change, it goes through your device's calling app. If the call can't go out from your WIGGWIGG number, call 911 with your device's calling app or from another phone. On the web, a pending consent request no longer blocks a call that is ringing or in progress: you can answer the call, mute your microphone, or hang up.

When an add-on could not be activated and its amount came back to your credits, the mobile app invited you to try again without mentioning that refund. It now shows the refunded amount, written the usual way for your language: $5.75 in English, 5,75 $ in French. On the web, “your number” no longer takes a capital letter in the middle of a sentence.

A number's free trial is activated only with its own button. The cart now refuses to add one, since it could not activate it anyway. A trial left in a cart is refused when the total is calculated and at checkout, and nothing is charged.

Before, if you left the card payment page without paying, the payment stayed pending in your cart, and the credits applied to the purchase stayed set aside until you cancelled the payment yourself. Now, if you come back to your cart through the payment page’s return link, the payment is cancelled and your credits go back to your account. As before, you can also cancel the payment yourself with the “Cancel this payment” button in your cart. Your items stay in your cart, except for a phone number whose hold ended in the meantime.

A usage record that reached us late, after a number was released, could set that number back to active in your account. It then reappeared in your list of numbers and counted toward your number limit. A released number now stays released: the late record is still saved, but it no longer changes the number's status.

Saving an edited entry in the mobile app erased details the form does not show: the password history, the date the password last changed, the note that an entry was imported, the confirmation that the password was changed on the site, and the section order you had chosen. The mobile app now keeps them, and when you change a password there, the old one also goes into the history, as on the web. This fix does not bring back details that were already erased.

The app regularly renews your session to keep you signed in. If your phone could not save that renewal, you could be signed out later. The app now retries, including when you return to it, and keeps you signed in while it stays open. If saving still fails and the app closes, you may need to sign in again. On the web, a server that is busy or receiving too many requests no longer signs you out during this renewal: the app tries again later.

In the web app, tags added to a vault entry, for example in the mobile app, are turned into labels. If creating a label failed, the tags could disappear for good. They now stay in the entry, and the web app tries the conversion again later. An edit made on the web no longer stops that conversion either. Tags already lost this way do not come back.

After your vault's automatic encryption upgrade, or after a password change, some entries and contacts could show as unreadable for up to 15 minutes. Your data was not affected: the server was sending back a copy of your lists from before the change. It now sends the up-to-date version as soon as the change is done.

When you edited a vault entry, an identity or a contact in one tab, another tab already open could stop showing that item until you reloaded the page. It now updates itself before showing it. We also fixed the automatic update of these items' encryption, which could finish while leaving some items behind, impossible to show afterwards. It now finishes only once every item has been encrypted again. Otherwise, it leaves everything as it was and tries again later. This fix does not bring back items that were already left behind.

When you opened a vault entry, its page could show “No security issues found” even though the vault list had just flagged it “No 2FA” or “Site breached”. The entry could also disappear from the filtered list. The warnings now stay visible on the entry page and in the list. If they had already disappeared, they return with the next vault scan, or right away if you choose “Rescan”.

On the web, your password tiles and score still counted issues you had acknowledged, and the weekly plan still asked you to fix them. They now leave those out. Keep in mind: a password found in a data breach and acknowledged no longer lowers your score, and the page can show “All your passwords look good” if nothing else needs fixing, but that password stays exposed until you change it. Breached sites and sites to check still count and stay in the plan, even when acknowledged. The Vault Health Digest in your notifications uses the same count, including when you read it in the mobile app.

In the mobile app, your password health score still counted issues you had acknowledged on the web. It now follows the same rule as the web. A password found in a data breach and acknowledged therefore no longer lowers your score, and the app can show “All clear” if nothing else needs fixing, but that password stays exposed until you change it. Breached sites and sites to check still count, even when acknowledged.

On the web, an issue you acknowledge on an entry's page no longer appears in the Vault Premium password security guide, except for entries on a breached site, which always stay listed. When every issue in a step is acknowledged, the guide says so without presenting the step as done, names the entries and explains how to bring those issues back.

The short message asking you to wait when an action reaches a limit always appeared in English, even when the app was set to French. It now follows the language chosen in the app.

When you pressed Speaker while your call was ringing, nothing seemed to happen: the ringing stayed in the earpiece and the button did not change. Speaker now works as soon as you dial: the ringing plays on the speaker, and the call stays there when the other person answers. Speaker, Mute and Hold also light up clearly when they are on, and screen readers say which ones are on.

While your phone was ringing, the app made an unnecessary request to our servers, and in some cases the call ended as soon as you tapped Answer, before it was picked up. The app no longer makes that request while a call rings. And if your phone cannot read the detail that identifies it at the moment you answer, the app tries once more instead of ending the call right away.

A Cmd-click (Mac) or Ctrl-click (Windows) on a vault entry now opens it in a new tab, like any link, and a middle click does the same. It works on “View details”, in list view and in your dashboard Favorites. A plain click still opens the entry in place, and in multi-select mode a click still selects. On the keyboard, in list view and your Favorites, pressing Enter on a copy button now copies instead of opening the entry.

A call setup problem could make the web app think your session had expired. It then tried to renew your session or showed “Unlock Your Data”, even though you were still signed in. It no longer does that. This fix removes the incorrect unlock request; it does not resolve the call setup problem itself. The browser still needs to be ready before you can make or receive calls.

On the web, a website saved without a prefix in a contact, such as example.com or an IP address, opened a WIGGWIGG page instead of the site. This could happen with a website added in the mobile app, or imported into the mobile app from your phone's contacts or a vCard file. The link now opens the site in a new tab, with “https://” added. An address now shows as text with no link if it starts with another prefix (such as “ftp://”), contains a username or password, or is not valid.

When you imported your passwords from another manager, an email address used as the sign-in identifier landed in “Username”. It now goes in “Email”, and any other identifier stays in “Username”. If the file already has a different email address for the same entry, that one goes in “Email” and the identifier stays in “Username”. When you export as Bitwarden JSON, the email address of an entry without a username now serves as its sign-in identifier, and it is added as a custom field when the entry also has a username. Entries you already imported do not change.

If your internet drops while you sign up, on the web or in the Android app, a screen now checks whether your account was created, instead of showing an error and leaving you to wonder. You can check again or try signing in.

When you asked to delete your account, a phone number you had already released still counted as active: you were asked to release it first, with nothing left to release. Now, among your numbers, only those still active or suspended block deletion. The other conditions, such as an active subscription or an unpaid invoice, do not change.

The Early Access page, the article that announced its opening and the preview shown at sign-up, on the web and in the Android app, now say: “Early Access is a real, paid service, but a product still in development: screens may change from one update to the next, and an announced feature can be pulled while it is rebuilt.” They no longer say that core features can break. The article carries a dated note that quotes the old wording. The checkbox you accept at sign-up keeps its old wording for now.

Some pages of the website said you could forward your calls to any phone and your texts to your cell. That is not what the service does, and the site now says so correctly. Only incoming calls can be forwarded, to your identity's verified Canadian number, confirmed by a code. Texts are never forwarded: you send and receive them in WIGGWIGG, in the app or the browser. A forwarded call your phone answers, even with its own voicemail, uses your WIGGWIGG units. Advanced Routing business hours change what happens to a call, never which number rings. Finally, the phone page no longer mentions a $1 hold: WIGGWIGG places none.

Our pages that compare WIGGWIGG with other services presented a single federal law, PIPEDA, as the framework that applies to us. That was not precise enough. They now say that WIGGWIGG INC. is a Quebec company, and that Quebec and Canadian privacy laws govern how it handles your personal information.

Several pages of the website, including the FAQ, the About page, the application security page and the press kit, presented WIGGWIGG as subject to a single federal law, PIPEDA. They now say that Quebec and Canadian privacy laws govern how WIGGWIGG INC. handles your personal information. On the comparison page, the “Built for Canadians” card also says that your calls and texts go through our carrier in the United States. Finally, the answer about accessing your information now follows our Privacy Statement instead of citing a law.

The FAQ said an “Export Data” button downloaded all your information instantly. That button does not exist, and exporting does not work that way. The answer now gives the real steps, on the web and in the mobile app: WIGGWIGG may ask for your password, the export is prepared in the background, you get a notification when it's ready, and the file stays available for 7 days. It also says what the file contains and what it leaves out: the encrypted content of your identities, contacts and messages stays encrypted, and you get vault passwords, MMS attachments and voicemail recordings elsewhere in WIGGWIGG.

The explanations that come with your data export were not accurate. The HTML file said you could decrypt some data with your password, and the web app and the FAQ suggested the file could be decrypted in the app. The web app also said WIGGWIGG could not open that data, without naming any exception. In the web app, the HTML file and the FAQ, the explanations now name the data that stays encrypted in the file and say that WIGGWIGG offers no tool to decrypt it. They also name data WIGGWIGG can still read or recover, including a small set of messages retained from the private beta, and your contacts' phone numbers while you keep contact recognition turned on. We also removed the estimate that an export is ready in under a minute, because the time depends on how much data there is.

In the HTML export of your data, your invoice amounts and the credits earned with your achievements appeared 100 times too small: a $12.34 invoice showed as $0.12. The credit balance showed the amount of a single transaction instead of your balance, and the monthly price of each number and your earned and used credit totals showed $0. The page now shows the real amounts and your general credit as the app shows it, with your partner phone credit shown separately if you have any. The monthly price per number no longer appears, since what you are billed is in your invoices. The earned and used credit totals no longer appear either, because this export does not fill them in. The same fix applies to the balance in the JSON export, which also includes a note explaining its amounts.

Your data export now includes each credit transaction: its date, type, amount and, where applicable, the invoice the credit was applied to. It separates general credit from partner phone credit and shows which transactions count toward your balance. In the HTML file, the “Credits history” table follows your balance. The JSON file includes the same information, with a note explaining how the balances are calculated.

The application security page said your encrypted data stayed encrypted in your account export and that WIGGWIGG could not open it. That was broader than what we can promise: WIGGWIGG can still read some of that data, including a small set of messages retained from the private beta. The page now names what stays encrypted in the file: the encrypted content of your identities, contacts and messages, as it is stored. To read it, you use the app, not the file.

The application security page said our illegal-content check covered SMS and MMS messages, in memory, before encryption. That check covers only the pictures in MMS messages, and the text of a message is never fingerprinted. The page now says so.

The 911 emergency service page described how a 911 call placed abroad would be routed. Outside Canada, do not rely on your WIGGWIGG number to reach emergency services: dial that country's emergency number from your mobile phone or a local phone. The page now says so. It also no longer calls the service “compliant” and no longer suggests 911 could be turned off: 911 is never switched off on any WIGGWIGG number.

The page said a file's signature proves it came from us. It now says the signature confirms the file was signed with the key whose fingerprint the page publishes. When the page offers a build signed with the same key as the Google Play app, it also says that Google holds a copy of that key and so could sign an update your phone would accept. It no longer says the app checks for a new build as soon as we publish one: it checks roughly every half hour, and every time you bring it back to the screen. Finally, this page and the Mobile Apps page in the web app said the stable and preview builds behave the same on privacy. The encryption is the same, but the preview build allows screenshots and screen recordings, while the stable build blocks them.

Two headings on our comparison pages, about KeePass and APhone, suggested that WIGGWIGG could read none of your data. That holds only for some data. These headings now name the data in question: your protected passwords and identity details. On the English LastPass page, the answer about LastPass security now matches the French answer.

In the Help panel, opened from the question mark at the top of the page, each item's icon was centred on all of its text. When the text wrapped, the icon ended up next to the description instead of the title. It now lines up with the first line of the title, right where your eye looks for it.

An app installed from Google Play could offer you an update downloaded from wiggwigg.ca. It now sends you only to Google Play, and so does the website for that version. The variant without Google still downloads from wiggwigg.ca, as a stable or preview build. The preview can have bugs, and its look and features can change along the way.

On the variant without Google, the update button now opens the mobile apps page on wiggwigg.ca instead of Google Play, where this variant is not offered. The download page in your account no longer offers a preview build older than the stable one. The variant without Google installs alongside the Google Play app without replacing it, and our pages (FAQ, roadmap, Early Access, press kit) now present it as the only direct download.

Obtainium is an app that tracks updates for apps downloaded outside Google Play. The mobile apps page now shows a button for each build of the new app without Google. Each button opens Obtainium already set up for the right app and the right build, stable or preview, whichever you picked, and not the other one. If Obtainium was already following the variant without Google before 0.13.0, the page explains how to move to the new app.

Android now recognizes the variant without Google as a separate app. It can live on the same phone as the Google Play app, and neither one can replace the other during an update anymore.

Call and message notifications now use a service supported by the version of the Android app you installed. A remote update could previously cause the app to choose the wrong service. When the app switches notification services, the old one is removed as soon as the new one is registered, so notifications no longer continue through both.

On Android, when you had no identity yet, the vault's “Create Your First Identity” button opened the web app in your browser. It now opens the creation form right in the app. On iPhone and iPad, this button also opens the form in the app.

When the app can't read some of your identities, the vault list and the add-entry form now say so: you can add or move entries only under the identities that could be read. A “Try again” button lets the app try reading them again. Before, the vault said nothing, and the form could show a message that didn't fit the situation. Separately, on iPhone and iPad, tapping some links saved in a contact or a vault entry did nothing. A short message now tells you this version can't open the link.

When you have no active identity, the vault's add-entry form now asks you to create one or restore an archived one in the app's Identities section, instead of sending you to the web dashboard. While your identities load, it no longer says you have none. If your identities can't be loaded at all, it says so and offers a “Try again” button. If all your active identities are read-only, it asks you to free a slot. Separately, when the full identity list can't be confirmed, the warning now says you can manage the identities shown, and that adding identities and choosing which ones move to read-only stay paused until the list is confirmed.

When you selected several vault entries to move them, the list also offered your read-only identities, which is what identities become when you go over your identity limit. Choosing one of them moved nothing, and no message explained why. The list now offers only the identities that can receive entries. The “Move to identity” option appears only when at least two of your identities can receive them.

In the web app, when you selected several vault entries, the “Move” menu also offered read-only identities. Those identities cannot receive entries, so choosing one showed “Failed to move entries”, and no entries were moved. The menu now offers only identities that can receive entries, and it appears only when you have at least two of them. Read-only identities stay in the vault filters.

In the web app, when all the entries you selected were in the same identity, the “Move” menu also offered that identity. Choosing it showed “Failed to move entries”, and no entries were moved. The menu no longer offers it. If your selection mixed entries from several identities and you chose one of those identities, the move stopped at the first entry already there and showed the same message: some entries could already have moved, and the rest had not. Now the entries already in the chosen identity stay where they are, instead of stopping the move for the others. The message that confirms the move counts only the entries that moved, and the menu stays disabled while a move is under way.

In the mobile app, the vault screen shown until you have an identity presented all identity management as zero-knowledge encrypted. It now says that this encryption protects the names, emails and addresses in your identities.

Vault filters such as “No 2FA” or those in the “Acknowledged” section disappeared when you opened an entry and came back with the browser's Back button. They are now part of the page address: Back returns you to the same filtered list, and you can bookmark it or open it in another tab.

In your list of labels, the count also included items missing from the label's page, such as a phone number you had released. A label could therefore promise one item and open on an empty page. It now counts only what its page shows: a released number, an archived identity, a contact in the trash or a deleted vault entry no longer counts.

When you added a custom authenticator app to a vault entry, every letter you typed was added to the “Recently Used” list: for Aegis, the list also contained A, Ae, Aeg and Aegi. Aegis didn't need quite that many nicknames. And once the name was chosen, the “Authenticator App” field stayed empty. The name is now added only once, when you leave the “Custom app name” field, and it stays shown. Partial names the list shows as used once disappear the next time you pick or type the full name.

The help button in the bottom-right corner showed a different drawing of Patch than the one at the top of the “Human Support” panel it opens. It is now the same one. The area you can click follows his new outline and covers no more of the page than before. If you turned off “Patch, your helper” in your settings, nothing changes: you still see the plain support button.

When a vault entry's card offered both the “Password” and “Username” buttons, the “View details” link ran out of room and spilled right off the card. The link took “thinking outside the box” a little too literally. It now moves to its own line, on the right, and both buttons keep their full names.

The web app could show “Too many requests” and block every page for up to 15 minutes, sometimes right in the middle of working in the vault. The cause: an automatic check that restarted on every page and made the app believe its overall limit had been reached. That check no longer repeats from page to page. And when one specific action reaches its own limit, only that action waits: the rest of the app keeps working. If the overall limit is reached, the “Too many requests” banner still pauses everything until its countdown ends.

When a single action reached its own limit, the mobile app showed the “Too many requests” banner with a countdown. Now only that action waits out its delay, and the banner no longer appears for it. If you started that action yourself, a short message still asks you to wait. If the overall limit is reached, the banner still appears until its countdown ends.

On the web, editing an entry made the app reload your whole vault several times in the background. The app now reloads only the changed entry, including when the change comes from another device. It still reloads the whole vault in some cases, such as when you add or delete an entry.

On the web, opening the vault could start up to three loads at once. Once is enough. Three times was a little overenthusiastic. It now loads once, and the security scan, search and export use the same data. If loading fails, a message lets you try again. If you are offline, the app says so and loads the vault when your connection returns.

When you verified a personal number on a second identity after already verifying it on another identity in your account, sometimes no code arrived and nothing explained why. The second identity now uses the number your account already verified, without a new code. No need to prove twice that it is really your phone.

The pricing pages highlighted a “Most common” setup, a “Popular” example, a 300-unit pack presented as “the most common size” and “real” examples. We did not have data to support those claims. Those mentions are gone. The four setups are shown the same way, the examples become three sample profiles, and the 300-unit pack simply says what it contains.

The cart and the checkout windows, on the web and in the Android app, now say that anything renewing automatically keeps the price locked in when you bought it. If your subscription ends and you restart it later, it comes back at the price listed that day and can't return to a plan that is no longer offered. When you keep a number, it moves to the per-unit plan at the price listed that day. And if an invoice is overdue, the change-plan window reminds you that paying it without changing plans keeps your current price.

When you scan a two-factor (2FA) QR code for a vault entry, the Android app now reads it with a built-in scanner, right on your phone, without an Internet connection. ML Kit, a Google component, is no longer included in either Android variant, and the variant without Google no longer contains Firebase or Google Play services either, which had remained in it. Light codes on a dark background now scan too. On iPhone and Android, if the camera does not start, a message tells you that you can enter the setup key by hand.

The generator once again produces realistic names, addresses, phone numbers, emails and usernames to use instead of your real details, for example for a newsletter or a loyalty program. Because everything is random, these details can match real people, and the employers and schools it suggests are real. A warning, on the web and in the mobile app, reminds you to put in a phone number and email you control before a sign-up that sends a code, and never to use this identity with a bank, employer, landlord, government office or anyone else entitled to your real identity. Government ID numbers remain test values, not real numbers.

On the web, a “Do you want to keep this number?” card invites you to choose a plan from the first day of the trial, with the date the trial ends. The number's page also offers that choice. Once the trial has ended, the card shows the date until which the number is kept for you, free of charge, and each number trial has its own line in your subscriptions. When you cancel a number's subscription, the messages show the date until which the number is held, or mention a limited time when that date is not known, instead of announcing 30 days every time. The hold itself does not change: a cancelled number is still held for 30 days. After a cancellation from an identity's page, the message mentions a limited time for now.

On the web, an invoice page now shows a “Supplier” block with our legal name, WIGGWIGG INC., our postal address and the tax registration numbers printed on the PDF. A business claiming input tax credits finds our supplier details there. The PDF now also shows WIGGWIGG INC., as the Privacy Statement does, and a long line in its footer no longer overlaps the next one.

On the page where you buy a number, the trial button is now called “Activate this number for free”, and the trial starts right there, without going through the cart. When the trial cannot be activated, the reason stays in the card instead of vanishing in a short message, with what you can do: accept the current Privacy Statement, confirm your province, remove a trial already in your cart, or take the number with a paid plan. If a number's reservation has expired, you can reserve it again on the page if it is still free. And if someone else is in the middle of reserving the same number, the page tells you and lets you try again.

In the Android app, the free trial card now follows the terms our servers send, and its button is called “Activate this number for free”. When the trial cannot be activated, the reason stays in the card, with what you can do, instead of vanishing in a short message. If a number's reservation has expired, a button lets you reserve it again if it is still free. On a cancelled subscription's page, the number's release date and the price to keep it now come from our servers, so they stay current.

When you activate the free trial of a phone number, an in-app notice confirms it with the date the trial ends. It reminds you that nothing turns into a paid plan unless you choose one, and it opens your number's page. On the web, “Trial Activated” notices you already received no longer mention a length.

The About page has a new “At a Glance” block. It presents WIGGWIGG INC., an independent Quebec company, registered with the CRTC as a reseller of telecommunications services since May 12, 2026, with a link to the CRTC directory. It also mentions its CRTC licence for basic international telecommunications services since July 6, 2026, noting that calling and texting abroad are not offered yet. It says where your data is hosted, with its exceptions, and that our whitepaper is published but not yet checked by an independent audit. A few style touch-ups complete the page.

The business page now focuses on self-employed people. It explains which number to publish, what you control and the limit of each setting, what it costs at the listed prices, and the limits of the service, stated plainly. It also says where to get the app for your phone, and its FAQ leads to the new self-employed guide.

A screenshot attached to a message no longer takes the whole width of the conversation: it shows as a preview, and one click opens it full size. The messages can get a word in again. The attachments and context sections are slimmer, side by side on a large screen. The “Ticket resolved” banner under the conversation is gone, since the request's status and the “Reopen” button at the top of the page already said so.

On the Password Health page, tiles like “Reused” and “Weak” showed a count and then left you to it. Any tile with at least one problem now opens the guide on the step that fixes it. “Open the Guide” also skips the welcome screen and takes you to the step for the most serious kind of problem. The welcome screen is still there if you go back in the guide.

When an account sends you its two-factor codes by email, the “Email for 2FA” list only offered the email of the linked identity. If that identity had none, you had to retype an address the entry already held. The list now offers, under “This entry”, the entry's email, as well as the username when it is an email address. The choice is made on the web, and the mobile app keeps and shows the address chosen. One less address to retype.

The two-factor editor always opened on the authenticator app, even for a site that offers only another method, such as codes by email. With Vault Premium, when your vault's analysis shows that a site offers a single method, the editor now opens straight on that one. If it is email, the address is already filled in with the entry's, or the linked identity's if the entry has none: all that is left is to save. In every other case, the editor still opens on the authenticator app.

On a vault entry's page, the website address could only be copied. It is now a link that opens the site in a new tab, and an address without a prefix, such as example.com, opens with “https://” added. The “Visit Site” buttons and their O keyboard shortcut now open the site too, instead of a WIGGWIGG page. An address stays as text you can copy, with no button to open it, if it starts with another prefix (such as “ftp://”), contains a username or password, or is not valid.

To set up each call, the mobile app contacted a Google server that helps two devices connect over the Internet. Google then saw your phone's public IP address at the time of each call. The app now uses the equivalent server from Telnyx, the provider that already carries your calls, and no longer contacts that Google server. This change covers only that server: on the Google Play version, the push notification that wakes the app for an incoming call still goes through Google's notification service.

The blog publishes “Self-employed: which phone number to put on your business card, quotes, and website”. It compares the options, says what WIGGWIGG does not do yet, such as bringing over an existing number, and explains how the article was prepared and checked. Worth a read before you print 500 of them.