Daasity Vulnerability Disclosure Policy

October 30, 2026

Daasity welcomes reports of security vulnerabilities from researchers, customers and partners, and commits to acknowledging every report within 3 days. This policy replaces the 2020 Daasity Vulnerability Disclosure.

Scope

In scope: any service operated by Daasity, including:

  • The Daasity platform at app.daasity.com and api.daasity.com
  • Daasity integrations and apps listed in partner marketplaces, including the Shopify App Store
  • Other daasity.com hosts and Daasity-owned public code

Out of scope:

  • Third-party services we use or integrate with (for example Shopify, Snowflake, Looker or AWS). Report those to the vendor.
  • Denial-of-service and load testing, spam, and social engineering or phishing of Daasity staff or customers
  • Physical attacks on offices or data centres
  • Findings with no security impact, such as missing headers on static pages or self-XSS

How to report

Email security@daasity.com. The same address is published in our security.txt.

Please include:

  • The affected host, URL, endpoint or app
  • Steps to reproduce, with any proof-of-concept code or screenshots
  • The impact you believe the issue has
  • How we can reach you, and whether you want to be credited

Please report in English. Do not include customer data you may have accessed; describe it instead.

Our commitments

When you report a vulnerability to us in good faith, we will:

  1. Acknowledge your report within 3 days.
  2. Confirm whether the issue is valid and give it a severity within 5 business days.
  3. Update you at least every 14 days until the issue is fixed, and tell you when it is.
  4. Fix confirmed issues within the remediation timelines below.

Remediation timelines

We rate severity with CVSS v3.1, adjusted for real exposure in our environment. Timelines run from the day we confirm the issue. They match our Vulnerability Management Policy and Incident Response Plan.

SeverityCVSS v3.1 scoreFixed or mitigated within
Critical9.0 – 10.03 days
High7.0 – 8.930 days
Medium4.0 – 6.960 days
Low0.1 – 3.990 days

If a fix needs a third party and cannot meet its timeline, we put a mitigation in place within the timeline and tell you the new date.

Testing guidelines

While researching, please:

  • Test only against accounts you own or have permission to use
  • Stop as soon as you reach data that isn't yours, and don't keep, copy or share it
  • Not degrade our service: no denial-of-service, heavy automated scanning or brute force
  • Not change or delete data, or keep access beyond what is needed to show the issue
  • Not tell anyone else about the issue until it is fixed

Safe harbour

If you follow this policy, we will treat your research as authorised. We will not take legal action against you or report you to law enforcement for it, provided that you:

  • Test without harming Daasity, our customers, employees or third parties
  • Do not use or alter any data you access during your research
  • Do not carry out social engineering, spam or phishing
  • Do not test the physical security of any Daasity or third-party property
  • Do not carry out denial-of-service or resource-exhaustion attacks
  • Comply with applicable criminal laws, and with other applicable laws except those whose breach would result only in claims by Daasity

If a third party takes action against you over research that followed this policy, we will make it known that you acted under it. Daasity reserves all of its legal rights if this policy is not followed.

If you are unsure whether something is allowed, ask us at security@daasity.com before you test.

Public disclosure and credit

Please do not disclose the issue publicly until it is fixed. We will agree the details of any disclosure with you. With your permission, we will credit you by name once the fix is out. We do not run a paid bug bounty.