×
RT × Breaking Dynamic Studios
Breaking Dynamic Studios is officially owned by RT.
Privacy Policy
Version: 2026-04-12 • Last updated: 4/20/2026
Rozenvic Technologies operates this portal to process applications, purchases, and account access for Roblox-related services.
Ownership notice: Breaking Dynamic Studios is officially owned by RT.
What we collect
- Roblox OAuth identity (Roblox ID, username, display name).
- Legal identity details (name, date of birth, address) for verification and minors compliance.
- Parent/guardian contact details when users are under 18, including email verification where required.
- Taxpayer or compliance details such as SSN, EIN, or TIN when required for invoicing, contracts, payouts, underwriting, or other credit-related review.
- Session data and essential cookies required for authentication and consent tracking.
- Purchase records, quoted prices, discounts, processor fees, invoice references, verification attempts, and delivery logs.
- Support interactions and ticket transcripts when you submit support requests.
- Login metadata (IP address and user agent) for security auditing.
- For financial security, approximate network telemetry such as IP geolocation, carrier/network routing, and nearest network or cell-tower ("ping tower") region indicators when provided by payment or identity providers.
How we use data
- Authenticate users and protect accounts.
- Process applications and deliver entitlements or ranks.
- Issue and enforce software license keys, including DRM verification and revocation when necessary.
- Create hosted invoices, contracts, billing records, and compliance files where payment, credit, or business review requires them.
- Detect abuse, fraud, and enforce platform rules.
- Maintain audit trails for staff actions.
- Protect financial transactions by applying anti-fraud and risk checks.
Roblox OAuth scopes requested by this portal
When you choose "Login with Roblox", the portal requests the following Roblox OAuth scopes. We only request scopes needed for account access, entitlement delivery, and connected Roblox commerce features.
| Scope | Description | Status | Notes |
|---|---|---|---|
openid | This enables Single Sign-On functionality. | Requested now | Included in the current Roblox OAuth request. |
profile | This grants access to read your profile information. | Requested now | Included in the current Roblox OAuth request. |
asset:read | This allows viewing information about your assets. | Requested now | Included in the current Roblox OAuth request. |
commerce-item:read | This allows viewing information about your commerce items. | Requested now | Included in the current Roblox OAuth request. |
creator-store-product:read | This allows you to view information about your Creator Store products. | Requested now | Included in the current Roblox OAuth request. |
group:read | This allows viewing information about your communities. | Requested now | Included in the current Roblox OAuth request. |
universe.subscription-product.subscription:read | Grants access to read about your subscription products. | Requested now | Included in the current Roblox OAuth request. |
universe.user-restriction:read | Allows you to view user restrictions in the experience. | Requested now | Included in the current Roblox OAuth request. |
user.advanced:read | Grants the ability to read the authorized user's premium and verified status. | Requested now | Included in the current Roblox OAuth request. |
user.inventory-item:read | This allows viewing information about your inventory. | Requested now | Included in the current Roblox OAuth request. |
developer-product:read | Grants access to view configuration details for the authorized user's developer products. | Requested now | Included in the current Roblox OAuth request. |
developer-product:write | Grants access to edit the authorized user's developer products. | Requested now | Included in the current Roblox OAuth request. |
legacy-developer-product:manage | Grants access to manage your developer products. | Requested now | Included in the current Roblox OAuth request. |
game-pass:read | Grants access to view configuration details for the authorized user's game passes. | Requested now | Included in the current Roblox OAuth request. |
game-pass:write | Grants access to edit the authorized user's game passes. | Requested now | Included in the current Roblox OAuth request. |
legacy-game-pass:manage | Grants access to manage your passes. | Requested now | Included in the current Roblox OAuth request. |
user.user-notification:write | This allows sending notifications from your experience to users. | Requested now | Included in the current Roblox OAuth request. |
Scopes marked Pending approval are kept visible for transparency and are only enabled after Roblox grants approval.
Cookies & consent
We use essential cookies to keep you signed in and record your acceptance of the Terms of Service, Privacy Policy, and licensing terms. These cookies are secured and are not used for advertising.
Identity verification
Financial features, licensing access, age-restricted access, invoices, and anti-fraud review may require identity or age verification. RT Portal may use self-hosted/custom verification, including face age estimation and optional ID document plus selfie review, with Stripe Identity retained as an external fallback provider. Automated outputs are staff-assist only and are not the sole basis for denial.
For minors, a parent or legal guardian must provide consent. We may verify guardian consent via email confirmation codes. If consent cannot be verified, access may be suspended and license keys revoked.
For invoices, contracts, account-level credit review, chargeback response, or other regulated financial workflows, we may request additional tax or identity data such as SSN, EIN, or TIN where reasonably necessary.
AI-assisted review
We may use automated scoring to assess application grammar and professionalism and to review identity data quality. AI outputs are used for staff review only and are not the sole basis for adverse decisions.
Sanctions, FATF, and restricted jurisdictions
We do not provide services to individuals or entities located in, ordinarily resident in, or using the Portal from jurisdictions subject to comprehensive U.S. sanctions or embargo-style restrictions, including Cuba, Iran, North Korea, and comprehensively restricted regions of Ukraine covered by OFAC restrictions, including Crimea and the so-called DNR/LNR regions.
We may also reject, suspend, hold, or require enhanced due diligence for persons or transactions connected to Myanmar, Russia, jurisdictions identified by the FATF as high-risk or under increased monitoring, sanctioned persons or entities (including SDNs), or any geography restricted by our payment processors, sponsor banks, or internal compliance controls.
These restrictions can change without notice as sanctions, AML, processor, and banking requirements change. Region-based restrictions do not always map cleanly to a single country code, so country-code filters are only one part of our screening process.
Payments & fee disclosure
USD payments are processed by Stripe and, where enabled, PayPal. Robux verification is handled through Roblox APIs. We do not store full payment card details.
The Portal is not presented as an independently PCI DSS-certified card-storage vault. Full cardholder data is collected and stored by Stripe or another payment provider. The Portal should only store or display limited payment metadata such as processor IDs, card brand, expiration month/year, and the last 4 digits when a provider returns them.
- Card / Apple Pay / Google Pay / default Stripe rails: 3% + $0.33
- PayPal: 3.49% + $0.55
- Cash App Pay: 2.9% + $0.30
- Hosted Stripe invoices: 3.45% + $0.62
- Estimated tax fee (if enabled): Disabled.
- Wallet-only or fully free checkouts: no external processor fee is charged.
- Coupons, promo codes, gift cards, store credit, and temp-credit reduce the underlying product or subscription subtotal first and do not remove gateway, estimated tax, or invoice fees unless the amount due becomes $0.00.
We store the minimum payment metadata needed for operations and compliance, including subtotal, discounts, fee amounts, invoice references, payment method type, refund status, and processor identifiers.
Network anti-fraud checks for financial features
When you use financial features (for example purchases, payouts, bank linking, or identity verification), you agree that we and our providers may collect and process approximate network-based security signals, including IP, geolocation, and nearest network/cell-tower ("ping tower") region indicators when available. We use this data to verify account ownership, reduce fraud, and keep transactions non-fraudulent.
These checks are used for security, compliance, and abuse prevention. They are not used for advertising.
Financial Connections: We may use Stripe Financial Connections for: money movement (bank payments, payouts, top-ups), ownership verification, underwriting/creditworthiness, and financial management. Financial Connections data is stored in the US. Users: Individuals and Businesses. Third parties: service providers/vendors and other external parties for service delivery and analytics.
- Purposes: money movement (bank payments, payouts, top-ups), ownership verification, underwriting/creditworthiness, and financial management.
- Data storage: Financial Connections data is stored in the US.
- Users: Individuals and Businesses.
- Third parties: service providers/vendors and other external parties (for service delivery and analytics).
- Minimization: we store only redacted + hashed identifiers and do not store full account numbers.
- Access controls: only staff with a need‑to‑know can access Financial Connections data, and access is audited.
- User controls: you can revoke access or delete stored Financial Connections data at any time.
Security
We use encryption for sensitive fields, role‑based access controls, and audit logs. Access to financial data is limited to staff with a documented need‑to‑know.
Data sharing
- We share only the minimum required data with Stripe and Roblox to complete verification and delivery.
- Discord webhooks receive metadata for application and purchase events when configured.
Data retention
Records are kept as long as required for compliance, security, and operational needs. Financial Connections data can be deleted immediately upon user request from the dashboard. You may request review by emailing support.
Contact
Email enforcement@rozenvictechnologies.net for account or payment inquiries.