Last Updated: July 24th, 2026
- Introduction
Abacor, a brand of Abakus Financial, Inc. ("Abacor," "we," "us," "our"), handles confidential information belonging to accounting firms and their clients, and we take reports of security weaknesses seriously. If you believe you have found a vulnerability in our service, we want to hear from you. This policy explains how to tell us, what we will do in response, and what we ask of you while you are looking.
- How to Report
Email [email protected] with "Security" in the subject line. Please do not report security issues through public channels such as social media or a public issue tracker.
So that we can reproduce and fix the issue quickly, please include as much of the following as you can:
- the affected URL, endpoint or feature, and the type of issue you believe you have found;
- the steps needed to reproduce it, including any request or payload involved;
- what an attacker could achieve with it, in your assessment;
- any logs, screenshots or proof-of-concept code that help demonstrate it;
- how you would like to be credited, if you would like to be.
- What We Will Do
- Acknowledge your report within five business days of receiving it.
- Assess and triage it, and tell you whether we have been able to reproduce it and how we have rated its severity.
- Keep you informed at least every thirty days while the issue remains open, until it is resolved or we explain why we do not intend to act on it.
- Fix what needs fixing, prioritised by severity, and let you know when a fix has shipped so you can confirm it.
- Credit you if you would like us to, once the issue is resolved.
We do not currently operate a paid bug-bounty programme and do not offer monetary rewards. We are nonetheless grateful for reports made in good faith and will treat you and your work with respect.
- Scope
In scope: the Abacor web application and marketing site at abacor.com and its subdomains, our public API hosts, and our mobile applications.
Out of scope:
- services operated by third parties on our behalf — please report those to the provider concerned. This includes our identity provider, payment processor and meeting-recording provider;
- denial-of-service, volumetric or resource-exhaustion testing of any kind;
- social engineering, phishing or physical attacks against our staff, our users or our offices;
- spam, or reports produced solely by an automated scanner with no assessment of exploitability;
- findings that carry no practical security impact, such as missing headers on a page that serves no sensitive content, or software-version disclosure with no known exploitable defect.
- What We Ask of You
While you are researching, please protect the people whose data we hold:
- Use only accounts you own or have explicit permission to test. Do not access, modify or delete data belonging to anyone else.
- If you do encounter someone else's data, stop, do not save or share it, and tell us immediately what you saw and how.
- Take only the minimum action needed to demonstrate the issue. Do not exfiltrate data in bulk, and do not pivot further into our systems than the finding requires.
- Do not degrade or interrupt the service for our users.
- Give us a reasonable opportunity to fix the issue before disclosing it publicly, and please coordinate the timing of any disclosure with us.
- Comply with applicable law, and do not use the finding for extortion or any other unlawful purpose.
- Safe Harbour
If you make a good-faith effort to comply with this policy during your research, we will regard your activity as authorised, we will not pursue or support legal action against you in relation to it, and we will work with you to resolve the issue promptly. If a third party brings legal action against you in connection with research you carried out in accordance with this policy, we will make it known that your activity was authorised by us. This policy does not give you authority to act in ways that are unlawful, and it cannot bind third parties whose services we use. If you are unsure whether something you intend to do falls within this policy, ask us first.
- Contact
Security reports: [email protected]
Machine-readable contact information: /.well-known/security.txt
Privacy enquiries: see our Privacy Policy.