This policy explains what Gets Quin collects, why it is collected, how long it is kept, who can see it, and what choices you have. It covers the public website, investor accounts, administration consoles, KYC files, support mail, and blockchain hashes you submit. It does not cover third-party wallets or explorers you use outside this site.
1. Who is responsible
The operator identified in Admin → Settings (site name, support email, and postal address when published) decides how personal data is processed for this installation. Payment-verification mail is read by the payment desk. If that inbox is empty, support receives those messages. For a legal demand, use the Contact form and mark the request clearly.
2. Data we collect
Account data includes name, email, phone, country, password hash, referral code, and sign-in metadata such as IP address and user agent. Profile data may include a BNB withdrawal address and government-id fields you type during KYC. Transaction data includes deposit hashes, expected amounts, investment snapshots, profit rows, withdrawal destinations, and ledger reasons. Support data includes the messages you send and files you attach. Technical data includes session cookies, CSRF tokens, and security logs.
We do not ask for, and you must not send, wallet private keys or seed phrases. Those secrets are not needed to credit a deposit or complete a withdrawal.
3. Identity documents
When KYC is required, you upload an image or PDF of a government document and related details. Reviewers can approve, reject, or ask for more information. Files are stored in the private uploads path, not in a public folder. Access is limited to administrators with KYC permission and is written to an audit trail when a decision is taken.
4. Blockchain data
A transaction hash you submit is a public network identifier. The platform stores it uniquely so the same hash cannot credit two accounts. Optional RPC verification may read receiver, asset, and confirmation count from the configured network. That check does not give the operator control of your personal wallet.
5. How we use data
We use data to create and secure accounts, confirm deposits, snapshot package terms, post daily profit, pay qualified referral commissions, review withdrawals, detect duplicate or abusive activity, answer support and payment tickets, meet record-keeping duties, and publish only the operating figures the operator has chosen to show on the public site.
6. Legal bases
Processing is required to perform the account contract (ledger, packages, withdrawals), to meet legal duties where identity and transaction records are required, and to protect the service against fraud and abuse. Where a local law requires consent for a non-essential cookie, that cookie is not injected until the operator configures it.
7. Who we share with
Hosting, email, and (if configured) blockchain RPC providers receive the minimum needed to run those services. Administrators see data according to their role. We do not sell investor lists. We may disclose records when required by a lawful order, or to defend the operator against fraud. Public homepage cards that show names and balances are operating-snapshot figures published by the operator; your newly registered account is not added to that grid until you actually use the book, and your private dashboard remains your own ledger.
8. Retention
Account, ledger, and hash records are kept for the life of the book and for a further period the operator sets for audit and dispute handling. KYC files are kept while the account can withdraw and for the statutory period that applies to the operator. Support mail is kept long enough to close the ticket and show a history. Session files expire according to the configured lifetime.
9. Security measures
Passwords are hashed. Sessions are marked HTTP-only. Administrative two-factor authentication is available. Financial mutations take row locks and write ledger and audit rows. Uploads for KYC sit outside the public web root pattern used for marketing files. No control is perfect. You still protect your own email inbox and personal wallet.
10. International access
The Hostinger (or other) host you see in the address bar may store data in the region of that server. Administrators may sign in from other countries. If you access the site while travelling, logs will show those locations.
11. Your rights
Subject to local law, you may ask for a copy of the personal data on your account, ask for a correction, or ask for limits on processing where the law allows. Closing an account does not erase immutable ledger rows that record value that already moved. Use Contact and choose Support. We may need to verify that the requester controls the email on the account.
12. Children
The service is not offered to children. If an administrator believes an account belongs to a minor, the account can be closed and deposits handled under the refund and AML rules.
13. Changes
This page is the current policy. The operator may update it when products, hosts, or law change. The “last updated” cue is the page’s database timestamp. Continued use after a published change means you have read the new text.
14. Privacy contact
Write to the support address in the footer or use the Contact form. For a hash dispute, choose Payment verification so the payment desk sees the ticket first.