Your data, with a clear purpose.

What information is processed?

Only your verified email address and stable Google account identifier are used. Your name and profile photo are neither used nor stored. You enter your phone number yourself. Only its format is checked: no SMS, email code or call is sent. Ownership of the number is not verified.

Purpose and protection

This information is processed to create your assistant account, recognize returning users, contact you when needed and prevent abuse. Email and phone details in the server account file are encrypted with AES-256-GCM. Only a keyed hash of the Google identifier is saved. Keys are kept separately in the server environment.

Sessions and daily allowance

A secure HttpOnly session cookie remembers your browser; JavaScript cannot read it. It contains no email or phone number. Its 400-day lifetime renews with use. Each account receives 3 model answers a day, resetting at midnight in Istanbul. Off-topic and personal-history questions do not consume this allowance.

Preventing abuse

A keyed hash of the IP address is kept for up to an hour for login attempts and until the end of the Istanbul calendar day for account creation limits. Raw IP addresses are not written to the account file. Usage counts reset when the day changes. Hashes of used security challenges are retained for five minutes. Hosting connection logs must be considered separately.

What reaches the AI provider?

Your Google sign-in details, registered email, phone number and account identifier are not sent to DeepSeek. When the live model is enabled, your question, up to four recent messages and site notes are processed. Questions containing an email or phone number do not trigger a model call; identifiable contact details are removed from prior messages. Do not put personal or sensitive information in the chat. Conversations are not persistently stored on the server.

Retention and deletion

Account details remain until you delete the account. “Delete my data and sign out” in the assistant immediately removes your account, sessions and associated usage from the active file. Short-lived abuse counters expire separately. If the operator keeps backups, its deletion and backup retention policy must also reflect this requirement.

Services and data controller

Google sign-in and Cloudflare Turnstile may process connection details to provide their services. Cenk Akkaya is the data controller. Use the contact page for data requests and questions. Notice version: 27 October 2026.

Contact · Terms of use

Google privacy policy · Cloudflare privacy policy

FIND THE FUTURE YOU’RE CURIOUS ABOUT.

Explore projects, articles and Cenk’s story. ESC to close.