Security
figtick connects two accounts people trust — their Figma and their Jira — so the way it handles a vulnerability report matters as much as the code. This page is the public version of that process.
Reporting a vulnerability
Email security@figtick.com with enough detail to reproduce the issue: the endpoint or screen, the steps, and what you were able to see or change that you should not have been. A proof-of-concept helps; a video is fine.
Please report privately first. If you need to encrypt the report, say so in a first message and we will exchange a key.
What to expect
figtick is maintained by one person, so these are commitments that can actually be met rather than aspirational ones:
| Stage | Target |
|---|---|
| Acknowledgement that a human has read it | 3 business days |
| First assessment — is it a vulnerability, how serious | 7 business days |
| Fix for a vulnerability that exposes customer data | as fast as possible, and you will be told the date it shipped |
| Fix for anything else | agreed with you, based on severity |
You will get a reply either way, including when the answer is "this is working as intended" — with the reasoning, so you can disagree.
Scope
In scope: api.figtick.com, the figtick Figma plugin, and figtick.com.
Out of scope: Figma and Atlassian themselves (report those to Figma and Atlassian), findings that require a compromised device or account, volumetric denial of service, and reports generated by a scanner without a demonstrated impact.
Safe harbour
If you make a good-faith effort to follow this policy, we will not pursue legal action over your research. Please stay within these lines: use only accounts you own or have permission to test, do not access, modify or delete anyone else's data, do not degrade the service for others, and give us a reasonable chance to fix the issue before publishing.
How figtick is built
Not a substitute for an audit — figtick holds no security accreditation — but this is what is actually true of the system today:
- Credentials. Figma and Jira OAuth tokens are encrypted at rest with AES-256-GCM. Plugin session tokens are stored only as SHA-256 hashes, so the database never holds anything that can be replayed as a session.
- Least privilege. figtick asks Figma for the narrowest scope set that works and drops any it stops needing. It never uses an operator-wide credential: every call is made with a specific person's token.
- Authorization. A Figma file key is not treated as a secret — it appears in every Figma URL. Every request about a file is authorized by asking Figma whether that caller's token can read that file.
- Untrusted input. Webhook deliveries are treated as a notification, not as fact: their passcode is compared in constant time against the registration they claim to be, and the content is re-read from Figma rather than taken from the payload.
- Secrets in transit and in logs. Everything is HTTPS. The one secret that has to travel in a URL (Jira gives dynamic webhooks no alternative) is redacted from access logs and rotated whenever the webhook is re-registered.
- Data location. The application server and its Postgres database run on the same machine in Germany (Hetzner, Falkenstein), so data at rest stays in the EU. The database is not reachable from the internet.
- Dependencies. Production dependencies are checked for known vulnerabilities; the current audit is clean.
Accreditation
figtick holds no security accreditation — no SOC 2, ISO 27001, PCI DSS or equivalent. It is a small product maintained by one developer, and claiming otherwise would be worse than admitting it. If your organisation needs a formally audited processor, figtick is not currently that.