Status and responsible operator
LLM Citely is preparing for release as a company-operated product in the United States. The operator has confirmed the United States and described the area as Silicon Valley. The full legal company name, registration state and any required public notice address are still pending. This is a policy preview; no effective date has been assigned.
The final notice must match the actual operating entity and launch configuration. The shared public request inbox is support@llmcitely.com.
Public tools that run in your browser
The buyer-question builder, saved-answer review, supplied-HTML audit, crawler-rules checker and llms.txt validator process the text you paste in your browser. The report, audit, action-plan and content-brief templates, pricing workload planner and contact message builder also prepare their results locally. These public tools do not submit their input text to an AI provider or a contact inbox.
Copy and download actions create files you choose to keep. Answer-review JSON can contain the complete pasted answer; worksheets and content briefs can contain your notes and client information. Review the export before sharing it. Local draft state is cleared when the page is closed or refreshed.
A mailto link opens your email application. Sending from that application is a separate action that delivers the message to the published inbox through your email provider. Account creation, website-entry and authenticated project actions are separate workflows that can submit information to the service.
Account and project records
The account workflow is built to process a name, email, verification and session records, workspace membership, roles and invitations. Session records can include an IP address and browser information for access and security controls.
Project work can include a website domain, business context, buyer questions and revisions, original collected answers, source links, collection status, tasks, notes, content drafts and reports. The purpose is to maintain access, collect requested evidence, support review and preserve the history needed to interpret a result.
A question can contain client or personal information. Check your authority to use the material and remove unnecessary sensitive details before submitting it. The data and access overview explains the product’s current access boundaries.
Service providers and optional connections
The current service design uses Cloudflare for application hosting, database, object storage and background work; Better Auth for account authentication; Resend for account email; Stripe for subscription checkout and billing; and Bright Data or DataForSEO for configured answer collection. Optional AI processing paths include DeepSeek and Cloudflare Workers AI. A code integration is not evidence that a provider is active in production.
Google connections can support selected Analytics and Search Console properties. Gmail connection capabilities include reading mail and sending a user-requested message. Connecting an account and requesting an action are distinct steps. The final notice must describe which permissions are requested and the data used by each enabled feature.
Before launch, this inventory needs to be reconciled with the enabled services, processing locations, provider agreements and any cross-border arrangements. Those details are pending. The platform page describes collection scope; it is not a complete privacy provider register.
Billing information
If paid subscriptions are enabled, Stripe-hosted checkout handles payment entry. The product maintains the subscription, customer reference, plan state, operation references, usage events and reconciliation records needed to apply an allowance and review charges. Internal cost records are restricted to authorized finance operators. Monthly plan prices and point allowances are confirmed on the pricing page. Ordinary collection is confirmed at one point per question–platform run. Shared-point reservations and expense reconciliation have passed local verification; live provider charges, higher-cost quotes and commercial rules still require acceptance. Purchasing remains closed.
Monthly plan prices exclude applicable taxes. If tax applies, the tax amount and final total will be shown before payment. Tax rates, collection jurisdictions and local price-display requirements still need verification. This approved display policy does not enable payments or tax collection in this preview.
A billing or usage record is different from a browser-only tool result. The final retention schedule must cover both operational project data and records that may need to be retained for accounting, dispute or other applicable obligations. No specific legal retention period is asserted here.
Retention, exports and deletion
A complete retention schedule is still being finalized for accounts and sessions, active-project inputs, original evidence, reports, connected-account data, logs, billing history and backups. The specific window for projects paused by a downgrade is described below; it is not a universal period for every data category.
Selected project records have export functionality. An export is not an assurance that every stored category is included. Disconnecting Google access does not by itself erase information already imported into a project.
The current product does not provide a verified, complete self-service purge of every account, project, billing record and backup. The final notice must explain how to request access, correction, deletion or disconnection, which records can be removed, any justified exceptions and the response process. The paused-project expiry policy below is separate from these broader deletion requests; no universal deletion deadline is promised here.
Business records and saved reports for projects paused by a downgrade are retained for 90 days from the date the lower plan takes effect. During that window, authorized users can view and export the existing records without starting new paid tasks. This window does not set retention for active projects, billing, refund or reconciliation records, or backups. The expiry policy below describes access and cleanup after this window.
The approved reminder policy schedules email and in-app notices to workspace administrators 7 days and 1 day before paused-project history expires. Projects in the same workspace with the same expiry date are combined in one reminder at each notice time. Reminder delivery is not enabled by this preview.
When the retention window ends, projects still paused by the downgrade lose access to view and export expired history. Eligible business records and saved reports are automatically cleaned up. Restored projects are skipped; anomalies defer cleanup for manual review. Active projects, billing, refund, cost-ledger and financial-reconciliation records are excluded. Backup retention and deletion are decided separately. This approved rollout policy does not enable access restrictions or data deletion in this preview.
See the paused-project policy preview. These records are distinct from financial records and backups, whose retention rules remain separate.
Questions, rights and publication
For privacy and data questions, email support@llmcitely.com or prepare a privacy request. Identify the account or project category and the action you want reviewed. Avoid passwords, tokens and unnecessary client records. The website prepares a draft; it does not submit the request.
The operator still needs to finalize identity checks, request handling, retention and deletion procedures for the launch configuration. No response deadline, complete account purge or policy effective date is promised by this preview. Published policy changes will need a review date and an explanation of material changes.