CiteKit US$19 one-time
US$19 one time per site, plus applicable tax shown at checkout. Payment is handled by Paddle.

Privacy Notice

Last updated: 12 September 2026

This notice covers the CiteKit website, checker, preview and ZIP delivery. 9213651 CANADA INC., Canada, operates CiteKit and is responsible for its handling of personal information. Contact the operator about privacy at idealstoronto@gmail.com. Payment and hosting providers have their own privacy policies for their services.

What we process and why

  • Submitted URL and website content. We process the URL, including any query string, and public content fetched from it to check installation gaps and generate your files. Do not submit credentials, confidential or sensitive content, or a URL containing an access token.
  • Fetch scope. A check reads the submitted page and probes /llms.txt. Generation can read up to eight HTML pages on the resulting origin and also request its sitemap, /llms.txt and possible Markdown versions of those pages. An initial redirect can establish a different public HTTPS origin; subsequent crawling stays on that origin. Fetch phases can repeat for previews, rechecks and downloads. Each response is capped at 2 MB. A ten-second network budget applies to each check or crawl phase, not the entire customer flow. We do not sign in to your site, execute its JavaScript, or schedule background crawls.
  • Checkout and delivery references. To associate the ZIP with the submitted site, the app keeps a random checkout reference, the submitted URL, a checkout identifier, confirmation timestamps and temporary download keys. When checkout opens, CiteKit asks Paddle to create the transaction and sends the site's URL and reference identifier as signed metadata. It does not send your IP address to Paddle. Your browser then loads Paddle's checkout script and contacts Paddle directly, so Paddle receives your request data, including your IP address, under its own notice.
  • Payment information. Paddle collects checkout information such as payment details, billing information and an email for receipts. CiteKit confirms payment by reading the transaction and its adjustment history (refunds and chargebacks) from Paddle's API, and by receiving signed webhooks. Those reads also let a buyer recover a download after losing browser state. Its fulfillment cache keeps the identifiers and URL needed for delivery; it does not store full card numbers. Order details may also be available to the operator through Paddle for customer support and payment administration.
  • Technical data. Railway hosts the app and handles network requests. Technical logs may include IP addresses, request paths, times, status codes and infrastructure metadata. CiteKit also keeps recent IP-based request counts in memory to limit abuse. The application excludes query strings from its own access log; hosting-provider logs are managed separately.
  • Support messages. If you contact the operator, your email address, message and relevant order details are used to respond and handle the request. The approved contact is a Gmail mailbox, so Google processes this correspondence as the email provider. See Google's Privacy Policy. Do not send payment-card details, identity documents, passwords or a private download key.

Browser storage and cookies

CiteKit uses browser session storage to remember the submitted URL, check results, checkout identifier and temporary download key in the current tab. This supports returning from checkout and downloading or rechecking. Session storage generally ends when the tab is closed, though browser session restoration can preserve it. You can remove it through your browser's site-data controls.

The CiteKit app does not set advertising or analytics cookies and does not load third-party analytics, advertising scripts or remote fonts. Paddle's checkout script is loaded from Paddle's content delivery network only when you open checkout; it is not loaded for visitors who only check or preview a site. Paddle's checkout may use its own cookies and technologies. See its policy before proceeding.

Storage and retention

  • Fetched HTML is processed in memory for the request. Generated previews and ZIP files use temporary files that the app removes when the operation finishes. A crash can leave temporary files until the hosting instance is replaced or they are cleaned up. CiteKit does not keep an archive of generated packs; keep your downloaded copy.
  • Checkout references expire after 48 hours. Cached payment confirmations expire seven days after the most recent confirmation. Cached refund or chargeback flags expire seven days after they are first recorded locally. Download keys expire about one hour after issue. A new confirmation can create or refresh a cached record; these cache windows do not erase an order or a refund from Paddle, which the app re-reads before each delivery.
  • The running app checks for expired fulfillment records and expired rate-limit entries about once per minute. It also prunes fulfillment records on startup and state writes. If an instance is stopped, cleanup resumes when it starts. The app's local storage is not a permanent order history and may be lost during redeployment.
  • Hosting logs, provider records and support correspondence are separate from the app's fulfillment cache. Their retention depends on the provider's policies, the support issue and applicable recordkeeping obligations. The cache expiry periods above are not a promise to delete those separate records or provider backups within seven days.

Providers and processing outside Canada

Railway provides the web hosting and infrastructure. The current application deployment is in the United States (US West). Request data, website content and fulfillment records are processed there. See Railway's Privacy Policy.

Paddle provides the current checkout integration, payment confirmation and transaction services, including receipts, and acts as merchant of record. Its providers may process information in other countries. See Paddle's Privacy Policy and Buyer Terms. The integration runs in Paddle's live mode, so completing checkout charges your payment method.

Google provides the Gmail mailbox used for support, refunds and privacy correspondence. Its processing and retention are governed by Google's Privacy Policy and applicable account settings; correspondence may be processed outside Canada.

The public service currently generates files without sending site content to an external AI model. We do not sell submitted URL lists or use submitted content to train a public model. If the public service's providers or processing change materially, this notice must be updated before the new processing starts, and consent obtained where required.

Information processed outside your country may be subject to that country's laws and lawful access requests. CiteKit may disclose relevant information when required by law or to handle a payment dispute or security incident.

Your choices and privacy requests

You can browse the product, policies and sample without submitting a URL. Submitting a URL requests the processing described above. If you do not want your site processed, do not submit it. You can stop future checks and clear your browser's site data.

Email idealstoronto@gmail.com to request access, correction or deletion of personal information held by CiteKit, or to raise a privacy concern. Include only enough information to identify the request, such as the submitted public URL and order reference. The operator may need to verify that you are entitled to the information. Some records may need to be retained for legal or dispute-related reasons; those limits will be explained where applicable. Requests about Paddle's own payment records can also be made directly to Paddle.

You may raise a concern with the Office of the Privacy Commissioner of Canada or the relevant privacy authority where you live. Nothing in this notice limits your rights under applicable privacy law.