Your customers' drawings, handled with care.

Inspection data is stored in a PostgreSQL database and files (drawings, models, attachments, CMM output) in private object storage, both hosted by Supabase. The hosting region is configurable per deployment; ask us which region your workspace is in.

The Deburr API runs on Render. Files are never public: every upload and download goes through a short-lived signed link that the API issues only after checking that you belong to the organization and have the right role.

Every record carries its organization ID, and every query is scoped to the organization you're working in. Live updates in the browser are protected by Postgres row-level security.

In transit: all traffic between your browser, the API, storage and our providers uses HTTPS (TLS).

At rest: the database, file storage and backups are encrypted at rest by our hosting provider.

To read a drawing, Deburr sends the drawing image and its text to an AI model provider. Copilot messages are sent the same way. We use API terms where providers don't train on your data.

We don't use your drawings to build training or test sets without your written permission. Ask us which AI provider your workspace uses and we'll tell you.

The AI suggests; people decide. Uncertain reads are flagged for review, and the copilot can't sign, approve or delete anything. Those actions always need a person to click.

Each person in your organization has a role: owner, admin, approver, inspector or viewer. The API checks membership and role on every request, not just in the interface.

You can require an independent approver, so nobody approves their own first article. Approved reports are locked until someone with the right role reopens them, and the reopening is logged.

When you share a report with a customer, the link is read-only, expires, and can be revoked.

Every reading, edit, comment and signature is written to an append-only event log. The database refuses edits and deletes on it, and each entry includes a hash of the one before it, so any tampering breaks the chain. Deburr can re-walk the chain to verify it.

E-signatures require re-authentication. The signer re-enters their password (or a fresh one-time code) at the moment of signing. Each signature records the signer's name, its meaning (prepared or approved), the time, IP address, browser, and a SHA-256 hash of the report content as signed.

ITAR and CUI work is available as an add-on at added cost. It runs in a separate, access-controlled workspace, priced on top of your plan. Ask us for a quote and the details.

The standard workspace is for commercial work. On upload, we scan each drawing for export-control markings such as ITAR, EAR99, "export controlled", CUI and USML references. If one is found, the upload is blocked and the stored file is deleted, and we point you to the ITAR add-on.

This scan is a safety net, not a guarantee: it can only catch drawings that are marked. Keep controlled technical data out of the standard workspace.

Files: ask us to delete specific drawings or files and we will. Admins can also delete first articles in the app.

Your whole organization: the owner can delete the organization from settings in one click. That permanently removes its database records and stored files. An active subscription has to be cancelled first.

Copies in our hosting provider's encrypted backups expire on the provider's backup schedule.

Card payments are handled by Dodo Payments, our merchant of record. Card numbers never reach Deburr's servers. Annual plans can also be paid by invoice or purchase order.

We're a young company and we'd rather say so than imply otherwise. We don't hold a SOC 2 report or ISO 27001 certificate today. SOC 2 is on our roadmap. In the meantime we're happy to fill in your security questionnaire and get on a call with your IT team.

Found a vulnerability? Email hello@getdeburr.com with "Security report" in the subject. We'll reply quickly and credit you if you'd like.