figtick

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:

StageTarget
Acknowledgement that a human has read it3 business days
First assessment — is it a vulnerability, how serious7 business days
Fix for a vulnerability that exposes customer dataas fast as possible, and you will be told the date it shipped
Fix for anything elseagreed 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:

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.