Privacy Policy

1. Who controls your data

Kono'S is operated by 通用創新有限公司 (General Revolution Corporation), Taiwan (company no. 60545939; 3F.-5, No. 9, Zhuangjing 6th St., Shixing Village, Zhubei City, Hsinchu County, Taiwan). We handle the personal data described here. If you use Kono'S for an organisation, that organisation may also determine how workspace content is used. Contact us at seanlin@generalrev.com for privacy questions or rights requests.

2. Data we process

Storage in your browser

The following items are stored by the Kono'S pages in this browser's site storage. Preferences and feature state are optional; entries needed for a particular action are identified below.

• konos_site_lang, konos-name, konos-ob, konos-cancel-feedback, konos-ios-install-offered and konos-tpl-offered-{workspaceId} remember the selected site language, cached display name, onboarding completion and whether optional prompts were shown. They are not required for core app use.
• konos-ws-current remembers the last workspace selected in this browser. konos-join temporarily keeps an invitation's workspace ID, account ID and timestamp across sign-in or reload; it expires after seven days and is needed only to continue that invitation.
• konos-push, konos-push-off and konos-push-asked remember this browser's push registration and prompt or opt-out choice; they are only for optional push notifications. konos-file-consent remembers acknowledgement of the first-upload notice; its consent timestamp is also saved with the account. konos-tpl-shares-{date} counts template shares for the daily feature limit.
• konos-ck-{widgetTitle}-{date} stores checklist ticks and konos-cv-{uid}-{canvasId}-v{version} stores custom canvas widget state on this device. These are optional local progress; clearing them loses that device's saved state.
• konos-privacy-export:{uid}:{scope}:{workspaceId-or-self} stores an export job ID and scope so this browser can resume checking a background export after reload. The export job itself is kept server-side.
• Older installs may still have otto-* entries. During upgrade the app copies a value to the matching konos-* key if that new key is absent; it does not remove the old entry.
• Only when account compatibility migration is enabled, konos-compat-client:{targetProject}, konos-compat-receipt:{targetProject}, konos-compat-drain:{targetProject}:{uid}:{clientId} and konos-compat-drain-proof:{targetProject}:{uid}:{clientId} hold a client ID, migration receipt and progress/completion markers. They are needed only for that migration flow.

sessionStorage holds konos-oauth-redirect-pending while sign-in returns from an OAuth redirect, konos-link-oauth-pending while an account-linking redirect completes, and konos-aha-view briefly to highlight a just-opened view in the current tab. The OAuth markers are needed only to finish those flows; the highlight is optional.

In hosted mode, Firebase Authentication can persist sign-in state in browser storage, including IndexedDB where supported, and Firestore can use an IndexedDB cache for offline work. The browser and SDK choose the available persistence backend.

In self-hosted LocalStore mode, konos-localdb-session in localStorage holds the account ID and email, ID token, refresh token and session generation. It is needed to keep you signed in and authorize requests to that instance; clearing browser site data signs you out.

Browser storage is separate from account data saved for the instance. When you use a feature, related information may also be sent to the Kono'S service handling that instance, as described above. Clearing browser storage resets local preferences or sign-in state; it does not delete account data stored by that service. SDK-internal storage keys are disclosed by category and purpose rather than listed one by one.

We do not sell product content or use it to train our own models. We process personal data to provide and maintain Kono'S, secure accounts, handle integrations and payments, diagnose failures, comply with law, and respond to users' requests.

3. Shared workspaces need shared judgment

Workspace members can see shared messages and content. Depending on their role, owners or admins can manage membership, agents, approvals and exports. A member's contribution may remain in the shared workspace after that member leaves because it is part of the team's record. Do not place another person's personal or confidential data in a workspace unless you are authorised to do so. Contact us if a personal rights request involves content held in someone else's workspace.

4. AI services and your connected subscription

Kono'S is designed primarily to use the AI subscription you connect yourself. When you connect Claude Code or Codex through a Kono'S Connector, your prompt, relevant Kono'S context and tool results needed for the request are sent to the selected AI service under that provider's terms and your account settings. If you select another available route, request data may instead be processed by Google Vertex AI (including Gemini), Microsoft Azure OpenAI, Anthropic, OpenAI or an OpenAI-compatible provider. We send the information needed for your request, not your entire account on every turn.

If you configure an API provider, Kono'S uses the credentials and settings you provide to make the requests you select. Credentials are handled separately from prompt content and are used only for the selected provider calls.

The AI service you select receives request data under its own privacy, retention and model-training terms. Review those terms and settings; Kono'S does not control a provider's handling of data after it receives a request.

5. Live Browser profiles and third-party sites

When you sign in to a third-party website in Live Browser, you enter your password on that website through the browser; do not paste passwords into Kono'S chat. The website may store its own cookies or other browser data. If enabled for your account, Live Browser may retain a browser profile, including session cookies and local storage, between runs. Page content, screenshots and requested actions may be sent to the AI service selected for that turn.

Persistent Live Browser profiles will be offered only after profile isolation and deletion controls are ready and enabled for your account. When enabled, account deletion removes profile data held by Kono'S. Third-party websites keep their own copies under their terms; you may need to delete cookies or revoke sessions there as well.

6. Service providers and other recipients

Third-party websites, MCP servers, calendars and locally connected agents are independent recipients. They receive information when you connect them or authorise access; their own terms apply.

7. Storage location and international transfers

Kono'S hosted Cloud Run and GKE services and its Firestore (default database) are in Google Cloud us-central1, United States. The Firebase JavaScript SDK used by the browser is served from Google's www.gstatic.com; the delivery location for static SDK files may differ. See Firebase data storage and processing locations.

AI services, Cloudflare, payment providers and websites or integrations you connect may process data in other countries, depending on the service you select and its terms. Review each service's data-location and privacy settings before connecting it.

8. Export

Settings can request a background export for your personal account. Workspace owners and admins can request one for a shared workspace. The worker builds a private ZIP containing the tenant root, the known product collections (including tasks, notes, messages, memories, routines, files, public-page data, notifications, approvals and task events), plus actual user-file objects stored under that scope. It removes credential fields, encrypted secret material, private calendar-feed links and other access tokens.

The export does not include the credential vault, browser profile/cookies, Firebase Authentication security records, provider-side data, global billing/legal records or unrelated workspaces. The download link is private and short-lived. For a broader access or portability request, contact us rather than assuming the in-app ZIP is the complete response.

9. Deletion and retention

Account deletion is a resumable server job. It removes tenant subcollections and task history, stored files and upload requests, published-page registry entries, workspace-join requests, export archives and job records, and vaulted credentials before removing the tenant root. Shared workspaces you solely own must be explicitly confirmed for deletion; a shared workspace with other members must be transferred or separately deleted. The Firebase Authentication user is removed after the product-data purge succeeds.

Waitlist emails are used only to announce the launch and are deleted 90 days after the announcement. You can ask us to delete your email sooner using the contact above.

Deletion is not an unconditional promise that every record disappears immediately:

• Billing records needed for tax, accounting, fraud prevention, chargebacks or legal claims may be retained for as long as those purposes or applicable law require.
• Provider backups and point-in-time recovery may retain deleted data until the configured recovery window expires.
• AI providers, connected services and third-party websites may retain data under their own terms. You may need to exercise rights with them as well.
• Persistent Live Browser profiles will be offered only after isolation and deletion controls are ready and enabled for your account.

We retain operational logs and export-job information for as long as needed to provide the service and maintain security. Transaction records may be retained for tax, accounting or legal claims. The right to erasure can have legal exceptions; see the European Commission's official explanation of erasure and its limitations.

10. Your choices and rights

Depending on where you live, you may have rights to be informed, access data, correct it, request erasure or restriction, object to certain processing, receive portable data, withdraw consent, and complain to a data-protection authority. The European Commission explains these rights in its information for individuals and explains the conditions for data portability.

To make a request, email seanlin@generalrev.com with your account email and enough detail to locate the data. We may verify your identity before acting and will respond within the period required by applicable law. If we cannot fulfil a request, we will explain why.

11. Security, children and changes

We use reasonable technical and organisational measures to protect data, including encryption in transit and at rest, tenant-scoped access controls, least-privilege service accounts, secret redaction, short-lived download links and approval steps for sensitive actions. No system is perfectly secure; report a suspected privacy or security issue using the contact above.

Kono'S is not intended for children under 18 or below the minimum age required to consent to online services where they live. Contact us if you believe a child provided personal data.

We will update this notice if our service or data practices materially change. The current version and its effective date appear at the top of this page.

Last reviewed 2026-09-30. Product features and provider terms can change; this page states our current privacy practices.