This Privacy Statement describes how WIGGWIGG INC. (“we”, “WIGGWIGG”) collects, processes, uses and shares personal information about individuals browsing the WIGGWIGG website (“Website”) and about individuals using the WIGGWIGG web application or mobile application (collectively the “WIGGWIGG Service”).
The use of the second person (“you”, “your”, “yours”) refers to a visitor of the Website or user of the WIGGWIGG Service.
The contact details of the person responsible for processing personal information under this Privacy Statement are as follows:
Privacy Officer WIGGWIGG INC. 100-394 boulevard Maloney Ouest, Gatineau, Quebec J8P 6W2, Canada privacy@wiggwigg.ca (For any inquiry concerning the WIGGWIGG Service, please contact us through the WIGGWIGG Service)
What we corrected on September 9, 2026
The previous Privacy Statement incorrectly said that the stored copy of your message bodies and voicemail audio was sealed to a key specific to your device. We corrected that description and the related security boundaries:
- Under our current method, that copy is sealed to the account communication key. Supported clients open that key after you sign in and unlock. It is tied to the account, not to one device.
- Some communications retained from the private beta remain readable by our servers. Today, only signing in and unlocking with a supported web client automatically starts a bounded pass, for up to 50 eligible SMS rows. Mobile sign-in does not start that pass. The pass does not re-seal private-beta voicemail, legacy call-log numbers, MMS attachments, retained object copies, or every remaining SMS row at once. Those excluded copies remain server-readable until later passes or separate maintenance.
- On iOS, the notification extension currently receives a copy of the raw account communication key after the device’s first unlock, even when notification previews are hidden. That copy remains available when the vault or device locks and can open account history sealed to that key, not only a notification preview. The app attempts to erase it at sign-out, but does not confirm that the erasure succeeded or retry after a failure. Android instead uses a separate key limited to notification previews.
The communications corrections describe how the current system works. This version also covers the information requested to calculate taxes on a purchase or renewal. It is encrypted separately from your vault and remains readable by WIGGWIGG. Necessary tax records are generally kept for six years after the end of the last relevant year, including after account deletion. A specific legal requirement may extend that period. You confirm where you live at checkout, or when you update it for renewals.
1. Collection of personal information
1.1. User Information
We minimize our collection of personal information as much as possible. We process information you choose to provide and operational information generated by the features you use. The applicable categories, purposes, and retention periods are described in this Statement.
WIGGWIGG does not hold the keys needed to read your password, zero-knowledge-encrypted identity details and contacts, or message content in the default sealed-storage path. Your password is not uploaded. Identity details and contacts are encrypted on your device before upload. Calls and messages pass through WIGGWIGG and telecommunications providers in plaintext so they can be routed. Message content is also checked as described below. After that transit and those message checks, stored message bodies and voicemail audio in the default path are sealed server-side under one-time keys WIGGWIGG does not hold. This statement does not cover operational data needed for phone routing, billing, and support, optional features that require server-side processing, the illegal-content check we run on picture messages, or copies preserved when content is flagged. Server-readable data and the exceptions you choose to enable are described below.
The app includes a performance telemetry switch, off by default. If you turn it on yourself in settings, the app sends performance measurements and error reports to our own observability server, with no cookies or account identifier. On mobile, a random code groups ordinary traces from one app launch without being tied to your account; the incoming-call wake diagnostic omits it. Separately and regardless of this switch, the mobile app reports startup failures, uncaught global errors, and unhandled promise rejections so we can diagnose an app that will not open. Those reports contain a truncated error message, name and stack, whether the error was fatal, the build commit, app version, operating-system summary, time, and a random per-launch code. They contain no account identifier or form values, and query strings are removed from web addresses in stacks. An error message or stack can still contain personal information if the error itself includes it. The setting is synced with your account, so it applies to all your devices.
Registration asks for no billing country, province, or address, and those details do not determine your account tier. When you make a digital purchase or update your residence information for a digital subscription’s renewals, we separately ask for your country and province, territory, or state, and your confirmation that this is where you live. Checkout for Canadian phone service asks for a Canadian province. Phone-trial activation validates the province without adding it to the trial payment session or the record used to enforce one trial per account.
To enforce one phone trial per account, we retain the link between your account, the trial payment session, and the time its $0 checkout was accepted. If a verified permanent failure occurs while activating the number, this same record retains the time when your first and only replacement attempt was authorized. The next accepted attempt replaces the failed-session link with the new session; the authorization time remains on the record to prevent another replacement. The record is deleted with your account. If you remove your verified personal number after using your phone trial, we keep a keyed fingerprint of that number, linked to your account, with the verification’s dates and technical references, until the account is permanently deleted. Until then, no other account can verify that number, so it cannot be used for a second trial. We delete the number itself from the verification and from your identities, but we hold the fingerprint’s key and can test whether a given number matches it; encrypted backups that still contain the number age out within about a month. Our phone-verification audit log also keeps, as a security record, a keyed fingerprint of every number verified or submitted for verification on your account, with the account link and the date and result of each attempt. That log has no deletion schedule yet: it is kept even after your account is permanently deleted, until we set and apply a retention period. We also count total accepted $0 phone-trial checkouts per UTC day, without an account identifier, to monitor cost and abuse and to stop new activations if necessary. That stop does not disable activated numbers or 911 service.
1.1.1. Optional signup information, customer research, and onboarding measurement
WIGGWIGG may offer you several separate optional choices. One of them records a limited signup-information bundle to produce grouped statistics about how people find WIGGWIGG and the app or device type used to sign up. On the web, this bundle can contain three signals: the signed opaque code for a WIGGWIGG-controlled campaign, when one is present; a broad previous-site category reduced locally from a closed list of exact hostnames; and the web registration category. In the mobile app, the separate choice written for that app may record the signed opaque code for a WIGGWIGG-controlled campaign or a broad source category passed by a WIGGWIGG signup link, together with the iPhone (iphone_native), iPad (ipad_native), or Android (android_native) category; if the app cannot determine that category reliably, it records unavailable. Previously recorded iOS signups remain in the historical ios_native category. A link passes either a campaign code or a broad source category, never both. The app accepts only these closed formats, keeps the value in memory until your decision, and uses only the platform information already provided by iOS or Android to distinguish these categories. It uses no user-agent string, screen size, device model, or device identifier. It records no raw campaign parameter, web address, previous page, or other technical device information for this measurement. Another choice lets you answer short questions about discovering WIGGWIGG, your intended use, or your trial experience. During functional onboarding, a separate box can also let you agree that WIGGWIGG record the general Phone, Identity, Vault, or Explore path you already choose. Leaving that box unchecked does not change the path or service and saves no optional onboarding choice or research response on our servers. The “First successful inbound delivery within 48 hours” measurement is also separate and requires its own consent. It is not a behavioural activation measure. Agreeing to one choice does not authorize any other choice, a partner offer, or a referral.
Each choice starts unchecked and has its own notice. Current WIGGWIGG clients send none of the optional signup-information bundle unless you check its separate choice. If you leave it unchecked, none of that information is sent for this measurement or linked to your account, and your account is created normally. WIGGWIGG accepts this optional bundle only during the first hour after our server creates your account. If that hour expires, your account, trial, service, and entitlements are unchanged, the submission is not saved, and no retention period begins for it. For research questions, “Not now,” “Don’t ask again,” and “Skip for this trial” record neither consent nor an answer. Declining or not answering the “First successful inbound delivery within 48 hours” choice does not change your trial, service, or entitlements.
Research questions and the optional onboarding-path choice use predefined choices only, with no free text. For discovery, you choose a category and then, when relevant, the search engine, AI assistant, social platform, app store, or type of recommendation. We keep only your final choice, without inferring it from the previous page. “Other” and “I don’t remember” are separate answers. The onboarding-path choice records only phone, identity, vault, or explore; it does not record the route you later visit or infer product use from activity. An early-journey form may be offered after 72 hours to understand how you discovered WIGGWIGG, whether your context is personal or work-related, and what you hope to accomplish. A Phone form may be offered during the final 48 hours of your active trial, or when you return to the app after the trial ends, only if you have never made a plan commitment for that subscription. Vault and Identity forms are opened voluntarily in settings. Each question can be skipped separately. Only predefined answers that remain visible in the selected branch are saved. A question already open may remain available until its short response window ends. These answers describe people who choose to respond, not everyone who registers or everyone who does not choose a plan.
To present these questions without asking repeatedly, WIGGWIGG keeps server-readable operational events, such as whether a question was shown, deferred, or skipped. These events never contain answer content. They stay linked to your account for no more than 60 days, appear in subject access and your data export, and are erased when you delete your account. If you withdraw an answer, the events may remain until that 60-day limit but are excluded from new statistics. “Not now” and “Skip for this trial” are neither consent nor answers.
To honour “Don’t ask again” or the withdrawal of a research answer, WIGGWIGG may keep until account deletion a record of which form it was, its version, whether it was withdrawn or hidden, when and how often it was offered, its response deadline and, when applicable, the trial it covered. This record contains no answer. It appears in subject access and your export, is excluded from new statistics after withdrawal, and cannot show that form again after suppression or withdrawal.
The campaign code appears only in the link fragment. The marketing site immediately removes it from the visible address. So it can survive navigation between marketing pages, it may be kept only in the current tab’s session storage, under wiggwigg:acquisition:registered-campaign, until the handoff to signup or until the tab closes. It is neither sent nor counted when you open the link. At handoff, it is removed from that storage and kept in application memory until your decision. If you leave the choice unchecked, it is discarded. If you agree, it is sent with the other optional signup information, then validated before it is recorded as a WIGGWIGG-controlled campaign.
When you arrive at the marketing site in a tab, your browser locally reduces any available previous page to a closed category such as Google, Bing, Kagi, ChatGPT, Claude, a social network, another external site, or no usable previous-site category. The marketing site temporarily keeps only that category in the tab’s session storage, under the key wiggwigg:acquisition:observed-source, in the format v1.<closed category>, for example v1.google. The value contains no web address or hostname and disappears when the tab closes. When you continue to the application, the category is handed to the application in your browser, removed from the visible address, and kept in memory until your decision. Our servers receive it only if you check the optional choice during signup. Current WIGGWIGG clients do not send raw UTM parameters for this measurement. An older installed client may still transmit legacy raw UTM compatibility fields with account registration, but the server discards them before logging, forwarding, persistence, export, or measurement. They are never saved or used to produce these statistics. For this optional measurement, we neither send nor keep a full link address, a hostname, a search term, an AI-assistant conversation, the user-agent string, or other technical details about your device. The mobile app may send the closed campaign code or broad source category received through a WIGGWIGG link, together with its platform category as described above, only if you accept its optional choice.
If you agree, WIGGWIGG uses the existing server-readable time when your account was created only to determine whether the first-hour collection window remains open. We retain the first accepted server time with the consent and evidence record. Those timing values and the accepted signup information are included in access to your information and your data export, remain linked to your account in our live systems for no more than 60 days, and are then unlinked no later than 60 days after collection. They are used only to produce grouped statistics for understanding discovery, registration surface, intended use, and the trial experience. These statistics may relate the accepted signals to post-trial plan commitment and approved conversion outcomes: external payment, payment mixed with credits, or credit-only activation. These consents do not authorize the separate “First successful inbound delivery within 48 hours” measurement.
If you consent separately to this measurement, we keep your consent and, only if a first successful inbound delivery occurs after that consent, one closed result indicating whether it happened before or after 48 hours following provisioning. No negative or uncertain result is recorded in your account-linked information. At D60, the absence of a qualifying delivery may contribute only to an identifier-free grouped statistic when completeness evidence has been verified. An unknown state describes only the availability of statistics; ineligibility is a transient decision that creates no measurement record. It counts an inbound SMS accepted into the WIGGWIGG inbox, or an inbound call answered by your device or handled by WIGGWIGG voicemail. It excludes ringing, missed or rejected calls, blocked or held messages, verification, tests, emergency callbacks, duplicates, retries, and every event that happened before your consent became effective. We keep no number, counterparty, content, communication identifier, duration, exact time, provider text, device detail, or timeline. The linked result is kept no later than D60, appears in access to your information and your export, and is erased if you withdraw your consent or delete your account. Only identifier-free grouped statistics are published. Cells with fewer than ten accounts and complementary cells that could reveal them are suppressed. This is not a behavioural activation measure and never changes your access, eligibility, prices, offers, communications from us, support, fraud detection, or any other individual treatment. This information is never used to make an individual decision about your access, registration, trial, prices, support, the offers you see, or your eligibility. It does not authorize contact from us.
An authorized WIGGWIGG administrator can see only the source, medium, and campaign of a registered campaign by opening a specific account after recent reauthentication; that read is audited. This is the programme’s only person-level exception. No internal person-level view shows the broad previous-site category, registration surface, a research answer, or an intended-use situation.
You can separately view optional signup information, research answers and choices, your decision and result for “First successful inbound delivery within 48 hours,” and the information used to remember when forms were offered in Settings > Privacy & Data > Manage your data and in your data export. Partner offers and referrals remain in their existing authoritative programmes; these optional measurements do not create or activate them. While a voluntary research answer or choice is still linked, you can withdraw it. You can also separately withdraw consent for the first inbound delivery measurement. Withdrawal stops future collection for that measurement, erases its linked result, and invalidates prepared exports that contain it. Withdrawing a research answer or choice erases that linked answer, prevents its inclusion in new statistics, and invalidates prepared exports that contain it. The operational events and form record described above may remain for their stated periods to preserve the withdrawal and suppression, without answer content. The optional signup-information bundle has no withdrawal control and is unlinked automatically under the schedule below. A copy you already downloaded cannot be recalled.
No later than 60 days after collection, we erase the link to your account. This is the retention limit for person-linked research evidence, not the limit for trend history. We may keep identifier-free monthly grouped cohort releases without a fixed deletion date so we can compare long-term trends, including year over year. These releases contain no account identifier. Cells with fewer than ten accounts, complementary cells that could reveal them, and unsafe adjacent releases are suppressed. We can no longer remove your contribution from a grouped release already produced in that form. An encrypted copy of the linked information may physically remain in our routine backups for about 30 more days. It is not used to produce new statistics. If we restore a backup, we reapply withdrawals and erasures before returning the service online.
A recorded campaign means only that a valid code was submitted with your consent. A previous-site category means only what the browser could reduce at registration. These signals do not prove what caused the registration, a recommendation, an endorsement, association membership, or a partner relationship. They do not create a referral or activate an offer or benefit.
1.2. Calls and Messages
Calls, SMS and voicemails travel over the public telephone networks. That transit is not encrypted and stays visible to carriers, as it does for any phone service that interoperates with the public network. No phone provider can encrypt that segment. For a conversation that needs to stay end-to-end encrypted, use a service built for it, such as Signal.
Carrier and telecommunications rules require automated checks on SMS and MMS traffic. We go further than those rules require and also check picture messages for known illegal content; running that check is our decision. Those checks run in transit, on the plaintext, before encryption. When nothing is flagged, we keep no fingerprint of the content at all, only the result of the check and minimal metadata, and a 90-day sweep deletes those records. For images, when something is flagged, we also keep a keyed one-way fingerprint, so the same image is recognised if it comes back. We keep no fingerprint of the text of your messages, flagged or not. One exception applies: when content is flagged as illegal, we preserve a copy, as the law requires. We also preserve a copy when a detector flags a picture as harmful to children without placing it in its confirmed-illegal category; that is our decision rather than a legal obligation. That category is not a finding that the picture is legal: nothing is reported automatically, but if a review concludes the material is criminal in Canada, we report it. Neither copy can be deleted at your request.
We save a copy of your messages and voicemails in your account, and we do not use them for any purpose other than providing our services. Under our current sealing method, stored message bodies (SMS, MMS) and voicemail audio are encrypted at rest under a one-time key, which is itself sealed to the account communication public key. Supported WIGGWIGG clients open the corresponding private key after you sign in and unlock. The key is tied to the account, not to one device, and we keep no key that can decrypt the sealed copy. This is not end-to-end encryption: it protects what is stored, not what is in transit.
Some communications retained from the private beta still use our older server-side encryption and remain readable by our servers. Today, only signing in and unlocking with a supported web client automatically starts a bounded pass that can re-seal up to 50 eligible SMS rows. A mobile sign-in can provision the account key but does not start that pass. The pass does not re-seal private-beta voicemail, legacy call-log numbers, MMS attachments, retained object copies, or every remaining SMS row at once. Those excluded copies remain server-readable until later passes or separate maintenance.
The exceptions, which we state explicitly:
- Listen by phone. If you turn this on for a number, new voicemails on that number are kept in a form our servers can read, so you can hear them by calling your voicemail. The option is off by default. Turning it off returns new voicemail to account-key sealing, but does not automatically re-seal older server-readable voicemail from the private beta. That older voicemail remains server-readable until separate maintenance.
- The intros your callers record. If you use call screening, the short recording in which the caller says who they are is kept in a form our servers can read, because the phone network has to play it to you when the call rings. The caller has no account and no key with us.
- Automatic replies. The text of your automatic replies is kept in a form our servers can read, because our server is what writes and sends them on your behalf.
- Contact recognition on calls. If you turn it on, a keyed fingerprint of each contact’s number is stored so we can recognize a known caller on incoming calls and a known sender on incoming texts; while it is on, those numbers are recoverable by our servers. Off by default; turning it off erases the fingerprints from our live systems, and encrypted backups age out within about a month.
- Calling devices. After you accept the current Privacy Statement, official WIGGWIGG clients automatically register up to 10 active browsers or mobile devices on your account when you sign in and unlock your data so they can receive your calls. The random recognition code stays on the device that created it and is sent to us only transiently for recognition; we neither log nor store the raw code. We retain a keyed, account-scoped fingerprint. While the registration is live, we can read the account link, a random internal device id, browser-or-mobile class, account-local display number, associated phone ids, lifecycle state, and registration, readiness, and lifecycle activity timestamps. For each phone number, we can also read whether all devices or only the devices you choose may ring and infer the selected device links. A custom device name is encrypted on your device and is not readable by us. A historical calling-device decline or withdrawal remains a server-readable paused routing state until you explicitly turn calling devices back on after recent authentication; we do not retain a separate date for that state change. Removing a device immediately stops new calls to its registration, but provider cleanup may take time. After cleanup is confirmed, we erase the active metadata and encrypted name. We retain only the account link, random internal id, keyed fingerprint with its key version, and revoked status. While that minimal record exists, it blocks reuse of the old code. The record is deleted with your account or earlier when its fingerprint key is retired. The WIGGWIGG app creates a new recognition code when it registers again. A separate account-scoped event ledger, containing only a random internal id, the account link, and the attempt time, enforces rolling registration limits and is swept after its 24-hour window.
- iOS notification decryption. After the device has been unlocked once, the current iOS app copies the raw account communication keypair into a device-only shared keychain so its notification extension can decrypt notification content. It does this even when your notification display setting is Nothing. The copy survives vault lock and device lock, and it can open all history sealed to the account key, not only notification previews. The app attempts to erase the copy when you sign out, but does not confirm that the erasure succeeded or retry after a failure. The copy is not uploaded to WIGGWIGG. Android uses a separate display key whose scope is limited to notification previews.
- Your phone lines. Your WIGGWIGG numbers, the personal number you verify for call forwarding, and the greetings, pickup announcements and caller prompts for a line, whether you write them or record them, are readable by our servers, because they are what the phone network runs on. When the phone trial requires a verified personal number, the number you verify is also used for trial eligibility: among other reasons, the trial is refused if another account has already verified that number, if it is already an active WIGGWIGG number, or if it is an internet-based or toll-free number.
- Line-type lookup. When the phone trial requires a verified personal number, that number is sent to Telnyx, in the United States, to learn its line type and carrier, to check its eligibility for the trial. For protection against unwanted calls and texts, the number that calls or texts you is also sent to Telnyx, unless you turn this lookup off for the WIGGWIGG number that receives the call or text. If contact recognition on calls is turned on, a number recognized as one of your contacts is not sent. We keep, in Canada, for 90 days, a keyed fingerprint of the number with the carrier name and line type; we hold the key, so we can test whether a given number matches it. We generally reuse that result instead of asking Telnyx again. The link to the account that triggered the lookup is cleared about 2 days after the lookup.
- Support requests. The content of your support tickets is encrypted, but the ticket text is readable by you and by WIGGWIGG support, so we can handle your request; files you attach are stored readable by our servers, so support can open them to help you. You can also choose to attach technical details about your device, your app or your browser, to help us reproduce the problem: this is optional, you decide when you send the request, and those details are readable by WIGGWIGG support too. No one else can access it.
- Call metadata. Call detail records (date, time, duration, your own line’s number) are encrypted under a server key: we need to be able to read them for billing and for our regulatory obligations.
Our servers, databases and file storage are in Canada. Temporary copies of files we keep for you may also sit in our content delivery network’s caches, including outside Canada (see section 3). Our providers and the third parties the service must work with run their own infrastructure, including in the United States: telephone traffic passes through our carrier and payments through our payment processor. What they retain, where, and for how long is governed by their policies, not ours.
1.3. Information collected through the Website
On the Website, your browser may automatically reduce the previous page to a broad category and temporarily keep it in the tab’s session storage, as described in section 1.1.1. This processing stays in your browser. Our servers receive the category only if you check the optional choice during signup.
If you subscribe to our newsletter, you voluntarily provide your email address and the language and country you pick. We encourage you to use an email address that does not identify you. Newsletter signup forms do not send campaign parameters, the previous page’s address, or technical details about your device to our subscription service. We do not use any analytics tools on the Website.
1.4. The community forum
WIGGWIGG operates an optional community forum (community.wiggwigg.ca), hosted on cloud infrastructure we operate in Canada and not on a third-party community platform. Access is only through your WIGGWIGG account; the forum creates no separate password and sends no email.
You take part under a display name that you choose. We send the forum this display name, a pseudonymous identifier irreversibly derived from your account, and a synthetic email address, never your real name, your account identifier, or your real email address. We do not publicly link your identity to your messages, but if you reveal personal information in what you post, it may be associated with you.
The forum does not receive your real IP address: it is replaced with a constant value before reaching the forum. As with the rest of the WIGGWIGG Service, our load balancer and our cloud provider’s firewall briefly log connection IP addresses for security purposes, retained for at most 90 days. We no longer add a fingerprint of your IP address to our databases, and we are erasing the ones that are there; our backups still contain some until they are deleted. A temporary fingerprint of your address is still used to limit the number of requests, and it is not kept. The firewall also counts requests per address and blocks the ones that go over its limits. Our cloud provider’s audit trail records some file accesses with the IP address, and the source address of administrative requests, for up to seven years.
The forum offers an anonymous mode that hides your display name from other members, but not from the system: the technical link between the anonymous profile and your membership still exists. After roughly a week without anonymous activity, the forum issues you a new anonymous profile, and posts made under the previous one are not tied to the new one.
Unlike data subject to our zero-knowledge architecture (section 1.1), the content you post on the forum is readable by the forum software and visible to the public or to members, depending on the category. Post accordingly.
1.5. The referral program
When the referral program is open to your account, you can invite someone with your referral code or link.
- Your code. When the program is open, a random referral code is linked to your account when you choose to create one on your referral page. The link between that code and your account is encrypted, and WIGGWIGG can read it. The code is deleted with your account.
- The link between two accounts. When someone signs up with your code, or you sign up with someone’s code, we keep the link between the two accounts, meaning who referred whom, along with the signup date and the status of the invitation. The referral offer becomes the account’s welcome benefit only if the invited person then chooses it on the welcome offers screen; that choice is final, and the account keeps a record of it. If the invited person chooses a partner offer instead, or does not choose an offer within 30 days of signing up, the invitation ends and the link between the two accounts is deleted. The invitation also ends if the person confirms a first qualifying paid purchase before choosing an offer. A purchase paid entirely with credits counts; a free trial and a $0 transaction do not, and a later refund does not reopen the invitation. About a week before that deadline, an invited person who has not chosen anything yet gets a reminder in their account.
- Phone-number setup. The referral program no longer records phone-number setup or its date in the referral record. Some older records may still contain this milestone, encrypted on the server and readable by WIGGWIGG. It follows the same retention and deletion rules as the referral record. Setting up a phone number is not a referral eligibility step and does not trigger a credit.
- The inviter’s credit. To know whether that credit is due, we go through the invited person’s invoices, payments, and disputes to find the paid periods of their phone plan: amounts before tax, discounts, credits used, and refunds. We keep a record of the two paid periods that count until the invitation ends: when the credit is paid, when either account is deleted, or 12 months after the offer was chosen if no second eligible month has started and been paid by then. If that second month starts and is paid in time, the record stays until the credit is paid or refused, which the 30-day wait, a dispute, or a review can delay.
- The welcome credit. The details used to apply it are erased about 30 days after the offer was chosen if it went unused, otherwise about 14 months after that choice. Credits are part of the billing records described in section 3.
- Who can read this information. WIGGWIGG can read it. The link between the two accounts is encrypted at rest, but not zero-knowledge: we keep keyed fingerprints and can read who referred whom, because our servers need that to pay out credits. Your code and the choice of the referral offer are stored without encryption of their own. The inviter sees neither the name nor the Account ID of anyone who signs up with their code. Their page shows numbers (friends invited, friends who subscribed, credit earned), and a notification announces each credit paid, saying that someone they invited has paid their second month. Depending on how many people used their code and when those numbers change, they can still work out that a particular person signed up, became a customer, then paid a second month of a phone plan.
- If either account is deleted. Before either account is deleted, we pay the inviter’s credit if it is already due, meaning the 30-day wait on the second paid month is over and no dispute or review is holding it. The deletion then ends the invitation: a credit that is not yet due will not be paid, and the link between the two accounts is deleted with the account. However, if the inviter’s account is deleted before the invited person has chosen an offer, the invited person can still choose the referral offer until the earlier of 30 days after signing up or confirmation of their first qualifying paid purchase. Until then, their account keeps a record of the invitation, with no link to the deleted account; if they do not choose the referral offer, that record is deleted by the end of those 30 days at the latest. A credit already paid stays in the inviter’s billing records, but once either account is deleted, those records no longer connect the two accounts. When the invited person’s account is deleted, their choice of the referral offer is deleted with the account, unless that choice has already given them their welcome credit; in that case, it stays in their billing records without naming the person who invited them. The deletions described in this section apply to our live systems; routine encrypted backups age out within about a month.
- Initial-program limit receipts. For this limited initial program, each admitted invitation creates a permanent receipt containing a random internal identifier associated with the code, the admission time and CA$5 of reserved face value. It contains no Account ID, relationship ID or public referral code. While your code exists, the receipt is pseudonymous and you can see it in your export and privacy dashboard. If your code is deleted, the link between your code and this internal identifier is deleted; the identifier and receipt remain, but then have no link back to you in the live database. Encrypted backups can retain that link for about a month, until they age out. We keep the de-linked receipt so deleting an account cannot reopen the initial program’s lifetime financial limit.
2. Processing of personal information
We process personal information collected through the WIGGWIGG Service for the purpose of operating the WIGGWIGG Service. When you give a separate consent described in section 1.1.1, we also process the applicable optional information to produce grouped statistics about discovery, registration surface, intended use, or the trial experience and to improve the service. This optional processing is used for no other purpose.
Automated checks run on message content in transit (section 1.2). We have no access to the content of your calls.
3. Personal Data storage and retention
Our databases and file storage are in Canada (AWS ca-central-1). Exception: our content delivery network may keep temporary copies of files we keep for you, such as voicemail, the intros your callers record and support attachments, at edge locations in the United States, Mexico, Canada, Europe, Israel and Türkiye. Copies of files our servers can read, such as support attachments, are cached in that same readable form.
Any information transmitted on telecommunication networks transits through infrastructure located in the United States and operated by Telnyx, our telecommunication services provider. We do not keep User Data at rest in the United States, except the temporary cached copies described above.
We retain User Data while the relevant User has an active account on the WIGGWIGG Service, subject to the shorter periods described in this Statement. Account deletion has a 30-day grace period during which signing back in cancels the request. After that, personal data is permanently deleted except for invoices and necessary tax records; verdicts for content checks that flagged something and the preserved copy for either match class described in section 1.2, only one of which is legally compelled; security audit logs kept up to seven years for service security; and the phone-verification audit log described in section 1.1, which has no deletion schedule yet.
Retained billing records include amounts, dates, taxes, payment-method type, and the product billed. They also include the information needed to support the tax treatment: the country and province, territory, or state you selected, and your confirmation that this is where you live. The information collected to support the tax treatment is encrypted separately from your vault and remains readable by WIGGWIGG. It does not include your vault contents or communications.
Issued referral credits and offer choices that gave a welcome credit remain in billing records, without identifying the other account after either account is deleted. No referral link between the two accounts remains in our live systems after permanent deletion. The initial-program limit receipt remains permanently; deleting the code removes its link to the account in the live database. Encrypted backups can retain the former link for about a month, until they age out. Section 1.5 gives the detailed rules.
We keep these tax records for the period required by law, generally six years after the end of the last relevant year. A specific legal requirement may extend that period. Account deletion does not end this obligation.
4. Security Measures
User data is hosted on servers operated by our service providers and is protected by industry-standard security measures. Our zero-knowledge protections cover the specific data classes identified in section 1.1: your master password is not uploaded, and WIGGWIGG does not hold the keys needed to decrypt password entries in your zero-knowledge vault, encrypted identity details and contacts, or the default sealed storage copy of your message content. Other account, billing, routing, safety, audit, and opt-in feature data remains server-readable as described in this Statement.
Our employees and suppliers are informed of the confidential nature of personal information collected through the WIGGWIGG Service and are made aware of the appropriate security measures to prevent unauthorized access to personal information.
5. Disclosure of Personal Information
We only share or disclose personal information in the manner described in this Privacy Statement or when we have obtained your express consent. Your personal information may be disclosed to the categories of persons described below for the following purposes.
5.1. Employees
Personal data is accessible to our officers and employees who must access it in order to use the same as set forth in this Privacy Statement and to provide our services to our Customers.
5.2. Service Providers
We process encrypted personal information through our service providers, who undertake to keep this information confidential and to limit its use to what is necessary to support our services.
Our current service providers (subprocessors) are:
- Amazon Web Services (AWS): cloud hosting of our databases, encrypted media storage and application servers, located in Canada; its content delivery network keeps temporary cached copies at edge locations in the United States, Mexico, Canada, Europe, Israel and Türkiye.
- Telnyx: voice, SMS/MMS and 911 (E911) connectivity, and line type and carrier lookup, located in the United States.
- Stripe: payment and subscription processing, in the United States and globally.
- Blockonomics: cryptocurrency payment processing (Bitcoin), for subscription and donation payments, global.
- Resend: delivery of our newsletter (and unsubscribe confirmations) to addresses subscribed on the Website, located in the United States.
- Canadian Centre for Child Protection (Arachnid Shield): automated scanning of media messages for child sexual abuse material (CSAM). The picture’s perceptual fingerprint is computed on our servers and only that fingerprint is sent; no detector ever receives the picture. Confirmed matches are preserved and reported as the law requires. Located in Canada.
- Microsoft (PhotoDNA): automated scanning of media messages for child sexual abuse material (CSAM), alongside Arachnid Shield. The PhotoDNA hash is computed on our own servers using Microsoft’s edge-hashing library and only that hash is sent; no detector ever receives the picture. Confirmed matches are preserved and reported as the law requires. Located in the United States.
- Apple (APNs): push notification delivery to iOS devices (device tokens and encrypted notification payloads).
- Google (FCM): push delivery for the Android app installed from Google Play (device token, encrypted payload). Our de-Googled build uses our own relay instead.
- Browser push services (Google, Mozilla, Apple, Microsoft): web notification delivery, only if you allow notifications in your browser. The service is the one your browser uses, in its provider’s region. It receives the push endpoint and an encrypted payload.
- Have I Been Pwned (Pwned Passwords): breach checks for the passwords saved in your vault and for the password you choose for your WIGGWIGG account. Each password being checked is hashed on your device, and only the first 5 characters of its SHA-1 hash are sent, through our own edge cache or our servers; never the password or its full hash. When our edge cache cannot answer a request itself, it forwards the request to Have I Been Pwned, which may then receive your IP address. Requests that go through our servers reach it from our servers’ address only. Located in the United States and globally.
- Vercel: hosting for our marketing website only, not the WIGGWIGG application.
We may update this list as our services evolve. The current, detailed list is available on our Subprocessors page.
The content of calls and SMS sent through telephone or mobile networks may be monitored by our telecommunication services providers and telecommunication carriers. This is not specific to WIGGWIGG and happens with all audio calls and SMS transmitted through the telephone or mobile networks. We hold no real-world identity to associate with them; call and message records are linked only to your account ID. If you reveal personal information in your messages or calls, it may be associated with you.
5.3. Legal obligations
We may also disclose personal information to third parties if we are required to do so by law, or if we are compelled to do so by a competent authority. We may disclose personal information in connection with legal proceedings if absolutely necessary to protect our rights.
6. What are your rights regarding your personal information?
6.1. Access your data
You may access your data through your user account on the WIGGWIGG Service. Any personal information we have about you is only accessible through the WIGGWIGG Service. We do not collect your email address, so you cannot request access to your personal information through email.
6.2. Withdrawal of Consent
You may withdraw your consent to our processing of your personal information by unsubscribing from our newsletter, by withdrawing consent for an optional feature that offers this choice in settings, by removing a calling device, by removing information from your WIGGWIGG account, or by deleting your WIGGWIGG account altogether.
6.3. Deletion
You may request deletion of your account through the WIGGWIGG Service. The request begins a 30-day grace period; signing back in during that period cancels it. After the grace period, we permanently delete personal data except for the limited records described in section 3: billing records retained under Canadian tax law, flagged content-check records and preserved match copies, security audit logs retained for service security, and the phone-verification audit log, which has no deletion schedule yet.
Issued referral credits and offer choices that gave a welcome credit remain in billing records, without identifying the other account after either account is deleted. No referral link between the two accounts remains in our live systems after permanent deletion. The initial-program limit receipt remains permanently; deleting the code removes its link to the account in the live database. Encrypted backups can retain the former link for about a month, until they age out. Section 1.5 gives the detailed rules.
6.4. Complaint
Depending on your jurisdiction of residence, you may have the right to file a complaint regarding the processing of your personal information with a supervisory authority responsible for the protection of privacy.
7. Modifications
We may modify this Privacy Statement from time to time to reflect changes in our personal information processing practices or applicable law. If a modification is made, we will notify you through the WIGGWIGG Service and the modified statement will be available through the WIGGWIGG Service and on the Website at the following address https://wiggwigg.ca/en/privacy-policy/. We will not do any additional processing of your personal information without your express consent.
8. Additional Information
For any additional information with respect to our processing of personal information, please contact us through the WIGGWIGG Service. Any inquiry made by email should concern information collected through the Website only.