Version 0.10.0

You create a WIGGWIGG account from any country, with no invitation and no seat limit. The account, the vault, contacts, two identities, and the 30-day Vault Premium trial cost nothing, wherever you are. Phone numbers, the 7-day Canadian-number trial, and anything paid, including Vault Premium after the trial, require a Canadian province you select and confirm yourself for taxes. Open registration includes no promised sign-up credit, and a validated invite code keeps the terms it displays.

After you accept the updated Privacy Statement, your devices appear automatically when you sign in to WIGGWIGG and unlock your data. If you previously chose not to use calling devices, that choice remains in effect until you turn them back on. By default, devices that are ready can ring. You can name them and remove the ones you no longer use. In the web app, you can also choose which devices ring for each number. Custom names are encrypted on your device.

For a few days, starting the free trial failed on every number, whatever you did: a generic error, then “reservation expired” on a number you had just reserved. Five defects sat one behind the other on the same path. All five are fixed, and activation succeeds on the first try while your reservation is live.

The page had you build a paid plan before revealing, four steps later, that you did not have to. It now asks who owns the number, offers the free trial, then lets you build a plan if you want one. The trial card says what it includes, what happens when it ends, and what becomes of a unit pack chosen below it. The price shown separates what recurs each month from what is charged once. The mobile app follows the same order.

An account created today opened its first session to a “What’s New” badge for a version released a week before it existed. Release notifications no longer reach back before your sign-up. And starting the trial after your 30-minute reservation on a number has expired now tells you the reservation is over, instead of showing you a server error.

From the Contacts, Phone, Messages and Vault tabs, tapping the cart icon played the press animation and did nothing else, so nothing could be bought from the app. The cart now opens from every tab.

An add-on added to a running subscription is $0 in the cart because it bills on the subscription’s next invoice. The cart called that an early-access perk, called any $0 basket a free trial, warned about a 30-minute reservation with no number in the cart, and dated an add-on’s renewal from today. It now reads what it holds: a trial, an add-on deferred to the next invoice, or a purchase covered by your credits, each with its own wording.

The cart mistakenly priced the first month of a number plan at $0 for every Early Access account, with no perk behind it: the subscription then renewed at full price, with nothing backing that $0. No free month is part of Early Access. The cart now follows the same rules billing does and shows the real price from the first month.

A pay-per-unit line could show under the name “Lite”, because a plan change never updated the name. And the header printed the plan’s base price where the subscription total belongs, which made two prices for one page. The name now follows your plan, the header no longer shows the base price as if it were your total, and that line is called “Base Price”.

Some voicemail add-ons had been billed and never activated: callers were hung up on instead of reaching voicemail, and the owner could not save a greeting. Activation and purchase now happen in the same transaction, and an activation that fails makes the purchase fail instead of passing in silence. The affected accounts have been repaired.

The payment page could offer a US-dollar price beside the Canadian one, with a warning about exchange fees. Your taxes are computed in Canadian dollars from your province, and your invoice is a Canadian-dollar document; the payment page no longer offers another currency.

The cryptocurrency pay button spun and then did nothing: no address was ever generated. It now leads to a payment page with the amount, the address, a QR code, the confirmations and the expiry. A purchase completes on its own once the payment is confirmed, a pending address is reused if you come back, and a failed payment tells you so and that nothing was charged. A saved wallet is bitcoin only.

Settling an invoice never recorded the amount received, so a paid invoice kept its pre-payment balance forever. Six screens, including the tax document, printed a balance owing on an invoice marked paid. The amount your card actually paid is now recorded and the balance drops to zero. This covers purchases; subscription renewals follow in a later fix.

The purchase notification added the subtotal and the taxes without subtracting your credits, so a purchase settled partly with credits announced a higher figure than your card was charged. It now shows what your card paid, and names the credits you used. On mobile this is the only place that figure is shown to you.

The choice between refunding a card and issuing credit rested on a figure settlement never kept up to date, which would have returned card money as non-cashable credit once that figure was corrected. The choice now rests on the invoice total. Your data export also wrote the remaining balance where the subtotal and total belong; it now writes the real amounts, and so does the lifetime figure on the transparency page.

When a refund was granted, the invoice could not move to “refunded”: the system refused that status, and everything that was supposed to follow the refund, including withdrawing the refunded service, was abandoned in silence. The status is now accepted, it is only written on an invoice that was actually paid, and the invoice list and detail show it correctly. The amount returned does not appear on the invoice yet; that follow-up is under way.

Reading an invoice whose payment had failed made the read itself fail, which affected payment reminders and your data export. Your invoice list, payment reminders and data export open again, failed invoice included.

After a purchase, the receipt page asked the server for the same invoice every two seconds for a quarter of an hour, spent your account’s request budget, and locked the rest of the app behind a warning about your identities. The page now stops asking, a list that was already loaded stays on screen when its refresh fails, and the app retries on its own once the limit lifts.

The plan line said “Voicemail and a dedicated identity included”. Voicemail is an add-on, not an inclusion; the line now says a number adds an identity slot. The Vault Premium note now says it is the trial that needs no card. And on the web, opening the notification list now marks it read, incoming texts and missed calls included; the setting stays in the menu if you prefer the old behaviour.

The unit comes off when the carrier accepts your text, because that is the only moment we can take it. Its verdict arrives later, sometimes hours later, and nothing gave the unit back when that verdict was a failure. A text the carrier refused, or accepted and then did not deliver, now gives its unit back, and a picture follows the same rule. A text whose delivery is never confirmed stays charged: nobody can say it failed. If returning the unit fails on our side, we fix it by hand: tell us about a text that was not delivered and stayed charged.

The price of a picture sent internationally was worked out from the text rate instead of the published picture rate, which produced a far higher amount than the rates page shows. Calling and texting abroad is not available yet, so nobody paid it. When international opens, the published price will decide, and a test now blocks any gap between the price shown and the price charged.

An international send takes its amount off your International Balance before it leaves, and until now it came back only if the carrier refused the send outright. Calling and texting abroad is not available yet. When international opens, a text the carrier refuses, or accepts and then drops on the way, will return its amount, once, even if the notice reaches us several times. As with a text in Canada, a text with no delivery confirmation stays charged.

Before, a text refused because you had reached your sending limit showed an English error about a content policy violation. It was not one: you had simply sent a lot of texts in a short time. The retry button stayed there, and every attempt was refused the same way. Now the text tells you that you have reached your account’s sending limit, which counts across all your numbers together, and invites you to wait for room to free up. The retry button is gone, because waiting is the only thing that resolves it. Reaching this limit costs you no trust points.

Our screens tell you that deleting your account becomes final after 30 days, apart from the records the law or the security of the service requires us to keep, and that you can cancel until then. Nothing put that promise into practice: the only way to cancel was a control none of your pages offered, and asking for deletion closes all your sessions. Signing all the way back in, second factor included, now cancels the deletion, exactly as the promise says.

When you recover your account with your 24 words, WIGGWIGG now shows you your new recovery phrase and has you confirm it before saving your new password. Nothing changes until you have confirmed. If the page loses your 24 words along the way, it asks for them again instead of failing, and if an old phrase can no longer unlock your data, it tells you clearly.

Changing your password while keeping your 24 words no longer makes them unusable: WIGGWIGG now refuses any change that would leave your phrase unable to unlock your data. If your account holds encrypted data or a second sign-in check without an active recovery phrase, WIGGWIGG tells you so and holds new entries until you create one. Accounts whose phrase predates this update are offered a one-time step to bring it up to date with the same 24 words.

Creating an account on a phone froze for about 30 seconds before the 24 words appeared, with nothing on screen to say so. The computation now runs off the interface. Nothing changes in the words or in what they protect; an older build keeps the old path, slower but identical.

The account-creation steps opened as sheets over the form, which stayed readable underneath, account ID and password included. Each step now takes the whole screen. The 24 words stay concealed until you ask to see them, and the step that called itself the last one no longer does.

After signing out, the registration screen said “we cannot check registration right now” until the app was force-closed. The check now goes through the public path, like everything before sign-in.

A manual sign-out never removed the device’s push registration, so the account kept sending pushes to a device it no longer served. Deregistration is now the last request of the session, before the session is closed.

The Early Access terms were shown according to the general launch state, not the offer your code gave you. An invite code leading to Early Access therefore created an account without ever showing them or recording your acceptance. The terms now follow your code’s offer, on web and mobile.

A freshly created account has no identity; the number search let you search, tap Reserve, then show an error. A panel above the search now creates your first identity in one tap, and says what it does before you tap. The welcome credit earned by creating it is disclosed afterwards, in a note, rather than by the full-screen celebration.

Renaming a contact on the web made it disappear from the mobile app, favourites included, until a restart: mobile checked the contact against a stale picture of its vault and quietly set it aside. It now resyncs as soon as a contact or identity changes.

After too many password attempts, every screen refused you with the same message and never said how long the lock lasted. The web, the app and the lock screen now tell you what happened and when to try again, and offer account recovery if you no longer remember your password.

When a picture matches material confirmed illegal, the law requires us to keep a copy and send a report to the RCMP’s National Child Exploitation Crime Centre, in Ottawa. The report stays in Canada. Our wording used to name a United States organization that does not receive our reports. The other category, the one the Canadian detector flags as harmful to children, is blocked and kept by our own decision: nothing there is reported as a matter of course, and it is a review concluding it is criminal that leads to a report. The suspension notices, the picture-message consent screen, and the security page now tell that distinction the same way in both languages, and on mobile once the update is installed.

Automated checks warn you without rejecting the call or message. Your most specific personal rule decides whether the call or message is rejected. We removed switches that could not block yet and kept one warning on Apple’s incoming-call screen, “Likely spam,” when confidence is high enough.

Contact recognition has applied to incoming calls and texts from the start, but our descriptions only mentioned calls. The settings card, the Privacy Statement, and the whitepaper now say so plainly, and also spell out what happens to the fingerprints when you turn the option off.

The “Record by phone” option did not work. You called your number, you recorded your pickup announcement or the prompt for your callers, and the recording landed in your voicemail instead of replacing the announcement. This is fixed. Like the text read by a synthetic voice and the audio files you upload, this recording is readable by our servers, because the phone network is what has to play it during the call. Our privacy pages now name it.

Caller-intro screening had never rung anyone since it launched: the caller recorded their intro, then waited in silence until they gave up. Announce mode failed too, silently, for any caller whose carrier supplied a name, and the call came straight through as if the setting were off. Both work: your device rings, hears a short line and then the intro, and the pound key ends a recording wherever the prompt promises it. Callers now hear that they are being recorded and have ten seconds after the beep, then ringback while they wait. A caller you do not accept gets whatever your number already does on no answer, your own greeting included, instead of a generic one. A declined intro is no longer filed in your voicemail.

Pressing the accept key waited five seconds before acting, and the caller had hung up in the meantime, so accepting the call is what dropped it. The key now acts on the first press, in all three screening modes.

One voice badly described by the provider failed the whole list, so the voice pickers for your greeting and your screening showed nothing. A voice whose gender is unknown is no longer presented as male by default, web and mobile apply the same rule, and an empty list is treated as a passing outage rather than the retirement of the voice you had chosen.

On a passcode-locked iPhone the call rang, slide-to-answer did nothing, and the app ended the call: the session data needed to answer was only readable once the phone was unlocked. It is now readable after the first unlock since boot, on that device only. Your master key stays protected as before.

Even once a locked iPhone could answer, the call dropped a second and a half later: the registration made when the app woke was already stale, and the hang-up intent from a previous call applied to the next one. A reinstall could also ring the same iPhone twice for one call. All three are fixed.

A reconnect loop re-registered the device every few seconds, spent your account’s request budget in minutes, and showed “Too many requests. Please wait.” when you had done nothing; the account’s other devices were blocked without saying so. The loop is cut at its source, a reconnection waits out a known limit instead of spending into it, and a blocked device stays blocked for less time.

The moment the maintenance screen or the forced-update screen had to appear, the app crashed at launch, in a loop. This is fixed.

Removing an address asked the carrier to disable the number’s emergency service, not only to drop the address. 911 does not switch off: add, edit and remove apply to the address, and the service is part of the number. A removal that half-failed also left your civic address at the carrier; it now completes. Our records are corrected; if your number has no emergency address, it now says so and asks you to add one. The app and our FAQ talk about the address rather than a 911 that could be switched on or off.

A 911 call was metered like any other call, and could even bill at the overflow rate on an account past its balance. It is now marked at dial time and never metered.

Adding the MMS add-on to a trial number failed with no explanation: the dialog never showed the photo check you have to consent to. All four web purchase screens now share one consent panel, and a refusal is explained in your language. The “add an emergency address” reminder on a number’s card could never appear; it now shows when an address is missing and clears as soon as one is saved. A trial that carries add-ons also shows the amount its first renewal would bill.

During signup, the control that plays your anti-phishing security sound stayed silent on Safari for iOS while it worked elsewhere. The sound now plays as soon as you press it, with an indicator while it gets ready, and playback is unchanged on other browsers.

Contact recognition on calls existed, but settings search could not find it, on web or mobile. Searching for “contacts,” “recognition,” or “address book” now takes you straight to the setting, whether you want to turn it on or off.

After unlocking, your identities could disappear until you refreshed the screen. They were still there. The complete list now reloads on web and in the mobile app. If something still gets in the way, the screen tells you clearly.

A contact added on the web could appear without a phone number, email address, or call and message buttons even though its details were still saved. Its card now shows the right primary phone number and email address, along with the actions that depend on them.

Under a text that could not be delivered, the web app showed a Resend button above an explanation about a new, billed send, then handed your text back to the composer and sent nothing. The word you read and the action that runs are now the same thing.

At the two-factor step, leaving the app to open your authenticator, or simply taking a screenshot, wiped the pending challenge. What was left was a sheet with no field, no control to verify, and no way forward: only signing in again from the start got you out. Your verification screen now waits for you when you come back.

A new voicemail did not tell you. No notification on your phone, no entry in your notification list, no count on the Phone tab. You had to open your voicemail to find it. This is fixed: you now get a notification when the message arrives, and it takes you straight to the right number. Marking a message read or deleting it no longer fires a false notification on your other devices.

The web inbox showed “Couldn’t load this recording” for every voicemail received since the last encryption update: the player demanded a key those recordings do not need, then handed it the still-encrypted message as if it were a corrupt audio file. The player now asks for the right key and refuses to play anything but a decrypted recording.

Sending a picture from the app failed: the carrier refused the way we handed it the image, and the error told you the recipient’s number was invalid. A picture message is never end-to-end encrypted, so the carrier has to receive a readable copy. We place it behind a secret link that expires within minutes, the carrier fetches it, and we erase it. Your own copy, once past the illegal-content check, stays sealed in your account. Our privacy pages describe this hand-off.

The web composer offered to sell you the MMS add-on your number already has, and hid the attach button with it, so no picture could leave from the web. Received pictures did not display either, for the same reason as voicemail. Both are fixed, and sending now goes through the same path as on mobile, the one that encrypts the image.

Opening a text conversation left its badge at 1, open after open: the web counted one column and the server marked another. Both now count the same thing, a message that arrived while the tab was in the background is marked when you come back, and marking a conversation unread holds until you open it again.

When a connection remains stalled, the app now automatically attempts to restore real-time delivery. It no longer briefly reports an interruption during startup or a normal reconnection. When you start a repair manually, it shows its progress and result.

The notice bar at the top of the app showed only one message at a time. Some account warnings never go away until you act on them, such as two-factor authentication to turn on or more identities than your plan allows. Those warnings always won, so the people carrying one never saw outage or scheduled maintenance notices. The bar can now show a service notice underneath an account warning. Lower-priority news still waits its turn, so the bar does not become a wall.

The web used two words for the same thing and two verbs for unlocking an accomplishment, while notifications and the mobile app already used one of each. The settled term and verb are now everywhere, with three grammar mistakes fixed and one emoji removed from interface text.

The international rates preview showed English country names beside French prices. Country names and unit words now appear in your language, everywhere in the preview.

Switching language on the What’s New page translated the heading but left the release notes in the other language until you reloaded. Everything changes at once now, and the address follows too: in French it is /nouveautes. A release’s date also showed a day early, and that is fixed. The release notes now carry an index of every change, and you can copy a link to a single change to share it.

We fixed a few phrases that mixed up units, balances, and unit pools. The site now names each thing the same way the product does.

The long press that offered Paste stopped appearing: a code copied from your authenticator had to be retyped digit by digit. An explicit Paste control replaces the gesture. It works on both platforms, a screen reader can reach it, and it accepts only content holding exactly one code, so a phone number in your clipboard cannot submit itself.

The code field on the web gets the same fix as the mobile app: the extra frame around the boxes is gone, and pasting a code copied from your authenticator works again.

On Android, every digit you typed was drawn twice: once in its box, and once in black on top of it. The selection highlight spilled across the boxes too. Your digits now appear once.

You can now find a contact with any of their email addresses, including addresses added on the web. The first address no longer has a monopoly on the results.

The time shown in a web conversation carried no date and followed your device’s zone rather than your account’s, so a thread spread over weeks read as one afternoon. The date and time now appear in your language, the way they do in the mobile app.

On a sign-in or unlock screen taller than the window, the middle content painted over the WIGGWIGG logo and the footer. Every element now has its own room on both screens.

On a tablet, WIGGWIGG still asked you to unlock with your phone. The copy now says “this device.” Tablets no longer have to pretend they’re phones.

An identity name showed two asterisks instead of one. One is plenty to say a field is required.

The creation screen said you were editing an identity. It now says “New Identity” and saves “Edit Identity” for identities that already exist. Everyone gets the right screen.

The credit pill in the achievement celebration drew its amount in the same colour as its fill: invisible in dark mode, faint in light. The banner’s title and description also lacked contrast. All of it is readable, and the amount uses your language’s format.

A disabled button was made half transparent twice, once for the button and once for its label, which left the label nearly invisible in light mode. A disabled button is now an opaque muted surface with a readable label, for every variant. A busy button keeps its colour.

The phone-number colour was applied seven different ways, and one of them left white text too faint on the two-factor and phone-verification confirm buttons. Four number tiles also rendered a dull steel blue in dark mode, because their gradient was invalid. Tiles now share one recipe, two-factor takes the security colour, and an automatic check keeps white text from coming back on a fill too pale for it.

The invoices page printed its dates in US English beside French labels, and other pages passed France French or US English to the formatter. Some pages also came up blank because the date the server computed did not match the browser’s. Every date now carries your language and your time zone.

On a number’s page, the “Right now” line, which says which devices ring, could keep, for a minute or until a reload, an answer from a rule that had been deleted. It now updates as soon as a rule, an override or a setting changes, on the number’s page and on the cards in the list.

An achievement earned while the real-time connection was down only showed on the bell once you opened it. The counts now refresh when you return to the tab. This is a mitigation: the cause of the missed event is still being investigated.

The site used five French names for the same credits; one remains: “achievement credits”. The credits page also announced an amount as a grant: it is a ceiling, in five one-dollar tasks, one of which needs a number and therefore a Canadian province. It now says “up to”, with the condition, and no longer mentions trial credits or multi-month discounts that do not exist.

The seven trial sentences ran as one pale grey block. They are now grouped into paragraphs, in a readable colour, and your chosen number sits in its own block at the top of the setup step, as on the web.

On the number setup step, the trial and purchase buttons could sit inactive without saying why. Each now names the first thing missing: an identity, a province, your confirmation, or a choice of units.

Saving a number jumped it to the top of the results, under your cursor. Results now keep the order they arrived in, saved numbers have their own section above, and the red heart is replaced by the same yellow star as everywhere else. Two notices that did not help choose a number have left the search page; the province is still asked at the point where it matters.

Hiding the list on the dashboard made it disappear for good, and nothing else said which steps earn a credit. The credits page now keeps it as a reference, collapsible but never hidden. The card’s buttons were also nearly invisible in both themes; they read now, and hiding the list no longer looks like a destructive action.

On the web, creating an account now ends with your 24-word recovery phrase, with no step to skip. You see it, you keep it, you confirm it, and the account is created. It is your only way back in if you forget your password: WIGGWIGG cannot replace it for you.

If your account holds data only a 24-word phrase can recover and that phrase does not exist, both web and mobile say so at all times, with the link to create one. Everything you already have stays readable and usable, and this message affects neither your calls nor your messages. Adding new contacts or new vault entries waits for your phrase, whether one at a time or by import, because adding is the one thing that grows what you could lose.

Copying gave 24 words on one line, while the website expects the numbered list the web produces. Mobile copy is now numbered, one word per line, tells you if it failed, and the clipboard is cleared after 30 seconds as long as the app stays open.

Every identity field now has a Copy button and long-press to copy, with a confirmation. Every identity value is treated as protected: the copy is kept out of the clipboard preview and keyboard history on Android, and the app clears the clipboard after 30 seconds if it is still open. Hidden fields hide themselves again when you leave the app. Screen readers hear the label and the displayed value, never a masked one, and the edit screen is translated.

The newsletter form accepted the page you arrived from, the browser and device you were using, and three campaign tracking codes, on top of your email address. It no longer accepts them, but what was collected before this change stays on file. It now asks for your email address, the list you chose, your language, and a short label saying where the signup came from. A country is asked only for international updates, where it tells us which countries people are asking about. When a signup fails, the technical note it leaves holds neither your email address nor your country.

The sign-up panel answered a question nobody had asked about a sign-up credit; it now says what registration includes. The trust badge on the home and sign-in pages names the four encrypted data classes, passwords, identity information, contacts and stored message content, no more, and is no longer a link. The responsible-disclosure page is a link in the welcome step. On mobile, the warning under the 24 words explains why a screenshot is a risk, and the three badges stack instead of sharing the screen in three columns.

It rendered as small grey text with its icon stranded at the far edge of the card. It now has a link’s colour, its icon beside it, a large enough target, and a name assistive technology announces.

The page asked the same question twice: three cards at the top, then the same buttons lower down. Each card now ends in what it promises, the web app or its own Android variant with the version, date and file fingerprint. A variant with no file available no longer offers a button to nothing.

The page announced three contributor categories and named people in only one. It now has a design section and a founder’s note for the helping hands: a loaned old iPhone, more than fifty bug reports, and the support of family. Crediting the tools behind Patch and the Wiggs makes public, for the first time, that all mascot art is AI-generated from the founder’s own reference images; our page on how we use AI says so too, with the intention to hire an illustrator when the project can pay for one.

A blue band appeared at the top of the app to tell you a new version was ready, and refreshing forced you to unlock your vault again. The interruption cost more than it gave, so it is gone. You still get the latest version whenever you open or reload the app normally. A tab left open for a very long time may keep running the version it started with.

Your phone now rings as soon as the call arrives, without waiting on the steps that prepare your notifications.

Your dashboard and phone number pages open faster, especially with several numbers. They used to look things up one number at a time.

The web app’s pages showed a loading shimmer before your content. They now arrive ready, and nothing shows until WIGGWIGG has confirmed your lock state.

In some cases a failed unlock attempt could reopen your session unlocked without asking for a factor again. Your session now stays locked until an unlock succeeds, and a lock required by your security policy applies immediately. Unlocking with a time-based code or a passkey keeps working.

The readable copy a picture message leaves with the carrier was only removed by a cleanup rule, up to four days later. It is now destroyed as soon as the carrier has fetched it, and again when the message finalizes if the first confirmation never arrived. Verified in production: seconds after a send, nothing of that copy remains.