Privacy

Each dossier is about one person in a professional capacity: what they have said, in public, about how they choose investment managers. We compile it from public sources only — podcasts, recorded conference panels, published interviews and articles, and published documents such as investment policy statements and annual reports.

Everything a dossier says a person said is a verbatim quotation, shown with the source it came from, the date, and a link to the original. We record where every field came from. No claim is shown without its quotation, and nothing is shown before it has been reviewed. The database itself refuses to approve a quotation that does not match its source word for word.

Some sections are our own analysis of those quotations: the questions a person is likely to ask a manager, chapter titles for a recording, how a person's view has changed over time, allocators who think alike and, for a signed-in manager, how their fund meets the person (“Your angle”). They are labelled as ours, reviewed before they appear, and every line links to the quotations it rests on.

Where a quotation comes from a recording, a member can hear it: the page plays the publisher's own audio file, or its YouTube video through YouTube's privacy-enhanced player, from the moment the quotation begins. Nothing loads from the publisher or YouTube until the member presses play; when they do, that service receives the request as it would from any podcast app or website. We host no recordings.

We hold no non-public contact details and guess none. The only route to a person we ever show is one their organisation has itself published — a general enquiries page, an investor-relations address, a public profile — copied exactly from that page, with the page recorded. We do not infer email addresses from name patterns or domains, and no software of ours is permitted to.

Transcripts of third-party recordings are shown in full, with attribution and a link to the original, to members only. They are never offered for bulk download.

Beside the dossiers, members can browse a directory of the people who allocate capital for institutions — endowments, foundations, pensions, sovereign funds, insurers, family offices, health systems, outsourced investment offices, funds of funds, multi-manager and wealth platforms, seeders and consultants — and of the institutions themselves. For each person we hold their name, their current and past professional roles and the firms they held them at, where they have spoken in public, and how complete our research on them is: a score from 0 to 10, with the checks behind it.

All of it comes from public sources: organisations' own websites, public filings, and public recordings and articles. Every role is shown with the source and the date that place the person there, and a role we last saw years ago is shown as such, never as current. The directory is for members only and is never offered for bulk download.

Its purpose is to help fund managers understand who allocates capital and how, so that they approach the right people with something relevant to them. We rely on legitimate interests: the information is professional, already public, and limited to what serves that purpose.

We never hold contact details beyond a publicly documented route, or anything about a person's private life. An allocator's profile may show their photograph, but only one their own organisation publishes on its own website, with that page recorded. We crop and tone every photograph the same way and show it in black and white; we don't otherwise alter it. Photographs are shown to signed-in members only, never in emails, share previews or anything public, and we remove one the same day anyone asks.

To correct an entry, or to object to being listed, write to privacy@allocatorconnect.com. A correction is made against the source. An objection removes the person from the directory, and we keep a record of it so that they are not added again.

If a manager uses the site to write to you at the address your organisation published, and chooses to let us record it, we keep the date and the fact of that note in their account only, for no more than 24 months. Write to privacy@allocatorconnect.com and we'll stop the site offering your address to any manager.

If you are named in the directory or on a dossier and something is inaccurate, or you would rather not appear at all, write to us at privacy@allocatorconnect.com and say so. A correction is made against the source; a removal request is honoured — the page and everything compiled for it are taken down. We do not require a reason.

A manager who joins shares a few of their own investor letters or presentations. From those we build a profile of how they invest and how they write, every sentence of which cites a passage they wrote. That profile is used for the uses described on this page, among them ranking the allocators against the manager's fund and drafting first notes in the manager's own voice. The letters and the profile are used for nothing else and shared with no one.

A manager can set a goal: how much they aim to raise, by when, and mainly from whom. We use it only to order the suggestions on their desk. Their desk, its weekly moves and the “Useful / Not for me” choices they make are readable by their account only, never shown to allocators or other members, and never pooled across members; we read the choices only to improve what we suggest to that manager. When a manager uploads a letter, we also use it to suggest which allocators on their list it speaks to, to draft their notes and a post, and to point out passages worth checking; the post is theirs to edit and publish or not. An applicant who agrees on the application lets us prepare their desk before they first sign in, if we admit them: we read public material about their firm (its website, letters it has published, regulatory filings such as Form ADV, and interviews the manager gave), draft their profile, shortlist and first notes from it, and list everything we read. Other people at the firm appear only by their role. Nothing is built for an applicant we don't admit, and a member who withdraws or asks has it deleted within seven days. Suggestions marked as drafted with AI were written by Anthropic's Claude models and checked by our code; flags on a letter are questions to take to the manager's own compliance adviser, not legal advice.

To build the profile, read uploaded letters, rank the allocators, match gives and write the drafts, the letters, the gives and the allocator quotations are sent to Anthropic's Claude models through Anthropic's API, under terms that exclude use of the content for training. They are sent to no other service.

When a member asks a question on a profile (“Ask”), the question and that person's published quotations are sent to Anthropic's API on the same terms. The question and its answer are kept in the member's account, and we read them only to check the quality of answers. A member can ask up to twenty questions a day.

The schools and past employers a manager enters on their fund page are used only to point out shared ground on profiles, and are shown to no one else. A manager's Following list is private to them; we send no emails or notifications about it.

A manager can also upload letters here. An uploaded letter is held in private storage that only our reading step can open, until we have read it, usually by the next morning and never longer than seven days. It is then kept on an AllocatorConnect computer with the other letters and removed from this site. The profile built from the letters — including the passages it quotes — and the manager's ranking and drafts are stored in the manager's account, readable by that account only.

A manager can keep a give library: things from their own work they could share with allocators, such as observations, short write-ups, resources, questions and people they could introduce. They type these in, or keep the ones we suggest from their letters. We use the library only to suggest which give suits which allocator and to draft that manager's own notes. It is readable by their account only, never shown to allocators or other members, never pooled across members, and never used to train any model. For people a manager could introduce, we keep only the name, organisation and topics the manager enters; we never contact them, and we never make introductions.

Members can ask us to suggest a plan for becoming better known: what they might be known for, where the people they want to reach already appear, and drafts of posts and essays in their own words. For that we use what they have already given us (letters, their profile, their style answers and their list of people), plus a few answers, links to their published work and, if they choose, a CV. We never read their social media accounts. Drafts are shown only to their account on the site; we read them to check them before they load. We never publish, post or send anything for a member, and we never use one member's plan, choices or drafts for another member, for our research, or to train any model. Text a member pastes into the publishing check is checked in their browser and is not sent to us. Removing an answer or a file removes everything built from it.

Some members can have us draft a presentation about their firm. For that, they can upload documents such as fact sheets, due-diligence questionnaires, return statements and an existing presentation. Uploads are held in private storage until we have read them, usually by the next morning and never longer than seven days, then kept on an AllocatorConnect computer with the member's letters and removed from this site. Before anything is sent to Anthropic's API, we remove email addresses, phone numbers, account and tax numbers, and the names of investors the member lists for us; we refuse documents that name investors, such as subscription agreements and capital statements. The presentation, its drafts, the member's notes and the facts we drew from their documents are shown only to their account on the site; we read them to check them before they load. We never send a presentation to anyone, never use one member's documents for another member or for our research, and never use them to train any model. Removing a file removes everything drawn from it.

A manager can also keep a private list of people they know who might introduce them to an allocator: a name or a label, an organisation, a role, how the person knows the manager's work, and which allocators the manager thinks they know. We use it only to suggest who might introduce that manager, by setting it against the public record about the allocator, and to draft the manager's own request, which the manager sends themselves. We keep no contact details for these people, we never contact them, we never research them, and we never make introductions. The list is readable by that manager's account only, never shown to allocators or other members, never matched against another manager's list or pooled across members, and never sent to an AI model. A person left untouched for two years is removed unless the manager keeps them.

A manager can mark the events they are considering, going to or speaking at, and note whom they met there. We use these only to plan that manager's own steps with the people they want to meet and to show them which events led anywhere. They are readable by that manager's account only, never shown to organizers, allocators or other members, never counted or pooled across members, and never sent to an AI model.

A manager can leave at any time by writing to privacy@allocatorconnect.com. We delete the account, which removes everything stored under it — profile, ranking, drafts, gives, uploaded letters, presentations, drafts and uploaded documents, plans, drafts and the publishing log, people they know, introduction requests, event plans, check settings, note choices and kinds of note, notes, logged touches, relationship paths, contacts, requests, working-style answers, angles, background, raise settings, follows and questions — and we delete the letters and every working copy we hold.

Pilot members may be asked to complete one or two short feedback surveys, hosted on Google Forms. Their answers are used only to improve the product, and are never shared or published without their permission.

Everything a manager adds — their stage with an allocator, their notes, the touches they log, their relationship paths (what they sent, what the allocator replied, any history or text they paste, and the dates an allocator named), their raise date and fund status, the drafts, the contacts they already know, the people they could ask for an introduction and what came of each request, the events they plan to attend and whom they met there, and any request to research one of those contacts — is stored in their own account and readable by that account only, with the one exception set out below for a dossier request. This is enforced by the database, row by row, not by the application; we test it after every change to the database's access rules, with real accounts trying to read each other's rows.

A manager can also tell us how they like to work — whether they enjoy calls, how much they will travel, what they want to protect — and get an outreach plan built from the answers, along with a note on each dossier of how that allocator's stated approach fits them. The answers are stored in their account and readable by that account only. The plan is worked out by fixed rules on our own site, so the answers are sent to no AI model and no other service; they are never shown to an allocator or another manager, and never used to rank anyone. The manager can delete them from the page at any time.

Relationship paths suggest each manager's next step with one person. The plan is worked out by fixed rules on our own site, from the dates and kinds of contact the manager logged. Each morning we also draft the next step for paths that have one due, with a Claude model through Anthropic, from public information about the allocator, the manager's mandate as we hold it, the kind of step and its dates. We never send it the text a manager pasted or the notes they sent. To keep any one person from being crowded, we count, without names, how many managers our own news feed has suggested write to the same person in a week, and space those suggestions out. We never count, pool or share managers' paths or event plans.

Before a manager sends a note, the site can read it and point out habits that waste allocators' time, with a suggested rewrite. The check runs by fixed rules inside the manager's own browser, using what the site already shows that manager about the allocator and their own path with them. The note is not sent to us or to any AI model, and is not stored unless the manager chooses to keep it with their path. If a manager turns off a kind of suggestion, or tells us whether their email signature carries a postal address, that is stored in their account and readable by that account only. We never count, pool or share what the check finds.

When we suggest notes, we show two kinds side by side and learn which kinds each manager prefers from the notes they copy, mark as preferred or record as sent. That record is readable by the manager's account only, never counted or pooled across managers, and can be cleared at any time from My style. A manager may also paste notes they have sent, so we can propose a kind of note in their style. We remove names, email addresses and phone numbers before reading them, send them to Anthropic's Claude models through Anthropic's API only, and delete what was pasted once it is read; we keep only the proposed kind and two examples without names. Papers a manager adds are read the same way, and we keep only the title, date, a short summary and the topics.

If an allocator asks to be removed, their dossier is taken down and every manager's notes, logged touches, paths, drafts and stage for that person are deleted with it.

A contact a manager adds is theirs. It is never added to the shared allocator list, never shown to another manager, and never researched unless that manager asks us to build a dossier on the person. It has no path into the shared research.

That request is the one thing a manager adds that we read, because acting on it is what it asks: it reaches us with the note and the person's name, title, organisation and LinkedIn page — enough to research the public record. Never the email address or the notes the manager keeps on them.

A manager can save an allocator's contact from their page, as a file for an address book or a CRM. It holds only what the page shows: the person's name, title and organisation, the public route their organisation publishes, their LinkedIn page and a link back to the profile. To count the weekly allowance, we record whom the manager saved and when, in their own account, readable by that account only.

We send no email on anyone's behalf. A draft is text the manager sends from their own email, or does not: the site can open a new message in the manager's own mail with the note filled in, and the manager presses Send. We do not connect to anyone's inbox, calendar or contacts, and we hold no access to any mailbox. We do not track opens, clicks or replies.

If a manager chooses, the messages they send this way carry one hidden copy address of theirs, so the site can record that a note was sent. From that copy we keep the person it went to, the time, and which suggested note it was, and only when it went to a published address on a profile here; anything else is discarded unread. We delete the text unless the manager chooses to keep it with their path, and we keep the record for no more than 24 months. Replies never come to us. The manager can turn this off, or replace the address, at any time. This record is not a manager's books-and-records archive.

We take no money from event organizers: no fees, sponsorships, paid listings or referral payments. Organizers cannot list or change events. We do not register anyone for an event, book meetings or contact speakers.

Anyone can apply for access at /apply. The application asks for your name, work email, firm and role; the firm's website; whether you are a fund manager, an investment advisor or launching a firm; its registration and CRD or SEC number; a short description of your strategy; the vehicles you use; your stage and a broad band for assets under management; and, if you choose, how you heard about us. With it we record when it arrived, the tag on the link that brought you, if there was one, and the IP address it came from, which we use only to stop abuse. It asks nothing about personal characteristics, and nothing of the kind is ever considered.

Applications are stored in the database and readable only by AllocatorConnect's administrators: not by members, and not by the site itself once the application is saved. We review an application against our principles using what it says and public records, such as the firm's website and regulatory filings, and may use Anthropic's Claude models to help us do it. Every decision is made by a person. The form uses Cloudflare Turnstile, as the sign-in page does (below).

If we decline an application, we delete it 12 months after the decision. We keep only a one-line record that it was declined, so that we recognise the firm if it applies again.

Access is by invitation. Signing in creates an account; reading anything additionally requires that account to be on an access list we maintain by hand. Sign-in is by a link sent to your email address; we store no passwords. Data is held on Supabase in the European Union (Ireland) and the site is served by Vercel. To stop scripts from asking for sign-in links, the sign-in page uses Cloudflare Turnstile. Its check runs in your browser and sends Cloudflare your IP address and technical details of your browser and connection, which Cloudflare states it uses only to tell people from bots.