1. Who we are
KIVOSYSTEMS develops and operates RHEON and is the controller of the personal data described in this Privacy Policy. You can reach us about privacy through the contact page of the Service. This policy explains what we collect, why, who we share it with, how long we keep it, and the rights you have.
2. Beta service
RHEON is beta software. Please do not enter personal data of other people, or any confidential, proprietary, regulated or export-controlled information, into the Service. Beta data may be reset or lost without notice.
3. Information we collect
- Account data: your name, email address, a salted and hashed password (we never store your password in readable form), email-verification status, and the date and version of the Terms and Privacy Policy you accepted. If you sign in with Google, we receive your name, email address, profile image and whether Google has verified your email.
- Workspace data: projects, flowsheets, components, property-package and solver settings, simulation results, snapshots, comments, saved studies, saved Dynamics models and their versions, project memory, share links and gallery publications.
- Uploaded documents: when you upload a PDF or Word file, we record its file name, size, page count, a fingerprint (hash) of the file and the results of our security checks. If it passes, we keep what our software reads from it: its text and tables split into referenced passages, equations, a summary of its contents and values found in it, images of its pages that we render ourselves, and images contained in Word files (re-saved by us). The original file itself is not kept; see section 8.
- AI interactions: prompts you write to the flowsheet agent, AI engineer or tutor, the replies and proposals, and your feedback on them. Tutor conversations on assignment work are stored with your submission so that the class instructors can review them.
- Classroom data: classes you create or join, your role, assignments, the flowsheets you start for them, check results, submissions, tutor conversations, feedback and grades.
- Team data: teams you create or join, your role, and which projects are shared with them. Everyone in a team can see team members' names and email addresses and open, edit and solve the projects shared with it.
- Contact requests: the name, email address, company, subject and message you send through the contact form.
- Usage statistics: which features are used (for example that a solve, study, export or AI request happened, whether it succeeded, how long it took, and for AI requests the model and the number of tokens processed). These records contain no names, email addresses, IP addresses, prompts, replies or flowsheet content; they are linked only to a one-way pseudonym derived from your account with a secret key, and their time is rounded to the hour.
- Technical data: IP address, browser and device information, request logs, timestamps, error logs and security events, collected automatically by us and our hosting provider to run and protect the Service.
4. How we use it and our legal bases
- To create and run your account, save your work, run calculations and provide the features you ask for — necessary to perform our contract with you.
- To send verification codes, account-deletion codes and other service emails — contract performance.
- To keep the Service secure: authentication, rate limiting, abuse prevention, fraud and incident investigation — our legitimate interests in protecting the Service and its users.
- To fix bugs and improve reliability and features of the beta — our legitimate interests.
- To understand how the Service is used as a whole and what it costs to run (for example the number of active users, which features are popular, and AI usage and spend), using the pseudonymous usage statistics described above — our legitimate interests in running and improving the Service. Only our owners can view these statistics, only as aggregates, and any figure that would describe fewer than five people is hidden. You can object to this processing by contacting us.
- To respond to contact requests — legitimate interests, or steps you asked for before entering a contract.
- To run classes: showing instructors their students' names, email addresses and assignment work, and showing students their checks, feedback and grades — contract performance.
- To keep a record of your acceptance of these documents, and to comply with legal obligations and enforce our Terms — legal obligation and legitimate interests.
We do not sell your personal data, we do not share it for cross-context behavioural advertising, and we do not use it for automated decision-making that produces legal or similarly significant effects on you.
5. AI processing
When you use AI-assisted features, your prompt and relevant context from the current flowsheet and project (and, in anonymised form, matching public gallery examples) are sent to one of our AI providers, OpenAI or Anthropic, to generate a response. We use their APIs under commercial terms that, according to each provider, do not use API data to train their models by default; the providers may retain data for a limited period for abuse and safety monitoring. Do not include personal or confidential information in prompts. We record how many tokens each AI request used, to manage costs and fair-use limits, but not its content in those statistics.
When you attach an uploaded document to an AI feature (for example the AI engineer or building a Dynamics model from a document), the content we have read from it, including passages of its text, its summary and images of its pages, is sent to our AI provider so that the AI can read it and build or answer from it. This happens only for documents you attach, each time the AI uses them. The original file is never sent; only what our software extracted from it. The provider processes this content under its own API terms, as described above, and we are not responsible for the provider's handling of it under those terms. Do not attach documents you are not entitled to share in this way.
6. Who we share data with
We share personal data only with service providers that process it on our behalf to run the Service, under contractual confidentiality and data-protection obligations, namely:
- Vercel — application hosting, networking and logs, and file storage (Vercel Blob) for uploaded documents while they are checked and for the page images we render from them;
- Neon — managed PostgreSQL database hosting;
- OpenAI and Anthropic — AI-assisted features, including the content of documents you attach to them (only when you use them);
- our email delivery provider — verification, deletion and contact emails;
- Google — only if you choose Sign in with Google; and
- PubChem (US National Library of Medicine) — only the text of a component search that our own chemical database cannot match, never any account data.
We may also disclose data if required by law or a valid legal request, to protect the rights, safety or property of users, us or others, to investigate abuse or security incidents, or in connection with a merger, acquisition or sale of assets (in which case this policy will continue to apply). Content you choose to share by link or publish to the gallery, together with your display name, is visible to anyone with access to it. If you join a class, its instructors can see your name, email address and the assignment work you create for that class.
7. International transfers
Our providers may process data in countries outside your own, including the United States. Where data protection law requires it, we rely on adequacy decisions, the EU–US Data Privacy Framework where the provider is certified, or standard contractual clauses approved by the European Commission, together with appropriate supplementary measures.
8. How long we keep data
- Account and workspace data: while your account is open. When you delete your account, your account, projects, flowsheets and related data are deleted from the live database immediately.
- Backups and logs: residual copies may remain in provider backups and logs for a limited period (typically up to 30 days, and longer only where needed for security or legal reasons) until they are overwritten.
- Uploaded documents: the original file is stored only temporarily, in a private storage area with Vercel Blob, while our security checks and extraction run, and is deleted as soon as that finishes, whether or not the file passed. Files that fail the checks are not kept. The extracted content, page images and summary of a document are kept until you delete the document, or until you delete your account, when they are deleted from the live database and file storage at once (backup copies as above).
- Usage statistics: up to 13 months, after which they are deleted automatically. They are deleted straight away when you delete your account.
- Contact requests: for as long as needed to handle the request and for up to 24 months afterwards, unless the law requires longer.
- Acceptance records: for as long as your account exists and for a reasonable period afterwards where needed to establish or defend legal claims.
9. Security
We use reasonable technical and organisational measures appropriate to a beta service, including encrypted (HTTPS) connections, automated checks of uploaded files in an isolated process with no access to your account or our credentials, private file storage, salted PBKDF2 password hashing, hashed one-time codes, short-lived signed service tokens, per-account ownership checks on every workspace request, rate limiting, and keeping secret keys only on the server. However, no internet service or storage system is completely secure, and we cannot guarantee the security of your data. You are responsible for using a strong, unique password and keeping it confidential. If we become aware of a personal data breach, we will notify you and the competent authorities where the law requires us to do so.
10. Your rights
Depending on where you live, you may have the right to access your personal data, correct it, delete it, restrict or object to its processing, receive a portable copy, and withdraw consent where processing is based on consent. You can update your name and password and permanently delete your account yourself from the settings page. To exercise other rights, contact us through the contact page; we may need to verify your identity, and we will respond within the time required by law. If you are in the EU/EEA or the UK, you also have the right to lodge a complaint with your local data protection supervisory authority. California and other US-state residents may have similar rights to know, delete and correct, and we will not discriminate against you for exercising them.
11. Cookies
We use only cookies that are strictly necessary to run the Service: a session cookie that keeps you signed in and security cookies that protect sign-in requests. We do not use advertising, analytics or cross-site tracking cookies, and our usage statistics are recorded on our servers without cookies or device identifiers. Your browser may also store non-identifying interface preferences locally.
12. Children
The Service is intended for adults and is not directed at anyone under 18. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we will delete it.
13. Changes to this policy
We may update this Privacy Policy. When we make a material change we will update the version date and ask you to review it before you continue to use the workspace.