Privacy policy
This policy explains what personal data Scienvera collects when you use the research and writing tools at tools.scienvera.com (the “Service”), why, who else sees it, how long we keep it, and what you can ask us to do with it. It is written to meet the EU and UK General Data Protection Regulation (GDPR) and the Turkish Personal Data Protection Law No. 6698 (KVKK). If you are in Türkiye, our KVKK information notice gives the same information in the form that law asks for.
1. Who is responsible
The data controller is:
- Data controller
- Anıl Sayar (Scienvera)
- Legal form
- Individual (not a company)
- [email protected]
- Website
- tools.scienvera.com
For anything about your data, write to [email protected].
2. What we collect
Account
Your email address, and your name if you add one or sign in with Google. Sign-in is handled by Stytch: we never receive a password, and with Google we receive only the basic profile you approve. We also keep your workspaces and roles, your research field if you choose one, and when you accepted our terms and gave or withdrew consent.
What you create and upload
Projects and the documents you write, reading lists and saved papers, notes, saved searches (watches), saved reports, and files you upload to your library. Uploaded files are split into passages and indexed so you can search them. All of this is private to your workspace unless you share it.
What you type into the tools
Searches, claims to check, questions and draft text you send to a tool. We need this to run the tool. We keep a log of activity (the kind of action, timing, result counts, safety flags) to run credits, prevent abuse and fix problems; the text of searches in that log is stored encrypted.
Verification reports, the AI-help log and hand-ins
So that a project’s verification report and AI-use declaration can say what help was used, each project keeps a log of the AI features used on it: the kind of action (for example a draft check, an accepted AI rewrite, a source suggested by the tool and then cited), a count, the identifiers of the papers involved, who did it and when. The log holds no text from your draft, prompts or answers. Everyone with access to the project can see it in the report.
In a workspace set up as a class, you can choose to hand in a project’s report. Only then, a copy of the report as it is at that moment goes to the workspace’s admins (your instructors) with your name and email: the project name, the sentences that cite a source, your sources and their checks, totals from the AI-help log and your declaration, but not the rest of your draft. Nothing is handed in automatically, and nothing is handed in from a personal or lab workspace. You can take a report back at any time. How your instructor or institution uses a handed-in report for the course is up to them and your institution’s rules.
Feedback and how you use results
To make search rank the right paper first, we record which results a list showed and what you did with them, by position (for example: the third result was opened, the first was saved, a suggested source was cited). Each list gets a random id; the text of your search is not stored with it. We also keep the ratings you give (👍/👎 and reasons, “was this useful?”, the occasional 0–10 question), messages you send through “Feedback & support” with the page you were on and your browser name, and which days you used the app. If you tick “share my search text” on a rating, that search text is stored with it, encrypted, and only the Scienvera team can read it.
Billing
Your plan, credit balance and credit history. If you buy a plan, Polar (our merchant of record) takes the payment; we receive a customer reference and what you bought, never your card number.
Technical data
IP address, browser and device type, and request details, which our servers and Cloudflare process for security and rate limiting. See the cookie policy for what is stored in your browser.
We don’t ask for sensitive data (health, religion, ethnicity and the like). Please don’t put it, or other people’s personal data, into documents or prompts unless you have a lawful reason to.
3. Why we use it, and on what legal basis
| Purpose | Legal basis (GDPR · KVKK) |
|---|---|
| Create and run your account, workspaces and the tools you use; credits and plans | Contract · Art. 6(1)(b) GDPR, Art. 5(2)(c) KVKK |
| Keep the Service secure, prevent abuse and fraud, fix errors, improve reliability | Legitimate interests · Art. 6(1)(f) GDPR, Art. 5(2)(f) KVKK |
| Improve search ranking and the tools from what people use and rate; answer your support messages; see whether people come back | Legitimate interests · Art. 6(1)(f) GDPR, Art. 5(2)(f) KVKK |
| Keep the AI-help log of a project to build its verification report and declaration; give a copy of a report to a class’s instructors when you hand it in | Contract (a feature you use, at your request) · Art. 6(1)(b) GDPR, Art. 5(2)(c) KVKK |
| Keep a search text you chose to share with a rating | Consent (the box you tick) · Art. 6(1)(a) GDPR, Art. 5(1) KVKK |
| Keep records the law requires (invoices, answers to authorities), handle disputes | Legal obligation, legal claims · Art. 6(1)(c) and (f) GDPR, Art. 5(2)(ç) and (e) KVKK |
| Send you emails about your account (sign-in links, changes to these terms) | Contract · Art. 6(1)(b) GDPR, Art. 5(2)(c) KVKK |
| Transfer your data to providers outside Türkiye (see section 5) | Explicit consent under KVKK Art. 9 · for GDPR, the safeguards in section 5 |
We don’t send marketing emails, sell personal data, show ads, or use advertising or third-party analytics trackers. The usage records above stay on our own servers. We don’t make decisions with legal or similarly significant effects about you by automated means alone.
4. AI features
Some tools use large language models. When you use one, the text it needs (your question, the draft passages being checked, excerpts of papers or of your own documents) is sent to our AI provider to generate the answer. Your email and name are not sent. We don’t use your content to train AI models. Answers are produced by AI and can be wrong: check them against the sources.
5. Who receives your data
We use these providers. Each only gets what it needs for its job and works under a contract with us.
| Provider | What for | Which data | Where |
|---|---|---|---|
| OVH SAS | Servers and databases (hosting) | Everything stored in your account | Germany (Frankfurt) |
| Stytch, Inc. | Sign-in, sign-in emails, sessions | Email, name, workspace membership, sign-in and device details | United States |
| OpenCode (opencode.ai) | AI model access: summaries, draft checks, claim checks, reports | The text you send to an AI feature (questions, draft passages, document excerpts). Not your email. | United States and the model hosts it uses |
| Pinecone Systems, Inc. | Search index for relevance and for your uploaded documents | Search text and passages of documents you upload | United States |
| Backblaze, Inc. (B2) | Storage of files you upload | Uploaded files (such as PDFs) | European Union (Netherlands) |
| Cloudflare, Inc. | DNS, content delivery, protection against attacks | IP address and request details | Global network, United States |
| Polar Software, Inc. | Payments as merchant of record (only if you buy a plan) | Billing name, email, country, payment details (we never see card numbers) | United States / European Union |
Academic databases (OpenAlex, Crossref, Europe PMC, PubMed (NCBI), arXiv, DOAJ, DBLP) receive the text of your searches, never who you are. We may also disclose data where the law requires it, for example to a court or authority with a valid request.
Inside Scienvera: people you share a project with see it, including its AI-help log. In a class workspace, the admins see the reports you hand in, and the names and emails of the members who haven’t handed one in.
International transfers. Our servers are in Germany, and some providers are in the United States. For transfers out of the EEA/UK we rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission’s Standard Contractual Clauses. For transfers out of Türkiye we ask for your explicit consent under KVKK Art. 9, separately from accepting the terms.
6. How long we keep it
- Account and content: while your account exists. You can delete projects, lists, watches and files at any time.
- When you ask us to delete your account, we delete or anonymise your data within 30 days. Backup copies are overwritten in the normal backup cycle.
- Activity and security logs: only as long as needed for security, abuse prevention and credits.
- A project’s AI-help log: while the project exists. A handed-in report: until you or an admin takes it back, or the project or the workspace is deleted.
- Result usage records and the days you were active: two years, then deleted automatically. Ratings and support messages: while your account exists.
- Consent records and answers to data requests: for as long as we may need to show we acted lawfully.
- Billing records: as long as tax law requires.
7. Your rights
You can ask to access your data and get a copy, correct it, delete it, restrict or object to its use, receive it in a portable format, and withdraw consent at any time (this doesn’t affect what was done before). Under KVKK Art. 11 you can also learn whether and why your data is processed, who it was transferred to in Türkiye and abroad, ask that corrections and deletions be passed on to them, object to a result reached solely by automated analysis, and claim compensation for damage from unlawful processing.
Most of this is self-service in Settings → Profile → Privacy and your data: download a copy of your data, see and withdraw your consents, and ask us to delete your account. Otherwise, write to [email protected] from the address you sign in with. We answer within one month (KVKK: 30 days), free of charge.
You can also complain to a supervisory authority: in Türkiye the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu, kvkk.gov.tr); in the EU or UK, the data protection authority where you live or work. We’d appreciate the chance to fix things first.
8. Security
Data is encrypted in transit (TLS), access is limited to the people who need it, search text in activity logs is encrypted at rest, and admin access to sensitive records is logged. No system is perfectly secure; if a breach affects your data we will tell you and the authorities as the law requires.
9. Age
The Service is for people aged 16 and over. If you are under 18, use it with your parent or guardian’s permission. We don’t knowingly collect data from children under 16; if you think we have, contact us and we’ll delete it.
10. Changes
We’ll update the date at the top when this policy changes. For important changes we’ll tell you in the app or by email, and where consent is needed we’ll ask again.
See also: Terms of Service, Cookie policy, KVKK notice.
Questions about this page? Write to [email protected].