Privacy policy

The two kinds of data

OpsChisel handles two very different categories, with different roles and rules:

• Your account & contact data - name, work email, sign-in identity (Entra ID), and what you tell us via the contact form. For this we are the data controller.
• Captured message data - the dead-letter messages OpsChisel drains from your Service Bus namespaces on your instruction. These can contain anything your systems put in them, including personal data. For this we are a data processor acting on your behalf; you remain the controller.

Account & contact data

• Sign-in is Entra ID only - we never store passwords.
• We record the identity claims of signed-in users (name, object id, tenant) to enforce access control and to build the audit trail your compliance depends on.
• Contact-form submissions are used to respond to you and to manage early access. No marketing lists without explicit consent.

Captured message data

• Message bodies and properties are stored durably and encrypted at rest and in transit, in Azure (Cosmos DB / Blob Storage), within the service's Azure region.
• Access is scoped to your workspace and governed by your own role assignments - tenant isolation is enforced at the storage partition level.
• Retention follows your plan's retention window; deleting a workspace purges its captured data.
• We do not read, mine, sell or train on your message content. Operational access by our staff is exceptional, logged, and only ever for support you have requested.

Subprocessors

The service runs on Microsoft Azure. Payments are processed by Stripe (self-serve) or the Azure Marketplace - card data never touches OpsChisel.

Your rights

Under the GDPR you can request access, correction, export or deletion of your personal data, and object to processing. Write to hello@opschisel.com - we respond within 30 days.

Contact

OpsChisel · hello@opschisel.com