Privacy policy
Effective version: 2026-10-27-v4. Operator: UPCOMINGSOUNDS S.R.L., Str. Nerva Traian nr. 27-33, Birou 6, Scara B, Etaj 1, Sector 3, Bucharest, Romania.
Who is responsible
SolveLang is operated by UPCOMINGSOUNDS S.R.L., Romania (the Operator), registered office Str. Nerva Traian nr. 27-33, Birou 6, Scara B, Etaj 1, Sector 3, Bucharest, Romania, Trade Registry J2026027621002, fiscal code (CUI) 54564122. The Operator is the data controller for the processing described in this policy. Contact hello@solve-lang.com or +1 786-420-3128 for privacy questions and requests.
Website visits and requested services
Serving web pages and protecting the service requires technical request information such as IP addresses and browser details at the hosting and security providers. We use this for delivery, security and abuse prevention under our legitimate interests. When you contact us, we use your email and the information you provide to answer your request or take steps toward a contract. Do not include passwords, access tokens or unrelated personal information.
Workflow and browser data
Workflow Studio and the initial Workflow Preflight scan process your workflow locally in your browser. Saved projects, preferences and recovery data can remain in browser storage until you remove them. Studio usage counters stay in memory during the current use and are not sent to an analytics provider. If you explicitly enable Studio account saving, projects, versions, and traces are uploaded to your authenticated account on AWS. You can export the account snapshot or remove it using Studio; local copies remain until you remove them. Storage backups may follow the hosting retention policy. Usage counters are not included. This local processing description does not extend to optional remote services you explicitly invoke.
Remote MCP and plugin requests
When you explicitly use SolveLang through a hosted MCP or plugin integration, the workflow or Solve Graph JSON needed for the requested analysis is transmitted to SolveLang infrastructure so the requested deterministic analysis can run. The remote analysis service is designed to process that JSON in memory, does not execute the workflow, does not inspect credential values, and does not intentionally persist raw workflow or graph payloads. Hosting and security infrastructure may process ordinary request metadata such as IP address, timing, size, and abuse signals. Do not submit secrets or personal data that are unnecessary for the analysis.
Your content is never used for training
We do not sell your content, and we do not use your workflows, code, Solve Graph data, or the outputs generated for you to train artificial intelligence or machine learning models. Your content is processed only to provide the service you requested, to secure it, and to comply with the law.
Payments, accounts and optional services
Account and purchase features may process contact information, identifiers, payment status and acceptance records to perform the contract, prevent abuse and meet legal obligations. Payment and security providers include Stripe, Cloudflare and AWS where the relevant feature is used. See the Workflow Preflight privacy notice for the specific checkout data flow. A feature being described here does not mean it is publicly enabled.
Who receives data
Hosting, communications, payment and security providers receive the data needed for their functions. The companies that process personal data on our behalf are listed on the Subprocessors page, with their purposes and processing locations. Authorities may receive data when legally required.
How long we keep data
| Data | Retention |
|---|---|
| Account and contact data | While your account is active, then deleted or anonymised, subject to legal record-keeping duties. |
| Purchase, invoice and acceptance records | For the period required by Romanian accounting and tax law, up to 10 years for financial records. |
| Studio account-saved projects, versions and traces | Until you remove them using Studio controls or your account is closed. |
| Raw workflow or graph payloads sent to hosted remote analysis | Processed in memory; not intentionally persisted. |
| Security and abuse-prevention logs (request metadata) | No more than 30 days, unless an active security investigation or a legal duty requires longer. |
| Support correspondence | For as long as needed to handle the request and any related dispute, then deleted. |
| Browser-local Studio data | Until you remove it through the product controls or your browser settings. |
International transfers
Some providers process data outside the European Economic Area, including in the United States. Where such a transfer takes place, it relies on an adequacy decision or on the European Commission's standard contractual clauses, as described in the Data Processing Addendum for business customers.
Cookies
SolveLang currently uses only the cookies and similar storage that are strictly necessary to deliver and secure the services you request. We do not use analytics or marketing cookies. If that changes, non-essential cookies will be used only with your prior consent, as described in the Cookie policy.
Children
SolveLang accounts are for users who are at least 16 years old. We do not knowingly offer accounts to younger children.
Your choices and rights
Where applicable, you can request access, correction, erasure, restriction or portability of personal data, object to processing based on legitimate interests and withdraw consent for future optional processing. We respond to rights requests within one month. Contact hello@solve-lang.com. You may complain to the Romanian data protection authority, ANSPDCP (www.dataprotection.ro), or another competent authority, and you may also bring a claim before the courts. We may need proportionate verification to protect your data. We do not require marketing consent to use support.
Changes
We may update this notice as the service changes. Material changes are published with a new effective version and, where the law requires, notified in advance. Optional processing requiring consent must not be enabled merely by publishing revised text.
Workflow Preflight privacy details · Subprocessors · Data Processing Addendum