AI search intelligence for agencies and consultantsSee how we measure
LLM Citely · pre-release

Terms of service preview

The service workflow and evidence limits you can review now, with commercial and legal conditions clearly marked as pending.

Draft reviewed · no effective date

Operator details and final policy decisions are pending. This preview is kept out of search indexing and is not a finalized legal agreement.

Status, parties and effective date

These are preparatory service notes, not a finalized contract or an offer to purchase a plan. Company operation in the United States and the shared support@llmcitely.com inbox are confirmed. The complete legal company name, registration state, any required notice address, eligibility rules and effective date remain to be finalized.

The operator must approve the final terms before public service activation. The final agreement will identify the contracting entity, what constitutes acceptance and which version applies.

Service workflow and current coverage

LLM Citely organizes buyer questions, collected answers, explicit source links, review tasks and reports for a client project. Availability depends on the enabled collection surface, provider access, account permissions and operational capacity. Check the current platform scope before planning a collection.

The demo uses labelled illustrative records. The public saved-answer review inspects text supplied by a visitor; it does not query ChatGPT. A workload calculation or generated question set does not reserve a paid service or enable an integration.

What a sampled answer can establish

An answer is evidence from a particular question, surface, market and point in time. An explicit URL in an answer and a brand mention are different observations. Missing collection coverage must remain visible when interpreting a result.

A sampled result cannot establish all users’ answers or guarantee rankings, citations, traffic, leads or revenue. Provider output and source pages can change. Review the original evidence before making a recommendation or publishing a client claim. The measurement methodology explains the intended interpretation.

Accounts, teams and submitted material

Authenticated work associates projects and records with a workspace and its permitted roles. Invitations and connected services can grant access beyond one person. Before enabling them, confirm who is entitled to view the client material.

The final agreement needs to specify account eligibility, credential responsibilities, permitted use, authority to submit client data and restrictions on abusive or unlawful activity. These are review items; this page does not create an unapproved indemnity or transfer of rights. Keep credentials and unnecessary sensitive information out of question text and public-tool exports.

Prices, plan limits and payment

The pricing page lists confirmed USD monthly prices, client-project limits and shared point allowances. Purchasing is not open; live-provider acceptance, higher-cost point quotes, live tax configuration and remaining commercial terms are pending. The approved unused-account refund policy is described below. No free trial, unlimited allowance or service-level commitment is offered by this preview.

The existing subscription workflow is designed around Stripe checkout and a billing portal. Before purchasing opens, the operator must verify tax rates, collection jurisdictions and local price-display requirements, apply the confirmed period-end cancellation policy, and verify the information shown at checkout. The approved monthly prices do not activate a payment flow.

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.

See the tax display policy.

Collection usage and unresolved runs

The shared-point workflow has passed local verification. It reserves points before a new paid operation, settles a delivered result once and returns the customer point reservation for a failed task. Ordinary website collection is one point per question–platform run. Higher-cost research or drafting needs a verified quote and ceiling; an unknown route is blocked. Saved results can be read or exported without starting another collection.

A submission whose outcome is uncertain is reviewed before another paid request is made. Returning customer points is separate from any money refund and does not assert that a supplier refunded its charge. Operational limits are separate from the plan allowance. Live provider and payment acceptance remain pending; final terms still need to define retriable work, overages and any remedy when service cannot be delivered. Any service-failure remedy is reviewed separately from the unused-account refund window.

Plan changes, cancellation and refunds

Cancellation stops renewal at the end of the current paid billing period. Access remains available through that period. This policy is confirmed for rollout; purchasing remains closed while live billing acceptance is completed.

Monthly points are valid only within their paid billing period and do not carry over. If you cancel renewal, unused points remain available until that paid period ends. Point expiry follows your billing period, not a shared calendar-month cutoff.

The upgrade, downgrade and refund policies below are confirmed for rollout. Their payment and entitlement-processing workflows still need acceptance. Returning customer points for a failed task is separate from a cash refund. The paid period and cancellation status must be shown consistently by the billing service before purchasing opens.

The final terms also need to explain suspension, account termination, notice and record availability after access ends. No post-termination access period is invented by this preview.

Upgrade charges, points and billing period

After the upgrade payment succeeds, the higher plan takes effect immediately. For the current billing period, you pay the full difference between the two plan prices, without time proration. Only the difference between their monthly point allowances is added. The billing period and renewal date stay the same.

Consumed points and existing reservations stay recorded. Upgrading does not reset usage or issue a new full point allowance. Added points expire at the original billing-period end, including when you upgrade close to renewal. The next billing period uses the new plan price and allowance. Upgrade payments and automatic point adjustments are not open yet.

The pricing examples show the approved USD plan-price and point differences. The payment confirmation must show the pre-tax price difference, any applicable tax, final total, point addition and unchanged period-end date before the customer commits. Live tax configuration and upgrade processing remain pending. This preview does not start a subscription change or charge a payment.

Downgrade timing and extra projects

Downgrades take effect at the next billing period. The current period keeps the existing plan price, point allowance and access. The lower plan's price and monthly point allowance apply when the next period begins.

Before the downgrade starts, choose which projects continue within the lower plan's project limit. Extra projects pause new paid collection, research and generation. Existing records and saved reports remain available to view and export as read-only history within the retention window below. Projects are not automatically deleted just because a plan is downgraded.

Example: moving from Agency to Pro with 10 projects means choosing 3 to keep running. The other 7 pause new paid work while their existing records remain available under the final retention policy.

The pricing policy uses the same rules. Actual downgrade scheduling, project selection and paid-task restrictions remain pending implementation and acceptance. The approved paused-project retention window is described below; reminder delivery and cleanup execution still need implementation and acceptance. This preview does not pause projects or delete records.

Retention for projects paused by a downgrade

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.

The pricing policy uses the same window. The actual retention controls, reminder delivery and cleanup workflow still need implementation and acceptance. This preview does not set deletion dates or remove records.

Unused-account refund requests and exceptions

For your first payment, you may request a full refund within 7 calendar days if no customer-authorized paid collection, research or generation task has started. The 7-day limit applies to submitting the request, not completing the review. Requests are reviewed manually.

After paid use starts, routine change-of-mind refunds are not offered. Duplicate or incorrect charges, failure to activate a paid account, service non-delivery and legally required remedies are reviewed separately. The unused-account condition does not automatically reject those cases. Returning points for a failed task is separate from a money refund.

To request a review, prepare a billing enquiry for support@llmcitely.com. Include the payment date, account email and invoice reference if available; do not send payment-card details, passwords or API keys.

This policy is confirmed for rollout. Refund processing and live billing acceptance are still pending. Preparing an enquiry does not submit a request or confirm a refund; review and send it from your email application. The pricing policy uses the same rules.

Content, exports and third-party services

Projects may contain customer-supplied material, third-party answers and linked source pages. An export can preserve evidence without changing the underlying ownership of that material. A link to an AI product or source site is not a claim of partnership or endorsement.

The final agreement needs to define customer ownership, any permission required to operate the service, third-party restrictions, feedback rights and permitted reuse of reports or generated drafts. This preview does not assign ownership or publish a training-data policy that has not been approved.

Privacy and data at the end of use

The separate privacy preview describes the current data flows and outstanding privacy decisions. Local public-tool drafts are different from submitted account and project records.

Selected project exports exist, but a complete self-service account purge is not verified. A connection being removed does not automatically erase previously imported data. Retention, deletion requests, backup treatment and any records retained after termination must be finalized together with the privacy notice.