Trust & Security Center
Security standards for everything we build and operate.
This page describes the controls applied across Exobean LLP consulting engagements and commercial software platforms, the isolation model of each product, our sub-processors and how to report a vulnerability.
Secure development lifecycle
Corporate SDLC and consulting security standards
Threat modelling before build
Every system and every product release starts with a written threat model covering trust boundaries, data flows and abuse cases.
Peer review and automated checks
All code is reviewed by a second engineer. Static analysis, dependency auditing and secret scanning run on every change.
Least-privilege platform scopes
Marketplace applications declare the minimum scopes required and never request customer, order or payment access unless the function demands it.
Encryption in transit and at rest
TLS 1.2 or higher on every connection. Stored secrets and access tokens are encrypted with managed keys; platform-hosted storage inherits the platform's encryption.
Logging without personal data
Operational logs contain identifiers and events, not personal data or secrets, and are retained for a bounded period.
Incident response
Security incidents are triaged within one business day, contained, and reported to affected customers without undue delay and within applicable statutory windows.
In consulting engagements these standards are applied to client codebases and infrastructure as part of delivery. Clients receive the threat model, the dependency audit and a written security summary as deliverables, and may request that Exobean engineers work within the client's own identity, repository and secrets management.
Product isolation matrix
How each platform isolates and protects customer data
| Platform | Compute | Storage | Egress | Tenant isolation | Deletion |
|---|---|---|---|---|---|
| SLACredit Atlassian | All application compute executes on Atlassian Forge functions inside Atlassian Cloud. | Forge SQL and Forge Key-Value Storage provisioned for the installing Atlassian site. | None. The application has no egress permissions and makes no calls to Exobean LLP infrastructure. | Contract, ledger and waiver data persist exclusively in Forge SQL and Forge Key-Value Storage within the customer tenant region. | Uninstalling the application triggers Atlassian-managed deletion of Forge storage. Administrators may request confirmation via privacy@exobean.com. |
| DimGuard Shopify | All catalog reads and writes use the Shopify GraphQL Admin API, version 2027-01, under minimal declared access scopes. | Encrypted application database operated by Exobean LLP on cloud infrastructure, partitioned per shop. | Data is exchanged only with the Shopify Admin API for the installed shop. No data is sold or shared with advertising or analytics brokers. | Every record is partitioned by shop domain; no query path can read another merchant's data. | The shop/redact webhook triggers deletion of all shop data within 48 hours of uninstall, in line with Shopify requirements. |
SLACredit: Built natively on Atlassian Forge with zero external data egress
- 01All application compute executes on Atlassian Forge functions inside Atlassian Cloud.
- 02Contract, ledger and waiver data persist exclusively in Forge SQL and Forge Key-Value Storage within the customer tenant region.
- 03The application declares no external fetch permissions. No ticket, SLA or account data leaves Atlassian infrastructure.
- 04Access is governed by Atlassian product permissions and Jira project roles; SLACredit introduces no separate identity store.
- 05Period locks are verified with SHA-256 digests on read so that any divergence between stored and computed state is surfaced.
DimGuard: Built on the Shopify GraphQL Admin API with strict shop-level isolation
- 01All catalog reads and writes use the Shopify GraphQL Admin API, version 2027-01, under minimal declared access scopes.
- 02Every record is partitioned by shop domain; no query path can read another merchant's data.
- 03HTML from product descriptions is parsed in a sanitizing parser and never re-rendered unescaped.
- 04CSV output neutralises leading formula characters and CSV input is validated against a published schema.
- 05The merchant data footprint is minimal: product identifiers, dimension fields, snapshot metadata and audit results. No customer personal data is required for operation.
- 06Mandatory Shopify GDPR webhooks (customers/data_request, customers/redact, shop/redact) are implemented and verified with HMAC signatures.
Encryption and integrity
Standards applied across platforms
- Transport. TLS 1.2 or higher for every browser, API and webhook connection; HSTS on exobean.com.
- At rest. AES-256 or platform-equivalent encryption for application databases and secrets; Forge storage inherits Atlassian encryption.
- Integrity. SHA-256 digests over locked financial periods (SLACredit) and HMAC-verified webhooks (DimGuard).
- Input handling. Sanitizing HTML parsers, CSV formula neutralisation and schema validation before any write.
- Access. Platform identity (Atlassian, Shopify) governs user access. Exobean staff have no standing access to customer tenants.
Sub-processor transparency
Third parties that may process data on our behalf
| Sub-processor | Purpose | Location |
|---|---|---|
| Atlassian Pty Ltd | Hosting, compute and storage for Atlassian Forge applications; Marketplace billing | Customer-selected Atlassian Cloud region |
| Shopify Inc. | Platform APIs, webhooks and billing for Shopify applications | Shopify global infrastructure |
| Cloudflare, Inc. | DNS, edge delivery and hosting of this corporate website | Global edge network |
| Cloud infrastructure provider | Application hosting and encrypted storage for Shopify applications | Region disclosed on request |
Changes to this list are published here before they take effect. Customers with a data processing agreement are notified by email.
Coordinated vulnerability disclosure
Report a security issue
We welcome reports from security researchers and customers. Write to security@exobean.com. A machine-readable policy is published at /.well-known/security.txt.
What to include
Affected product or URL, steps to reproduce, impact assessment and any proof-of-concept. Please do not include customer data.
Our commitment
Acknowledgement within two business days, triage within five, and a remediation timeline agreed with you. We credit researchers who wish to be named.
Safe harbour
Good-faith research that respects this policy, avoids privacy violations and service disruption, and does not access data beyond what is needed to demonstrate the issue will not result in legal action by Exobean LLP.
Out of scope
Denial of service, social engineering, physical attacks, and issues in Atlassian, Shopify or Cloudflare infrastructure, which should be reported to those vendors.