Information you provide
When you request an exchange, you provide the card brand, stated balance, card number or redemption code, contact email, and chosen payout method and account or wallet address. The request also includes the calculated service fee, estimated payout, and a request reference.
Card details depend on the selected brand. Retail gift cards may require a PIN or access number. Prepaid card requests include the expiration date and CVV or CID entered in the dedicated fields.
The contact form collects your name, email address, and message. Use your request reference for follow-up questions; do not include full card details or security codes in a support message.
How your information is used
Exchange information is sent to support for manual card review, follow-up questions, and handling of an approved payout. Contact details allow support to respond about your request. The website calculates an estimate from the balance you enter; it does not check the balance with the card issuer.
The website also checks submitted fields and uses limited technical records to detect repeated submissions and restrict excessive sending attempts.
Delivery to support through Telegram
Exchange requests and contact messages are delivered through Telegram to the designated AllianceGift support chat. Telegram processes the messages, and people with access to that chat can view them.
Exchange messages include the full card number or redemption code, any submitted gift card PIN, applicable prepaid card expiration date and CVV or CID, stated balance, service fee, estimated payout, payout destination, and contact email. Contact messages include your name, email, and message. Consider this handling of your information before submitting.
Where submitted details remain
The website application does not keep a local customer order database or a log of submitted message contents. Submitted details are held in the receiving Telegram chat, and the website does not automatically delete those messages.
Separate protection records contain hashed identifiers, delivery status, timing, and attempt counts. These records do not contain readable card details, payout accounts, email addresses, message contents, or raw IP addresses. Card duplicate checks last 24 hours, and expired protection records are removed when a later request is processed. This period does not determine how long a message remains in Telegram.
Cookies and submission protection
The exchange and contact forms use a session cookie to associate a submission with your browser and protect the forms against misuse. This cookie contains a random identifier, not your card or payout details. Blocking it can prevent a form from being submitted.
The application also processes your IP address to limit repeated sending attempts. Its protection records store a hashed identifier instead of the raw address.
Questions, corrections, and deletion requests
Contact support to ask about information you submitted, correct a mistake, or request deletion. Include the request reference and a description of what you need, without repeating card codes or security codes.
Closing this website does not withdraw a request or remove a message already delivered to support. Ask support to confirm the status of your request.
For privacy questions, use the contact form or email [email protected].