Seldeo, Inc. thanks the security researchers below for reporting vulnerabilities through our coordinated disclosure process and giving us the opportunity to fix them before public discussion.
How to submit a report
Reporting guidance, safe-harbour terms, and response-time targets are published in our canonical security contact file. In short:
- Email: security@seldeo.com
- Canonical file: /.well-known/security.txt
- Acknowledge receipt: within 3 business days.
We currently accept unencrypted reports over TLS-protected email. If you would prefer to encrypt your submission, request a signed PGP public key from security@seldeo.com; we will provide the current key out-of-band and confirm the fingerprint here once the program is generally available. Please do not attach a raw copy of the vulnerability details unencrypted to a follow-up email chain if you have concerns.
Acknowledgement policy
- Attribution is added below with the researcher's consent, as either a real name, a handle, or
Anonymous. - Order is chronological by the date the report was confirmed valid (not by severity).
- Consent to remove: researchers can request that their entry be edited, moved to anonymous, or removed entirely at any time by emailing security@seldeo.com, subject "Acknowledgement update — ".
- What is NOT published: the technical detail of any specific report, the affected surface, the CVSS score, or the fix — those live in our private security incident tracker.
Acknowledged researchers
No public entries yet. Seldeo has not launched its apps to the public store as at the effective date of this page, so no external reports have been received. When the first valid report lands, it will be added here.
Corrections
If you believe your acknowledgement is missing, incorrect, or should be removed, email security@seldeo.com and we will respond within 5 business days.
Related pages
- security.txt — the canonical machine-readable security contact record.
- Safety at Seldeo — the user-facing safety toolkit.
- Transparency at Seldeo — current public disclosures; no report cadence has been announced.
Changes to this page
The version number and effective date at the top of this page are updated on each material change (new acknowledgement, policy tweak, or PGP-key rotation).