What we hold, and why we hold it

1. Who this covers

MetaOpus is a business-to-business platform. Our customer is the organisation that subscribes to it. Most of the personal data in the platform is not our customer's — it belongs to the consultants, contacts and companies our customer works with — so for that data our customer decides what is collected and why, and we process it on their instructions. Where we decide, such as the accounts of the people who sign in to administer the platform, we are responsible for it directly.

2. Where opportunity data comes from

A central function of MetaOpus is bringing requirements together from the places they are published or sent. Those are:

• Public applicant-tracking APIs — the job boards employers publish through, such as Greenhouse, Lever, Ashby and Workday. These are public endpoints intended for syndication.
• Licensed aggregators — services that syndicate postings under their own terms.
• Mailboxes the customer connects — vendor requirement mail, read over IMAP from a mailbox or label the customer nominates, with credentials they supply.
• Chat exports and inbound webhooks — group messages the customer exports and uploads, or relays from a bridge they operate.
• Records the customer enters — requirements typed or imported directly.

Each source carries its own terms, reviewed before it is enabled, and a retention period after which its postings are removed. We do not circumvent access controls, and we do not collect from a source whose terms forbid it.

3. What the platform holds

• Requirement records — title, description, company, location, rate and engagement terms where stated, and the source it arrived from.
• Consultant records — the profiles our customer maintains: name, contact details, skills, work authorization, availability, rates, and resumes and supporting documents they upload.
• Company and contact records — the vendors, partners and clients our customer deals with, and the people at them they correspond with.
• Activity — submissions, interviews, offers, placements, messages sent through the platform, and the outcomes recorded against them.
• Account and usage data — sign-in records, actions taken, and metered usage.

4. Automated processing

MetaOpus classifies requirements, extracts stated terms, and scores how well a consultant matches a requirement. Two things about this are deliberate and worth stating plainly.

Where a fact is not stated, the platform records that it is unknown rather than guessing it. A requirement that does not state corp-to-corp terms is marked unstated, not assumed.

A match score is a ranking aid shown with its reasons, not a decision. The platform does not reject a person, and no submission leaves it without somebody choosing to send it.

5. Who can see what

Every record belongs to one customer, and that boundary is applied when data is read rather than when it is displayed. A customer sees the shared corpus of requirements only through the sources they have been granted.

Within a customer, access is governed by permissions their administrator assigns. Sensitive fields — rates, margins, costs — are removed from the response for anybody without the permission to see them, so they are absent from screens, exports and reports rather than hidden in them.

6. Sharing

We do not sell personal data, and we do not share it between customers. Data leaves the platform in three circumstances: when our customer sends it, such as a submission to a vendor; to service providers that operate the platform under contract, such as hosting, email delivery and document storage; and where the law requires it.

7. AI assistants

When a customer turns it on, a person may connect an AI assistant — such as Claude, ChatGPT, Gemini or Microsoft Copilot — to MetaOpus through the Model Context Protocol. The assistant signs in as that person and can only read what that person can already see; it cannot change, send or spend anything.

• What MetaOpus receives: the tool the assistant calls and its arguments, such as a search. MetaOpus does not receive the person's conversation with the assistant.
• What MetaOpus returns: the answer to that call, within the person's access. Contact details, consultants' contact details and resume text, where requirements come from, and margins are never returned.
• Where it goes: to the assistant's provider, under the person's own account and that provider's terms. MetaOpus does not control how long the provider keeps it.
• What MetaOpus keeps: a record of each call — who, when, which tool, a summary of the arguments with free text reduced to its length, and how many rows were returned — in the customer's audit log, kept as audit records are (section 8); and each connection, with when it was made, last used and ended.
• Ending it: the person can disconnect any assistant from their AI assistants page, and the customer's administrator can end any connection or turn the feature off. Either takes effect at the assistant's next request.

8. Retention

Requirement records are removed according to the retention period set on the source they came from. Consultant, company and activity records are kept while our customer's account is active and for the period they configure. Audit records are kept longer by design — their value is answering questions about the past — and are removed on a schedule agreed with the customer. On termination we delete or return customer data on request.

9. Security

These are practices the platform implements, described so they can be checked:

• Data in transit is encrypted. Data at rest is encrypted by our hosting and storage providers.
• Tenant isolation is enforced in the query, not in the interface.
• Access is role-based, composed from individual permissions, with sensitive fields separately gated.
• Sessions are bound to the device they were issued to; multi-factor authentication is available and can be required for privileged actions.
• Uploads are typed from their contents rather than their filename, and scanned where a scanner is configured.
• Outbound requests are guarded against being directed at internal addresses.
• Sensitive actions are written to a tamper-evident audit trail, each entry chained to the one before it.

We do not currently hold SOC 2, ISO 27001 or any equivalent certification, and we do not claim one. If you need evidence for a security review, write to us and we will describe what we do and do not have.

10. Your rights

Depending on where you live, you may have the right to ask what data is held about you, to correct it, to have it deleted, or to object to how it is used. Where the data is our customer's, they decide, and we will pass your request to them and support them in answering it. Where it is ours, write to hello@metaopus.ai and we will respond.

If you are a consultant and did not know your details were in MetaOpus, they were most likely provided by a staffing firm you have dealt with. Tell us and we will identify the customer and put your request to them.

11. International transfers

The platform is operated from the United States, and data may be processed there. Where data originates elsewhere, transfers rely on the safeguards available to us under the applicable law.

12. Changes

We will update this document as the platform changes and revise the date at the top. A change that materially affects how personal data is used will be notified to the affected customer before it takes effect.

13. Contact

MetaOpus, 2800 Regal Rd, Plano, TX 75075. hello@metaopus.ai · +1 (469) 715-8680