How Wobli collects, uses, stores, and shares account information and game-project content.
1. Who Is Responsible for Your Data
Operator and personal-data controller: Martin Skondrojanis. Contact address: Konečná 23, 39010, Czechia. Email: info@wobli.site.
This policy covers wobli.site and the Wobli companion plugin’s connection to the service. Wobli is an independent service, not Roblox Corporation or Google. Those companies are responsible for the accounts and platform services they provide under their own policies.
2. Information We Collect
Wobli is a web workspace for creating and refining Roblox games, with a companion plugin for Roblox Studio. This document describes the information processed by wobli.site and its Studio connection.
- Account information: a Wobli account identifier, display name, sign-in email when supplied, and the identifiers of connected Google or Roblox accounts. Your profile may also contain a bio or images you upload.
- Onboarding answers you choose to provide: intended use, age range, experience, and how you found Wobli. The application does not request a full date of birth during onboarding.
- Creative content: prompts, chat messages, uploaded reference images and files, generated images, scenes, scripts, project titles, saved versions, and build or preview results.
- Studio connection information: approved device and connection identifiers, project and Roblox place identifiers, plugin version, connection status, and the content you ask the plugin to apply or send back as a preview.
- Billing and usage information: subscription, customer and payment identifiers, plan and renewal status, credit reservations, charges, refunds, and provider-usage records. Payment details entered at checkout are processed by Whop; Wobli does not store your full card number or security code.
- Technical information: request times, IP addresses and browser information processed by hosting infrastructure, authentication and rate-limit records, errors, and build activity. Optional notifications require a browser push endpoint and associated delivery keys.
3. Google Sign-In Data
If you choose Continue with Google, Wobli requests the openid, email, and profile permissions. Google supplies an account identifier, a verified email address, and basic profile information. Wobli stores the identifier, email address, and display name to create or find your Wobli account, sign you in, and associate your workspace with the correct account.
Wobli does not request access to Gmail messages, Google Drive files, contacts, calendars, or your Google password. The current sign-in integration does not request offline access or retain Google access or refresh tokens for ongoing access to Google services.
Google sign-in information is kept in Wobli account storage and backups. It is not included automatically in prompts sent to the game-generation model. Wobli does not use Google sign-in data for advertising or to train a general-purpose AI model, and does not sell that data.
Wobli uses information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements where applicable. You can remove Wobli access through your Google Account connections page. Removing access prevents future Google authorizations but does not itself delete the existing Wobli account, projects, or an already active Wobli session.
4. How We Use Information
Wobli uses account information to authenticate you, show your profile, keep projects associated with their owner, and connect the Studio device you approve. Google or email sign-in does not automatically authorize access to a Roblox account; Roblox linking is a separate action.
When you request generation, relevant prompts, project context, reference images, scenes, or scripts are sent to the service performing that operation. Text planning and game-code generation on wobli.site currently use Microsoft Azure. The response and recorded usage are saved so you can review the result, return to earlier versions, and see the resulting credit charge. Information you type into a prompt or include in a file can be part of that request.
We also use information to run subscriptions and credit accounting, prevent unauthorized access and duplicate charges, investigate errors, respond to support requests, and send optional build notifications. We do not operate a public feed that automatically publishes your private projects.
If email sign-in is enabled and you request a link, your email address and the sign-in message are sent to Resend for delivery. If a voice-input feature is enabled and you choose it, audio is processed for transcription before the resulting text is used as your input.
5. Legal Grounds for Processing
Under the EU General Data Protection Regulation (GDPR), we use the following grounds according to the purpose of the processing. Accepting the Terms of Use is not blanket consent to unrelated uses of personal data.
Contract and steps you request before entering a contract (Article 6(1)(b)): creating and authenticating your account, saving your work, performing requested generation, connecting Studio, providing subscription access, and handling service requests. We need an account identifier to provide a private workspace. We need the content relevant to an operation to perform it. Optional profile and onboarding answers are not required for unrelated processing.
Legitimate interests (Article 6(1)(f)): protecting accounts, preventing fraud and duplicate charges, diagnosing faults, maintaining reliable records, and establishing or defending legal claims. These interests must be balanced against your rights; you can object to this processing.
Legal obligations (Article 6(1)(c)): records and disclosures required by applicable tax, accounting, consumer-protection, or other law. Consent (Article 6(1)(a)), where required: optional browser notifications and other optional processing presented with a consent choice. You can withdraw consent without affecting processing that was lawful before withdrawal.
We do not sell personal data, build advertising profiles, or use your Google account information to train a general-purpose AI model. Generation produces creative output; Wobli does not use it to make automated decisions about you with legal or similarly significant effects.
8. Storage and Security
Public Wobli account and project records are stored in Cloudflare D1, with files and recovery copies in Cloudflare R2. Scheduled backups are encrypted before they are stored separately from the running application.
The public website uses HTTPS. Account ownership checks limit access to saved projects; Studio device and project checks control plugin access. Web-session, email-link, and plugin connection tokens are stored as hashes on the server. Provider credentials are held separately from public browser code. These controls reduce risk but cannot guarantee that storage or transmission will never be compromised.
9. Data Retention and Deletion
We retain account identifiers, sign-in email, profile information, saved projects, uploaded files, generated results, and project history while they are needed to provide your workspace. These records are not automatically removed simply because you stop signing in or cancel a subscription. You can request account closure and deletion by email; there is currently no self-service account-deletion screen.
On a verified deletion request, we assess and remove or anonymize personal information that is no longer needed, including connected-account identifiers and saved content. We may keep specific records when required by law or needed for an existing dispute or legal claim. We explain a refusal or restriction rather than treating cancellation or deletion as a waiver of your rights.
Short-lived authorization requests and links stop working at the expiry times above. Expired OAuth and email-link records are removed during subsequent authorization activity. Expiry of a login session does not delete the account or its content.
For billing and credit records, retention is determined by the applicable accounting or tax obligation, reconciliation of the transaction, and any open refund, dispute, or legal claim. For support and security records, retention depends on resolving the request or incident and the period in which a related claim may be brought. We limit retained data to what the relevant purpose requires.
Encrypted backups are separate recovery copies and are not erased instantly when active records are deleted. Backup removal is handled by the operator; there is currently no automatic rotation period. A deletion request includes review of recovery copies, removal when they are no longer needed for recovery or a legal obligation, and restricting any temporarily retained copy to that purpose. If a backup is restored, applicable deletion requests must be reapplied. We do not promise that independent payment or identity providers delete records they must retain for their own obligations.
10. Your Choices and Privacy Rights
You can edit supported profile fields, export saved work, sign out of web sessions, revoke a Studio connection, remove Wobli access in your Google or Roblox account, and turn off browser notifications. Revoking a provider connection, signing out, or cancelling a subscription does not automatically erase saved Wobli data.
Under the GDPR, subject to its conditions and exceptions, you can request access, correction, deletion, restriction of processing, or a portable copy of data processed by automated means on the basis of consent or a contract. You can object to processing based on legitimate interests and withdraw consent for consent-based processing. You can also complain to a supervisory authority, including the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, ÚOOÚ) or an authority in the EU country where you live or work.
We respond without undue delay and normally within one month of receiving a privacy request. If complexity or the number of requests lawfully requires up to two additional months, we explain the extension within the first month. Requests are normally free. We may ask for proportionate information to verify account ownership; do not send identity documents unless specifically needed and requested through an appropriate channel.
Send privacy and account-deletion requests to info@wobli.site. Include enough information to identify your Wobli account, but do not send passwords, payment-card numbers, or login tokens.
11. Adults Only
Wobli accounts and paid services are intended for people aged 18 or older. This is Wobli’s eligibility rule, not a statement that every online service must use the same minimum age. We do not offer an under-18 account or a parental-consent exception.
A Roblox or Google account does not establish eligibility for Wobli. The application currently asks for an age range rather than verifying a date of birth or identity document. An age answer is not verified proof of age.
If you believe a person under 18 has supplied personal data or holds a Wobli account, contact info@wobli.site. We will investigate, restrict ineligible access where appropriate, and remove personal data that is not required for a legal obligation or claim.
12. Provider Privacy Information
These providers describe their own processing, retention, and security practices. Their policies do not replace Wobli’s responsibility for its account and project data. Email and other optional services process data only when their feature is configured and used.
13. International Processing
Wobli uses Cloudflare and the external services described above. Processing can take place in countries other than your own according to those services’ infrastructure and account settings. Wobli does not currently promise that all data stays in one country or in the European Union.
The service operator is based in Czechia. Transfers of personal data outside the European Economic Area require a lawful basis for that transfer. Depending on the destination and recipient, the relevant protection can be a European Commission adequacy decision or appropriate safeguards such as the Commission’s Standard Contractual Clauses, with additional measures where required.
Cloudflare’s published Data Processing Addendum describes its international-transfer arrangements, including the EU Standard Contractual Clauses and eligible Data Privacy Framework transfers. Other providers describe their processing in the policies linked above. You can contact us for information about the safeguards applicable to your data or a copy of relevant safeguards, subject to necessary redaction of confidential information. We do not claim that every provider or every processing location has the same certification or transfer mechanism.
14. Changes to This Policy
The date above identifies the latest revision. We update this policy when our processing changes. For a material change, we provide an appropriate notice before it takes effect where required. If a new use requires consent, a policy update alone does not supply that consent.
15. Contact
Operator and personal-data controller: Martin Skondrojanis. Contact address: Konečná 23, 39010, Czechia. Email: info@wobli.site.