Village
Log in

Your data stays yours.

Village is independently audited under SOC 2 Type II, runs each workspace on its own machine, and never trains on your data. Here is how it fits a fund’s security review.

Explore our Trust Center

Independently audited under SOC 2 Type II

An independent auditor has examined Village’s security controls and how they operated over time, not just how they were designed. The report, our security controls, and our subprocessor list are published on the Trust Center for your review.

Request the report

How Village protects your work

  • Never trained on your data

    Village does not use your data to train or improve any AI model, whether its own or a third party’s, and our model providers may process it only to fulfil your requests. Requests reach Anthropic and OpenAI through Village’s own proxy, which meters usage without storing prompts or responses. The commitment is written into our Terms of Service and Privacy Policy.

  • A machine of your own

    Each workspace runs on its own machine, with its own encrypted volume, on its own private network. Your files, data, and agent runs never share a machine with another customer. Access passes through a gateway that checks workspace membership on every request and issues short-lived tokens. Delete the workspace and its machine, storage, and repository are deleted with it.

  • Useful before you share anything

    Village is useful from the first prompt. Agents work from public web sources and the datasets Village provides, so your firm can run a full evaluation without uploading a file or connecting an internal system. Uploads and connections to the data services you license are optional, and you decide if and when to add them. Reviews move faster when the pilot touches nothing internal.

  • Public and licensed sources

    Village’s web collection follows robots.txt, paces its requests to one at a time per site, backs off when a site asks, and never crosses a login. Agents draw on those public pages and on the data services your firm already licenses, and their reports cite where each finding came from, so compliance can trace a claim back to its source.

  • Encrypted at rest and in transit

    Workspace volumes and datastores are encrypted at rest, and every connection runs over TLS, from your browser to the gateway to the model providers. API keys you connect are submitted through a form that keeps them out of the chat transcript and are stored on your workspace’s own machine, never in a shared database.

  • Deployed where you need it

    Institutional customers can request a dedicated deployment, or regional processing for storage and inference, where a mandate requires it. Talk to sales about the region and the timeline you need.

Questions from security reviews

Anything else? Email [email protected]

Does Village train on my data?

No. Village does not use customer data to train or improve any AI model, whether its own or a third party’s, and our model providers may process your data only to fulfil your requests, never for their own training.

Do I have to give Village my firm’s internal data?

No. Agents work from public web sources and the datasets Village provides, so you can evaluate the product end to end without uploading a file or connecting an internal system. Connecting the data services you license is optional and under your control.

Where does my data live?

In your workspace, which runs on its own machine with its own encrypted volume on a private network. Your files, data, and agent runs never share a machine with another customer. Dedicated deployments and regional processing are available to Institutional customers on request.

Who can access my workspace?

Members you invite. Every request to a workspace passes through a gateway that checks membership and issues short-lived tokens, and internal services are never exposed as customer previews.

Which AI models process my requests?

Models from Anthropic and OpenAI, reached only through Village’s proxy. The proxy meters usage without storing prompts or responses, and neither provider may use your data for its own purposes, including training.

How does Village collect data from the web?

Village’s crawler follows robots.txt, makes one request at a time per site with a pause between requests, backs off when a site asks, and never crosses a login. It records evidence of the technology on public pages, not personal data.

How does Village help with MNPI concerns?

Village gathers evidence from public web pages and from the data services your firm already licenses. Agents never log in to a site on your behalf unless you give them access, and their reports cite the source of each finding, so compliance can trace where a claim came from.

What happens to API keys I connect?

Keys are submitted through a form that keeps them out of the chat transcript and are stored on your workspace’s own machine, encrypted at rest. They are used only when agents call that service on your behalf.

What happens when I delete a workspace?

Its machine, storage volume, and repository are deleted with it. Email [email protected] to delete a workspace with billing history, or to exercise data rights under GDPR or CCPA.

Can I get your audit report, subprocessor list, or a DPA?

Yes. Our Trust Center publishes our SOC 2 Type II report, security controls, and subprocessors. A data processing addendum is available to business customers on request.