Harmont

Security

Last updated: July 2, 2026

Security is a core consideration throughout how Harmont Intelligence LLC builds and operates Pricing Beacon, Carmel Go, and its own systems, since our customers trust us with sensitive operational data.

1. Pricing Beacon — dedicated instance per organization

Pricing Beacon is deployed as a dedicated instance for each customer organization. Your data lives in its own database, on its own infrastructure, and is never shared with any other tenant. Every price entry, structural change, and period closure is logged permanently, so the process stays auditable and independent of any one individual. A Data Processing Addendum (DPA) is available on request for customers with their own procurement/compliance review.

2. Infrastructure

3. Access control

4. Third-party processors

We rely on established infrastructure and AI providers (see the Privacy Policy for the current list) for hosting, and to process calls and messages handled by Guta. We select providers based on their own security practices and only send them the data necessary to perform their function.

5. Carmel Go

Carmel Go's courier-dispatch and messaging infrastructure is documented in its own Privacy Policy. At the Harmont Intelligence LLC level, note only that it follows the same access-control and third-party-processor principles described above.

6. Operational security

7. Responsible disclosure

If you believe you've discovered a security issue in any Harmont-operated system, please contact security@harmont.io. We appreciate responsible disclosure and will investigate all legitimate reports before any public discussion of the issue.

8. Changes

We may update this page from time to time. Material changes will be reflected here with an updated "Last updated" date.