Your voice is public.
Your login is not.

Information we use and why

• Account information: your email, verified sign-in identifiers and session information let us sign you in and protect account access. Your chosen name, handle, bio and avatar provide your public profile.
• Content and activity: headlines, amounts, reactions, follow-ups, display records, friendships, invitations and profile history run the board and its social features.
• Safety and support records: reports, moderation decisions, account restrictions, administrative action records and support correspondence help us investigate issues, apply rules and review decisions.
• Technical information: cookies, connection information and operational logs support sessions, display deduplication, troubleshooting and abuse prevention. Hosting and authentication providers may process IP addresses and browser or device information.

For abuse limits, the service derives keyed, one-way identifiers from account identifiers or visitor cookies. Private abuse records contain the action category, this protected identifier and a timestamp. The application does not use an IP-based identifier for these limits. Rate-limit buckets expire, and denial-event records become eligible for deletion after 48 hours; cleanup runs as traffic is processed, so eligible records may remain until cleanup occurs. Provider security logs, moderation records and support records have separate retention needs.

What visitors can see

Your profile name, handle, bio, avatar, published headlines and author follow-ups are visible to visitors, including people without accounts. Ranks, amounts, display counts, reaction counts and recorded moments at number one are also public. Dislike counts are hidden while a headline is number one and return if it loses the lead. Individual reaction records are not publicly listed.

Friendship lists and pending gifts require the relevant signed-in account. An accepted Encore post and its attribution are public. Your sign-in email, authentication tokens, private account-linking records, reports and internal moderation notes are not published on your profile.

Display counting uses account or browser signals and limited-lived verification of board visits. These signals are not a count of verified unique people and cannot prevent every attempt to switch cookies or devices. Avoid putting sensitive details in public content. Visitors can copy, share or save it outside HeadlineNow; hiding it here cannot recall those copies.

Providers and browser storage

The service uses OpenAI Sites and Cloudflare for hosting and storage, Supabase for authentication, and Resend for sign-in emails. Google processes authentication information when you choose Google sign-in. These providers receive information needed for their roles, and processing may take place outside your country.

Cookies maintain your session, sign-in flow, signed-out state and visitor-counting identifier. The visitor cookie can remain for up to one year. Browser storage may also save interface preferences. You can clear these through your browser, but doing so may affect sign-in and display deduplication; it does not delete your account or server records.

Dodo Payments hosts checkout. We send the selected product, amount, order reference and checkout-environment identifier. Dodo collects the checkout email and billing details you enter under its own privacy policy and may email receipts. For paid purchases, Dodo processes checkout information as merchant of record.

HeadlineNow stores private order and payment references, amount, currency, tax, delivery and refund states, the accepted policy version and timestamps to verify delivery and handle requests. We do not store full card numbers or card security codes. We may disclose relevant records to service providers for these purposes or when necessary to respond to legal obligations, protect users or resolve a payment dispute.

Retention and removal

Public content and profile history remain available for the archive unless hidden or removed. Hiding a headline changes public visibility; it does not erase all underlying records. Legacy comment and selected-reply records are no longer offered or displayed but remain private and can be included in a removal request.

Account, support, moderation, audit and payment records are retained as needed to operate the service, investigate abuse, resolve disputes and meet applicable obligations. Some safety or financial records may need to remain after a deletion request. Providers and backups may have separate retention periods. We do not promise that logging out, hiding content or submitting a request immediately deletes every copy.

Make a privacy request

You can edit your profile and hide your own headlines. Account deletion is currently handled by email, not a self-service control. To request access, correction, deletion or review of a privacy concern, email goog98@gmail.com from your sign-in address. Include your handle and the account or content involved.

We verify account ownership before disclosing or changing private data, clarify the request if necessary and reply with the action taken or the reason any records must remain. If you cannot use your sign-in address, explain that in your request so we can discuss appropriate verification. Do not send passwords, sign-in codes, full payment details or identity documents in your initial message. Applicable privacy rights remain available even where the interface has no dedicated control.

Children and updates

The service is intended for adults aged 18 and over. Contact us if you believe a child has submitted personal information. Changes to this notice will appear here with an updated date.