Know what happens to your data.

1. Controller and contact

Privacy requests: admin@rtwochain.com (subject: Cloudburg privacy).

2. Website delivery and security

Cloudflare provides website hosting, transport security, the account database and operational infrastructure. Network data such as IP address, request time, URL, browser metadata and security events may be processed to deliver the service, prevent abuse and diagnose errors. Application error logs contain the exception type rather than project content.

Legal basis: Article 6(1)(f) GDPR, our legitimate interests in a reliable and secure website. When providing a requested account service, Article 6(1)(b) GDPR also applies. Necessary network data cannot be omitted while using the website.

3. Project files and local drafts

Selected project files, paths, originals and edits are held in memory in the current tab. The project desk does not upload them to Cloudburg. Reloading, closing or changing account scope clears that in-memory work. Download before leaving. Your independent downloads are stored according to your browser settings.

Saving a workflow or campaign stores its text in this browser’s local storage, separated by account or local mode. Saved drafts have no automatic expiry and remain after sign-out until cleared in Workspace settings or the browser. The language preference is stored separately. These stores implement the save and language choices you request; they are not used for third-party advertising.

The requested tools are provided under Article 6(1)(b) GDPR. Terminal storage needed to perform an expressly requested save or language choice is used for that requested function under § 25(2) no. 2 TDDDG. No analytics or third-party advertising SDK is integrated in the application.

4. Accounts, recovery and workspaces

When registration is enabled, we process your display name, username, external contact email, verification status, reserved Cloudburg address, Developer ID, File Wallet, password hash, session information, policy acceptance and account timestamps. The contact email is used for account verification and password recovery, not for marketing subscriptions. Workspace names, ownership and membership records are stored when that feature is enabled.

Legal basis: Article 6(1)(b) GDPR for the account and requested recovery; Article 6(1)(f) GDPR for abuse prevention and security limits. The details marked required are necessary to create and secure an account; without them you may still use the local project tools. System messages are sent through Cloudflare Email Service to your selected contact address.

The authentication session uses a Secure, HttpOnly, SameSite=Lax cookie, normally with 24-hour validity. Session renewal can extend a signed-in session. Cookie validity is separate from database retention. Sign-out revokes the current session; it does not delete the account or saved browser drafts.

5. GitHub and other websites

Public Git import makes requests directly from your browser to GitHub for repository metadata and the selected files. GitHub receives your network request and the requested repository/file identifiers. This happens when you request the import. Read the GitHub privacy statement ↗.

Where Sign in with Cloudburg is enabled for a registered website, the consent screen identifies the website and requested identity scopes. Only the granted identity data is shared. It does not grant project, mailbox, AI or billing access. Revoking a consent prevents future authorization under it but does not promise immediate deletion of data or sessions already held by that website. Verified account owners can register public authorization-code/S256 web clients in Developer apps (beta).

6. Providers and international processing

Cloudflare, Inc. and its disclosed subprocessors provide the hosting and account infrastructure. The account database is configured with EU jurisdiction; this does not make all website, security, support or email processing EU-only. Cloudflare operates internationally, including in the USA. Its published data-processing terms describe safeguards including applicable adequacy frameworks and EU standard contractual clauses for relevant transfers. Copies and provider details can be requested from the controller.

Cloudflare data-processing terms ↗ · Cloudflare privacy information ↗

7. Retention and deletion

Browser-memory project data lasts for the current tab as described above; saved local drafts and the language preference remain until cleared. Account, workspace and consent records are kept while needed for the requested account and permissions. Expired credentials and sessions stop authorizing access. Use the security center for account export and deletion. Contact the operator for access requests beyond the included snapshot.

Security logs and request-limit records are retained only as needed for their security purpose, incident investigation and applicable legal claims. Where a legal duty or a documented dispute requires retention, the affected records may be retained for that purpose rather than normal account use. Provider backup/log lifecycles can differ from the active database. Requests are assessed by data category and applicable obligations; clearing local drafts or signing out does not purge provider backups, other websites or your downloads.

8. Your rights

Subject to the GDPR conditions, you can request access, correction, erasure, restriction and portability. You may object to processing based on legitimate interests, and withdraw a consent for future processing where consent is the basis. Contact the controller above; do not send your password. You can complain to a data protection authority, including the authority for Lower Saxony where the controller is based.

Lower Saxony data protection authority ↗

9. AI, advertising and decisions

OpenAI is not connected in this release; the Autopilot panel does not submit prompts. Customer mailboxes, incoming project transfers and campaign sending are not active. Private Cloud files upload only on your explicit instruction. Promotions are for Cloudburg only. No decision with legal or similarly significant effect is made solely by an automated system in this release. Material new data flows will be described before the related feature processes your content.

Account security and activity

Optional authenticator protection stores the TOTP setup secret and backup-code records encrypted in the identity database. Activation requires a valid code. Password reset preserves an enrolled factor and invalidates pending authentication challenges. No trusted-device bypass is offered.

Selected security and workspace-administration events contain a fixed action, result, reason category, timestamp, request reference and necessary account/workspace references. They contain no passwords, setup keys, codes, tokens, raw request bodies or project text. Security activity expires after 90 days and is then excluded from account views and exports. An internal hourly process deletes expired application records in bounded batches. Provider logs and backups follow separate lifecycles.

Session revocation, account export, deletion and workspace renaming require your current password and a recent authenticated session. The self-service export identifies its records and exclusions. Account deletion removes credentials and account access; retained security records lose their account/workspace references. It does not erase browser-local drafts or data already held by another website. Contact the operator for privacy requests beyond these controls.

Sign in with Cloudburg and developer apps

When you authorize a website, it receives only the identity fields covered by the permissions shown: an account identifier, profile fields when requested, and your private external contact email and verification status only with the email permission. Review the exact callback address before allowing access. App names, brands, domain ownership and legal identities are not verified merely by registration. Other websites control their own sessions, retention and copies of your profile.

Developer app records contain the owner account reference, app name, public client ID, registered callbacks, fixed policy and timestamps. Creation references and unresolved-operation records are retained for reconciliation and removed with the account. App-action history expires after 90 days and is deleted by bounded internal maintenance. Saving or disabling an app revokes Cloudburg-issued authorization codes, access tokens and consent; an already issued ID token can remain valid until its expiry, at most five minutes.

Cloudburg Connect is an optional live test website. It keeps short-lived tokens encrypted on the server, with a test session of at most five minutes and a pending sign-in transaction of ten minutes. Expired records are removed by internal maintenance. Its cookies are separate from the main account session. No OAuth token is written to browser storage.

Private Cloud files

When you explicitly upload through Cloud files, Cloudburg stores the contents in private Cloudflare R2 object storage for your account. The database records the owner account reference, relative path/filename, byte count, SHA-256 digest, upload reference, state and timestamps, plus an internal object reference. Paths and filenames can contain confidential or personal information. Upload only content you are entitled to store.

Your verified session authorizes listing, download, deletion and reconciliation. Workspace membership and public Developer ID/File Wallet names do not grant another person access. Requests have account limits for capacity and abuse prevention. Routine application errors omit contents, raw upload bodies, credentials and free-form file paths. The account snapshot includes bounded file metadata with a completeness indicator; download file contents separately. No file is automatically scanned, executed or sent to AI.

The private R2 bucket has EU jurisdiction for its object data. This does not make all request handling, account services, security logs, support or provider processing EU-only. The provider and international-transfer information above still applies.

Contents remain until you delete the cloud file, subject to service restrictions and terms. Unconfirmed operations remain tracked and reserve capacity. Confirmed-deletion metadata is normally retained for 30 days and then removed by bounded maintenance, or earlier with account deletion. Backlogs may delay cleanup. Upload replay protection uses retained references; after their retention window an old reference may no longer be recognized. Pending/deleting records are not blindly purged. Provider backups/logs and independent downloads have separate lifecycles.