Security and data handling
Use current security materials and keep workflow evidence within its intended audience.
Current security materials
Use the RamAIn Trust Center for current security documentation and available assurance reports. For contractual terms, consult the Privacy Policy, Terms, and Data Processing Addendum.
Older product docs included dated certification timelines, infrastructure assumptions, and blanket retention claims. Those are not a substitute for the current reports and your agreement.
Practical workflow controls
Choose the correct workspace, restrict management permissions, use Password references for credentials, and inspect integration scopes. Runtime connections and model providers depend on your deployment configuration.
Recorded screenshots, prompts, files, and outputs can contain information from target applications. Review them before sharing an SOP or run evidence. A redacted credential field does not make an entire customer record suitable for public sharing.
Review evidence before sharing
A workflow screenshot can show an entire page, including unrelated records around the action target. Before sharing an SOP or run result, inspect the image at full size, its caption, the surrounding instructions, and any attached files. A cropped thumbnail may conceal information that is still present in the full-size image.
Use a safe example when creating public training material. Avoid including real API keys, password values, one-time-code seeds, customer messages, or sensitive downloads. The documentation walkthroughs use safe example data and identify form previews separately from completed actions.
Keep credentials and connected accounts in scope
Store reusable login secrets in Passwords and refer to them by their saved key. Check the account and scope when authorizing an integration. An available provider, a connected account, and a linked chat identity represent different configuration steps.
Choose the intended workspace before editing membership or uploading reference documents. If access must change, use the relevant team or integration controls and verify the result with that account. Removing a local screenshot from your computer does not change a workflow record already stored in the application.
Questions and enterprise deployment
Contact security@ramain.ai for security diligence and privacy@ramain.ai for privacy questions. Discuss private-network or customer-managed deployment requirements with RamAIn; the standard browser workflow does not by itself provision private infrastructure.
Was this page helpful?