Wigglo
Privacy policy / Wigglo
Last updated: 18 November 2026
1. Data controller and contact
Wigglo is operated and published by HALBCO LLC, the data controller for the personal data described here. Its principal office and mailing address is 30 N Gould St Ste 52443, Sheridan, WY 82801, United States. For privacy questions and rights requests, email support@halbco.com with Wigglo in the subject, or visit Wigglo support.
2. Data we collect and why
Account and sign-in data includes your verified email, permanent account ID, account and session state, and sign-in and deletion verification records. We use it to operate your account, authenticate you and send sign-in and account deletion codes. Wigglo does not ask for or import a phone number for sign-in or profiles, and does not request access to phone numbers from Google.
Where Google or Apple sign-in is available in your version and you choose to use it, Wigglo processes the provider name, provider-specific subject identifier and verified email, including an Apple private relay address. The Wigglo server verifies the provider credential; Wigglo does not import the provider's profile name or photo. Provider account links remain while your account exists. Signed Apple account and relay-change notifications support account management. An encrypted Apple revocation grant may be retained on the server to revoke Apple access during deletion.
When Google sign-in is enabled, Google processes sign-in information separately from the fields Wigglo imports. This can include account and profile information, user and device identifiers, IP-derived approximate location, and usage and technical information for authentication, fraud prevention and Google service analytics. Google's SDK privacy declaration includes analytics uses even though Wigglo has no separate product-analytics SDK. Google handles this information under its privacy policy; see also its sign-in data disclosure. Versions with social sign-in disabled do not initialize Google sign-in through the app.
For Apple's private email relay, Wigglo classifies only addresses at the exact domains privaterelay.appleid.com and private.icloud.com as relay addresses. Ordinary icloud.com addresses are not classified as private relay.
Profile data includes your first name, private surname, self-declared date of birth and derived age, gender, photos and optional Instagram handle. Current profile setup has four steps: name, date of birth, gender and photo; there is no interest-selection step. We use profile data, discovery preferences, Traces, optional preset status tags stored as Trace notes, winks, matches and encounter records to provide discovery and matching.
The discovery preference saved on the server is your age range. Legacy gender preference values may remain until overwritten or account deletion, but are ignored for discovery. Your age range and legacy preferences are not shown to other users. You can also filter the displayed results by Trace status tags on your device; those filter selections are not sent to the server.
Chat data includes message text, sender, match, sequence and timestamps, plus read and mute state. We store it to let matched participants communicate and show conversation history. The other participant can read the messages you send. Reports, report reasons, optional report text, blocks and reported message evidence are processed for moderation, safety and abuse prevention.
Technical data includes a random app-generated installation identifier and secure installation key, session records, client IP addresses used for security and rate limits, and technical logs and security/operations metadata such as request identifiers and API failure information. We use these to bind sessions to an installation, prevent misuse and operate and troubleshoot the service. The installation identifier is not a hardware identifier.
Wigglo does not sell personal data or use personal data for behaviourally targeted advertising. Wigglo has no ads or separate third-party tracking or product-analytics SDK. Google sign-in service analytics, when that sign-in method is enabled, is described above. The mobile app does not use a third-party crash-reporting service. Push notifications are currently off and this release does not collect device push tokens.
The API can use Sentry for server error reporting when enabled in its deployment configuration. Error reports can include diagnostic details, request paths, browser or app information from the User-Agent header, and release and environment information. Before sending, the API removes request bodies, cookies, other request headers, user identity fields, and URL query strings and fragments. Sentry tracing, logs and metrics are disabled.
3. Location and visibility
Discover shows active people in the same area. An active Trace is required to send or respond to a wink. Instagram is optional and is not required to leave a Trace, wink or chat.
When you leave a Trace (İz), your precise foreground location is captured once and saved for proximity calculations and assignment to a map cell. Wigglo does not collect background location, request Always location access or track your movement. Without an active Trace, opening or refreshing Discover reads your location once to show nearby people. The server processes that reading only for the request: it is not saved, shown to anyone or used to track you. Leaving a Trace takes a separate location reading.
The device that creates a Trace also temporarily keeps its fixed location in secure local storage to show you where you left it. This copy is cleared when the Trace ends, expires or is replaced, or your session ends. Expired stored copies are removed when loaded.
Only active Traces contribute to Discover and the Map. Other users see an approximate area, normally a map cell of about 250 metres, and a neighbourhood name when available. The Map shows approximate numbers of people in areas, not individual people. Sparse cells are combined into larger areas or hidden; the Map does not show counts for areas with fewer than three active Traces. People close enough to wink at are labelled Nearby. Your exact coordinates, movement, address, venue and exact distance are not shown to other users.
Your card and profile can show your first name, age, gender, photos, preset status tag, Trace duration and end time, and approximate area. Your email, surname and date of birth are not shown. Your Instagram handle is optional and, if supplied, is shown only to a person you match with.
Map images are loaded from MapTiler, which receives your IP address and the map area you view. To find a neighbourhood name, the server sends MapTiler only the centre of the approximate area.
4. Retention
Traces last 30 minutes, 1 hour, 2 hours or 4 hours, unless ended earlier. Ending a Trace removes discovery visibility; it does not immediately erase its stored record. Thirty days after the Trace ends, the retention process replaces its precise coordinates with the map-cell centre. The reduced Trace record remains until account deletion.
Account, profile, photo and discovery-preference data remains until account deletion. Pausing keeps this data. Winks and matches create encounter records for Where we crossed paths. These contain the approximate area, neighbourhood, part of the day and day, plus a creation timestamp for ordering, but no coordinates. The exact creation timestamp is not shown to other users; the encounter summary shows the part of the day and day. Encounter records remain until either participant deletes their account.
Blocking or ending a match closes the conversation for both people. Normal messages and conversation state are cleaned up 30 days after closure, or through account deletion. Pausing retains chat history and prevents new messages while paused.
When a message is reported, the selected message and up to five preceding messages are retained separately for authorized moderation for 90 days from the report, including after account deletion. A completed, nonidentifying deletion-status receipt remains for 90 days after completion and then expires.
Shared wink, match, block and report records needed for integrity or safety may remain after deletion under replacement participant identifiers, without a mapping to the deleted account identity. The same replacement identifier can link several retained records; these records are pseudonymized, not fully anonymous.
5. Service providers and disclosure
Wigglo uses Railway-hosted API and database infrastructure, Cloudflare R2 for photo/object storage, Mailjet for email delivery, and MapTiler for maps and neighbourhood names. Sentry processes server error reports when that service is enabled, as described above. These providers process data to deliver their respective services. Google and Apple process sign-in information when you choose those sign-in methods; Apple also handles access revocation. Profile visibility, match-only Instagram disclosure and message sharing with the other participant are described above. Reported content is available for authorized moderation.
A mutual match enables in-app text chat. If you choose to contact a match on Instagram, that communication takes place outside Wigglo and is subject to Instagram's own terms. Wigglo does not collect or disclose phone numbers for this contact.
Report and block is one action: it blocks the reported person, ends your match and pending winks, and closes your conversation. The reported person is not notified of the report. You can remove a block from the Blocked list, but this does not restore the old match.
6. Legal bases and international processing
HALBCO LLC is based in the United States and uses the service providers listed above. For information about the legal bases applicable to your data, processing countries and international transfer safeguards, contact support@halbco.com. The processing purposes and verified retention periods are described in this policy.
7. Pausing and deleting your account
Pause Account is reversible. It hides you from Discover and the Map, signs you out, ends your active Trace and pending winks, and keeps your profile, photos, preferences, Traces, matches and chat history. Your matches can still read existing chat history but cannot send new messages while your account is paused. You can return by signing in and reactivating your account.
To delete permanently, open Profile > Account information > Delete account and data and confirm. You can also request and confirm deletion with an email code on the Wigglo account deletion page. If you need help, contact support@halbco.com. Do not send Support sign-in or deletion codes, deletion receipts, reactivation grants, session credentials, storage keys or exact location.
An app deletion receipt stays in the app where you started the request and is used there to check deletion status. The web account-deletion page does not accept that receipt; it uses a separate email verification code. Enter that code only on the official Wigglo account-deletion page and never share it.
Deletion is irreversible. Confirmation immediately removes product access; physical erasure completes asynchronously. The deletion worker removes account identity, profile fields and photos, stored photo objects, Traces and locations, encounter records, discovery preferences, sessions, installations, normal messages and conversation state. The retention exceptions for reported chat evidence, shared pseudonymized safety records and the deletion-status receipt are described above.
If Apple access was used, deletion is not marked complete until the required Apple revocation finishes. Temporary provider failures can delay physical deletion and are retried; they do not restore access. Pausing is not deletion.
8. Your rights
Where the GDPR applies, and subject to its conditions, you can request access, correction, erasure, restriction of processing and data portability, and object to processing. Where processing relies on consent, you can withdraw that consent. You can complain to the competent data protection authority. See the European Commission's information on GDPR rights.
Under KVKK, where applicable, you can ask whether your personal data is processed, request information about the processing, its purposes and recipients in Türkiye or abroad, request correction or deletion under the statutory conditions and notification of those actions to recipients, object to adverse results arising solely from automated analysis, and seek compensation for damage from unlawful processing. You can also complain to the Turkish Personal Data Protection Authority under the applicable procedure. See KVKK data subject rights.
For requests, contact support@halbco.com or write to HALBCO LLC at the address above. You can edit the profile fields and preferences available in the app and use the in-app or web deletion process.
9. Adults only
Wigglo is only for adults aged 18 and over. Date of birth is self-declared, and profiles with an under-18 date of birth are rejected. This is not identity-document or biometric age verification. Report a suspected underage account through Report and block or contact support@halbco.com.
10. Related service information
See the Terms of Use and Community Guidelines for rules on profiles, photos, Trace notes, messages and safe interactions. For account access, safety, privacy or app issues, visit Wigglo support.