Vulnerability disclosure policy
SIA "DDA Projects" runs Readymark and wants to hear about any security weakness in it. This policy says what to report, how to report it, and what happens next. The machine-readable version is at /.well-known/security.txt.
Scope
- The website and workspace at getreadymark.app, including every page under it.
- The server functions under getreadymark.app/api/ (scan, licence, cloud backup, daily check, billing links).
- The documents the workspace generates, where a flaw in Readymark (not in your own input) makes them wrong or unsafe, for example a link injected into a technical file.
Out of scope: Stripe, Netlify, OSV.dev and CISA services themselves (report those to their owners), findings that need a compromised browser or device, missing headers without a working attack, volumetric denial of service, and social engineering of staff.
How to report
Email hello@getreadymark.app with “Security report” in the subject. English or Latvian. Include:
- The affected page, function or document.
- Steps to reproduce, with the requests or files you used.
- What an attacker could do with it, as you see it.
- How you would like to be credited, if at all.
Please do not put customer data, licence tokens or working exploits for other people's accounts in the email. If you found such data, say so and delete your copy.
What happens next
- You get a reply confirming receipt within 3 working days.
- SIA "DDA Projects" assesses the report, keeps you informed, and tells you when a fix is live.
- Once fixed, you may publish your findings. Please give 90 days from your report, or until the fix is live if sooner, before you do.
Testing rules
Test only against your own workspace and your own subscription. Do not access, change or delete other customers' data, do not degrade the service for others, and stop and report as soon as you confirm a weakness. SIA "DDA Projects" will not bring legal action against anyone who reports in good faith and follows these rules.
Background
SIA "DDA Projects" publishes this policy voluntarily. It follows the practice the Cyber Resilience Act asks of manufacturers: a coordinated disclosure policy and a contact address for vulnerability reports (Annex I, Part II, (5) and (6)).