1.Overview
Zilligo is designed around minimal data collection. Placing an order needs a free Zilligo account. Creating one asks for no email address and no ID document: the user picks a nickname and a handle, and Zilligo generates a sign-in key and a recovery code for the user to save. An order can be placed without a passport upload or selfie. The purpose of this policy is to explain what information may be handled when someone uses the website, creates an account, places an order, or contacts support.
2.Your account
Creating an account asks for a nickname and a handle, the name the user signs in with. Zilligo then generates a 4-word sign-in key and a recovery code and shows them once. Both are stored only as secure hashes, never in readable form, so Zilligo cannot show them or send them again. The sign-in key is only for Zilligo; it is not a wallet seed phrase. The account also records when it was created and when the user accepted the terms.
An email address is optional. A user can add one in Profile and confirm it with a 6-digit code sent to it; while that code is open, the address waiting for confirmation is kept with it, and it becomes the account's email only once it is confirmed. A confirmed email receives order updates and sign-in alerts, and it can be used to set a new sign-in key if the key and the recovery code are both lost. The user can change or remove it in Profile.
Users may add a phone number and their country of residence; both are optional. Identity documents are not collected as part of the standard service. The account keeps the user's language and email choices: order updates are always sent to a confirmed email, sign-in alerts are on unless the user turns them off, and news and offers are off unless the user turns them on.
Saved payout details, the ones a user keeps for later orders such as a PayPal email or an IBAN, are stored encrypted and shown masked in the account.
3.Sign-in and security
To protect the account, Zilligo keeps a record of each signed-in session, including the IP address and the browser's user agent. In the account, sessions are shown to the user only as a browser and operating system. Zilligo also remembers the devices that have signed in to the account. On an account with a confirmed email, a sign-in from a new device must be confirmed, with a code Zilligo emails or, when two-factor login is on, with the two-factor code; if sign-in alerts are on, Zilligo then emails an alert about the new sign-in. An account without an email relies on its sign-in key, on limits on failed sign-in attempts and, when it is on, on two-factor login. Two-factor login with an authenticator app is optional.
5.Order data
When a user places an order, Zilligo processes the selected service, coin, network and amounts, the deposit address, the payout method and the destination detail needed for that service, the order ID, the status history, timestamps, transaction hashes and support notes. Examples of destination details include a PayPal email, Cash App tag, IBAN, gift card region, or phone number for mobile top-up. Destination details are stored encrypted. Each order is linked to the account that placed it.
Orders placed as a guest, before accounts existed, may still be opened from the link in their order emails. When a user confirms their email address, guest orders placed earlier with that email address join the account.
6.Emails Zilligo sends
For an account, Zilligo emails only the address the user has confirmed, apart from the code that confirms a new address; an account without a confirmed email gets no email. Zilligo sends news and offers only if the user opts in; this is off by default. Today Zilligo sends only these account and order emails:
- a code to confirm an email address being added, and codes to confirm a new device;
- a code to set a new sign-in key when the user asks for one by email, and a notice to the earlier address when another email is confirmed in its place;
- a message when an order is created, and updates when its status changes;
- security notices when the sign-in key is changed, two-factor login is turned off or reset, a saved payout detail is added, changed or deleted, the user's data is downloaded, or a new device signs in;
- a confirmation when the account is deleted.
7.Services that help us
Zilligo uses one outside service that receives customers' personal data. Emails, with the email address they go to, any codes and the order details they contain, are sent through the email delivery provider SMTP2GO. Sign-in keys and recovery codes are generated by Zilligo and are never sent to an outside service.
8.Payment data
Zilligo may display wallet addresses, payment amounts, crypto networks, timers, and order references. Blockchain transactions are public on their respective networks. Zilligo cannot erase public blockchain records. Users should only send funds from wallets and networks they understand.
9.Support communications
If a user contacts Zilligo, the message content, email address or contact handle, order ID, and any attachments may be processed to answer the request. Support messages should not include seed phrases, private keys, unnecessary identity documents, or sensitive personal files.
10.Analytics and logs
The website may use security logs, error logs, uptime tools, and privacy-conscious analytics to protect the service, debug issues, detect abuse, and understand page performance. Zilligo aims to configure any analytics to collect the least data needed.
11.Data minimisation
Zilligo aims not to collect information that is not needed for the account or the selected service. The checkout is kept focused: service, amount, destination detail, coin, network, order ID, and payment status.
12.Retention
Order records are kept for 5 years after the order is placed, as required for anti-money-laundering record keeping. This includes the orders of an account that has since been deleted: after the account is deleted, they are kept without the link to the account, under the account's confirmed email address if it had one. Other account data is kept while the account exists, except that signed-in sessions expire after 30 days without use and expired sessions are deleted regularly, and remembered devices not used for 400 days are deleted. Support data is retained only as long as needed for operations, dispute handling, accounting, legal obligations, fraud prevention, and service improvement. Zilligo reviews its retention periods regularly as the platform grows.
13.Downloading and deleting your data
A signed-in user can download their data from Profile and security in the account: the profile, preferences, saved payout details and orders.
The account can be deleted from the same page once none of its orders is still open (waiting for payment, confirming, being paid out or on hold). Deleting the account removes the profile, including the handle, nickname, email, phone number and country, the sign-in key, the recovery code and two-factor login, saved payout details, signed-in sessions and remembered devices. Order records are kept for the retention period above, and if the account had a confirmed email, a confirmation is emailed to it. If the user later adds and confirms the same email address in a new account, those kept orders join the new account. Zilligo's internal security log keeps a record of the deletion, including the IP address of the request, and keeps its earlier entries too.
14.User responsibilities
Users are responsible for entering correct destination details, selecting the correct blockchain network, keeping their sign-in key, recovery code and devices secure, and complying with applicable laws in their location.
15.Changes to this policy
Zilligo may update this policy when products, laws, security practices, or data flows change. The date at the top of this page changes whenever a material update is made.
Questions about this policy? Write to us through the contact page, and include your order ID if it is about an order.