Privacy Notice

CiteFleet operates the CiteFleet service. For a privacy question or request, reply to an account, verification, or password-recovery email sent by CiteFleet. That reply reaches the configured service operator.

• Account information such as your name, email address, profile image, provider account identifier, password hash, and sign-in method.
• Security information such as session identifiers, request IP addresses, failed sign-in state, OAuth state, and password-reset records.
• Workspace information such as site names and domains, repository locations, hosting choices, IndexNow configuration, BotCentral key prefixes, webhook settings, task state, generated files, and audit history.
• Public website observations such as pages, sitemaps, DNS records, response headers, origin proof, and indexing or listing status.
• Integration and payment information returned or submitted during an authorized action, such as an invoice identifier, asset, amount, destination, transaction reference, or integration access token.

We use this information to create and secure accounts; provide audits, origin files, monitoring, listings, training, and support; carry out actions you request; prevent abuse; troubleshoot and improve the service; keep operational records; and comply with law.

Where privacy law requires a legal basis, processing may be necessary to provide the service or take requested pre-contract steps, to meet legal obligations, for legitimate interests in operating and securing the service, or with consent where required.

We disclose information only as needed to operate the service, complete an action you request, protect users and the service, or meet a legal obligation. Recipients may include infrastructure, database, and email providers, as well as these optional integrations:

• Google or GitHub when you use provider sign-in.
• GitHub when you authorize repository inspection or an origin-file write.
• BotCentral when you request listing, verification, API credit, or payment processing. Published site cards and proof are public.
• xAI when you invoke a Grok specialist for a campaign task.

Information committed to a repository or published to BotCentral may remain in public or third-party copies after it leaves CiteFleet.

CiteFleet uses necessary cookies for sign-in sessions and temporary OAuth state. These cookies keep an account signed in, protect provider callbacks, and enforce access. The embedded app preview may instead keep a temporary bearer token in browser session storage when normal cookies cannot reach the preview. The current product does not use advertising cookies.

We retain account and workspace information while the service is active and as reasonably needed for security, recovery, support, legal compliance, and dispute handling. Password reset links are single-use and expire after 30 minutes; related security records may be retained briefly to prevent abuse. Public listings and repository history follow the retention practices of the service where they were published.

CiteFleet uses access controls, hashed passwords and reset tokens, transport encryption, secret masking, and other technical and organizational safeguards. No internet service can promise absolute security.

Depending on where you live, you may have rights to access, correct, delete, restrict, or export personal information, object to certain processing, or withdraw consent. You may also complain to your local privacy or data-protection authority. Reply to a CiteFleet account email to make a request. We may need to verify your identity before acting.

CiteFleet is a business service intended for adults and is not directed to children under 13. Service providers may process information in countries other than your own, subject to safeguards required by applicable law. We may update this notice as the product or law changes; the effective date above identifies the current version.