SmartForms Security & Trust

Last Updated: September 2026

1. Security by Design

SmartForms uses a shared multi-tenant architecture with tenant-scoped configuration and routing.

2. Tenant Isolation

  • tenant-scoped configuration;
  • unique workspace and domain routing;
  • isolated destination references;
  • no intentional cross-customer data access.

3. Access and Secrets

Connector credentials and secrets are handled server-side and should not be exposed in client-visible configuration.

4. Data Minimization

SmartForms distinguishes platform and configuration data needed to operate the service from Customer submission data. Customer submission data is designed not to be permanently stored by default and may be processed transiently as necessary to provide the configured service.

5. Secure Delivery

Where supported, integrations should use least-privilege access and scoped permissions.

6. Attachments

Integrity controls may include preserving source bytes, filenames and hashes depending on the configured workflow.

7. Audit & Traceability

SmartForms may include:

  • submission IDs;
  • timestamps;
  • platform, form and configuration versions;
  • approved technical evidence.

8. Platform Updates

Duxni Tech maintains and updates the shared platform for functionality and security.

9. Customer Responsibilities

Customers remain responsible for:

  • their accounts;
  • endpoints;
  • identity providers;
  • DNS;
  • repositories;
  • licenses;
  • permissions;
  • user access;
  • their own environment security.

10. Compliance

SmartForms may be configured to support Customer security, privacy and compliance requirements depending on the plan, use case, agreements and Customer environment. Specific regulatory or contractual requirements must be evaluated separately.

11. Reporting security concerns

Security concerns may be reported to security@duxni.com.