What Lekta stores, and what it does not
Lekta reads public pages and grades them. It needs very little about you to do that, so this page is short: the data it holds, how long it holds it, the legal ground under KVKK and GDPR, and the terms of using the beta.
Every record, and how long it lives
What Lekta never collects
Legal basis and roles
Lekta processes personal data as the data controller — the role KVKK calls veri sorumlusu — and that controller is TECNONEST. For account records and audit history the ground is KVKK m.5/2-f — legitimate interest in operating and securing the service — and Article 6(1)(f) GDPR for visitors in the EU. Signing in with an e-mail address is a contractual necessity under KVKK m.5/2-c: without it there is no account to keep history for.
No consent-based marketing processing happens, because there is no marketing processing. No profiling, no automated decisions with legal effect, and no special-category data are involved. The pages you submit are public documents fetched over HTTP; Lekta treats their content as content, not as personal data about you.
Where the data sits
The application and its database run on our own server and reach you through Cloudflare’s network. Three processors are involved: Cloudflare, as the proxy in front of the site and the Turnstile bot check on anonymous audits; Mailjet, which delivers sign-in links and notification e-mail; and Ahrefs Analytics, a cookieless visitor measurement script that receives page-view events. Each is bound by its data-processing terms; a current list is available on request.
Exercising your rights
Terms of using the beta
The service is free and provided as it is, without a service level, an uptime promise or a warranty that a grade is fit for any particular decision. A grade describes what the engine measured at a moment in time; it is evidence, not advice, and it is not a search-ranking prediction.
Audit public pages only. Do not use Lekta to probe systems you have no right to test, to route load at a third party, or to work around another site’s robots.txt — how LektaBot treats it is documented at /bot, and there is no bypass. Automated submission outside the documented limits, and resale of the free tier as your own product, both end in the account being closed.
Reports are yours to share; the wording of the findings and this design are ours. Turkish law applies, and Istanbul courts have jurisdiction. If a clause turns out to be unenforceable, the rest stays in force.