Help us keep Astrixy safer
We appreciate researchers who take the time to identify and privately report potential security issues. This page explains how to contact us, what information helps us investigate, and the boundaries we ask you to respect while conducting research.
Machine-readable contact details are published at /.well-known/security.txt.
Our approach to disclosure
A useful security report gives our team a clear, reproducible description of a potential issue without putting users or services at risk. We ask researchers to communicate privately first, so we can assess the impact and work toward a fix before details are shared publicly.
If you are unsure whether something is a security vulnerability, you can still send us a concise description. Please avoid collecting more information than is necessary to demonstrate the issue.
What to report
Please report potential vulnerabilities that you reasonably believe affect Astrixy-owned applications or services.
In scope
- www.astrixy.app and astrixy.app, including the merchant dashboard.
- Merchant storefronts hosted on Astrixy subdomains, where you own the store.
- Our public API endpoints and webhook receivers.
- Astrixy mobile applications.
- Authentication, session handling, tenant isolation, entitlement enforcement, and payment orchestration logic.
Out of scope
- Findings from automated scanners without a demonstrated exploit.
- Missing security headers, cookie flags, or TLS configuration with no proven impact.
- Rate limiting on non-authentication endpoints, and self-XSS.
- Clickjacking on pages with no state-changing action; CSRF on logout or other low-impact actions.
- Email spoofing of domains we do not send from, and SPF/DMARC issues on parked domains.
- Content injected by a merchant into their own storefront.
- Vulnerabilities in third-party services — report those to the vendor; tell us if we are exposed.
- Physical security, and attacks requiring a rooted device or a compromised end-user machine.
Not sure if it is in scope? Send us the URL, a brief description, and why you believe it belongs to Astrixy. Do not probe third-party systems on our behalf.
Research with care
Please use only accounts and data you own or are explicitly authorized to use, and limit testing to the minimum needed to demonstrate an issue.
- Do not access, modify, delete, or disclose another person's data.
- Do not disrupt availability, degrade performance, or run denial-of-service tests.
- Do not use social engineering, phishing, physical intrusion, or attacks against employees or customers.
- Do not deploy malware, persist access, or exploit a finding beyond a minimal proof of concept.
- Do not publish vulnerability details before coordinating with us.
- Comply with all applicable law.
If you encounter sensitive information unexpectedly, stop testing, do not retain or share it, and tell us what you found through the security contact below.
Safe harbour
We will not pursue legal action against, or ask law enforcement to investigate, researchers who act in good faith and comply with this policy. We consider such research authorised access under applicable computer-misuse laws, and we will make that position clear if a third party raises a claim. If you are unsure whether a test is in scope, ask us first — we would rather answer a question than receive an apology.
How to send a report
Email your findings to security@astrixy.app. Use a subject line such as “Security vulnerability report” and include enough detail for us to reproduce the behavior.
- Identify the affected URL, feature, or component.
- Describe the expected behavior, observed behavior, and potential impact.
- Provide clear reproduction steps and a minimal proof of concept, if available.
- Share relevant screenshots or logs with sensitive data removed.
- Include a safe way to contact you for follow-up questions.
Protect sensitive information. Do not include passwords, access tokens, or other people's personal data in your email. Describe where the information appeared instead.
Encryption
For sensitive reports, request our PGP key from security@astrixy.app and we will supply the current fingerprint over a second channel before you send details.
What happens next
We will review reports sent to the security address, assess whether we can reproduce the issue, and prioritize any necessary remediation based on risk. We may contact you for clarification or additional context.
| Stage | Target |
|---|---|
| Acknowledgement | 1 business day |
| Triage and severity assignment | 3 business days |
| Fix — Critical | 72 hours |
| Fix — High | 7 days |
| Fix — Medium | 30 days |
| Fix — Low | 90 days |
We keep you updated at each stage and tell you when the fix is live so you can verify it. Please keep details private while we investigate and coordinate with us before any public disclosure.
Common questions
Is there a bug bounty?
Astrixy does not currently operate a paid bug bounty. We offer public acknowledgement in our security hall of fame with your preferred name and link, a written confirmation of the finding for your portfolio, and credit in the release notes. As revenue allows, we intend to introduce monetary rewards; researchers who reported valid issues beforehand will be considered when that programme launches.
Can I publicly share my finding?
Please contact us privately first and coordinate disclosure so users have an opportunity to be protected.
What if I found user data?
Stop immediately. Do not download, retain, or disclose it. Email the security team with a minimal description of how it was encountered.
Found something we should know about?
Your careful report can help protect the people who rely on Astrixy. Reach our security contact directly and share only what is needed to investigate.
Report a vulnerability
Astrixy