BaseCite Privacy
This public privacy notice describes the high-level data boundaries used by BaseCite. It is written for visitors, customers, uploaders, and agents evaluating whether the service is an appropriate integration target.
Data handled
BaseCite may receive account, organization, consent, upload metadata, file bytes, integrity digests, processing status, controlled summaries, access receipts, and operational security metadata. Customer-submitted originals and derived processing data are private workspace data. Public pages do not expose raw files, full OCR, object keys, private identifiers, access logs, or bulk exports.
Purpose and access
Data is used to provide scoped upload intake, integrity and processing controls, customer-authorized bounded AI context, auditability, support, security monitoring, and deletion workflows. Access is limited by organization, role, credential, visibility, and processing policy. An AI-readable result is not a truth, company, legal-authority, ranking, certification, or endorsement claim.
Retention and deletion
Retention depends on the applicable workspace, consent, contract, and operational policy. A supported withdrawal or deletion operation is intended to remove the original and derived context from configured storage backends while retaining only the minimum deletion receipt and audit metadata needed to prove the operation. Contact support@basecite.com or security@basecite.com for privacy requests and the applicable workflow.
Updates and questions
This notice may be updated when the service, processing providers, or legal requirements change. The canonical public contact route is https://basecite.com/contact. Do not place secrets or raw customer content in public forms, chat messages, or email.