Privacy Policy

1. Scope and contact

This Privacy Policy explains how 3Social collects, uses, stores, and shares information when you use 3social.io, www.3social.io, and related 3Social services. At the time of this update, 3Social is operated as an independent project. Privacy questions and requests can be sent to legal@3social.io.

2. Wallet-based accounts

3Social primarily uses wallet-based authentication rather than passwords. When you connect a compatible wallet and sign a Sign-In With Ethereum (SIWE) message, we receive your public wallet address and signature result. We do not receive or store your private key or seed phrase.

3. Information we collect

• Account and wallet data. Public wallet address, internal user ID, username, role, account status, connected-wallet records, last-login information, and related account metadata.
• Authentication and security data. Session-token hashes, session expiration, IP address, browser/user-agent information, SIWE nonces and signed-message records, and other information used to authenticate sessions, detect abuse, and investigate security events.
• Profile data. Username, display name, bio, avatar, cover image, payout preferences, and other profile/settings information you choose to provide.
• Content and social activity. Posts, media, comments, likes, follows, mentions, repost/remix relationships, bookmarks or similar interaction records, forum content, live-room activity, and content visibility/deletion state where supported.
• Visibility, relationship, and group data. Your profile-visibility setting (public or private) and when it last changed, follow-request state (pending, approved, declined, or revoked), user-to-user block records, and — for groups — group membership, roles, join requests, invitations, bans, and moderation-log entries recorded so groups can be operated and moderated.
• Messages and support communications. Direct messages, conversation metadata, and messages exchanged with 3Social Support are stored so the messaging and support features can function and so authorized administrators can respond to support matters.
• Provenance and content-integrity data. Cryptographic content hashes, ledger or registry identifiers, timestamps, derivative links, attribution relationships, and related audit data used to establish provenance and prevent duplicate or inconsistent processing.
• Pricing and metering data. Creator pricing policies, policy versions, free preview and cap settings, metering sessions, event type, accrued charge amounts, sequence/timing information, and charge intents used by MintScale.
• Payment, escrow, and payout data. USDC escrow balances and deposit-sync records, settlement amounts and status, creator/platform/upstream allocations, public wallet addresses, payout addresses and verification status, blockchain transaction hashes, chain IDs, and related reconciliation/audit information.
• Moderation and abuse-prevention data. Reports, report reasons and descriptions, moderation outcomes, bans/restrictions, abuse/risk flags, and audit records used to investigate manipulation, fraud, security incidents, or violations of the Terms.
• Usage and analytics data. Basic events describing use of platform features, such as page or feature interactions, search/discovery activity, and other events needed for feed ranking, product analytics, security, and metering.

4. How we use information

We use information for purposes including:

• authenticating users and maintaining sessions;
• displaying profiles, content, feeds, search/discovery results, messages, and notifications;
• operating MintScale pricing, previews, caps, metering, escrow, settlements, creator payouts, and attribution;
• registering content provenance and maintaining derivative/remix relationships;
• providing customer support and administering reports, moderation, and appeals or investigations;
• detecting abuse, fraud, engagement farming, unauthorized access, or settlement manipulation;
• maintaining, debugging, securing, measuring, and improving 3Social; and
• complying with legal obligations and enforcing our Terms.

We do not sell personal information. We do not currently use personal information for cross-context behavioral advertising.

5. Legal bases where applicable

Where laws such as the GDPR require a legal basis, our processing may rely on performance of a contract with you (for example, providing your account and requested features), our legitimate interests (such as security, fraud prevention, service improvement, and moderation), compliance with legal obligations, and consent where a specific feature requires consent. The applicable basis depends on the data and purpose involved.

6. Public and blockchain-visible information

Public profiles and public posts are visible to other users and may be accessible to search engines or other internet users. Public blockchain activity is also inherently transparent. Deposits, withdrawals, settlement transactions, wallet addresses, transaction hashes, contract events, and registered content hashes or ledger identifiers may be permanently visible on Base or another enabled public blockchain.

Making a post private, removing it from public surfaces, or deleting/revoking it in 3Social does not erase a blockchain record that has already been published. 3Social may also retain off-chain provenance, audit, moderation, and settlement records needed to preserve attribution and financial integrity.

7. Profile and group visibility; wallet-address privacy

3Social offers application-level controls over who can see your profile, posts, and group content — public or private profiles, approved-follower access, blocking, and public or private groups. When a profile is private, 3Social does not display that profile’s wallet address to viewers who are not approved followers: the address is omitted from the profile’s API responses, page metadata and link previews, profile URL, and any field derived from the address. Identicon/avatar seeds are generated independently of the wallet address so they cannot be used to re-identify it.

These are application-layer controls only, and they are not blockchain anonymity. Content-hash registrations, deposits, charges, settlements, and other transactions that have already been published to a public blockchain such as Base are permanent and publicly visible, and they may already associate a wallet address with prior activity. An outside observer can inspect that on-chain history independently of 3Social. Setting a profile to private, blocking a user, making a group private, or deleting content changes what 3Social shows going forward; it does not — and cannot — retract, hide, or delete information that is already recorded on a public blockchain. Choose what you publish on-chain accordingly.

Visibility choices also do not remove off-chain provenance, audit, moderation, settlement, or membership records that 3Social retains to preserve attribution and financial and operational integrity, as described elsewhere in this Policy.

8. How information is shared

• Other users and the public. Public profile/content information and public blockchain data are visible as described above.
• Service providers. We use infrastructure providers for hosting, managed databases, object storage, queues/cache services, blockchain RPC/node access, security, and related technical operations. They may process information on our behalf subject to their contracts and privacy practices.
• Administrators and support personnel. Authorized administrators can access information reasonably necessary for support, moderation, treasury/settlement operations, security, and platform administration. This can include user profiles, posts, reports, settlement history, payout status, risk data, and support/message threads relevant to their duties.
• Legal and safety disclosures. We may disclose information if reasonably necessary to comply with law, legal process, protect rights or safety, investigate fraud or abuse, or defend legal claims.
• Business changes. If 3Social is reorganized, transferred, financed, acquired, or operated by a new legal entity, information may be transferred as part of that transaction subject to applicable law.

9. Storage and international processing

Off-chain account and application data is stored in managed database and hosting infrastructure. Uploaded media is stored in S3-compatible object storage, and temporary background processing uses queue/cache infrastructure. Providers may process data in the United States and other locations where they operate. Public blockchain records are distributed globally and are not controlled by a single storage provider.

10. Data retention

We retain information for as long as reasonably necessary to provide the service, maintain account and financial integrity, preserve provenance, resolve disputes, enforce our Terms, meet security needs, and comply with legal obligations. Authentication sessions and temporary records expire or are removed according to operational schedules. Some transaction, audit, moderation, provenance, and settlement records may be retained after content or an account is no longer public where needed for those purposes.

Information written to a public blockchain may be effectively permanent and cannot be deleted or modified by 3Social.

11. Your choices and privacy rights

You can edit supported profile/settings fields in the product, manage content visibility where available, disconnect your wallet, and withdraw unused escrow through supported contract/product controls. Depending on your location and applicable law, you may also have rights to request access, correction, deletion, portability, restriction, or objection regarding off-chain personal information, and to withdraw consent where processing is based on consent.

To make a privacy request, email legal@3social.io. We may need to verify that you control the relevant account or wallet before fulfilling a request. Some requests may be limited where retention is required for security, fraud prevention, legal obligations, financial records, provenance, or other lawful purposes. We cannot delete data from a public blockchain.

12. Children

3Social is a general-audience service and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that a child under 13 has provided personal information in circumstances covered by applicable child-privacy law, we will take appropriate steps to restrict or delete off-chain information as required by law.

13. Security

We use technical and organizational measures intended to protect off-chain information, including access controls, authenticated administrative routes, encrypted network connections, wallet signature verification for sensitive payout changes, and audit/replay protections for settlement operations. No system is perfectly secure. You remain responsible for the security of your wallet, private keys, device, and signing decisions.

14. Automated ranking, metering, and abuse detection

3Social uses automated logic to support feed ranking, metering, rate/cap enforcement, duplicate detection, and abuse/farming detection. These systems can influence what content is surfaced, whether an interaction generates a charge, or whether activity is flagged for review. Where applicable law provides rights relating to automated processing, you may contact us using the privacy-request address above.

15. Changes to this policy

We may update this Privacy Policy as 3Social changes. Material revisions will be reflected by the “Last updated” date and, where appropriate, additional notice in the product.

16. Contact

Privacy and legal requests: legal@3social.io. General support: support@3social.io.