Trust
Security and Trust
This page explains ThoughtCite’s beta trust posture in plain English. It avoids unsupported compliance claims and focuses on what customers should know before using the product.
What ThoughtCite does and does not do
ThoughtCite helps draft, score, review, publish with approval, track prompts, and benchmark competitors. It does not auto-DM, auto-connect, scrape private data, run engagement pods, guarantee reach/citations, or publish without user approval.
AI outputs and scoring signals can be inaccurate. Review facts, claims, originality, links, and compliance before publishing anything externally.
LinkedIn account safety
ThoughtCite uses OAuth-supported connection where applicable, requests the permissions shown by LinkedIn, and can publish only posts you explicitly approve through supported LinkedIn publishing permissions.
Manual paste is available when LinkedIn read access is not approved or not desired. ThoughtCite is not affiliated with, endorsed by, or sponsored by LinkedIn or Microsoft.
Data protection and AI providers
Account-level access controls are designed to keep customer workspaces separated, and provider-backed endpoints use practical rate limits where applicable. Sensitive tokens are stored server-side and are not exposed in the browser.
ThoughtCite uses AI and infrastructure providers to operate the service. Private content is not sold, but customer inputs may be sent to providers for service delivery. See the Subprocessors page for provider categories.
Billing trust and beta transparency
Stripe processes payment details. Trial conversion, renewal date, and amount should be shown before checkout confirmation. You can cancel before renewal, and refund requests should go through support.
Paid beta features may change, some integrations depend on provider/API approval and availability, and users should save/export business-critical content outside the app during beta.