Security and data processing

Session IDs now change at login, activation and admin impersonation. Login, password reset and activation have separate limits by IP and account. New reset and activation tokens are stored only as hashes; LinkedIn bearer tokens are encrypted in the database.

Uploads are checked by content. Images are re-encoded and stripped of EXIF and GPS data. Documents have type, size and decompression limits. Outbound downloads from user-controlled sources are subject to DNS, IP, redirect, size and time checks.

Imported content, media and user text are marked as untrusted data when sent to AI models. Upload-Post webhooks check signatures, timestamps and replays. Access, email and error logs no longer include the sensitive values found by the review. Local account deletion also removes legacy data and private uploads that are not linked by foreign keys.

Authentication, articles, calendars, brands, jobs and usage data are stored in the Roundcast application’s PostgreSQL database. Workspaces, original media and thumbnails are tied to sessions and users. The uploads directory is not served directly by Express or nginx. Short-lived signed media links are used where a publishing provider needs a publicly retrievable file.

Depending on the feature used, Roundcast processes data with Google Gemini for text and images, fal.ai for images and video, OpenAI for images, DataForSEO for keyword research, Nebius for knowledge summaries and material assessments, and Melious for media sorting. LinkedIn, Meta, Upload-Post and WordPress receive content or credentials when they are connected and used as publishing destinations.

The approved operating documents do not state a binding geographic location for the Roundcast database or every provider involved. This page therefore does not promise a particular storage location. Content already published or transferred to external services may remain outside the local Roundcast database.