Privacy Policy

Tool inputs

The current static tools process inputs in your browser. Inputs are not sent to a CiteKit server by this implementation. Visibility prompts, schema fields, crawler snippets, answer copy, alternatives briefs, checklist selections, and log-builder rows are handled locally unless you decide to copy, download, email, or otherwise share the output yourself.

Saved reports

If you use Save report, the generated Markdown report is stored in your browser localStorage on that device. Checklist progress and AI visibility log rows also use localStorage so checked items and prompt-run records can persist in the browser. CiteKit does not receive saved reports, checklist progress, or visibility log rows in the current static implementation. You can remove reports on the Saved Reports page, reset checklist progress on the checklist page, reset the visibility log on the log builder page, or clear browser site data.

Local browser storage checklist

Local browser storage is used only for features that need to remember work on the same device. Saved reports, checklist progress, and visibility log rows are intended as user-controlled draft artifacts. They are not a server account, and they are not synced across devices by CiteKit. Clearing site data in the browser removes the local records.

• Saved GEO reports: local Markdown drafts created by the user.
• Checklist state: checked audit items on the SaaS GEO checklist page.
• Visibility log rows: prompt-run records created in the AI visibility log builder.
• No server restore: users should download important Markdown or CSV files before clearing browser data.

No account system

CiteKit does not currently provide accounts, passwords, dashboards, server-side saved projects, or cross-device syncing. The site is designed as a static browser-based toolkit, which means most working data stays on the device where it was created unless the user copies, downloads, emails, or pastes it into another system.

Data minimization

Data minimization is part of the product design. The tools ask for public marketing-page details such as product names, URLs, category labels, feature copy, crawler snippets, and competitor names. The site does not need private customer records, payment data, internal analytics, or credentials to produce a useful SaaS GEO draft.

What not to enter

The tools are intended for public SaaS marketing pages, documentation pages, and comparison drafts. Do not enter credentials, private customer information, confidential roadmaps, paid analytics exports, personal data, or unreleased legal claims. Generated reports are meant to be reviewed and edited before they are published or shared with clients.

Analytics and advertising

CiteKit may use Google AdSense or similar advertising services after approval. Advertising partners may use cookies, identifiers, or contextual signals to serve, measure, and limit ads. Users can manage ad personalization through their browser and Google account settings. The site should not place ads where they can be confused with tool actions, reports, navigation, or downloads.

Advertising and cookies

The site may include the AdSense review script while a domain is being reviewed, and later may show approved display ads. Google or other advertising providers may use cookies or similar identifiers according to their own policies. CiteKit should keep advertising separate from the tool task, and it should not require a user to click an ad, create an account, or submit private data to use the free tools.

User control options

Users control the most important data paths in the current static implementation. You can avoid entering private data, copy only the parts of a generated report you need, download Markdown or CSV files for your own records, delete saved reports in the browser, reset checklist and log-builder state, clear site data, block cookies, or manage ad personalization through browser and Google account settings.

Third-party links

Some source pages link to Google, OpenAI, Perplexity, Anthropic, and other public documentation. Those sites have their own privacy and data practices. CiteKit links to sources so users can verify crawler, schema, helpful-content, and advertising guidance instead of relying only on a summary.

Contact

For privacy questions, contact feiyangkl3@gmail.com.