Security & Vulnerability Disclosure Policy
This page describes the security measures Valkiria actually uses and how to report a vulnerability to support@valkiria.pro with subject ‘Security’. We welcome good-faith research and will not pursue researchers who follow this policy. We do not run a paid bug bounty.
1. Our approach
1.1 We protect customer data with technical and organisational measures appropriate to the risk, as required by Article 32 GDPR. We do not currently hold SOC 2, ISO 27001 or PCI DSS certifications. Card payments are processed by our payment providers; we do not store full card numbers.
2. Measures in place
- Encryption in transit with HTTPS/TLS for the website, app and API.
- Application-level AES-256-GCM encryption for selected secrets, including ad account credentials, your own AI provider keys and guest portal links.
- API keys and one-time sign-in tokens stored only as hashes.
- Optional two-factor authentication with an authenticator app (TOTP), also enforced for social sign-in when enabled.
- OAuth 2.1 with PKCE (S256) for third-party apps, rotating refresh tokens and revocation.
- Rate limits on authentication, API, checkout and support endpoints.
- Approval rules that require a person for deletions, new spend and irreversible changes in ad accounts.
- Error monitoring with redaction of advertising platform data, and regular database backups.
- Account deletion and data export functions; see /legal/data-retention.
3. Reporting a vulnerability
3.1 Send reports to support@valkiria.pro with the subject ‘Security’. Our contact details are also published at /.well-known/security.txt.
3.2 Please include: the affected URL or endpoint, a description of the issue and its impact, steps to reproduce or a proof of concept, and how we can contact you. English or Slovak is preferred.
3.3 Do not include other people's personal data in your report beyond what is necessary to show the issue.
4. Rules for testing
- Test only with accounts you own or have permission to use.
- Do not access, change or delete other customers' data. If you reach such data, stop and report it.
- Do not degrade the Service: no denial-of-service, load or spam testing.
- Do not make changes in connected advertising accounts that cause real spend.
- Give us reasonable time to fix the issue before any public disclosure, and coordinate disclosure with us.
5. Scope
5.1 In scope: valkiria.pro, sys.valkiria.pro, the public API v1, the MCP server and OAuth endpoints, and our messenger bots.
5.2 Out of scope: third-party platforms we integrate with (report to them directly), customer-owned custom domains and content, social engineering of our staff or customers, physical attacks, findings from automated scanners without a demonstrated impact, missing best-practice headers without an exploit, and issues requiring a compromised device.
6. Safe harbour
6.1 If you act in good faith and follow this policy, we will consider your research authorised, will not take legal action against you and will not report you to authorities for it. This does not bind third parties or authorities acting on their own initiative.
7. What happens next
7.1 We aim to acknowledge reports within five business days, to give an initial assessment within ten business days, and to keep you informed until the issue is resolved. These are aims, not guarantees.
7.2 We do not run a paid bug bounty programme. With your consent, we are happy to credit you publicly once the issue is fixed.
8. Customer responsibilities
8.1 Use strong, unique passwords, enable two-factor authentication, limit team access to what is needed, and keep API keys secret. Report suspected account compromise to support@valkiria.pro with subject ‘Security’.