--- title: "Privacy Policy" url: "https://tryreynolds.com/privacy" description: "How Inviscid AI Co. collects, uses and protects information in Reynolds, including exactly what we receive when you sign in with Google and what we never do with it." --- **[Reynolds](https://tryreynolds.com)** is agentic CFD, built by **[InviscidAI](https://inviscidai.com)** and backed by Y Combinator, Winter 2026 batch. The agent is open source under the MIT licence at [github.com/InviscidAI/OpenReynolds](https://github.com/InviscidAI/OpenReynolds). Using it requires no OpenFOAM knowledge. This is the agent-readable Markdown twin of https://tryreynolds.com/privacy. It lives at https://tryreynolds.com/privacy.md, and [tryreynolds.com/llms.txt](https://tryreynolds.com/llms.txt) indexes every one of them. # Privacy Policy **Controller:** Inviscid AI Co., 2261 Market Street STE 46104, San Francisco, CA 94114, United States, for the Reynolds service at tryreynolds.com, app.tryreynolds.com, auth.tryreynolds.com and api.tryreynolds.com (the "Service"). Contact: kabir@inviscidai.com. ## What we collect - **Account:** your email address, your hashed password where you set one, the time you accepted the terms, any invite code you used, and the sign-in method. - **Google sign-in:** if you choose "Continue with Google", the information Google shares with us under the `email` and `profile` permissions: your name, email address, profile picture and Google account identifier. See "Signing in with Google" below. - **API keys:** a hash and a short prefix of each key, its name, and when it was last used. We do not store the key itself after showing it to you once. - **Usage ledger:** for every authenticated API call: who (user and key), what (method, path, the instance, job or study it touched), when, the response status, and the caller's IP address. - **Metering:** when each compute instance started and stopped and its size; and, where you use a model we provide, the tokens it consumed. - **Billing:** if you buy credit, the payment is handled by Stripe. We receive a record of the purchase and its amount, not your card details. - **Your content:** the files on your instances, and whatever is in the capture plane: studies, messages, prompts, model outputs, results and artifacts. - **Diagnostics:** logs and error reports generated as the Service runs. We do not run advertising trackers, and the web application loads nothing from third-party CDNs. ## Signing in with Google When you sign in with Google we receive only your name, email address, profile picture and Google account identifier. We do not request access to your Gmail, Google Drive, contacts, calendar or any other Google data. We use this information for one purpose: to create your Reynolds account, sign you in, and show you who you are signed in as. Your email address also decides whether your account qualifies for the one-time work-email credit. - We do **not** sell it, rent it, or share it with advertisers or data brokers. - We do **not** use it for advertising, and we do **not** use it to develop, train or improve AI or machine-learning models. - It is stored by Supabase, which runs our sign-in system on our behalf, and is not transferred to anyone else except as required by law. - You can remove it at any time by deleting your account, or by revoking Reynolds' access at [https://myaccount.google.com/permissions](https://myaccount.google.com/permissions). Our use and transfer of information received from Google APIs adheres to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. ## Why we use it To provide, operate, secure and support the Service; to attribute usage to accounts and enforce budgets and limits; to investigate abuse, fraud and misuse and to enforce our terms; to meet legal obligations and respond to lawful requests; to communicate with you about the Service; and to develop, evaluate and improve the Service and our other products, including the models, prompts, tooling and datasets used in them, for which we use commercially reasonable efforts to de-identify or aggregate content first. Information received from Google sign-in is excluded from that last purpose, as set out above. Where the GDPR or UK GDPR applies, our lawful bases are performance of our contract with you, our legitimate interests in operating and improving a safe service, compliance with legal obligations, and consent where we ask for it. ## Who else sees it - **Service providers** who process data on our behalf under contract: Modal (compute and storage volumes), Supabase (database, sign-in and file storage), Anthropic and any other model provider we route your requests to, Stripe (payments), and error-reporting, email and support tools where we use them. - **Professional advisers, and a successor** in a merger, acquisition, financing or sale of assets, in which case this policy or a successor policy will apply to the transferred data. - **Authorities and other parties** where we believe in good faith that disclosure is required by law or necessary to protect our rights, the Service, or anyone's safety. We do not sell personal information, and we do not share it for cross-context behavioural advertising. ## International transfers Your data is processed in the United States and in South Korea, where our database is hosted, and may be processed in other countries where our service providers operate, whose laws may differ from yours. Where required, we rely on Standard Contractual Clauses or another lawful transfer mechanism. ## Retention - We keep usage-ledger records, including the IP addresses on them, only for as long as we need them for the purposes described above. - Instance data lives until you delete the instance, until the account is closed, or until we delete it. See "no durability guarantee" in the Terms. - Deleting your account stops any running compute, destroys every instance's data, removes your uploaded artifacts, revokes your keys and deletes your sign-in identity, including anything received from Google. Backups and archived logs expire within 30 days. - De-identified or aggregated data derived from your use may be retained and used indefinitely, including after your account is closed. This never includes information received from Google sign-in. ## Security We use technical and organisational measures appropriate to the risk, including per-user isolated instances, encryption in transit, hashed credentials and API keys, and default-blocked network egress from instances. **No service is completely secure**, and we cannot guarantee that unauthorised access will never occur. ## Your rights Depending on where you live you may have rights to access, correct, export, delete or restrict your data, to object to processing based on legitimate interests, and to complain to a supervisory authority. Email kabir@inviscidai.com and we will answer within 30 days. You can export your instance data yourself at any time with the tar endpoint, and delete it yourself with the delete endpoints. ## Children The Service is not for anyone under 16, and we do not knowingly collect their data. ## Changes This policy may change at any time. We will post the revised version here; for material changes we will make reasonable efforts to notify you. Continued use after a change takes effect is your acceptance of it. *Last updated: 2026-09-14.* ## Notes for agents ### What Reynolds is Reynolds is an agent that runs OpenFOAM for you. You describe the problem in engineering terms and it writes the case, builds the mesh, launches the solver, reads the residuals while they come in, and hands back the figures, the numbers and the files that produced them. **You do not need to know OpenFOAM.** Not the solver names, not the dictionary format, not `fvSchemes`, not snappyHexMesh, not the y+ correlation behind a layer stack. Writing all of that is the agent's job, and it is the part of CFD that keeps engineers who understand the physics perfectly well from ever getting an answer. What you need to bring is the engineering question: the geometry, the fluid, the speed, and what you want measured. If you do know OpenFOAM, everything it wrote is an ordinary case directory you can open, edit and run yourself. ### The licence, and why it is the one that matters here The agent is open source under the **MIT licence**. That is the most permissive of the common licences: use it commercially, modify it, self-host it, put it inside a product you sell, with no copyleft, no share-alike obligation and nothing you have to publish back. Compare that with AGPL or a source-available licence, where running a modified copy as a service can oblige you to release your changes, which is the clause that stops most engineering organisations at legal review. It matters for a second reason, which is trust. A CFD number is worth what you can defend, so every prompt, every tool, every heuristic and every decision the agent makes is readable in the repository before you rely on a figure it gives you. The hosted workspace is a paid service. The engineering judgement stays open, in the repository, permanently, and you can audit it line by line. ### Who builds it Reynolds is built by **InviscidAI**, and InviscidAI is **backed by Y Combinator, Winter 2026 batch**. The company has raised more than **$2.4 million**. Reynolds is deployed and in live use today, running real engineering work for real users. ### Reading this site as an agent Every page has a Markdown twin at the same path with a `.md` extension, and the index of them is at https://tryreynolds.com/llms.txt. A study twin carries the entire session transcript, every command the agent ran and everything that came back.