OverviewHow it worksPricing
EducationResearch
Docs
Sign inGet started now

Navigate

Roleplay

Product

OverviewHow it worksPricing

Learn

EducationResearch

Resources

Docs
Get started nowSign in

Privacy Policy

Local-first testing with sanitized workbench collaboration.

Roleplay is operated by MARAM TECH VENTURES LTD and is designed to keep sensitive transcripts local unless you explicitly choose otherwise.

Default Data Model

  • Full transcript upload is off by default.
  • Sanitized finding uploads are the default cloud workflow.
  • Redacted snippets and secret redaction are on by default.
  • Project API keys are scoped to a project.

Account And Workspace Data

We store account, workspace, member, role, invite, project, protected-agent, API-key metadata, access status, and last-used timestamps needed to operate the workbench.

Cookies And Local Storage

Roleplay uses essential cookies and browser storage to support sign-in, security, site operation, onboarding progress, and saved cookie preferences.

Runs And Evidence

The workbench stores run metadata, sanitized findings, evidence metadata, severity, failed boundaries, regression keys, monitor results, verification status, and Agent Risk Profile data. Full transcript upload remains optional.

Local Artifacts

The CLI stores scenarios, transcripts, reports, and metadata in your environment under .roleplay unless you choose a different output directory.

Private Attack Packs

When you request a private attack-pack bundle, Roleplay verifies project entitlement and returns the scenarios needed by the local runner. Bundle requests are handled as product access events.

Transactional Email

Roleplay uses AWS SES for product-useful emails such as invites, critical findings, verification results, monitor summaries, and access lifecycle notices. Basic delivery records may be kept to confirm delivery, diagnose failures, and protect the service.

Billing And Providers

Stripe processes billing and stores payment details. Roleplay stores billing metadata such as customer, subscription, plan, and status. Real adaptive runs use your selected model provider and provider key; Roleplay does not need your provider key for mock smoke tests.

Optional Cookies

Optional cookies are used only after you allow them. Continuing with essentials only does not affect sign-in, billing, local tests, uploads, or workbench functionality.

Retention And Rights

Workspace settings control evidence retention where available. You can request access, correction, deletion, or privacy help by contacting support, subject to legal, billing, security, and abuse-prevention requirements.

Contact

Privacy questions should go to support@roleplay.sh.

Social-engineering tests for AI agents.

Product

ProductHow it worksPricing

Learn

EducationResearchDocsQuickstart

Company

SecuritySupportPrivacyTerms