Frequently asked questions
No! Jam Session is free for the foreseeable future as we see it as an accessibility tool.
This will only change if the costs of running it blow up, which feels unlikely. In that scenario we'd likely explore a Figma IAP just to cover costs without profit — probably a dollar or two per month.
This is planned, but not available yet.
No. Jam Session is visually designed to work hand in hand with FigJam to make participation feel like an extended experience, which we think is key to making hybrid workshops a success and not feel hacked together.
This product and plugin however is not formally affiliated with FigJam or Figma, Inc.
Absolutely. Behind the scenes, we use a unique identifier to differentiate submissions from different participants (so they can be grouped together on the board correctly), but if they don't enter a name we just call them 'Anonymous'. There's no way for anyone to attribute a submission to a specific participant if they don't enter their name.
Yes, temporarily. Text submissions are saved in our database, and images are stored in our cloud storage. At the end of every session all of your data is deleted immediately. It only remains on our database for the duration of your session.
The only scenario where data is stored for longer is if the facilitator's FigJam window crashes before being able to trigger the deletion. In this case, the system automatically checks at least once a day for old sessions and triggers the deletion manually. In the interest of transparency, this means the worst case scenario is your data being held for 23 hours and 59 minutes before being deleted.
Yes. Only the facilitator's FigJam window has the key to access any submission data. Nobody else can see any submissions, text or images submitted in activities. Any data sent to the database is encrypted and stored securely.
In addition, the difficulty in guessing your session code¹, API rate limits, session tokens, and 10 minute maximum session duration, means that is extremely unlikely someone will guess a session code. Even if they did, they wouldn't have enough time to do anything with it, and they wouldn't be able to access any data — only submit new things.
¹ Session codes are 6 characters that can be any number or letter (36 options per character) equalling 2,176,782,336 possible codes.
Not planned, as the vision for this is to be super-accessible on all devices and maintaining several native apps alone isn't sustainable.
Jam Session is live, but it's not perfect. There's no easy way to send early versions out to people to test, so we've launched on the Figma Community as a public beta until we're a bit more confident in its stability.