Security

Workshop, client, and production data - handled with the care the work deserves.

Bmfurn is a production tool for a workshop's most operational data - what things cost, who ordered what, when it will be ready. This page describes how that data is stored, protected, and scoped, in plain workshop language.

Encryption in transit and at rest

All traffic between the workshop's browsers or workshop-floor tablets and Bmfurn runs over TLS 1.2+. Order records, cost tables, vendor ledgers and attachments are stored encrypted at rest using AES-256.

Data scope - only what the engine needs

Bmfurn stores order specs, cost breakdowns, schedules, build stages, and vendor / material ledgers. Customer-facing status shares only coarse stage information - never internal capacity, other orders, or cost data.

Retention and deletion

Live order data is retained for the life of the account. Archived orders are retained for historical labor and rate analytics that improve future quotes; the workshop can request purge on written request and the record is expunged from live and backup systems within 30 days.

Role-based access

Manufacturer tier accounts scope views by role - owner, production manager, sales, and floor lead. Cost margins and vendor rates stay privileged to owner and production roles by default.

Access, audit and account controls

Every meaningful change - stage updates, cost overrides, schedule shifts - is logged with the user, timestamp, and prior value. Account owners can rotate access, revoke sessions and export the audit ledger.

Vendor and subprocessor discipline

Bmfurn uses a small, deliberate set of infrastructure subprocessors for hosting, mail delivery and analytics. The list is kept current and available to enterprise accounts on request.

Posture at a glance

Current, stated honestly.

Everything below reflects Bmfurn's current operational posture. Nothing is overclaimed - certifications will be added here only when independently held.

TLS 1.2+ for all traffic

Enforced end to end. HTTP is redirected and not accepted.

AES-256 at rest

Applies to primary data stores and encrypted backups.

Least-privilege internal access

Internal admin access to workshop data is limited, logged and used only for support with the workshop's knowledge.

No secondary-use of workshop data

Workshop cost, order, and vendor data is never sold or used to train shared models.

Security questions?

A workshop's data is worth a direct answer.

If you need a written security summary, subprocessor list, or a review call before an onboarding, contact us and we'll walk you through it.