How MeOnLink handles account, profile, and activity data.

When you create and use an account, MeOnLink stores the core information needed to run your profile and account securely. This can include your email address, password hash, display name, username, account type, bio, avatar path, and the links or groups you create.

MeOnLink also stores account security and lifecycle data such as email verification state, password reset requests, terms acceptance timestamp, and other account status fields used to keep access secure and manageable.

If you interact with public profiles, MeOnLink may record platform activity such as profile views, link clicks, likes, favorites, notifications, and search activity when those tracking tables are enabled in the current installation.

For security, moderation, and product analytics, MeOnLink can store limited technical metadata such as device type, referrer, country code, and a hashed IP value instead of a raw IP address where the feature is supported by the current codebase.

The application can also store security-event records for actions such as failed sign-in attempts, temporary lockouts, and rate-limit hits. These records help the site operator investigate abuse and protect the platform.

Cloudflare Turnstile is used on sensitive forms to reduce automated abuse. Verification tokens are validated server-side.

MeOnLink uses stored information to provide account access, publish profile pages, build group share pages, process password resets, verify email ownership, send support requests, and support profile and link management inside the dashboard.

Basic usage and activity records may also be used to support analytics, monitor platform health, reduce abuse, and investigate moderation issues when needed.

Your email address is used for account verification, password recovery, and essential account-related notices. It is not intended to appear publicly on your profile page.

Your public page may display your avatar, display name, username, bio, and any links marked as public. Group pages display only the links assigned to that specific group share token.

Information such as your email address, password hash, verification tokens, reset tokens, and internal security metadata is not intended to be public.

MeOnLink uses essential cookies and session storage to keep sign-in, CSRF protection, cookie preferences, and general account state working correctly. These are part of the normal operation of the product.

The cookie notice in the interface reflects this essential use. The current application does not present itself as a broad advertising-cookie platform.

MeOnLink may rely on infrastructure or service providers for hosting, email delivery, and abuse protection. For example, SMTP email delivery and Cloudflare Turnstile are integrated into the current application.

MeOnLink does not present a public interface for selling user data. Any disclosure should be limited to what is necessary to operate the service, comply with law, or protect the platform and its users.

Passwords are stored as secure hashes rather than plain text. Email verification and password reset flows use time-limited tokens. Sensitive form actions use CSRF protection and additional bot checks where configured.

Data retention depends on the feature and server configuration in use. If an account is deleted through the current user flow, the application is designed to remove the associated profile and related content from the active account state.

You can update your profile content, change links, manage group visibility, change your password, and delete your account using the current dashboard tools available in MeOnLink.

If you no longer want a link or a group page to be available publicly, remove it or change its visibility from the dashboard.

If you have questions about this policy or the handling of your account data, use the contact details or support channel made available by the site operator for the active MeOnLink deployment.

This privacy page describes the current product behavior as verified from the present codebase and may be updated if the application changes.