Türkçe
English
A structure designed for institutions
The access model, user verification and panel experience are shaped around centralized service delivery within the institution.
Universities and libraries
Benefits for Institutions
A nine-portal translation and proofreading service, a single entry point, institutional licensing and our data-protection approach, summarized on one page.
Why for your institution?
Libraries and research units are the first stop for researchers working with sources in different languages. Instead of scattered translation subscriptions, separate OCR software and individual proofreading tools, offering a licensable, manageable platform organized by language family fits the library service model.
- A single entry point for researchers and students
- Modern, historical and ancient languages on one platform
- Institutional management, licensing and access control
- Transparent privacy, KVKK/GDPR and usage policies
Engine selection criteria
The translation, OCR and transcription engine used in each portal is not chosen at random. It is evaluated for academic suitability against the criteria below.
The best engine for each language family
The strongest engine is chosen for each language: DeepL for widely used modern languages, Google for Turkic languages, OpenAI and Transkribus for Ottoman Turkish and ancient languages.
Built for institutions
Institutional accounts, central access and campus-wide usage scenarios are taken into account.
Access through a single platform
Users progress from a single panel instead of scattering across separate translation, OCR and proofreading sites.
Organization by language and task
Tools are grouped into portals by language family and task (translation, transcription, OCR, proofreading), not by brand.
Institutional management and licensing
Licensing, credits/usage, and authorization must fit institutional procurement and oversight.
Single portal
Portals, the full tool list and history share one session, reducing account and subscription fragmentation.
Organization by language family
Users ask “which language, which task?” rather than “which brand?”.
Institutional management and licensing
A manageable licensing model matters for libraries making purchase decisions.
- Usage rights can be defined for the institution
- Central credit / usage tracking is supported
- Access can be verified via institutional email or domain
- Support and requests can run through institutional channels
Platform coverage: portals
Nine portals organized by language family and task, each with translation, OCR and proofreading tools.
Portallar
Çalıştığınız dile ve işe göre dokuz portal.
Privacy, compliance, and policies
Library procurement needs a clear data-protection and usage frame. The sections below summarize the approach; binding text lives on the legal pages.
Data privacy
Account and usage data are protected against unauthorized access. The platform manages sessions with security headers and access controls. Purpose limitation applies when processing sensitive content.
GDPR alignment
In line with European data-protection principles: lawfulness, transparency, purpose limitation, and data minimization. Data-subject requests are handled within the legal framework.
KVKK alignment
Under Turkey’s Personal Data Protection Law (KVKK), notice, processing grounds, and data-subject rights are described in the privacy policy.
Processing of user data
Identity, contact, and usage records are processed for service delivery, security, billing/credit tracking, and support. Scope and retention principles are stated in the privacy notice.
AI usage policy
Tools support academic production; accuracy and ethical use of outputs remain the user’s responsibility. Institutions continue to apply their own academic integrity rules.
Copyright approach
Rights in content uploaded or entered by users remain with users / rightsholders. The platform does not claim ownership beyond what is needed to provide the service; lawful use of third-party content remains the user’s duty.
Content selection policy
Tools added to the catalog are assessed for contribution to academic workflows, usability, and fit for institutional delivery. Integrations that do not fit the service model are not kept in the catalog.
Detailed legal texts: Privacy Policy, Terms of Use
Let's talk about your institution
Contact us for institutional licensing, access models, and campus-wide use.