Security
Security at Tulpar
How to report a security problem, and how Tulpar protects your designs and your account. Last updated 31 October 2026.
Report a vulnerability
Write to hmamut39@gmail.com with “Tulpar security” in the subject. Say what you found, how to reproduce it, and what it affects. Tulpar is built and run by one developer, who reads every report and fixes confirmed problems as a priority, and will tell you what happened with yours.
Please test only with your own account and data, don't access other people's data, and don't run tests that disrupt the service. Give us a reasonable time to fix a problem before making it public.
Your designs and generated code
- A screenshot or frame is held in memory while your run is shown, and deleted within one hour. Working files on disk are deleted when the run finishes.
- Generated code never runs on Tulpar's own server. It is built and run in a sandboxed browser with the network blocked, or, for Java and C#, whose code runs on a server, on a throwaway machine that holds no secrets, blocks every outgoing connection, runs it as an unprivileged user and starts clean for every check.
- Generated code is also checked before you get it. A component made from a design never needs to call a server, run code from a string, read cookies, stored data or secrets, or write raw HTML. Code that does fails the safety check and is repaired. Such code is what a prompt injection would add: instructions hidden in a design's text or a library's docs. The model is also told that everything in a design is content, never instructions.
- To write the code, your design is sent to OpenAI's API with storage turned off. See the Privacy Policy for everyone who receives data.
Your account
- Tulpar has no passwords: you sign in with GitHub. Session cookies are signed, HttpOnly and SameSite=Lax, and all traffic uses HTTPS.
- Keys for the VS Code extension and the Figma plugin are shown once, and the server stores only their hash. Creating a new key replaces the old one, and you can revoke them all at tulparsi.com/connect.
- Your Figma token is used for your run only and never stored on our servers.
- Card details go to Stripe and never reach Tulpar.
How it is built and shipped
- Every release must pass an automated test suite, including tests inside the server image, before it deploys.
- GitHub Dependabot watches dependencies for updates.
- Tulpar is hosted on Fly.io in the United States.
Certifications
Tulpar is not accredited to SOC 2, ISO 27001 or similar standards. If your organisation needs them, please write to us before you use it with confidential designs.