Privacy policy

What do we collect and why?

Reference ratings and hashed browser/network identifiers

Record private feedback, prevent duplicate ratings and abuse, and support editorial review

Email, signup source, subscription status and delivery records

Send requested newsletters and account emails, manage delivery and honor unsubscribe choices.

Account name, email, X identity, avatar, login method and sessions

Create and secure your account, sign you in and show its private profile.

Saved reference IDs, first/latest save timestamps, Header revisions, collection names, collection share links and account preferences

Provide your private Saved collection and the collections you name, remember your choices and measure useful discovery in aggregate. Anyone with a collection’s share link can see its name and the references in it, but not your name, member number or other saves; stopping sharing turns the link off at once.

First-day Save-control exposure, click and failed-attempt timestamps

Understand where new members stop before their first save. These optional account measurements honor Do Not Track and Global Privacy Control; only aggregate counts enter our analytics dashboard, without reference IDs or browsing history.

Suggested URLs, messages, contact details, member credit and hashed IP addresses

Review submissions, keep messages sent through our former member chat, prevent abuse and credit contributions where appropriate.

Sponsorship links, contact and company emails, selected options and hashed IP addresses

Review sponsor requests, prevent abuse and follow up about a proposed placement.

IP address, request time, browser/device category and request or error information

Deliver and secure the site, enforce limits and troubleshoot failures.

Page paths, aggregate visits, realtime sessions, cursor or card positions and eligible public avatars

Measure aggregate use and provide live visitor counts and cursor activity.

Library page paths (including V2), referring sites, approved campaign tags, source clicks, search result-count ranges, filter use, country, browser/device category, performance timings and daily hashed visitor identifiers

Measure discovery, traffic and page performance with self-hosted, cookieless analytics. We process IP addresses to derive daily identifiers without storing the raw address in analytics. We exclude search text, source destination URLs, account identities, account/admin pages, shared collection links, owner previews and URL queries other than approved campaign tags, and honor Do Not Track and Global Privacy Control for this collection.

Text of library searches that find no results, normalized, with a daily hashed visitor identifier

Find missing work, synonyms and brand names. We drop searches that look like an email, handle, link, long number or sentence, and searches made under Do Not Track or Global Privacy Control. Only terms searched in at least three daily sessions are shown to the owner. Search text never enters our analytics.

Apps you connect over MCP (the name and sign-in address an app registers, and when it was connected and last used), the tool each read uses, a one-way hash of each request, and monthly, per-minute and daily account activity counts

Connect your agent to your account, enforce your monthly allowance and rate limits, and recognise an exact repeat of a recent request. We also use daily activity and anonymous tool totals to understand MCP adoption and repeat use. Usage records don't store the text your agent searches for, reference lists or prompts.

Plan, subscription status, billing period and Stripe customer and subscription identifiers

Provide paid plans, apply early-member pricing and reconcile payments.

Paid invoice amounts, the referral code an account came through, referral codes you own, daily link-click counts per code by referring site, and referral earnings

Credit referrals and calculate and pay referral earnings. Referrers see counts and their own earnings, never who joined. Click counts are daily totals per code, without IP addresses or visitor identifiers.

For an account that came through a partner's Dub link: Dub's click ID, our account ID and the amount of each Pro payment after tax and fees

Let Dub, which runs our partner program, credit and pay that partner. We send Dub no name, email or payment details.

Questions, requests and supporting evidence

Answer questions and handle corrections, rights requests, accessibility issues and security reports.

Public source posts, account names, profile images and credited work

Present and attribute editorial references with a link to the source.

Information comes from you, your browser, our providers and public sources linked from featured items. You can browse without an account or newsletter subscription.

Where a legal basis is required, we use:

• Contract performance for accounts, authentication, Saved collections and other features you request.
• Consent for requested marketing email and technologies that require consent.
• Legitimate interests to operate and secure the site, review suggestions, handle correspondence, measure aggregate use, provide live presence and publish source-linked editorial references.
• Legal obligations when the law requires us to keep or disclose information.

We do not sell personal information, use it for cross-site targeted advertising or make solely automated decisions about you that have legal or similarly significant effects.

Who receives your data?

Cloudflare processes network and security data. Resend delivers newsletters and account email. Stripe processes payments: card details go to Stripe and never reach posts.design, and Stripe's privacy policy covers what it collects at checkout. Dub runs our partner program and receives the partner referral data described above. X processes sign-in requests when you choose X login; posts.design does not retain X access or refresh tokens.

Header requests and legacy URL suggestions are saved in private review records and forwarded to a private Telegram review channel. Signed-in member suggestions and messages sent through our former member chat are kept in our private review records; changes to those records may be signalled through our realtime service.

Sponsor requests are saved in private review records and forwarded to the private Telegram review channel.

Reference ratings are private usefulness feedback. Aggregate ratings and a reference link may be sent to our private Telegram review channel; voter identities are not included. Editorial decisions remain manual.

Connected visitors can see participating visitors' cursor activity and, for eligible signed-in members, a public profile avatar. Names, handles, email addresses, account IDs and private session data are not sent through the cursor feed.

People helping operate posts.design may access information needed for their work. We may also share relevant information when required by law, to protect people or to establish or defend a legal claim.

Our providers may process information outside Honduras. Where applicable law requires transfer safeguards, we rely on the lawful mechanism available for that provider and transfer, such as an adequacy decision or contractual safeguards. Contact us for details.

When you connect an agent app over MCP, the references it reads are sent to that app, which handles them under its own terms and privacy practices.

When you follow a source, social or affiliate link, that provider handles your visit under its own privacy policy. Remote images or embeds can send request information to their provider, and an affiliate destination may receive referral information.

What do cookies and browser storage do?

Member sessions remain valid until you log out, revoke them, delete your account, or a security change invalidates them. The secure, same-site sign-in cookie lasts up to 400 days and is renewed when your browser refreshes its signed-in profile. Clearing cookies or browser-imposed retention limits may require you to sign in again. Email sign-in codes last 1 hour; X sign-in and deletion confirmation state lasts up to 10 minutes; deletion-status receipts last up to 30 days. These are secure, same-site cookies used for account access rather than advertising.

We also use local and session storage for preferences, newsletter interface state, navigation and realtime sessions. A six-month browser cookie remembers only whether you last signed in with X or email, so we can mark that choice next time; it does not contain your account identity. Persistent values remain until changed or cleared; session values normally last for the browser session. Clearing browser storage may sign you out or reset features, but it does not unsubscribe you or delete server records. Cloudflare may use cookies needed for access and security.

When you open someone's referral link (a posts.design address with ?via=), a secure, same-site cookie remembers only their code for up to 90 days, so we can credit them if you join or subscribe. A new account uses it up; it never identifies you. A partner's Dub link (with ?dub_id=) keeps Dub's click ID in the same cookie instead, and the last referral link you open counts.

When you choose to rate a reference, a secure browser cookie identifies your guest feedback for up to one year. A temporary IndexedDB record and a hashed server mapping support interrupted first ratings for ten minutes. Guest feedback expires with its cookie; clearing browser storage does not withdraw an existing rating.

When will we email you?

Creating an account with email does not subscribe you to marketing. A new X account with a confirmed email starts subscribed to Posts Weekly and Hot Headers; returning accounts and prior opt-outs keep their choices. Neither sign-in method subscribes you to Pro launch updates. You can manage Posts Weekly, Hot Headers and Pro updates separately in account settings.

Account, login, security, sponsorship follow-up, support and legal emails are service messages. Newsletter and product updates are marketing messages and include an unsubscribe option. Unsubscribing from marketing does not stop service messages. We use delivery, bounce, complaint and unsubscribe records; we do not build profiles from email opens or clicks.

How long do we keep data?

We keep account data while the account is active.

MCP request hashes are kept for 24 hours. Monthly read counts are kept for the current and previous month, and per-minute counts for about a minute. Daily account activity is scheduled for deletion after 90 days, including when you stop using MCP. Anonymous daily tool, app and outcome totals are scheduled for deletion after 400 days; these contain no account, grant or request identity. Records of connected apps are kept while your account is active; disconnecting an app stops its access at once. Deleting your account removes your MCP connections and usage records.

We keep first and latest save timestamps with your account to measure useful discovery. Removing a saved reference does not remove those timestamps; account deletion does.

Optional Save-step measurements keep only the first exposure, click and failed-attempt timestamps during the first 24 hours after signup, before the first successful save. We keep these timestamps with your account; account deletion removes them. They contain no reference IDs, page history or error text.

Member ratings remain until removed or the account is deleted. They stop contributing when account deletion starts and are removed during deletion cleanup. Guest ratings and anonymous sign-in bindings expire after one year. Daily hashed network identifiers enforce rating limits and expire after their daily window. Non-identifying alert receipts may remain to avoid repeated notifications.

Billing records, including payment and referral earnings records, stay after you delete your account, without your profile, for as long as tax and accounting law requires.

Detailed anonymous traffic records are scheduled for deletion after 90 days. Search text from searches with no results is kept for up to 14 days. Newsletter subscription, delivery and suppression records remain as needed to deliver requested email and honor opt-outs. Suggestions and correspondence remain while needed for review, credit, duplicate prevention, rights requests or disputes. Security logs, provider records and backups follow limited operational schedules and may be kept longer for an active security issue, legal obligation or claim. Non-identifying aggregate counts may be kept without a fixed period.

What does account deletion do?

Account deletion closes the account, revokes its sessions, removes Saved pointers, collections with their share links and local contributor identity, cancels any Pro subscription at once, cancels account Pro updates, and retires your referral codes so later payments earn nothing. You may separately unsubscribe the current email from the digest. Deletion does not recall messages, emails, public credits or copies already received by others.

What are your privacy rights?

Email [email protected] to request access, correction or deletion of your personal information. Depending on applicable law and the processing involved, you may also have rights to restrict or object to processing, receive portable data, withdraw consent or appeal a decision. We may ask for proportionate information to verify your request and may retain information where the law allows or requires it.

You can object to processing based on legitimate interests or direct marketing. Withdrawing consent does not affect earlier lawful processing. You may also complain to the data-protection authority where you live, work or believe an infringement occurred.

How do we protect your data?

We use HTTPS, access controls, restricted operational access and provider security controls to protect personal information. No online service can guarantee absolute security.

Is this site for children?

posts.design is intended for a general adult and professional audience and is not directed to children under 16. Contact us if you believe a child has supplied personal information that should be removed.

How can this policy change?

We will update the last-updated date and provide appropriate notice when this policy or our practices materially change. If a new use requires consent, we will ask before that use begins.