Privacy Policy
Last updated: 18 October 2026
Shingan has two products. The wallet guard is read-only and needs the public wallet addresses you choose to watch. The operator platform is an email account plus the work you ask Shingan to prepare. This page covers both. Neither product asks for KYC.
1. What we store
The wallet guard
- Your email address and a password hash.
- The public wallet addresses you connect and the chains they are watched on.
- Service state derived from public chains: approvals, events, alerts and risk scores.
- Plan, subscription and invoice records for paid guard plans.
The operator platform
- Your email address (if you add one) and a password hash. The password itself is never stored.
- Your five answers: country, payout rail, hours, skills, and the optional product or assets note.
- The chosen path, the plan, the steps and the prepared assets.
- Projects, project events, guided connections (the handle or email you enter) and the credit ledger.
- Top-up records and the transaction hash you provide. On-chain payment data is public.
- A first-party session cookie (
sg_app) that keeps you signed in. It is HttpOnly, Secure, SameSite=Lax, and is not used for advertising.
Both
- Standard server logs (IP address, timestamp, request) for security and abuse prevention.
- Coarse, country-level analytics. Website IP addresses are hashed, never stored raw. A random first-party identifier in local storage (
sg_vid) counts unique and returning visitors.
2. What we never collect
We never ask for or store private keys, seed phrases or signing material. We never ask for a platform password, a one-time code, or your payout account credentials. We do not require your name or any identity document, and we do not take card or bank details: paid plans and credits are settled in crypto.
3. How we use it
To operate and secure the service: deliver alerts, prepare and hold your projects, personalise the plan and its assets, charge and account for credits, prevent abuse, and debug. The LLM provider receives the answers and project context needed to write a plan or an evaluation; it does not receive keys, platform passwords or payment credentials.
4. Sharing
We rely on a small set of processors: email delivery, blockchain data providers (for example Alchemy), threat-intelligence providers (for example GoPlus), an LLM provider for the path, the chat and the evaluation, and a hosting provider. We do not sell your data.
5. Cookies and tracking
There are no advertising cookies and no cross-site trackers. The operator platform uses one essential session cookie to keep you signed in. The marketing site stores a random first-party identifier in local storage to count visits; it contains no personal data and is cleared with your browser storage.
6. Retention
Data is kept while the account is active and for a short period afterwards for security and backups. You can delete the web account or everything from Settings, or ask us.
7. Your choices
Sign in and open Settings to export a JSON copy, add or change an email and password, or delete the account. Deleting the account removes the email, password, projects, credits, connections, watched wallets, alerts and the guard. Removing a wallet stops future monitoring of it.
8. Security
Passwords are stored as PBKDF2 hashes. Sessions are HttpOnly and Secure. Secrets are held server-side with restricted permissions, and transport is encrypted. No system is perfectly secure; do not connect wallets you are not comfortable monitoring.
9. Contact
Email support or email support@shinganguard.com.
