Skip to content
Brokers

What about client confidentiality?

Quick answer

Each broker partner has an isolated tenant — you see only CAPE filings assigned to your Filer Code. Tenant isolation is enforced at the database layer with role-scoped access and audit logging. No cross-broker visibility, no aggregated client lists, and the partnership agreement bars Tariffi from soliciting your clients for customs brokerage services.

Detailed Answer

Client confidentiality is enforced at three layers: contractual, architectural, and operational.

Contractual protections:

  • The Broker Partnership Agreement explicitly bars Tariffi from initiating customs-brokerage services with any importer you referred.
  • Tariffi commits to referring any inbound customs-brokerage inquiries from your clients back to you.
  • Standard NDA provisions cover all client data shared through the platform.

Architectural protections:

  • Tenant isolation at the database layer. Each broker partner operates in a separate database tenant. Your queries only return data associated with your Filer Code — there is no "all brokers" view accessible to any partner.
  • Role-scoped access. Database access is restricted by role. Broker accounts can only access entries assigned to their filer code. Even Tariffi's internal admin tools enforce broker-tenant boundaries in every query.
  • Audit logging. Every data access event is logged per 19 CFR Part 163 retention requirements (7 years). If you ever need to verify that your client data was not accessed by unauthorized parties, the audit trail is available.

Operational protections:

  • Tariffi's support team cannot access your tenant data without a logged, reason-attributed support request.
  • No client data is used for marketing, aggregated analytics, or cross-selling to other broker partners.
  • Data retention follows 19 CFR Part 163 requirements — 7 years from the date of the relevant entry, then purged.

What other brokers see: Nothing. Other broker partners on the platform have zero visibility into your client list, your filing volume, your fee arrangements, or any data associated with your Filer Code. The isolation is not just access-control — it is structural. Each tenant's data lives in separate database rows with enforced foreign-key constraints that prevent cross-tenant joins.

Related Questions

Need help?

Upload your ES-003 to see how much you could recover, or talk to our team.