Privacy Policy

Kognilo is responsible for decisions about processing personal data in the service available at kognilo.com. Questions, requests, and privacy communications can be sent to contact@kognilo.com.

• Account and authentication data, such as name, email, profile image, OAuth provider identifiers, sessions, and technical tokens when needed to authenticate or link the account.
• Contact data provided during signup, such as name, contact email, and optional phone number.
• Learning profile data, including area, seniority, context, motivation, deadline, routine, language, and time zone.
• Learning content, such as goals, materials and documents sent when creating paths, diagnosis answers, paths, units, attempts, evidence, mastery, reviews, and unit conversation questions.
• Learning notes, annotated excerpts, links, and competency associations that you create or select. Notes are personal material and do not constitute mastery evidence.
• Final-assessment data, when requested, such as open answers, rubrics, structured evaluations, derived evidence, and reports or translations you choose to generate.
• Payment and credit data, such as balance, ledger entries, customer and subscription identifiers, and event confirmations. Kognilo does not store the full card number.
• Technical data needed for security and operation, such as session data, internal identifiers, sanitized error codes, environment, version, and permitted operational metrics.
• If you enable reminders, your browser provides a Web Push subscription and the device's IANA timezone. The endpoint is indexed by hash and the subscription payload is encrypted; these values are not shown in screens, logs, or telemetry.

When you choose “Continue with Google,” Kognilo requests only the basic information needed for authentication, usually your name, email address, profile image, and Google account identifier. We do not request access to Gmail, Google Drive, contacts, calendar, or content from other Google services.

This data is used to create or find your account, enable sign-in, maintain your session, and protect the service against abuse. Your account email may be shared with Stripe if you start a purchase or subscription. Google identity data and OAuth tokens are not sent to OpenAI or used for advertising.

Our use of information received from Google APIs follows the Google API Services User Data Policy, including applicable limited-use requirements.

• Create, authenticate, and protect your account and sessions.
• Personalize diagnoses, learning paths, units, and reviews.
• Generate grounded content, answer questions, evaluate a requested final submission, and record learning evidence.
• Process purchases, subscriptions, credits, and cancellations.
• Prevent fraud, investigate failures, and maintain service security and availability.
• Comply with legal obligations and exercise rights in proceedings.

Depending on the activity, processing may rely on providing the requested service, complying with a legal obligation, legitimate interests related to security and product improvement, or your consent when required.

The OpenAI API receives only the context explicitly necessary for the requested use case. This may include goals, answers, criteria, queries, sources for grounded generation, and the Markdown of documents you send to a path when the requested step uses them; selected notes, open answers, and rubrics are sent only when you choose an action that uses them. In a unit conversation, we send only the title, goal, question, any selected excerpt, and the applicable recent portion of history; we do not automatically send your entire notebook. OAuth tokens, payment data, and credentials are not part of this context.

Kognilo uses automation to recommend content, reviews, and mastery states. These outputs may contain errors and should be considered in an educational context. You can request information or a review by email.

• Neon, for the database, identity, sessions, and account content.
• Google, GitHub, and Better Auth, for authentication and session protection.
• OpenAI, only for explicitly requested generation, grounding, or evaluation and with the necessary context, including notes, open answers, or rubrics only when applicable.
• Stripe, for checkout, payments, subscriptions, and fraud prevention.
• Cloudflare, for hosting, delivery, queues, and network security.
• Sentry, only for sanitized errors and operational data, without prompts, responses, notes, rubrics, reports, cookies, tokens, or user identity.
• PostHog, only after consent and with a pseudonymous identifier, for permitted operational events and manual pageviews, plus low-sample Session Replay with masked text, inputs, and private content, without cookies, headers, tokens, or query strings.

We use cookies that are strictly necessary for authentication, security, language, and session continuity. We do not use behavioral advertising cookies. You can block cookies in your browser, but authenticated parts of the service will stop working.

We apply server-side access controls, ownership validation, secure cookies, encryption at rest for learning profiles and Web Push subscriptions, and data minimization in logs. The service worker does not keep offline caches of authenticated HTML, APIs, or private content. No system is completely immune to incidents, but we apply measures proportionate to the risk and restrict access to data.

While your account is active, we preserve progress, notes, conversations, path context documents, drafts, attempts, evaluations, and reports to maintain the experience. Reports already obtained remain readable and exportable after subscription cancellation; cancellation is not deletion. You can delete your account in Settings. The flow cancels an active subscription before removal and cascades deletion of associated local data, including Web Push subscriptions and deliveries, identity, sessions, goals, paths, documents, notes, evidence, conversations, drafts, attempts, evaluations, reports, and executions.

The external Stripe customer is not automatically deleted and may remain according to the processor’s legal obligations and policies. Backups and minimal records may also remain for their respective legal or operational periods. Additional requests can be sent to the contact listed in this policy.

Under applicable law, you may request confirmation and access, correction, information about sharing, portability when regulated, objection, withdrawal of consent, anonymization, blocking or deletion, and review of automated decisions that affect your interests.

Send requests to contact@kognilo.com. We may ask for information to confirm your identity and protect the account. If you cannot exercise your rights directly with us, you may contact the Brazilian data protection authority or consumer protection agencies.

This policy may be updated to reflect changes to the product, providers, or law. The current version and last-updated date will remain published on this page. Material changes will be communicated appropriately within the service.