1. Information We Collect
Depending on how you use SeeGive, we may process wallet addresses, publicly visible blockchain transaction data, project metadata, donation and withdrawal records, and information submitted through the assistance application flow.
Application submissions may include full name, date of birth, country, contact phone number, email address, emergency contact details, assistance details, service provider information, personal narrative information, donation targets, and supporting documents uploaded with the request.
2. How We Receive Information
We receive information directly from users, from connected wallets, from blockchain activity, and from service integrations used to operate the platform. Information may also be derived from publicly visible contract state and transaction events.
3. How We Use Information
We use information to operate the website, display project data, facilitate wallet-based interactions, publish assistance requests, prevent abuse, validate submissions, process supporting documents, maintain platform records, and improve service reliability.
SeeGive uses internal anti-abuse checks, including hidden honeypot fields and submission timing thresholds, to reduce spam and fraudulent submissions.
4. Cookies and Similar Technologies
SeeGive may use cookies or similar browser storage technologies to support core website functionality, remember certain user interface preferences, and improve the browsing experience. For example, we may store whether a cookie notice has been dismissed and maintain limited local state that helps the interface behave consistently across pages.
These technologies may also be used to support security, performance, analytics, or third-party service integrations. You can control cookies through your browser settings, although disabling some storage features may affect how parts of the website function.
5. Public Storage and On-Chain Publication
Supporting documents and serialized project metadata submitted through the request-help flow may be uploaded to public verification storage (IPFS) through Pinata. Project metadata hashes and transaction records may then be associated with public blockchain activity. Once information is published in this way, it may be publicly accessible, copied by others, and difficult or impossible to fully remove.
You should not submit information to SeeGive unless you are comfortable with the risk that the information may become public and remain available for an extended or indefinite period.
6. Third-Party Services
SeeGive relies on third-party components and service providers, including wallet connection software, wallet applications, blockchain RPC infrastructure, and Pinata for public file storage. Those providers may process information according to their own terms and privacy notices.
7. Retention
Off-chain service records may be retained for as long as reasonably necessary to operate, secure, audit, or defend the service. Information published to public verification storage or recorded on-chain may persist independently of SeeGive and may not be retractable by us.
8. Security
We use reasonable measures to protect the parts of the service we control, but no website, storage workflow, or blockchain interaction can be guaranteed fully secure. Users remain responsible for wallet security, careful review of submitted information, and limiting disclosure of sensitive data.
9. Your Choices
You may choose not to connect a wallet, not to submit an application, or not to provide optional contact information. Because blockchain and public verification storage publication can be irreversible, the most important privacy choice is deciding what information not to publish.
10. Policy Updates
We may update this Privacy Policy as the platform evolves. The current version will be posted on this page with the latest revision date. Continued use of the service after changes are posted constitutes acceptance of the updated policy.