figtick

Privacy policy

Last updated 29 October 2026

figtick is a Figma plugin and the service behind it. When someone comments @jira in a Figma file, figtick creates a Jira issue and keeps the two in sync. This page explains what that takes in personal data. It covers the plugin, the service at api.figtick.com and this website.

Who is responsible

figtick is operated by Grid Eight, which is the controller for the data described here. For anything about your data, email support@figtick.com.

What figtick stores

DataWhy
Your Figma account: user ID, handle, email address and avatar URLTo identify you in the plugin and to show who filed a ticket.
Access to Figma and Jira (OAuth tokens), encrypted with AES-256-GCMTo read comments, post replies and create Jira issues on your behalf. figtick never sees your passwords.
Your Jira site: its ID, address and nameTo know where to file tickets.
Figma teams you register: team ID, name and icon, plus the webhook figtick sets up thereSo Figma tells figtick when a new comment is written.
File mappings: Figma file key and name, Jira project and issue typeTo know which Jira project each file's tickets go to.
Each ticket figtick filed: the comment and frame it came from, the comment text used as the summary, the commenter's handle, and the Jira issue key and statusTo keep the Figma thread and the Jira issue in sync, and to list tickets in the plugin.
A plugin session token (stored only as a hash on the server, the token itself in Figma's plugin storage on your device)To keep you signed in. Sessions expire after 90 days.

To find @jira, figtick reads the comments of files that have been mapped to a Jira project. Comments that aren't tagged are only held in memory while they're checked, and are not saved. The frame screenshot is rendered by Figma and attached straight to the Jira issue; figtick does not keep a copy. figtick reads nothing else from your files, such as designs, layers or images.

Logs

Legal basis

Storing your accounts, mappings and tickets is necessary to provide figtick to you (Article 6(1)(b) GDPR). Logs and backups are kept on the basis of our legitimate interest in running a secure and reliable service (Article 6(1)(f) GDPR).

Where it is stored, and who else processes it

Figma and Atlassian are the services you connect. They process your data under their own privacy policies, and what figtick sends them (replies, issues, screenshots) is stored there under those terms. figtick does not sell data, show ads, or use analytics or tracking.

How long it is kept

Your data is kept while your figtick account exists. When you delete your account in the plugin (Settings → Delete account), your connections, teams, mappings and ticket records are deleted immediately. Nightly backups of the database (in which the tokens remain encrypted) are kept on the same server for 14 days, so deleted data disappears from those within two weeks. Issues and replies already created in Jira and Figma stay there; delete them in those tools if you want them gone.

Your rights

You can ask for a copy of your data, have it corrected or deleted, receive it in a portable format, or object to its processing. Email support@figtick.com and you will get an answer within one month. You can also disconnect Figma or Jira, or delete your account, yourself from the plugin's Settings. If you think your data is handled wrongly, you can complain to the data protection authority in the country where you live or work.

This website

figtick.com sets no cookies and loads nothing from other sites. Visiting it only leaves an entry in the server access log described above.

Changes

If this policy changes, the new version is published here with a new date. Changes that affect what figtick stores will also be announced in the plugin.