Company accounts and team members
When you register, we store your company name, owner email, username, website, and selected plan. Passwords are stored as hashes. Session cookies and workspace identifiers support sign-in. Team names, roles, permissions, display aliases, and agent photos are processed to operate your dashboard.
Your customers’ data
Radman processes conversations and website visitor data to provide support, routing, archives, and reports. This may include names, emails, messages, images, IP addresses, approximate countries, devices, browsers, pages, and traffic sources. Account fields such as user ID, username, balance, category, and btag are processed only when your website integration provides them. Your company is responsible for informing its users about this processing and configuring appropriate staff access.
Drafts and supervision
Customer drafts in the chat composer are visible to support staff. Agent drafts can also be viewed by authorized staff according to conversation and supervision permissions. This feature does not read other website fields. Drafts are temporary and used for live previews; sent messages and versions preceding edits are stored in conversation history.
Access and company separation
Each company has a separate workspace. Member access is controlled by roles, individual permissions, and conversation assignments. Subscription, payment, usage, and contact-request data are also available in Radman’s platform administration dashboard to operate the service. Technical events and moderation records are stored for troubleshooting and service maintenance.
Subscriptions, payments, and contact requests
We store your plan, trial end date, subscription validity, and payment history. Manual payments are checked using the network, amount, and transaction ID. When automatic payment is used, the information needed to create and verify a payment is sent to NOWPayments; Radman does not request your wallet’s private key. Our contact form saves your name, email, company, subject, and message and emails a copy to the Radman team. An IP hash is used to limit repeated requests.
Infrastructure and service providers
Application hosting, databases, live connections, and image storage run on Cloudflare infrastructure. DeoMail handles Radman team email. If a company connects its Telegram bot, Telegram processes messages through its own service; Radman stores the conversation and controls access to Telegram usernames and IDs. Telegram keeps its own copies under its policies. Service providers receive data in the workflows relevant to their functions. Player account integration depends on your website implementation and is separate from signing in to Radman’s dashboard.
Retention, deletion, and backups
Conversation text, edit history, account data, reports, and contact requests currently have no configured automatic deletion period. Chat image attachments are scheduled for deletion after 3 days; this does not apply to agent profile photos. Some removed conversations remain available for moderation review, so removal from the chat view is not permanent erasure. Removal from backups may not be immediate.
Requests about company data
Contact info@radman.chat with questions about company data, corrections, or deletion requests. We verify the requester’s authority before acting. Users of customer websites should contact that company first. A separate notice is available for chat-widget users.
Optional chat translation
If the company owner enables translation, message text requiring translation is sent to OpenAI. Original and translated text remain in chat history. Messages may contain personal information; attachments and account identifiers are not sent separately for translation. Provider data retention follows its own policies.