Privacy Policy

For clarity, this policy separates personal information you directly provide from device, browser, and operational log data.

If you create an account, submit a request, or donate, the direct information EasyNIH may store can include your name, email address, birthday, password hash, passkey public-key metadata, edit requests, moderation notes, digest topic selections, digest email settings, unsubscribe token, and related account timestamps.

EasyNIH does not intend to store full card numbers, CVC values, or similar full payment credentials.

Separately from direct account information, EasyNIH also creates limited technical and operational records needed to run the site.

Those records can include session identifiers, email-verification challenge records, request timing, browser restriction flags used for the under-16 gate, request IP address in limited admin or abuse-prevention contexts, and similar system metadata.

Most of that information is technical or operational rather than profile information that you type in yourself. However, in some jurisdictions, certain technical identifiers can still be treated as personal information or personal data when they are reasonably linkable to a person, account, device, or household.

When a request causes EasyNIH to generate a new AI-assisted article review, the site may log operational details about that pull for internal administration and cost tracking.

Those log details may include the article identifier, when the pull happened, the page or request source that triggered it, whether the visitor was signed in, the signed-in account marker if available, the request IP address in that limited context, and token-usage information returned by the AI provider.

Passwords are stored as hashes rather than plaintext. Session cookies are used to keep users signed in. Email verification codes and other temporary challenge records are created as part of sign-up and recovery flows. Passkeys, when used, store public-key credential data and related counters, not private keys.

Stored data is used to run accounts, verify ownership of accounts, send or attempt to send email verification codes, authenticate users, moderate edit requests, support digest subscriptions, process donations, and enforce age restrictions and other account rules.

Accounts are restricted to users who are at least 16 years old. If the site determines that an account belongs to someone under 16, related account data and request data may be deleted, and the browser may be marked as restricted to help prevent renewed account creation attempts.

The site may use a configured email server or mailbox provider to deliver email verification messages. If email delivery is configured, the site transmits the recipient email address and verification content needed to send those messages.

If you enable current-topics digest emails, the site also stores and uses your selected digest topics, unsubscribe token, and delivery timestamps to send recurring digest messages and honor unsubscribe requests.

Donation payments on EasyNIH use Stripe-hosted payment fields rendered inside the site. Card details entered into those fields are sent to Stripe for payment processing rather than being intentionally stored by EasyNIH.

EasyNIH may receive and store limited donation-related data needed to support the transaction, such as amount, donor name or email if provided, message text if provided, payment status, Stripe identifiers, and basic fraud or failure responses. Full card numbers, CVC values, and similar full payment credentials are not intended to be stored by EasyNIH.

Account records, edit requests, passkey data, and moderation data may be retained until deleted by the operator, removed through age-restriction enforcement, or replaced by updated records. Temporary verification challenge data is retained only for limited periods needed for account security.

Reasonable efforts may be used to protect stored data, but no security measure is perfect. By using the site, you acknowledge that no system can guarantee complete security.

This policy may be updated by posting a revised version on the site. Continued use of the site after an update means you accept the revised policy.