Privacy Policy

When you start a paid rename, nameme.lol processes the proposed character name, public display name, optional Winner URL, contribution amount, character and auction identifiers, the then-current minimum/value/end time, your Rules and Terms acceptance and versions, timestamp, IP address, user agent, and Stripe Checkout identifiers.

After payment, records connect the Stripe Session and PaymentIntent identifiers, payment time and amount, rename event, resulting cumulative value, moderation status, and any refund information. Stripe may provide a payer email; nameme.lol stores only a keyed one-way hash of the normalized email for abuse and aggregate repeat-participation metrics, not the email itself.

Public reports store the reported character or rename, category, optional detail, time, user agent, and a keyed one-way hash derived from the reporter’s IP address. Rate-limit records contain keyed hashes of IP/browser identifiers and short-lived timestamps. Admin actions and moderation decisions are also logged.

When someone follows a winning Winner URL through a character profile, nameme.lol records the character, winning rename, stored destination URL, and click timestamp. This click tracker does not add cookies, fingerprinting, or visitor-profile fields. Ordinary hosting logs may still contain request metadata.

Vercel Web Analytics collects anonymized traffic measurements for public pages, including page views, daily unique visitors, referrers, country, browser, operating system, and device type. Admin and Checkout result routes are excluded from analytics collection.

When the public audience counter is enabled, the home page records a keyed one-way hash of the browser identifier, its first-seen time, and its most recent home-page heartbeat. These records produce approximate total-visitor and active-watcher counts; they do not contain the raw browser identifier. The counter is automatically hidden if its service is disabled or unavailable.

This information is used to process payments; operate and show rename auctions and attribution; measure and publicly report aggregate Winner URL referral activity; apply the Rules; prevent abuse and fraud; screen names and URLs; receive reports; handle disqualifications, refunds, and card disputes; troubleshoot and secure the service; and meet legal, accounting, or payment obligations.

Stripe processes payments. Payment-card details are entered with and handled by Stripe; nameme.lol does not directly store card numbers. Stripe receives the transaction information needed to provide Checkout and includes limited rename, auction, amount, and accepted-policy version metadata on the Checkout Session and PaymentIntent.

The application and database are handled by its hosting and infrastructure providers. Character images may be stored by Vercel Blob when that storage mode is configured. Proposed and display names may be sent to OpenAI’s moderation service when production moderation is configured. Winner URLs may be sent to Google Web Risk when that optional reputation mode is configured. These providers receive information only for the service functions described here.

nameme.lol does not sell personal information.

Proposed character names, public display names, contribution amounts, cumulative values, rename times/history, the winning name and attribution, a winning Winner URL, and its aggregate tracked click count can be displayed publicly. Public display names are unverified and are not necessarily unique.

Payer email hashes, IP addresses, user agents, Stripe identifiers, report details, and payment/refund records are not intentionally displayed to the public. Reports are reviewed internally.

When enabled, the audience counter and public Checkout flow set an HTTP-only nameme_browser cookie for aggregate visitor counting and rate limiting; it lasts up to one year. The public visitor total approximates unique browsers, so clearing or blocking the cookie can cause a browser to be counted again. The admin area uses a separate HTTP-only session cookie for operator authentication. The animated character-cameo feature uses session storage to remember recent cameo timing for the current browser session.

Vercel Web Analytics does not use analytics cookies and does not track a visitor across different days or websites. The codebase does not include advertising analytics, browser fingerprinting, or a separate error-monitoring service. Ordinary server logs are used for moderation and operational troubleshooting.

No fixed deletion schedule is currently implemented. Records, including hashed visitor-count records while that feature is enabled, are kept for as long as reasonably necessary to operate the service and public auction history, enforce the Rules, handle refunds and disputes, protect the service, and satisfy legal or accounting obligations. When rate limiting runs, it deletes rate-limit events older than approximately one day; the browser cookie may remain longer as described above.

You can avoid submitting optional Winner URLs and report details. You can block or delete browser storage in your browser, though rate limiting or other parts of the service may stop working as intended.

This page may be updated as the service changes. The effective date and version above identify the current policy. Historical Rules and Terms versions accepted for payments remain attached to those payment records.

Operator: Lettau Ventures LLC

Privacy/support contact: thenamemeapp@gmail.com. We may need enough information to identify the relevant record and verify the request.

Operator profile: https://x.com/lettauc