Spark KNE Verify Privacy Policy

The product interface is moving to English. Data handling and privacy choices are unchanged by this language update. Previous bilingual notice

Last updated: September 17, 2026

Spark KNE Verify provides user-initiated knowledge assessment through browser extensions and approved platform integrations. This page is static HTML so platform reviewers and users can read the full policy without running JavaScript. It explicitly describes data collection, processing and use, storage and retention, sharing and disclosure, user deletion, contact, and security.

Chrome Web Store Review Summary

• Collection: Spark collects account email, account ID, authentication state, anonymous trial identifier, usage quota, selected verification text, source page URL, page title when available, source-platform label, client channel, contribution content, feedback, blocking issue reports, consented interaction events, aggregate homepage install-link clicks, timestamps, trust-state results, review status, quota counters, diagnostic events, IP address, user-agent, and operational logs.
• Processing and use: Spark uses this data for login, beta access, anonymous trial verification, authenticated API calls, selected-text verification, source/evidence comparison, trust-state output, consented interaction-funnel measurement, aggregate install attribution, optional Verify history, contribution review, feedback review, issue debugging, quota enforcement, reliability, security, fraud prevention, and abuse prevention.
• Storage: Chrome extension storage is used for local settings, language, anonymous trial identifier, authentication token, account state, usage display, selected-text drafts (including text typed but not yet submitted), source-page context, latest verification state, consent state, interface preferences, and a temporary retry queue for consented interaction events that failed to reach Spark. Spark servers store account, anonymous trial usage, Verify history, contribution, feedback, issue report, quota, review, analytics, source gap, and operational records.
• Sharing: Spark does not sell, rent, trade, or share user data with advertisers or data brokers. Data is sent only to Spark-controlled services at https://knespark.com and infrastructure providers needed to host, secure, monitor, back up, and operate the service.
• Deletion: logout clears stored authentication tokens and the latest result, but does not erase all local data. Remove the extension or clear its browser storage to erase local drafts, source context, settings, consent, and queued events. Server-side deletion requests can be sent to seth@knespark.com.

Prominent Disclosure and Consent

• Spark sends data for verification only after you take an explicit action, such as selecting text and clicking Verify, using the context menu, copying a feedback package, reporting a blocking issue, or submitting a contribution.
• The current Chrome and Edge extensions show a data-use disclosure, privacy-policy link, and consent checkbox before anonymous trial verification, interaction analytics, login, registration, authenticated verification, feedback, issue reporting, debug-token saving, or KNE contribution can send data.
• By using anonymous trial Verify, signing in, using Verify, Submit to KNE, feedback, or issue reporting, you consent to the collection, use, storage, and sharing described in this policy.

OpenAI and Coze Platform Integrations

• When you explicitly invoke Spark KNE Verify inside an approved OpenAI or Coze experience, that platform sends the claim text and optional source URL you provided to Spark over HTTPS. Spark returns the trust state, explanation, evidence counts, and public source references to the same platform.
• The current OpenAI integration is anonymous and read-only. It does not request an OpenAI account identifier, Spark account, Verify history, contribution access, or KNE write permission.
• The current Coze integration uses a server-held platform key that is not exposed to end users.
• Spark applies Redis-backed platform quotas and may process IP address, User-Agent, request time, endpoint, status, source platform, client channel, optional source URL, and a limited claim excerpt in operational verification records for quota enforcement, security, debugging, service measurement, and abuse prevention.
• OpenAI and Coze independently process the conversation and returned tool result under their own privacy terms. Spark does not send platform-integration data to advertisers or data brokers.

Data We Collect

• Account data: email address, account ID, plan type, public beta status, quota state, login state, and role.
• Anonymous trial data: a locally generated anonymous trial identifier, hashed server-side identifier, anonymous trial quota state, and anonymous verification usage. Anonymous trial data is not counted as a registered public beta user.
• Authentication data: access tokens stored in Chrome extension storage and sent to Spark over HTTPS for authenticated API requests.
• Website content and personal communications: only the text you actively select or submit for verification, including AI chat text or other conversation text if you choose to verify it, plus source page URL, page title when available, and source platform label such as ChatGPT, Qwen, Claude, Doubao, Gemini, or web. Technical request metadata also identifies the client channel, such as Chrome extension, Edge extension, OpenAI MCP, or Coze plugin.
• User activity: Verify requests, contribution submissions, feedback submissions, blocking issue reports, interaction events, timestamps, quota counters, trust-state results, source hint counts, review status, and diagnostic events needed to operate the beta.
• Consented interaction analytics: after consent, Spark records extension open, selection captured, Verify clicked, verification result viewed, source-details opened, public evidence link opened, and first Verify outcome. Interaction metadata contains the entry point, selection presence, a coarse text-length bucket, request identifier, trust state, verification context, evidence group, and list rank as applicable; evidence-link events do not include selected text, source title, destination URL, or page URL.
• Homepage install attribution: clicking an install link on knespark.com records only the site locale, link placement, and campaign tags. This event does not include selected text or an account identifier.
• User-provided content: source URLs, source hints, corrections, challenges, notes, feedback text, issue report text, and selected text that you choose to submit.
• Location data: Spark does not collect GPS, precise location, or address data. Server and security infrastructure may process IP address as operational log data for security, reliability, fraud prevention, abuse prevention, and troubleshooting.
• Technical and operational data: client channel, extension or integration version, manifest version, build ID, package timestamp, request time, endpoint, status code, error category, IP address, user agent, security logs, and abuse-prevention signals.

How We Use Data

• To provide anonymous trial verification before login, limited to a small quota window.
• To authenticate your account and keep you signed in.
• To verify selected text against KNE sources, evidence candidates, trust policy, and review rules.
• To return trust states, source details, evidence gaps, and risk warnings.
• To store optional Verify history and help you revisit past verification results.
• To operate beta quotas, detect abuse, debug errors, monitor reliability, and improve the product.
• To measure consented interaction events and recover their delivery after temporary network failures.
• To review user-submitted sources, corrections, challenges, feedback, and issue reports.
• To measure aggregate public beta behavior such as activation, repeat Verify rate, source gaps, and blocker trends.
• To measure aggregate homepage install attribution across entry points and campaigns.

How We Store and Retain Data

• Local storage: the extension stores API settings, UI language, anonymous trial identifier, authentication token, account state, usage display, selected-text drafts (including text typed but not yet submitted), source-page context, latest verification state, consent state, interface preferences, and a temporary interaction event retry queue in Chrome extension storage.
• Retry queue: if a consented interaction event cannot reach Spark after a temporary network failure, the extension may retain up to 30 event records locally for retry. These records contain event type, source-platform label, client channel, extension version, event identifier, and interaction metadata; they do not contain selected verification text or a page URL. Delivered records are removed; older records are removed when the queue limit is reached.
• Server storage: Spark servers may store account records, anonymous trial usage records, Verify history, contribution records, feedback, issue reports, quota counters, review status, analytics events, source gap tasks, and operational logs.
• Retention: account, Verify history, contribution, feedback, and issue report records are retained while your beta account is active or while needed to provide the service, review contributions, improve KNE quality, ensure security, resolve disputes, prevent abuse, or meet legal obligations.
• Operational logs are retained only as long as needed for reliability, debugging, security, abuse prevention, or legal obligations.
• Logging out clears authentication tokens and the latest result; local drafts and settings remain. Clear the text field to erase its draft, or remove the extension or clear its browser storage to erase all local extension data.

Sharing and Disclosure

• Spark does not sell, rent, or trade user data.
• Spark does not share selected text, account data, authentication data, Verify history, feedback, or contributions with advertisers or data brokers.
• Data is transmitted to Spark-controlled services at https://knespark.com.
• For an approved OpenAI or Coze integration, Spark receives the user-requested claim from that platform and returns the resulting trust state and public evidence references to the same platform. Spark does not forward that claim or result to unrelated platforms.
• Current infrastructure processors include Vultr cloud servers and the browser/Chrome extension storage environment controlled by the user. These processors may handle data only as needed for hosting, database operation, HTTPS delivery, logging, security, monitoring, backup, and service reliability.
• Reviewed contribution content may be used inside KNE source and evidence workflows, but it does not directly modify KNE Core data without review.
• Spark may disclose data if required by law, security investigation, abuse prevention, dispute resolution, or to protect the service and users.

Limited Use

Spark's use and transfer of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Spark does not use Chrome extension user data for advertising, sale, resale, creditworthiness, lending, or unrelated third-party profiling.

Security

• Data sent between the extension and Spark servers uses HTTPS.
• Authentication tokens are stored locally in Chrome extension storage and are not sold or shared with advertisers.
• Server-side access to beta data is limited to service operation, debugging, abuse prevention, security, and KNE review workflows.

What Spark Does Not Do

• Spark does not monitor your clipboard.
• Spark does not record browser history in the background.
• Spark does not continuously read AI conversations.
• Spark processes the password you enter over HTTPS for account login or registration; server authentication uses password hashes. The extension does not persist your password. Spark does not automatically collect payment card numbers, government identifiers, health records, or precise location; avoid including sensitive information in text you choose to verify.
• Spark does not sell personal data.

User Choices and Deletion

• You control when text is sent by choosing Verify, Submit to KNE, feedback, or issue reporting.
• You can stop extension collection by disabling or removing the extension. Logging out alone does not revoke consent or stop consented interaction events and anonymous verification.
• To request account deletion, Verify history deletion, contribution deletion, tester feedback deletion, issue report deletion, or privacy support, contact seth@knespark.com.
• Deletion requests are handled by deleting or anonymizing relevant account and service records unless retention is required for security, abuse prevention, dispute resolution, or legal obligations.

Contact

For privacy or support questions, contact seth@knespark.com.