Privacy

Last updated: September 18, 2026.

FellowMakers.app is published by Aleksei Krasnoperov, who is responsible for the personal data described here. For privacy questions, corrections, exports or removal requests, contact hello@fellowmakers.app or use the contact page.

People on the map

A person is listed because they publicly asked to connect, in a post or a reply on X, and said at least who they are. The list exists so that the people who asked can see how many they are and find whom to connect with. We collect those public posts and replies, the public profile behind each, and information from linked project websites; the conversations are described on the about page. We leave out anyone who said they are under 18; an unknown age is accepted and never treated as verified adulthood, and no age is stored. A card can include a name, handle, portrait, biography, source quotation, location (where they said they are now, or, marked as such, where they said they are from), role and projects. Each card links to its source. Owners can update their details after signing in with X; original quotations keep their source links.

We organize and summarize those sources to help people discover other builders and their work. Categories, summaries and waves are editorial interpretations, and may be AI-assisted; they are not verified facts about a person. We do not use them to make decisions about employment, credit or eligibility. Likes, reposts, follower counts and impressions were read during research but are not published.

Cards, projects and edits are public, including through our JSON API and Markdown pages. Search engines and other readers can copy them. Portraits loaded from X's image host expose normal request information, such as your IP address, to that host.

Your card

Leaving is one step: sign in with the X account that wrote the post and choose Remove my card. Without signing in, write to complains@fellowmakers.app from any address and name the X account; a removal is done without questions. The same sign-in lets you change what the card says, and the change stays through every import. Signing in adds nobody to the list.

Writing a card

An X account that owns no card can write one from your profile: a name, what you are building and one line on it, a link, where you are, a short introduction and, if you choose, whom you would like to meet, with your agreement to its being published under your X handle. We store those words with the account's X identifier until a person has read them. Until then they are private: only the administrators named for this deployment can read them, through an operator endpoint, and they appear nowhere on the site, in the API or in the Markdown pages. Withdrawing the request from your profile deletes it; deleting your account deletes it too. Once a person has read it and added you, the words appear as a card like any other, public in every way described above and yours to change or remove; the request stays with your account, marked as handled, only so that a later one can be told apart.

Search queries

Search logs store queries, source, filters, results, timing and outcome from the website, API and MCP, without account or IP identifiers. Cloudflare Workers AI translates and ranks queries against public product and wave descriptions.

Accounts and browser storage

Reading the public site needs no account. Signing in with X stores its account identifier and display name and connects the account to its matching card, or to the card request it wrote (see Writing a card above). Signing in with Google stores its account identifier, email address and display name. Email is optional for X accounts.

Browser sign-in creates a server session and an HttpOnly cookie, normally lasting thirty days. We also store your theme preference in your browser. Connected applications receive only the access you approve; grants and credentials are stored so that access can be checked and revoked from your profile. Temporary sign-in state expires separately.

Services that help us operate the site

We use Cloudflare for hosting and storage and OpenAI as our LLM provider. Our analytics, feedback and diagnostics services are Simple Analytics, UserTold and Sentry. The descriptions below apply when the corresponding service or feature is enabled; not every visit involves every provider.

• Cloudflare delivers the site and stores accounts, sessions and landscape records in D1, and temporary authorization state in KV. It processes request information such as IP address, URL, browser information and timing for delivery, security and operational logs. See Cloudflare's privacy policy.
• Simple Analytics helps us understand aggregate traffic, such as pages visited, referrals, country and device or browser type. Its analytics is designed to work without tracking cookies or cross-site visitor profiles. See Simple Analytics' privacy policy.
• UserTold supports optional feedback interviews to improve the site. If you choose to participate, it can process your answers, audio and transcripts, page context and interactions during the interview, and screen recordings when offered and explicitly shared. The interview disclosure explains the recording before it starts. You can decline or stop an interview and still browse the site. Contact us to request removal of an interview. See UserTold's privacy policy.
• Sentry helps diagnose failures. Error reports can include error messages, stack traces, page or request information, browser details and diagnostic identifiers, and may contain personal data included in an error. See Sentry's privacy policy.
• OpenAI processes content supplied for AI-assisted work, such as source material, prompts and generated summaries, and interview content where AI interview features are used. Its API does not use submitted data to train models by default unless sharing is explicitly enabled. Retention depends on the endpoint and settings: abuse-monitoring logs normally remain for up to thirty days, with exceptions, and some stored application data lasts longer. We do not promise zero retention. See OpenAI's data controls.

X and Google also process sign-in requests under their own policies. Applications you connect and websites you follow from a card operate under their own privacy terms.

Why we process data

We rely on our legitimate interests to publish a useful, source-linked directory of public introductions, so that people who asked to connect can find each other, to respond to messages, understand usage and keep the service secure. You can object to the inclusion of your information. Account and authorization data are processed to provide the features you request. Optional recorded research relies on your consent; withdrawing it does not affect processing already carried out lawfully. We may retain information when required by law.

Providers may process data outside your country, including outside the European Economic Area. The applicable provider agreements describe their transfer safeguards, such as adequacy decisions or standard contractual clauses. Contact us for information about the safeguards applicable to your data.

Retention and deletion

Public listings and account records have no automatic deletion deadline; they remain until removed or no longer needed for the service. Operational logs, diagnostics and provider backups follow the relevant service's retention settings. Interview records are kept for the research purpose until no longer needed or a removal request is fulfilled. Contact us for the retention details of a particular record.

Your profile lets you permanently delete your account, public card, saved changes, card request, projects where you are the only listed builder, and editorial waves referencing that person or those projects. Shared projects remain without your profile. Browser sessions and connected-app credentials are removed. Technical fingerprints of excluded identifiers remain solely to prevent future imports from restoring erased listings.

This deletion applies to the site's live database. It does not delete original X posts, the separate research archive, historical Git snapshots, provider-managed backups or records held by the services above. Previously downloaded copies cannot be recalled. Contact us for requests concerning those records or an export; deleting an account alone does not submit those separate requests.

Your choices and rights

You can request access, correction, deletion, restriction or an export of your personal data, and object to processing based on legitimate interests. You can withdraw consent for optional research and revoke connected applications from your profile. Include the X handle, account address or interview details needed to find your record; we may need to verify that the request is yours. You may also complain to your local data protection authority.

Paid options

There are none today. Reading the site and being listed are free and stay free. If paid options are added for people or projects on the list, such as extra features or placements, this page will name the payment provider and what it receives before they go live; paying never decides who is listed.

Changes

We update this page when our practices change and show the revision date above. Our terms explain the rules for using the site.