Last updated: 19 October 2026
Privacy policy
This policy explains how Kinju handles information when you visit kinju.in or use its personal assistant application.
Kinju is an independently operated project in private development. It is intended for the operator and invited testing, rather than general public use. Account-level separation of assistant data is still being completed. Do not use the development application for confidential information or information about other people without their permission.
For privacy questions or requests, contact bharat2491@gmail.com.
1. Information we collect
- Google sign-in information. When you sign in, Google provides basic profile information, including your name, email address, verification status, and Google account identifier. Kinju creates an application identifier and stores account and session information to recognize you and maintain your login. Kinju does not receive your Google password.
- Information you provide. Your messages, assistant responses, tasks, commitments, preferences, and records you enter, such as food or water entries, may be stored to provide chat history, planning, and tracking features. Relevant conversation information may also become ongoing context for later assistance.
- Connected-service information. Google sign-in alone does not grant access to Gmail, Calendar, or Tasks. If a separate integration is enabled and authorized, Kinju can retrieve information and perform actions within its granted permissions. The applicable connection and its data use must be explained before it is offered to users.
- Technical information. Hosting infrastructure receives information such as IP addresses, browser details, request times, and network requests. The application also produces operational information about errors, timings, and service activity.
2. How information is used
Kinju uses account information to authenticate access and maintain sessions. It uses the content you provide to generate responses, preserve conversation history, organize plans, maintain relevant context, and record or retrieve your entries. Where background features are enabled, stored information may also be processed outside an active conversation to update plans or review commitments.
Technical information supports operating the service, diagnosing failures, and protecting access. The current public website does not contain advertising or analytics scripts.
3. AI processing and Google Gemini
Kinju uses Google's Gemini API to generate AI responses. This sends your message and relevant context, which can include earlier conversation content, saved preferences, planning information, or results from authorized tools, to Google. Information included in that context is therefore processed outside Kinju's own application server.
The intended hosted configuration uses a Gemini API project with active Cloud Billing. Under Google's paid-service terms, prompts and responses are not used to improve Google's products. This does not mean zero retention: Google may retain prompts and responses for a limited period for safety, security, and legal purposes. If Google Search grounding is used, Google specifies a separate 30-day retention period for prompts, context, and outputs used by that feature. See the Gemini API terms.
This policy does not claim that all submitted content can be automatically identified or redacted as sensitive. Do not enter passwords, authentication tokens, payment-card details, raw private emails, or similarly sensitive records into the assistant.
4. Storage, service providers, and access
The hosted service uses Oracle Cloud infrastructure. When durable storage is enabled, account records, login sessions, chat history, and assistant records are stored in the configured PostgreSQL database. Information is not confined to your browser or device.
Optional integrations, external memory services, or diagnostic services can introduce additional processing and storage when enabled. This policy and the relevant in-app information must identify those services and their data use before they are offered beyond private development. A Gemini-only AI configuration does not by itself disable other configured integrations.
The operator can access server-side records for administration, support, security, and troubleshooting. Diagnostic settings can affect how much request or response content is captured; the development application should not be treated as an end-to-end encrypted or confidential messaging service. Providers may process information in countries other than your own.
5. Cookies and browser storage
The public homepage does not set application cookies or use browser storage. The assistant application uses a session cookie to keep you signed in and a security cookie to help protect requests from forgery. It also stores interface preferences, such as appearance, in browser storage. Blocking these mechanisms may prevent login or other features from working.
6. Retention and deletion
Persisted chat history currently has a 14-day inactivity expiry. Cleanup happens when the application accesses or lists the relevant conversations; it is not a guarantee that every copy is erased exactly 14 days after the last message. Separate account records, extracted context, planning and tracking records, backups, and provider-held copies are not all covered by that chat-history expiry.
There is currently no uniform automatic deletion period for all assistant data. Some undo or removal controls hide or mark a record as removed while retaining the underlying record. Signing out ends your session; it does not delete your account or assistant records. Removing Google access stops future authorized access but does not automatically erase previously stored information.
To request access, correction, or deletion, email bharat2491@gmail.com and describe your request. Requests are handled manually, and we may need to verify your identity. Do not include passwords or other secrets. We will explain any relevant limitations, including records held by external providers or retained in backups, rather than promise immediate deletion from every system. There is no automated account-deletion workflow in the current version.
7. Your choices
You can choose not to sign in, stop using the application, sign out, and request changes or deletion using the contact above. You can also review or revoke Kinju's permissions through your Google Account connections. Revoking access may prevent connected features from working. Rights that apply to your information may depend on where you live.
8. Changes to this policy
As Kinju develops, its features and data handling may change. This page will show the updated date. Changes involving additional Google data or a new use of that data require updated disclosures and, where required, renewed permission before that use begins.