--- title: AI Translation Privacy, Security & Data Controls — SalamAI url: https://salam.cosinechat.com/security --- [SalamAI /](https://salam.cosinechat.com/) AI Translation Privacy, Security & Data Controls # Translation privacy & security: Your content. Your rules. SalamAI gives teams clear controls for saved files, audience access and live sharing. This page explains where audio is processed, what High privacy mode changes and which usage records remain. Check privacy controls Access · Saving · Sharing In short ## How does SalamAI handle your audio and data? Updated 30 October 2026 Live audio is processed by translation services so it can be translated in real time. What gets saved is up to you. Saved archives are encrypted in the browser before upload. In supported voice sessions, High privacy mode stops SalamAI saving recordings, transcripts, summaries and document PDFs, though basic billing and security records remain. Live caption feeds, overlays and audience captions need readable text on the sharing service, so control who can join before you enable them. Organisers set audience access with approval and link expiry. The website demo does not save audio or transcripts. This site does not claim a legal compliance certification, so review the data paths against your organisation’s needs. ### What controls who can listen? Each audience language has its own link and QR code, and the organiser decides how open it is. You can ask listeners for details, approve each listener before they join, and set the link to expire. Removing a link or creating a new one stops the old one working. Remote presenters and translation stations get their own temporary access, separate from team accounts. Treat a shared QR code like a door key: without approval, anyone who has an active link can join. For private meetings, turn on approval, set a short expiry and avoid posting the code where the public can see it. Read next [Meeting summaries & transcripts →](https://salam.cosinechat.com/beyond-the-session) [AI translation vs human interpreters →](https://salam.cosinechat.com/compare) High privacy mode ## Choose what is saved during a session. 01 ### Select it before you speak High privacy is available for supported one-way, two-way and station voice sessions. Select it before starting. Your organisation can allow, disable or require it. Campaign rules can also allow or require it for stations. 02 ### Do not save conversation content In high privacy, SalamAI does not save conversation recordings, transcripts, summaries or document PDFs. Live text is cleared when the run ends; Companion text tracks and caption feeds are unavailable. 03 ### Understand what still happens Live audio is still processed. Basic billing and security records remain. Translation providers, networks, devices and other recording systems have their own policies and controls. ### Check the features you need High privacy turns off saving, summaries, shared captions and several sharing tools. It supports the main voice translation modes only. Choose it before Start, then verify the privacy indicator in the console. [Explore two-way translation →](https://salam.cosinechat.com/two-way) Audio processing and storage ## How each feature handles your content. 01 ### Audio sent directly to a named provider Each translation type shows its model and provider in the console, such as Voice and subtitles - Model A (Google) or Model B (Qwen). Voice and subtitles - Model A (Google) sends audio directly from your browser to Google. SalamAI manages sign-in, temporary session access, limits and usage records. 02 ### Other audio passes through relay services Subtitle-only translation and optional language detection send audio through SalamAI services. Remote microphones and participant phones use access-controlled relays. Audience audio uses a separate delivery service. 03 ### Saved content is encrypted before upload Your browser encrypts optional recordings, History transcripts and saved SRT or Markdown files before upload. An authorised device decrypts them for playback or download. 04 ### Keep files only as long as you need For each event, choose how long that session’s recordings and transcript files are kept, from 1 to 365 days, within your organisation’s limit. High privacy sessions save no conversation content. 05 ### Shared text is readable by the sharing service Live caption feeds, screen overlays, audience captions and published summaries use readable text on the sharing service. They are separate from encrypted saved files. Choose what to share and control who can join, link expiry and removal. 06 ### Summaries process text on request A summary request sends the transcript for processing on the server. Publishing the result creates a readable shared copy. The language link’s access and expiry rules apply. The public website demo ## What happens to your data in the website demo? The homepage demo sends microphone audio through a secure relay to translation service providers. It returns translated speech and text. This differs from the main console’s direct voice connections. The demo does not save audio or transcripts on our servers or in browser storage. Text stays on the page until you clear it or leave. Our infrastructure and translation providers process the connection under their policies. Providers may keep operational records. To limit misuse, the demo uses a signed cookie valid for one day, network identifiers that change daily and temporary session records. The identifiers are coded values, not raw IP addresses. Usage-limit records are deleted after two days of inactivity. Speech content is not logged. When the demo produces translation, we email the SalamAI team a technical usage report through Postmark. It includes session times, language, result, audio and text counts, browser, device and approximate network location and details. It excludes recordings, speech or translation content, raw IP addresses, cookies and sign-in details. Temporary email delivery records are deleted after delivery or a limited number of retries. Email copies remain in our mailbox and with our email provider under their retention policies. You must accept this processing and allow microphone access before starting. The demo session ends automatically, or when you stop or leave the page. Use headphones to reduce feedback. Live AI transcripts and translations may contain errors. Privacy notices and consent ## Show your organisation’s notices. 01 ### Set your organisation and contact details Organisation administrators can set operator and contact details and publish privacy and terms notices in English or Malay. Preview notices before publishing. The default operator is Ordinexis Sdn Bhd. Notice languages are separate from the 37 public interface languages. 02 ### Ask users to accept updated notices Privacy and terms acceptance is required at the main console, campaign, audience, participant and remote-speaker entry points. A newly published version prompts acceptance again on the next entry. 03 ### Remember acceptance on return visits Account acceptance can be remembered. Anonymous acceptance is remembered in the same browser while its storage remains available; another device or cleared storage may require it again. Notices remain available to read through help or page links. ### Separate choices stay separate Privacy and terms acceptance does not replace recording consent, microphone permission or accuracy notices. These controls support an organisation’s policies; they are not a legal compliance certification. Account and sharing controls ## Manage access to your team and content. 01 ### Team data stays separated Each organisation’s data is restricted by both application permissions and database access rules. This adds a second boundary between teams. 02 ### Sign in with the right safeguards Use an authenticator app and backup codes for two-step sign-in. Where enabled, Magic Login email links and QR codes are short-lived and single-use. Access checks still apply. Password recovery is available, and teams remain invite-only. 03 ### Per-language audience permissions Set audio, original and translated captions, approval, summaries and expiry for each language link. An organisation can limit phone sharing to text only. 04 ### Keep a verifiable audit log Security and administrator actions are linked in a verifiable log so changes can be checked. These event records do not contain spoken content. 05 ### Limit and remove session access Provider keys stay on the server. Browsers receive temporary credentials limited to the session. Participant phones, remote presenters and station operators have separate access controls. Inside SalamAI ## Share a QR code for each language. Share a QR code for each audience language. It uses the SalamAI logo by default, or your organiser logo when configured. Set audio, captions and joining rules in the same place. Common questions ## Privacy and security questions ### Does High privacy mode save recordings or transcripts? No. In supported voice sessions, High privacy mode prevents SalamAI from saving recordings, transcripts, summaries and document PDFs. Live audio is still processed. Basic billing and security records remain, and external services and devices have their own policies. ### Are shared captions encrypted in the same way as saved files? No. Saved archives are encrypted in the browser before upload. Live caption feeds, overlays and audience captions need readable text on the sharing service. Control access before enabling them. ### Does the website demo save what I say? The demo does not save audio or transcripts on our servers or in browser storage. Translation services still process your audio. We email the SalamAI team a technical usage report without speech content or raw IP addresses. [Read the full demo data notice](#live-demo) . ### Is SalamAI certified to meet a specific legal standard? This website does not claim a legal compliance certification. Review the data paths, sharing settings and linked policies against your organisation’s needs. [Contact Ordinexis with security questions](https://ordinexis.com/contact) . ### Which AI providers translate the audio? Each translation type names its model and provider in the console: Model A (Google) for Voice and subtitles, Subtitles only, Same-language captions and Transcribe only, and Model B (Qwen) as an alternative voice engine where your organisation has it. Model versions and keys are not shown. ### How long are recordings and transcripts kept? Your organisation sets the limit. For each event, you can choose a shorter period, from 1 to 365 days, under “Keep this session’s files”. High privacy sessions save no conversation content at all. --- SalamAI is a product of Ordinexis Sdn Bhd. Contact: hey@ordinexis.com