Privacy Policy

Project: YOURVIEWS
Website: https://yourviews.org
Contact: Contact & Support
Last updated: 2026-08-24

1) What this document is about

This policy describes what data is processed when you use YOURVIEWS, why it is needed, and what options you have to manage it.

2) What data we process

• Wallet address and related public information (e.g., network/chain id, transaction hashes) required for Web3 functionality.
• Onchain data: wallet addresses, transactions, and smart contract events submitted to a public blockchain are public by their nature.
• X (Twitter) linking (if you connect it): public X identifiers and profile fields used to display the linked X name, username, or profile image. This data is obtained through OAuth.
• Content and content references: if you publish content via the service, it may be stored in external storage systems (e.g., via Irys/Arweave or similar) and may be publicly accessible according to their nature.
• Support and report data: information you submit through Contact & Support, such as the request category, message, email, wallet address, transaction hash, post/take references, and information required for a copyright notice.
• Post view data: an opaque browser cookie or a keyed server-side hash derived from an authenticated protocol user id, used to count one view per Post and viewer. The view record does not store the raw wallet address, browser cookie, IP address, user-agent, or referral source.
• Technical data: data typically sent with website requests (e.g., IP address, user-agent) and error/security logs to the extent necessary for stable operation and protection against abuse.

3) Why we process it

• To operate the service: wallet sign-in, linked X identity display, Posts, Takes, Signal, communities, and Journal features.
• To provide private Post view counts to authors and prevent repeated openings by the same account or browser from increasing the count.
• To maintain security and reliability: protection against spam/abuse and error diagnostics.
• To review content reports, copyright notices, security reports, wallet/payment issues, and product support requests; communicate about them when contact information is provided; and keep a record of the action taken.
• To display linked X profile information in the interface when you choose to connect an X account.

4) Who may process data

We use third-party services (“processors”) to run the service. We share only the data necessary to provide a specific function.

• Supabase — authentication and storage of offchain data, including private support request records.
• X (Twitter) — only for OAuth connection and operation of the X link.
• RPC providers (e.g., Alchemy/Ankr, etc.) — access to the blockchain network via standard RPC calls (reading data and/or sending transactions).
• Irys/Arweave (or similar storage) — if you use content upload/publishing features to such systems.
• Cloudflare/Turnstile (if enabled) — protection against bots/abuse.
• Hosting/infrastructure — to run and deliver the website (server/static hosting/SSL/CDN as needed).

We do not sell personal data. We do not request or store private keys/seed phrases — they remain with you.

5) Storage and deletion

• Offchain data (including an X account link and operational records) is stored as needed to operate the service. You can disconnect a linked X account through the wallet profile.
• Support requests are kept only as long as reasonably necessary to review the request, communicate about it, prevent abuse, document the outcome, and meet applicable legal obligations. Closed records may be deleted or anonymized when they are no longer needed.
• Abuse protection data: the support system stores a keyed server-side hash instead of the raw IP address in the support request table. Infrastructure providers may still process IP addresses in ordinary request and security logs.
• Post view records: opaque viewer hashes are retained with the Post to preserve deduplication. The anonymous viewer cookie expires after one year by default and may be deleted through browser settings.
• Onchain data cannot be deleted from the blockchain — this is a property of public blockchains.
• External storage (if used) may be designed so that uploaded data becomes public and/or practically undeletable.

6) Security

We apply reasonable security measures; however, absolute security does not exist. Never share seed phrases or private keys — the service will not ask for them.

7) Contact

For privacy questions, use Contact & Support. Do not include a private key or seed phrase in a request.