Frequently asked questions

SCIMIND Teknoloji Yazılım Eğitim ve Danışmanlık A.Ş. is a research technology company founded in Gaziantep, Türkiye on 3 July 2026. It builds software systems that carry the work researchers, educational institutions and decision makers do to produce, analyse and evaluate knowledge. Its products are not free text generators; they run defined workflows end to end.

The line has twelve products in total. Three are live today: ScholarGate, a library of research methods; Lacuna, literature and gap analysis; DecisionMind, multi criteria decision analysis. The remaining nine are in development or on the roadmap; each stage is written as it is, none shown ahead of where it stands.

Each product runs on its own and can be used on its own. At the same time, all of them complete the same chain: finding a method, literature and gaps, decision analysis. What they share is not passing data to each other, but the same provenance rule and audit trail; output produced in one becomes a defensible input in another.

Each of the three live products has its own address: scholargate.app, lacunamind.app and decisionmind.app. The applications run there, and account creation and login happen there. scimind.org, SciMind's corporate site, carries the products' registry information: who the company is, what the products do, and how institutional use is set up.

Verification is not a check performed after the fact, it is the workflow itself. Computation runs through defined steps, not free generation; the input, intermediate result and output of every step are recorded. The report carries in writing which data, method and steps produced it, and the user can read this trail start to end.

Yes. In ScholarGate, every method record is linked to the original paper it rests on. In DecisionMind, every method is bound to a manifest: which paper it rests on, which assumption it accepts and what it does not do. In Lacuna, every inclusion and exclusion decision is written to the decision log with its reason.

Yes. In DecisionMind, computation is deterministic: the same input matrix, method and settings produce the same ranking. In Lacuna, the method is sealed once the analysis closes, so the same corpus gives the same result. This is the precondition for reproducing a result in front of a reviewer; a result that cannot be repeated cannot be defended.

A general purpose tool generates text and can give a different answer if you ask the same question twice. The products here run a defined workflow: the method is bound to a source, the computation is repeatable, and every step is written to the audit trail. The difference is not the answer itself, but whether how it was produced can be shown.

Write to [email protected] for an institutional licence. We discuss the scope, the number of users and which products you want, then prepare the documents your procurement needs, including proforma invoice and technical specification support. The process follows the institution's own tender and direct procurement rules.

Yes, it is one of the options we discuss in institutional conversations. It usually starts with a single department or research group, a limited set of users, and a real piece of work. Scope, duration and evaluation criteria are set out in writing from the start. Write to [email protected] for details.

Training is one of the activities named in the company's legal title, and it can be included in an institutional conversation. Content matches the institution's need: using the products, choosing a method, or interpreting output. We do not publish a fixed catalogue; once we receive a request, we propose scope and format in writing.

Yes, write to [email protected] for a product demo; tell us which product you are interested in and your institution. The demo runs on the product's real interface, not a fixed presentation but a walkthrough driven by your question. Scope and terms are sent in writing after the call.

Your data is kept in the workspace tied to your account in the relevant product, processed only to run the analysis you started. Which data is processed for which purpose, how long it is kept, and who it is shared with is written in the privacy notice. If an institution needs a specific arrangement, we discuss it in writing at the contract stage.

You can write to [email protected] with questions about the processing of personal data. The data controller is SCIMIND Teknoloji Yazılım Eğitim ve Danışmanlık A.Ş. We answer institutions' legal and IT units in writing, including registry details, processing purposes and retention periods. The privacy notice is published on the privacy page.

Yes. Hosting infrastructure, server location and the list of subprocessors are shared in writing during the institutional conversation. We do not summarise this here, because it changes by product and institution, and an outdated sentence would become wrong information. Send your IT unit's questions to [email protected] and we answer in writing.

We do not currently have a published independent compliance certificate, and we do not present a document we do not have as if it existed. We answer compliance and security questions in writing: data processing purposes, retention periods, access rights and subprocessors included. When a certification process starts, we will announce it openly on the site.