Privacy Policy

This describes what Zenzei stores about you and why. It reflects what the platform actually does today — if that changes, this page changes with it.

What we collect

• Your email address and password. Needed to create and secure your account. Passwords are stored hashed; we never see them.
• A display name, only if you choose to set one.
• Code you submit and the results of running it — the source you sent, the run status, logs, and artifacts such as waveforms.
• Your entitlements — which tier your account has, and how it was granted.
• Feedback you send us, along with the context of the run it refers to, when you use the feedback button.
• When you use the simulator, and what you ran in it — that a session was open, which project or demo it had open, and for each simulation, synthesis, layout flow, or FPGA session: which tool, how long it took, and whether it finished, failed, was cancelled, or timed out. This is how we see that the shared simulator is working and how much of it is in use. It does not include your source code, which is covered above, and it does not include what you typed or clicked.

What we do not do

We do not use third-party analytics, we do not use advertising cookies, and we do not sell or share your data with third parties for marketing. The only cookies Zenzei sets are the ones that keep you signed in. We do record when you use the simulator and what you ran in it, as described above — that is operational, it stays on our own infrastructure, and no third party receives it. Nothing you do in the lessons or the editor is tracked beyond that.

Why we hold it

To give you an account, to run your code and return the results, to show you your own history, and to fix the platform when something breaks. Your submissions and feedback also help us find bugs in our own simulator — that is a stated purpose of the free beta.

Who processes it

• Supabase — database, authentication, and file storage.
• Our hosting provider — serves the website and its API.
• Our email provider — delivers account emails such as sign-up confirmation and password resets. Used only for that.

These providers process data on our behalf. We do not send them anything beyond what their function requires.

Who can see your code

Your submissions are yours. Access is enforced at the database level by row-level security, so other users cannot read your rows. Platform maintainers can access data where needed to operate or debug the service.

How long we keep it

Account data is kept while your account exists. Submissions and their artifacts are kept so you can revisit your own history. Simulator activity records are kept for 90 days and then deleted. During the beta, projects and submissions may also be reset as the platform changes.

Deleting a file in the simulator is reversible for 30 days. When you delete a file inside the editor, it stops being part of your project immediately, but a copy stays on the machine that runs your code for up to 30 days before it is permanently removed. There is no button to restore it — ask us, and if it is within that window we can usually get it back. This exists so a mistaken delete is not final; if you would rather a file were gone at once, tell us and we will remove it.

Deleting your account is not reversible, and is not delayed. Ask us to delete your account and we remove your account and the records tied to it: your profile, your projects and their files, your submissions and their artifacts, your feedback, any bug reports you sent us and the files attached to them, and your simulator activity. The working copy of your files on the machine that runs your code is removed too, including anything still inside the 30-day window above — account deletion overrides it. That last step depends on the machine being reachable, so it can lag by a few hours if it is offline; it is queued and happens when the machine is next up.

Your choices

• See and edit your display name on your account page.
• Review your own submissions at any time while signed in.
• Ask for a copy of your data, or ask us to delete your account.
• Depending on where you live, you may have additional rights over your data — tell us and we will honour them.

Security

Access to your data is restricted at the database level. Submitted code runs in a constrained environment isolated from other users' work. No system is perfect; if you find a security problem, please report it rather than testing it against other people's accounts.

Changes

We will update this page as the platform develops, and revise the “last updated” date above.