KnowMe
Terms of Service← Back to KnowMe
CRYPTOGRAPHIC PRIVACY PLEDGE

Your Privacy.
Our Core Architecture.

Learn what KnowMe collects, how anonymous questions work, and which privacy controls are available.

Last updated: October 2026•Privacy-aware analytics•Privacy controls

Private Questions

Questions never record your name, email, or account ID. The recipient cannot see who asked.

One-Way Hashing

Spam rate-limiting uses salted, irreversible hashes. Creators can block senders without knowing their identity.

Zero Ad Trackers

We do not run invasive cross-site ad pixels, sell browsing history, or broker your personal data.

Deletion Controls

Withdraw public answers and request account deletion. Limited moderation and audit records may be retained as described below.

OFFICIAL POLICY

KnowMe Data Protection Standards

Data privacy illustration

1Anonymous Questions & Cryptographic Hashing

When you submit an anonymous question to a KnowMe profile, your name, email address, profile picture, and account credentials are never transmitted to or accessible by the recipient. The question model in our database structurally has no sender identity fields.

To prevent automated bot abuse, threats, and harassment, our server computes an irreversible, salted one-way cryptographic hash from network metadata. This hash cannot be reverse-engineered into personal information, is inaccessible to creators, and is solely used to enforce rate limits and allow creators to block repeat abusive senders without compromising privacy.

2Public vs. Private Information

What is Public: Your public handle (e.g. knowme.fyi/you), display name, bio, chosen avatar preset, cover gradient, public social links, and any Q&A answers you explicitly publish. Visitors can browse your public profile without creating an account.

What is Private: Your private question inbox, withdrawn answers, account email, security tokens, and blocked sender lists are never exposed to the public. Internal diagnostic reads require developer authorization, are audited, and exclude anonymous sender hashes. Notification campaigns require a separate confirmation. Published unlisted answers remain accessible through their direct links.

3Information We Collect

We believe in minimal data collection. We only retain what is essential to run your profile:

  • Account Identification: Your Google account email and name (provided via Google Sign-In) to verify profile ownership.
  • Notifications: Private device tokens deliver optional push alerts. Question previews omit the question text and sender information. Reminder and announcement consent, time zones, quiet hours and cooldowns are enforced server-side. Notification history is available for up to 90 days.
  • Creator Profile Data: Your claimed handle, bio text, social link URLs, portfolio projects, and avatar configuration.
  • Aggregated Metrics: View counts, link taps, quiz activity and coarse country, device and traffic-source totals grouped by UTC date. We do not store individual visitor identities or precise locations in analytics. Audience measurement begins with this update; older country/platform history cannot be reconstructed. Daily audience data uses a 90-day retention window with periodic cleanup.
  • Notification Tokens: Optional push notification tokens to alert you when new questions arrive, which can be revoked at any time.

4Account Deletion & Data Retention

You have the absolute right to delete your data at any time. You can delete individual questions and answers instantly from your inbox, or request a complete account deletion.

Need to delete your account or data?
You can do this directly from the mobile app settings or visit our dedicated Account Deletion Portal. Upon confirmation, your username is released, and all associated messages and links are permanently erased.

5Contacting Our Privacy Team

If you have questions about our privacy design, data handling, or security practices, reach out directly to our engineering team at corvas.official@gmail.com.