Privacy Policy

Version: 2026-05-08 • Last updated: 6/19/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.

Discord bots: our Discord application-specific privacy disclosures are published separately at Bot Privacy Policy and Bot Terms of Service.

What we collect

• Roblox OAuth identity (Roblox ID, username, display name).
• Connected-account and SSO data such as Discord ID, Discord OAuth identity, Linked Roles sync state, Authentik / RT SSO account claims, and account-link timestamps when those features are used.
• When you authorize Discord account-linking or linked-role apps, Discord OAuth data such as username, global name, avatar, email, guild/server list, approved guild member snapshots in managed guilds, and linked third-party connection data when Discord provides it through approved scopes.
• 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, ITIN, or TIN when required for invoicing, contracts, payouts, underwriting, financing review, 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.
• Secure upload-link records, uploader identity details, upload notes, private file metadata, and stored contractor or employee source bundles when secure upload links are used.
• Manual credit-review records such as uploaded credit reports, report metadata, financing-request acknowledgments, signatures, contract acknowledgments, and owner-review notes when financing or invoice-risk workflows require them.
• Support interactions and ticket transcripts when you submit support requests.
• Harris AI chat logs, prompts, replies, attachment metadata, selected model tier, Discord context, and abuse-review flags when you use portal-gated AI bot features.
• Login, invite-route, and security metadata such as IP address, user agent, request timestamps, and referer data for security auditing, fraud prevention, and bot invite tracking.
• 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.
• Operate connected-account features such as Discord linking, Linked Roles syncing, RT SSO, and owner/admin Discord inventory or audit pages.
• Gate Harris AI access, enforce model-tier eligibility, investigate unsafe AI use, and maintain bot-side abuse-review evidence.
• 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, third-party financing records, and compliance files where payment, credit, upload, or business review requires them.
• Review secure uploads, service bundles, or contractor deliveries and make them available only to authorized owner/staff surfaces or on the actual server.
• 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.

Connected accounts, Discord, and SSO

If you link Discord, use Linked Roles, or sign in with RT SSO / Authentik, the portal stores the account-linking and session information needed to complete those flows, protect the account, and operate owner/admin review tools. This can include approved Discord OAuth data such as your Discord email, server list, managed-guild member snapshots, linked third-party connection data, OAuth scopes granted, and token refresh metadata. Some Discord and Aegis-linked disclosures are published separately at Bot Privacy Policy and Bot Terms of Service.

For Discord-linked flows, we may request approved scopes including identify, email, guilds, guilds.join, guilds.members.read, connections, and role_connections.write when those scopes are needed for account linking, linked roles, staff/server access, or abuse review. Discord currently documents activities.read as not currently available for apps, so that scope is not used unless Discord later makes it available to the relevant application.

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, ITIN, or TIN where reasonably necessary.

A Tax ID or SSN-equivalent (SSN, TIN, EIN, or ITIN) is required before invoice checkout or hosted invoice access is granted. Invoices are due within 10 days. After 30 days past due, notices shift from friendly reminders to direct escalation and related services may be paused. Final notice review begins at 45 days past due. Unresolved balances at 90 days past due may be referred for debt collections or legal review. Fees, taxes, and other disclosed charges remain due while the invoice is open. The portal does not automatically add percentage-based default or labor penalties; any added collection or legal costs must be separately disclosed and only used where permitted.

AI-assisted review

We may use automated scoring to assess application grammar and professionalism, review identity data quality, and assist support or moderation workflows. We may also use portal-gated AI bot features such as Harris, where user prompts, replies, selected models, and Discord/server context can be logged and reviewed for safety, abuse prevention, fraud review, and platform enforcement. AI outputs are used for staff review only and are not the sole basis for adverse decisions. Where configured, this can include our self-hosted AI gateway and associated internal services.

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. Some checkout surfaces may also expose third-party payment or pay-later methods routed through Stripe or the relevant provider, including services such as Affirm, Klarna, or Zip when enabled for the specific checkout. 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: 7% total buyer checkout fees (3% platform service + 2% technology/security + 2% payment processing)
• PayPal: 7% total buyer checkout fees for standard PayPal checkout; Pay Later uses no buyer payment-processing surcharge where detected
• Cash App Pay: 5% total buyer checkout fees; no extra payment-processing surcharge
• Hosted Stripe invoices: 5% total buyer checkout fees on hosted invoices
• PA sales tax: 6% PA sales tax.
• 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 checkout fees, PA sales 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, audit logs, protected internal bot APIs, and private file storage paths for secure uploads and manual credit-review files. Access to financial, identity, and secure-upload 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, Authentik / RT SSO, and internal bridge services receive the minimum data needed for account-linking, Linked Roles, SSO, bot logging, or portal-connected verification flows.
• Where enabled for a checkout, payment or pay-later providers such as PayPal, Affirm, Klarna, or Zip may receive transaction and identity data needed to authorize, process, or review the payment.
• Discord webhooks receive metadata for application and purchase events when configured.

Data retention

Records are kept as long as required for compliance, security, fulfillment, financing review, dispute handling, and operational needs. Financial Connections data can be deleted immediately upon user request from the dashboard. Secure upload files, manual credit-review files, and account-linking records may be retained longer when required for service delivery, fraud prevention, debt review, or legal compliance. You may request review by emailing support.

Contact

Email enforcement@rozenvictechnologies.net for account or payment inquiries.