Privacy Policy

Last updated: October 19, 2026

This policy describes how Khyoot and the Khyoot New Tab browser extension handle information. For privacy questions or account-deletion requests, contact ahmedelswerkey@gmail.com.

Browser extension

Khyoot New Tab replaces your new-tab page by navigating to your configured Khyoot website. It stores that website address in your browser’s local extension storage. It does not copy passwords, authentication tokens, or workspace contents into extension storage, and does not request access to browsing history, cookies, or other tabs’ contents. The website handles sign-in and synchronization after navigation.

Account and workspace information

Khyoot uses Firebase Authentication to manage sign-in. Depending on your sign-in method, account information can include your email address, phone number, display name, provider information, and account identifier. Authentication credentials are processed by Firebase.

Content you save—including ideas, tasks, projects, courses, notes, links, statuses, schedules, preferences, and work recordings—is stored in Firebase Firestore. Khyoot uses it to display your workspace, calculate summaries, and synchronize changes across your sessions and connected clients.

The website stores preferences such as language and appearance locally. Firebase may persist authentication state in your browser to keep you signed in. Browser storage may also contain earlier locally saved notes.

Optional features

• Editor integration: If you connect the Khyoot editor extension, work recordings and live session information are synchronized with your account to display activity and totals.
• Telegram: If you link Telegram, linking identifiers and messages you send to the bot are processed to create workspace items and provide the integration.
• Notifications: If you enable reminders, push-subscription information is used to deliver notifications. Notifications can display reminder content on your device.
• Sharing: If you share an item, its shared content becomes accessible through the sharing link. Recipients may retain copies.

Search and service providers

Submitting the new-tab search form sends your search terms to Google Search. The form does not save those terms in your Khyoot workspace. Google processes searches under its own privacy policy.

Google Firebase provides authentication and database services. The hosting provider serving your Khyoot website may process standard connection information such as IP addresses, request URLs, browser information, and service logs. The website also requests fonts from Google Fonts. Optional integrations communicate with their respective providers.

See Google’s Privacy Policy, Firebase privacy information, and, if you use Telegram, Telegram’s Privacy Policy.

Use and disclosure

Information is used to authenticate users, provide requested workspace and integration features, synchronize records, and operate and troubleshoot the service. Khyoot does not sell personal information or use workspace content for advertising. Information is shared with service providers as needed to deliver these features, with recipients when you choose to share, or when legally required.

Retention, deletion, and your choices

Saved cloud information remains available until deleted. You can edit or delete workspace items and export supported workspace data from the app. You can unlink Telegram, revoke notification permission in your browser, sign out, and clear local site data. Clearing browser storage or removing an extension does not delete your cloud account or workspace.

To request account deletion, email ahmedelswerkey@gmail.com. Account deletion is not currently available as a self-service button. We may need to verify account ownership before acting on a request. Service-provider logs and backups may have separate retention periods; deletion does not necessarily remove those copies immediately.

Security and changes

Khyoot uses authenticated access and database access rules to restrict private workspace data. No online service can guarantee absolute security. This page will be updated when the described practices change, with the revision date shown above.