Privacy Policy
Last updated: 2026-05-20
Operational draft: this privacy page explains current operational data handling in plain language, but it is not final legal advice and needs qualified legal review.
Key facts about GGSBot
| Marketplace type | Digital goods marketplace |
|---|---|
| Pricing | Visible USD pricing and stock indicators |
| Checkout | Crypto checkout with exact amount on the selected network |
| Delivery | Email delivery after payment verification |
| Use boundary | Lawful, authorized, policy-compliant use only |
Operational draft and legal review label
This Privacy Policy is an operational draft for GGSBot support, delivery, payment verification, and order review workflows. It should be reviewed by qualified legal counsel before being treated as a final privacy notice.
Data used for orders
Order review may use order number, product name, price, selected network, exact amount, checkout email, payment status, delivery status, and support messages. These details help connect payment verification with delivery and support review.
Checkout email
The checkout email is used for delivery, support matching, refund review, and privacy requests. Buyers should use an email they can access and should not submit unrelated third-party inbox data.
Payment metadata
Payment metadata may include selected network, expected amount, amount paid, payment time, transaction hash or proof, confirmation status, and manual review notes. GGSBot does not need private keys or seed phrases to review payment evidence.
Support evidence and screenshots
Support evidence can include screenshots, delivery email status, missing-delivery evidence, and communication history. Send only the evidence needed for the support issue and avoid unrelated personal data.
Technical logs
Operational logs may be used to protect checkout, diagnose routing or delivery issues, and investigate abuse. The exact retention and legal basis should be confirmed during legal review.
Privacy requests
Privacy requests should include enough order or checkout-email context to locate the relevant record. Do not send private keys, seed phrases, unrelated identity documents, or third-party passwords.
Items needing legal or business review
Legal/business review should confirm applicable privacy law, data retention, controller or processor wording, international transfer wording, user rights process, contact method, cookie/log disclosures, and record deletion limits.
Operational privacy review note
This privacy draft describes the order, payment, delivery, support, and log data used operationally. Legal review should confirm rights handling, retention, transfers, and contact process.
FAQ
Is this final legal privacy advice?
No. This page is an operational draft and needs qualified legal review before it is treated as a final privacy notice.
What data is used for delivery?
Delivery uses the order number, checkout email, product name, payment status, selected network, exact amount, and delivery status.
Should I send private keys or passwords?
No. Never send private keys, seed phrases, unrelated passwords, or unnecessary personal data for support review.
How do I make a privacy request?
Use the contact path and provide enough checkout email or order context to locate the relevant record.
What still needs legal review?
Data retention, user rights process, contact method, international transfer wording, cookie/log disclosures, and jurisdiction-specific obligations need legal review.