Uniqus
Uniqus Exchange
Invitation only
Last updated 2026-04-22

Trust & the conflict-free covenant.

Uniqus Exchange is where CAEs, Controllers, CFOs, and AC Chairs can ask the questions they cannot ask their auditor. That only works if the platform is demonstrably conflict-free, anonymity is structurally protected, and no Uniqus partner is using it as a sales channel. This page makes each of those commitments explicit, and tells you how to verify them.

1

Conflict-free by design

No audit practice · no opinion conflict

Uniqus Consultech does not operate an audit practice. We do not issue audit opinions, we do not compete with your auditor for the audit mandate, and we have no economic reason to influence how you answer a technical question. You can bring the question you cannot bring to your auditor — we have no opinion to protect and no mandate to win.

This is different from “conflict-managed.” It is structural: the firm’s services are advisory (accounting advisory, risk & governance, ESG, deal advisory, digital finance transformation, and GREP research). Audit is simply not a line of business.

Verification: our services and leadership are public at uniqus.com. Any change to that posture would be published there and here before it took effect.

2

Anonymity, structurally

Partner-only identity access · peer views are anonymous

Every member picks an anonymous handle at onboarding. Inside any Circle, peers see only your handle, your persona (e.g. “CAE”, “Controller”), and your broad home jurisdiction. They do not see your name, your employer, your email, or any company-identifying details unless you choose to reveal them in a post.

Only Uniqus partners — the small number of humans responsible for moderation, specialist responses, and member approvals — can see real identities. Partners are bound by engagement-quality confidentiality obligations and by the covenant in section 4 below.

The Chatham House rule applies to every Circle: discussions may be referenced, specifics may not be attributed. We enforce this by making attribution technically difficult, not merely policy-prohibited.

3

Data, residency, retention

What we store, where, and for how long
  • Where:Supabase (Postgres) hosted in AWS us-east-1. We do not replicate member content outside this region without written consent. Anthropic Claude is the sole model provider; prompts and responses are processed under Anthropic’s zero-retention enterprise terms.
  • What: your handle, persona, home jurisdiction, Circle memberships, thread/reply/Ask/consult content you create, and audit metadata (who vouched, who approved, who moderated). Real identity is stored once on the members row and not joined into the public-facing tables.
  • Retention: content you author persists while your account is active. On account deletion (see profile → delete account) your identity is purged within 7 days; your anonymous posts are reattributed to “[former member]” rather than deleted, so peer conversations are not broken.
  • Audit events: partner actions (approvals, suspensions, Desk handoffs) are logged with actor + timestamp and retained for 24 months for regulator-review purposes. Member-to-member content is not in this log.

Full details in the Privacy Policy and Terms of Service.

4

The no-BD covenant

What every Uniqus partner signs before they get access
Covenant language
  1. I will not use Uniqus Exchange as a channel for business-development outreach. I will not pitch engagements, send follow-up “let’s grab coffee” messages, or otherwise route platform conversations toward Uniqus services.
  2. I will treat identities I see as a partner as confidential. I will not introduce members to each other, to Uniqus partners, or to third parties without explicit member consent.
  3. I will respond to Uniqus Desk handoffs on their merits, not on the commercial value of the asker’s organisation. The Desk queue is first-in-first-out by SLA, not by prospect priority.
  4. I understand that a substantiated breach of this covenant — pitching, outreach, or identity sharing — results in loss of partner access and is reported to the Uniqus managing partner for follow-up under our engagement-conduct standards.
  5. I will support the anonymity architecture. I will not build workflows, dashboards, or exports that re-identify members, and I will flag to the engineering lead any design choice that risks doing so.
Partners who have signed (0)
The founding-cohort partners are completing covenant onboarding this sprint. Signatures will be listed here as they are recorded, so members can verify who is bound before engaging.

If something feels off

If you experience BD outreach, a re-identification attempt, or any behaviour that contradicts the covenant above, please email trust@uniqus.com. The inbox is monitored by the managing partner and is outside the Exchange moderator chain, so reports are independent of the partners you might be reporting.

You can also download an account export (profile, threads, replies) from your profile page at any time, and request permanent deletion from the same page.