MEME OBSERVER / PRIVACY

Privacy Policy

Effective date: October 17, 2026

This policy explains how Meme Observer (Meme观察站) accesses, uses, shares, stores, and deletes information when providing social and on-chain research features and Google sign-in. The service is a research tool, not financial advice. It does not predict prices, execute trades, or custody user assets.

Summary

Google sign-in is used to verify account identity, maintain a session, and display the account email. Google and Supabase Auth handle authentication. We do not access Gmail, Google Drive, Contacts, or Calendar, and we do not send Google account data to AI services. AI assists only with analysis of public social research content.

1. About the service and information processed

Meme Observer (Meme观察站) is a social and on-chain research tool for crypto users. It organizes public X posts into research leads, displays source posts and propagation evidence, and checks related token contracts and publicly available market data. Results may be delayed, incomplete, or incorrect and are not investment advice.

Google sign-in data

When you choose Google sign-in, the authorization flow requests the basic openid, email, and profile scopes. Google returns a stable account identifier and authorized basic profile details, which may include email address, email verification status, name, and profile picture, to Supabase Auth for authentication. We use Supabase Auth to determine sign-in status and display the account email. We do not access Gmail messages, Drive files, contacts, or calendar contents.

Service operation and public research data

Hosting and authentication providers may process necessary technical data such as request time, browser or device information, network information, and sign-in state to operate and protect the service. Research features process publicly accessible X post text, account names, source links, and available public engagement or follower snapshots. These public social data are handled separately from Google sign-in data.

2. Purposes, processing, and sharing

  • Authenticate users through Google and Supabase Auth, maintain sign-in sessions, and display account email;
  • Operate, protect, and troubleshoot the website; and
  • Create traceable research leads, summaries, and evidence views from public social content.

Google and Supabase Auth handle the sign-in flow. Supabase Auth processes OAuth callbacks, authentication, necessary account records, and sessions. Cloudflare provides hosting and network infrastructure. The AI summary feature may send public post text and related public evidence to configured third-party AI model providers for analysis. Google account identifiers, email addresses, names, profile pictures, and sign-in tokens are not used as AI inputs.

We do not sell Google user data, use it for advertising, or use it to train or improve AI models. We do not use Google APIs to generate, process, or distribute non-consensual intimate imagery (NCII); Meme Observer is not an image-generation service. Google, Supabase, Cloudflare, and AI providers process data they receive under their respective terms and privacy policies.

3. Storage, retention, sign-out, and deletion

Supabase Auth stores account records needed for authentication and account management. The Supabase client maintains sign-in state in the browser. We do not maintain a separate Google profile database. The exact storage location, validity period, and backup cycle for provider-held records and sessions depend on the Supabase project configuration and Supabase policies; we do not guarantee retention periods that the provider does not disclose to us.

You can sign out from the website to end the current session, or revoke Meme Observer’s Google access in your Google Account’s third-party connections settings. Revoking Google access is different from deleting a Supabase Auth account. To request deletion of your authentication account, email the support address listed on the OAuth consent screen. After verifying your identity, the operator will delete the corresponding account record through Supabase Auth and handle the request subject to applicable legal, security, and service-record requirements. Deleting an account does not automatically delete the public social source content.

Public social research evidence is stored in the research database for display, deduplication, attribution, and historical comparison. Infrastructure logs may be processed by providers as needed for service operation, security, and troubleshooting. Retention periods vary by data type and service configuration and may be subject to legal requirements.

4. Security and third-party services

OAuth client configuration is handled by the authentication service; OAuth client secrets are not placed in public frontend code. We take reasonable measures to limit data use and protect the service, but internet transmission and third-party services carry risks and absolute security cannot be guaranteed. Do not submit passwords, sign-in tokens, or unnecessary sensitive information to the website.

5. Children

The service provides crypto-asset research information for adults and is not designed for minors. If you believe a minor has submitted personal information, contact us using the support email below.

6. Contact and policy updates

For questions or requests to access, correct, or delete account-related information, email wanglujie1987@gmail.com. State the request type and the email address used to sign in. Do not send passwords, verification codes, or access tokens. We will verify the requester’s identity before handling account-data requests. The Google Cloud Console support email should match this address and be monitored.

This policy may change as product features, third-party providers, or data practices change. Updates will be posted on this page with a new effective date. We will update this disclosure if our handling of Google user data materially changes.

Back to Meme Observer →