Security and vulnerability disclosure
To report a security vulnerability in flintspark, email the contact address on this page with the subject "Security report". flintspark is an enterprise AI platform whose agent, Flint, runs under policy. We read every report, and there is no bug bounty.
- Report toadmin@flintspark.ai
- Subject lineSecurity report
- BountyNone
How do I report a vulnerability?
Send an email to the contact address with the subject "Security report".
Please do not post details publicly until we have had time to fix the issue.
What happens to a report
- You send itSubject "Security report"
- We read itEvery report is read by the flintspark team
- We reply and fixWe reply to the sender and credit you on request
What should a report include?
Enough for us to reproduce the problem without guessing.
- What you found, and the page, address or component it affects.
- The steps to reproduce it, and what you saw happen.
- What you think an attacker could do with it.
- How to reach you, and whether you want to be credited.
A report template
- Found
- A short description
- Where
- Page or component
- Steps
- 1, 2, 3
- Impact
- What could go wrong
- Contact
- Reply address, credit yes or no
What counts as good-faith research?
Research on the flintspark.ai website that stays within your own accounts and data, and stops as soon as you have shown the problem.
If you follow these rules we will treat your report as good-faith research and work with you on the fix.
Please do
- Use only your own accounts and data.
- Stop once you have shown the issue.
- Give us time to fix it before you publish.
Please do not
- Access, change or keep anyone else's data.
- Run denial-of-service or social-engineering attacks.
- Test services we do not run, such as our hosting or model gateway. Report those to their owners.
Is there a bug bounty?
No. flintspark does not run a bug bounty and does not pay for reports.
We read every report, reply to the sender, and credit the researcher on request once the issue is fixed.
- No bountyflintspark does not pay for vulnerability reports.
- A replyWe reply to every report from the address you wrote to.
Where are the product controls?
This page is about reporting problems. How Flint stays under policy, what needs a person's approval, the audit log and personal-data handling are on the trust and safety page.
flintspark holds no certifications today; the trust page says so for each framework.
Product controls
Approvals, audit log, redaction, policy
Questions about this page
Where do I report a security vulnerability in flintspark?
Email the flintspark contact address shown on this page with the subject "Security report". Say what you found, where, and how to reproduce it.
Does flintspark pay for vulnerability reports?
No. flintspark does not run a bug bounty. We read every report and reply to the sender, and we credit the researcher on request once the issue is fixed.
What am I allowed to test?
Test the flintspark.ai website, using only your own accounts and data. Do not access, change or keep anyone else's data, do not run denial-of-service or social-engineering attacks, and give us time to fix an issue before you publish it.
See Flint run
Bring one workflow you'd rather not do by hand. We'll show Flint learning one like it, and stopping before anything it can't undo.
We reply from hello@flintspark.ai.