Privacy Policy

Knite is responsible for the personal data described in this policy. For privacy questions or requests, email info@kniter.io. We may need to verify your identity before completing a request.

• Account and authentication data: email address, account ID, login method, session information, and basic profile information supplied by Google or Facebook, such as name, profile image, provider account ID, and email. We do not receive your Google or Facebook password.
• Threads connection data: when you choose to connect Threads, we may process your Threads account ID, username, display name, biography, profile image, verification status, public posts, replies, engagement metrics, insights, and the permissions granted to Knite.
• Workspace content: profile settings, drafts, scheduled content, watchlists, research queries, imported or synchronized posts, analytics, performance snapshots, notes, preferences, and other content you submit.
• AI feature data: prompts and the limited account, content, and performance context needed to produce a requested draft, idea, or reply.
• Technical and security data: IP address, request time, browser or device information, error and security events, and necessary browser storage used for sessions, OAuth integrity, and preferences.

• create and secure your account and keep you signed in;
• provide, synchronize, and maintain the workspace features you request;
• generate analytics, recommendations, drafts, ideas, and human-reviewed replies;
• connect to Google, Facebook, Threads, and other services at your direction;
• detect abuse, investigate errors, protect users, and enforce service rules;
• communicate about authentication, security, support, and material service changes;
• comply with legal obligations and establish or defend legal claims.

Where applicable, our legal bases are performance of our agreement with you, your consent, our legitimate interests in operating and securing Knite, and compliance with legal obligations. You can withdraw consent for a connected service by disconnecting it or revoking access with the provider.

Google and Facebook sign-in are used only to authenticate you, create or locate your Knite account, prevent account duplication, and display basic account information. Knite requests only identity-related permissions such as OpenID, email, and public profile. We do not use this information for advertising, sell it, or access your contacts, friends list, private messages, birthday, or gender.

Our handling of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements where applicable. Google and Meta may process information independently under their own privacy policies.

We do not sell or rent personal data. We share data only as needed with:

• Supabase: authentication, database, and session infrastructure;
• Google and Meta: authentication and provider features you choose, including Facebook Login and Threads connections;
• DeepSeek: prompts and limited workspace context when an AI-powered feature is requested and the provider is configured;
• Hosting and security providers: infrastructure, delivery, monitoring, and incident response;
• Authorities or transaction parties: when required by law, needed to protect rights and safety, or involved in a legitimate corporate transaction.

Providers receive only the information reasonably necessary for their role and may process data in countries other than yours. Where required, we use recognized safeguards for international transfers.

Knite uses necessary browser storage and similar technologies to maintain your session, complete secure OAuth flows, remember preferences, and protect the service. The current application does not use third-party advertising cookies or a Meta Pixel.

We generally keep account and workspace data while your account is active and as reasonably necessary to provide the service. Connected-account credentials are retained until you disconnect the account, revoke access, or request deletion, subject to security, backup, dispute, and legal-retention needs. Security records are kept only as long as reasonably necessary for protection and investigation.

We use access controls, encrypted transport, restricted server credentials, scoped authorization, and database row-level security to protect personal data. OAuth provider secrets are not placed in the browser. No system is completely secure, so we cannot guarantee absolute security.

Depending on your location, you may have rights to access, correct, delete, restrict, or receive a copy of your data; object to certain processing; withdraw consent; and complain to your local data-protection authority. Knite's analytics and AI suggestions do not make legal or similarly significant decisions about you, and publishing remains subject to human review.

Send requests to info@kniter.io. To disconnect Threads or request removal of connected Threads data, follow our data deletion instructions. You can also revoke Google or Meta access from the provider's account settings.

Knite is not directed to children under 13, or under a higher minimum age where local law requires it. If you believe a child has provided personal data, contact us so we can review and delete it where appropriate.

We may update this policy as the service, providers, or legal requirements change. We will post the updated version here, revise the date above, and provide additional notice when a change is material and applicable law requires it.

Privacy questions and requests: info@kniter.io
Website: kniter.io