Replit

The reviewed policy does not give a simple no-AI-training promise for all code, prompts, or workspace data.

AI coding workflows and service-improvement processing can still involve user code and workspace context.

Replit publishes privacy coverage for its website and related services instead of hiding code-workspace processing entirely.

Users can choose repl visibility and secrets-handling behavior to reduce unnecessary workspace exposure.

State privacy rights and request paths provide some leverage over how service data is handled.

Code and workspace data can still be exposed through public repls, collaborators, AI features, integrations, and service providers.

Third-party payment processors and linked-service connections add more recipients beyond the basic coding workspace.

Replit says it does not sell personal information under several state-law definitions.

The privacy policy documents access, deletion, anonymization, objection, and portability rights.

Users control whether repls are public or private and who collaborates on them.

Replit still collects device, software, IP, identifier, and service-interaction information.

The policy allows marketing, advertising, and personalization processing around the service and website.

The policy distinguishes strictly necessary cookies from broader tracking and marketing uses.

Users have privacy-rights channels that can reduce some ongoing data use.

Replit is a developer tool, not a consumer social feed built around behavioral advertising.

Retention varies by account state, service needs, logs, legal obligations, and public content.

Public repls, backups, and collaborative workflows can preserve content outside one deletion request.

Users can request access, correction, anonymization, deletion, and portability of data maintained about them.

Several state-specific access and deletion request paths are documented explicitly.

Users can also improve retention outcomes by making repls private and minimizing shared secrets or public content.

Users can control repl visibility, collaborators, secrets, and core account settings.

The policy documents request channels for access, correction, portability, and deletion.

Third-party connections are optional rather than mandatory for every workspace.

Public repls, leaked secrets, and AI coding workflows require active hygiene from the user or admin.

Controls do not remove every data-use path once code has already been shared, indexed, or connected to outside services.