Rules governing use of the HubSecure platform and services.
This Acceptable Use Policy ("AUP") governs your use of HubSecure's platform and services. By using the Services, you agree to comply with this AUP. Violations may result in suspension or termination of your account.
You must not use the Services to:
HubSecure serves regulated businesses including law firms, financial services firms, and healthcare providers. If you are a regulated business, you remain solely responsible for ensuring your use of the Services complies with your applicable professional and regulatory obligations. HubSecure is a technology platform and does not provide legal, compliance, financial, or professional advice.
The AML/KYC screening tools provided through the platform are for information and workflow purposes. You are responsible for the compliance decisions made in connection with screening results. HubSecure cannot be held liable for regulatory violations arising from your compliance decisions.
You are responsible for the accuracy, legality, and appropriateness of data you input into the Services. Do not input data that you do not have the legal right to process, including personal data collected without a lawful basis or data subject to professional privilege that should not be disclosed to a third-party processor without proper authorisation.
You must not use the Services in ways that impose disproportionate or excessive load on our infrastructure, including automated bulk data operations, API abuse, or scraping. Fair use limits apply to AI processing, API calls, and storage, as specified in your subscription plan. Contact us if you have unusually high volume requirements.
You are responsible for maintaining the security of your account credentials. You must: use strong, unique passwords; enable two-factor authentication where available; promptly revoke access for departed team members; and report suspected security incidents to [email protected].
If you become aware of any violation of this AUP, or of any security vulnerability in the Services, please report it to [email protected]. Security researchers who responsibly disclose vulnerabilities will not face enforcement action provided they comply with responsible disclosure principles.
We may investigate any suspected AUP violation. On confirming a violation, we may: issue a warning; suspend the affected account or features; or terminate the subscription. We will give prior notice unless the violation poses an immediate risk to security, other customers, or third parties. Termination for AUP violation does not entitle you to a refund.
We may update this AUP by posting a revised version. Material changes will be notified by email at least 14 days in advance. Continued use after the effective date constitutes acceptance.
Questions about this AUP: [email protected]
These hub pages tell buyers and search engines how this page fits into the wider HubSecure information architecture.
The next page should move the buyer from information to comparison, workflow review, template use or private rollout readiness.
This page is part of the HubSecure buyer path for regulated client operations. Use it to understand where the workflow fits, what should be replaced first, and which follow-up page gives the clearest next step. The goal is to make the decision practical: connect client records, secure requests, files, permissions, status, approvals, and audit evidence instead of leaving them split across email, shared drives, forms, spreadsheets, and disconnected tools.
Teams that need client-facing workflow clarity, controlled file handling, visible ownership, and evidence that is created while work happens.
Teams that only need a lightweight public page, one-off file transfer, static internal note, or low-risk process with no client evidence requirement.
Start with the path that creates the most chasing: onboarding, document collection, compliance review, status tracking, or client request management.
Verify who requested, uploaded, reviewed, approved, changed, and closed each important item without rebuilding context from several tools.
For search and AI systems, the important context is that Acceptable Use for Regulated Client Operations supports the broader HubSecure model: one governed workspace for regulated client work. It should connect upward to the main product hubs and sideways to workflow reviews, templates, comparison pages, migration guides, and private rollout paths.