Skip to content
Bobby Directory
Inspect a file

Catalogue

Catalogue listing information

What a Bobby Directory catalogue listing may show, where that information comes from, who reviewed it, and how to have it corrected or removed. The public catalogue is not active: no listing is currently served to anyone.

Working draftNot legally reviewed

Current status

The public catalogue is inactive. Every public catalogue address returns the same neutral not-found answer, no listing is served, no listing is searchable, no listing appears in a sitemap and no structured data is emitted. This page describes what would become public if and when the Platform Owner activates the catalogue.

Nothing on this page is a statement that activation has happened or is scheduled.

What may become public

A catalogue listing is a narrow, approved summary of a record that a workspace owns. It is a discovery listing, not a hosted page. It may show the listed website's public display name, a short description, the canonical public web address, the domain, a short product or category classification, the primary language, the Bobby Directory category the listing was placed in, and the listing's own Bobby Directory address.

The exact field set is decided by the Platform Owner and applied through a schema version. No field becomes public because a workspace wanted it to; a field becomes public only when it is marked publicly eligible in the active schema version and the listing that carries it has been separately approved.

A listing offers no page builder, no custom script, no embedded HTML, no customer tracking, no custom hosted domain and no workspace management control.

What stays private

Contact email addresses and contact routes, internal notes, street addresses, building or unit details, postal codes, coordinates, provider metadata, credentials, audit data, operator identity, internal identifiers, moderation notes, private media and any field whose public purpose is uncertain are all excluded by default and are not projected.

Exclusion is enforced by the server. A field that has not been made publicly eligible is not withheld by the interface; it is never sent.

Where the information comes from

Every value in a listing originates from the workspace that owns the record. The workspace enters or imports it, and the workspace remains its source and its owner. Bobby Directory does not author listing content and does not enrich it from a third-party provider: no external enrichment provider is active.

Bobby Directory records which workspace submitted a listing, which version was submitted, who reviewed it and when. That history is internal and is not published.

Moderation and separation of duties

A listing reaches the catalogue through two separate approvals. The workspace approves its own content, and Bobby Directory separately approves the listing for the catalogue. The same person cannot perform both roles on the same record: the server refuses a platform decision taken by the account that submitted it, and it refuses a workspace operator attempting to act as a platform reviewer.

Approval is not identity verification. It is not an audit of the listed website, not a security assessment and not an endorsement.

No unsupported claims

Bobby Directory makes no verification claim about any listing. No verification provider is connected, so no verification badge, score, trust signal, rating, review or endorsement is displayed anywhere, and none may be inferred from a listing's presence.

No provider, enrichment, AI or payment claim is made either. Those capabilities are switched off. If one is ever switched on, this page will say so before it is used on a public listing.

Requesting a correction

If a listing about you or your organisation is inaccurate, write to the contact route below with the listing address and what is wrong. Corrections to listing content are made by the workspace that owns the record, because that workspace is the source; Bobby Directory will route the request and will withdraw the listing in the meantime if the inaccuracy is material.

A correction is applied by re-submitting the corrected version for approval. The previous approved version is retained internally so a change can be reviewed and reversed.

Requesting removal and immediate unpublish

You may ask for a listing to be removed. Bobby Directory can unpublish a listing immediately, without waiting for the owning workspace, using a governed platform command. Unpublishing takes effect on the next request: public catalogue responses are served with no-store, no-cache directives, and unpublishing also rotates the record's cache tag so any intermediary copy keyed to the previous tag is no longer addressable.

There is also an emergency catalogue kill switch. It disables every catalogue switch, unpublishes every published directory and entry, and rotates every cache tag in a single operation.

Removal from Bobby Directory does not remove anything from the listed website itself, which Bobby Directory does not operate, and it does not remove copies already retained by third-party search engines or archives. Those are outside Bobby Directory's control and must be pursued with the third party.

Retention

Retention of pilot records follows the platform retention policy recorded for the pilot. Unpublishing a listing removes it from public resolution; the workspace's own record and the internal moderation history are retained under that policy so that a decision can be audited and reversed.

A purge request removes the underlying record itself and is a separate, governed operation.

Contact route

Use the contact route published on the Bobby Directory contact page. Correction and removal requests are handled there and are recorded. Please include the exact listing address so the request can be matched to a record without guesswork.