Privacy & contact
We collect what we need to run the journal. We do not sell your personal information.
Effective November 10, 2026. This policy covers plainnerd.com and its public API. PlainNerd is responsible for the information collected through this website. For editorial or privacy requests, email andrew.k@segunda.ai.
What you share with us
- Digest signup: your email address, signup date, and consent to receive the digest. We currently collect a launch list for the first issue; submitting the form does not send an email.
- Story submissions and drafts: your account identifier, name, email address, title, description, article content, submission date, and moderation status. We use these to review your work and contact you about it. We also store review status and feedback from the editors. Your email is not displayed publicly.
- Comments: your chosen name, comment, associated article, submission date, and moderation status. Approved comments and their names are public. Please keep private information out of your comment.
- Messages: if you email us, we receive your address and the information you include. We use it to respond to your request.
Your account
When Google sign-in is available and you choose to use it, we receive your name, email address, profile photo URL, and Google account identifier. We store this profile and the provider credentials needed to manage the connection in Cloudflare D1. Provider access and refresh tokens are encrypted at rest by the application. We do not receive your Google password or request access to your inbox or files. Signing in does not subscribe you to the digest or publish your profile.
We use an essential, HTTP-only session cookie to keep you signed in, and temporary cookies to secure the sign-in process. Session records include your IP address and browser user agent to support account security. Sessions expire after seven days without renewal; using the site can renew them. Signing out revokes the current session. Google also processes your sign-in under its own privacy policy.
Your public profile
A profile is optional. If you save one, we store the name, handle, short bio, about text, location and links you enter, and a photo if you upload one. Your browser crops and resizes the photo before it uploads, which also removes the file’s metadata, such as the place it was taken; the photo is stored in Cloudflare R2. We do not copy your Google photo into your profile.
A profile stays private until you choose “Show my profile publicly”. From then on anyone can open its page, it is available through our public API, and it appears beside articles you wrote. Your email address is never shown. Switch the setting off at any time to take the page and photo down; browsers and caches may keep a copy of the photo for up to a day. Search engines are asked not to index profiles of people who have not published an article here. Editors may hide a profile that impersonates someone or is used for spam.
What stays on your device
Previously saved guest bookmarks and local writing drafts stay in your browser. You can explicitly import bookmarks or recover a local draft after signing in. Signed-in bookmarks, articles you mark as read, and drafts you save are stored in your account so they are available across devices. We do not automatically record your reading history. You can remove bookmarks and clear your reading list from your profile. We do not use advertising cookies.
View counts
Each article shows how many times it was opened and how many times AI assistants or scripts fetched it. We store only a running total per article and day: no cookies, identifiers, IP addresses or user agents. Automated readers are recognised from the headers their requests send, such as the user agent, and counted separately from people. Requests from AI assistants, scripts and crawlers are also reported to PostHog with their user agent and the page they requested, without an IP address.
Usage analytics and cookies
We use PostHog to understand how the journal is read: pages viewed, the page you came from, clicks on links and buttons, device and browser type, and an approximate location estimated from your IP address. We configure PostHog not to store your IP address.
If you accept analytics cookies, PostHog stores an identifier in a cookie and your browser storage so it can recognise return visits, and it records session replays: how pages scroll, render, and respond to clicks. Replays mask everything you type, and your account pages, drafts, comments, and editorial tools are hidden from them. We use replays only to find bugs and confusing pages.
If you decline or have not chosen yet, PostHog runs without cookies or browser storage, records no replays, and counts visits anonymously. We store your choice in your browser. You can change it at any time with “Cookie settings” at the bottom of every page. If your browser sends a Do Not Track or Global Privacy Control signal, no analytics run at all.
Analytics requests pass through plainnerd.com, and editorial tools send nothing. PostHog processes this data on our behalf in its United States cloud; see PostHog’s privacy policy.
Hosting and security
Cloudflare hosts the website and stores submitted records in its D1 database. It processes technical request data, including IP addresses, to deliver the site, protect it from abuse, and provide operational logs. Our application uses IP-based rate limiting but does not save your IP address in the submission, comment, or signup tables. We do not intentionally log form contents or email addresses.
Our hosting and email providers may process information outside your country. Their infrastructure and retention practices also apply to technical logs and correspondence. See Cloudflare’s privacy policy. We may disclose information when required by law or necessary to protect the site and its readers.
Why we use your information
We use signup information with your consent. We use contributions, comments, anonymous usage analytics, and technical data to operate and improve the journal, moderate submissions, prevent abuse, and respond to you. Where applicable, these activities rely on our legitimate interests in running a safe independent publication. Analytics cookies and session replays rely on your consent. We do not use automated decisions to publish your work.
How long we keep it
- Anonymous pending or rejected submissions and comments are removed after 90 days. Anonymous submissions returned for changes are also removed after 90 days without an update.
- Anonymous accepted submission records, including the contributor contact address, are removed after 365 days. Published articles and approved comments remain in the journal unless removed through an editorial or privacy request.
- Launch-list signup records are kept until you ask to withdraw; we then delete your email address. We will update this notice if the digest begins and its subscription handling changes.
- Account profiles, saved drafts and submissions, editorial feedback, and linked identities remain until you request deletion. You can edit or empty your public profile and remove its photo yourself; deleting your account deletes both. Bookmarks and reading-list records remain until you remove them or delete your account. Expired sessions and temporary sign-in verification records are removed by the daily cleanup. Contact us to request account deletion or a copy of your account data.
- These limits are enforced by a daily cleanup of the live database. Deleted information may remain temporarily in the hosting provider’s recovery backups; D1’s recovery window can be up to 30 days.
- Privacy and editorial correspondence is kept only as long as needed to resolve the request and any related obligations. It is managed separately from the site database.
Your choices and requests
Email andrew.k@segunda.ai to withdraw your signup, request a copy of your information, correct it, or ask for deletion. Use the email associated with your submission when possible; for a comment, include its article URL and chosen name. We may ask for proportionate proof that the information is yours before changing or disclosing it.
Depending on where you live, you may also have rights to restrict or object to processing, receive your data in a portable format, and complain to your local data-protection authority. Withdrawing consent does not affect processing that already took place. We handle requests within the time required by applicable law.
Changes to this policy
We will update this page and its effective date when our practices change, including before introducing advertising trackers or a new use of signup information.