Privacy policy

We collect the information you provide when you create an account: your name, email, and the name of your workspace. We also collect the data you put into the product — press releases, URLs, source details, notes, and routing actions. We collect standard technical data (IP address and user agent) for session security and abuse prevention. We also record in-product events such as signup, policy setup, capture, and routing so we can measure whether the workflow is useful. Support requests retain the contact details and message you submit, their reference, time, and operator handling history. Signed-in reports include your account, workspace, and page, but do not automatically attach source material.

We don’t sell your data, ever. We don’t share it with advertisers. We don’t train AI models on your data without your explicit opt-in. We don’t track you across other sites.

Data is stored by the infrastructure providers configured for the ReleaseDesk deployment. Production operators are responsible for encryption at rest, encrypted transport, access control, backups, and tested restoration procedures.

When AI extraction is enabled, the raw text of a press release is sent to our AI extraction provider to extract structured metadata. The provider processes the data under their data processing terms. Provider retention depends on the production account and contract selected by the operator. We send the source text and your workspace’s editorial policy, but not teammate credentials or billing information.

Authorized workspace members can export items, scores, briefs, attachments, and activity as a JSON content archive. A personal account departure preserves shared editorial records and requires another administrator if you are the last one. Administrators can delete the workspace after the security and billing checks shown in settings. Workspace data is deleted from the primary database immediately; backup retention follows the production infrastructure policy.

We use first-party cookies for sign-in and security challenges. We don’t use third-party advertising cookies. Product events are stored in ReleaseDesk’s own database and are associated with a workspace or user when needed to understand activation.

Questions about privacy? Submit a privacy request.