Privacy

Privacy on this website

Updated September 15, 2026. The controller is Mohamed Lakbir, trading as dimbreaki studio, Rotdornstraße 13, 40472 Düsseldorf, Germany. Contact: support@dimbreaki.com.

Page delivery and hosting

This website uses no analytics or advertising trackers and no remotely loaded fonts. Images, fonts and scripts are served from our domain. The web server and hosting provider process IP address, time, requested address, data volume, status code and any referrer and browser information for delivery, troubleshooting and abuse prevention (GDPR Article 6(1)(f), our interest in safe operation). These technical data are needed to deliver the requested page. The host is IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany. Access logs and system journals rotate daily, including quiet days. Archived files are removed after 14 days through rotation; including the active file, this is approximately up to 15 days in normal operation. Necessary incident evidence preserved separately may remain until investigation is complete. Game-server database backups are explained below.

Language preference and cookies

Selecting DE or EN sets dimbreaki-language to de or en for your requested language. It has no individual visitor identifier and is a session cookie without a fixed expiry. Browsers can restore sessions after restart; you can delete the cookie in browser settings. Older year-long language cookies are replaced by session cookies on the next visit. Storage is solely for the expressly selected language (section 25(2)(2) TDDDG; related processing under Article 6(1)(f)). No optional analytics or marketing cookies are set.

Email contact

An email link opens your email program. We receive your address, message and optional attachments only when you send a message. General questions rely on Article 6(1)(f), our interest in responding; contract-related requests on Article 6(1)(b); privacy requests on Article 6(1)(c). We need contact details to reply by email. Do not send passwords, recovery codes or unnecessary personal information. Correspondence is removed after final resolution when no longer needed for the request or specific legal claims. Mandatory retention of relevant business records remains unaffected.

We use a Microsoft Exchange Online (Plan 1) business mailbox for support@dimbreaki.com, accessed through Outlook among other clients. Microsoft receives email data to provide the mailbox; simply visiting this website does not load Microsoft tracking. The Microsoft recipient details, international-transfer information and deleted mail information in the app notice below also apply to website email inquiries.

Public account deletion

The deletion form sends Player ID and recovery code through HTTPS to our game server to verify and carry out the requested account deletion (Article 6(1)(c) together with Articles 12 and 17). Player ID alone cannot authorize deletion. Use the recovery code only in the form, never in support email. It is not sent as a URL parameter. The app notice explains deletion scope, evidence, backups and separate email records. An interrupted response can mean deletion has already taken place. Account deletion is not withdrawal from a purchase.

Your rights

Subject to legal conditions you have rights to access, rectification, erasure, restriction and portability. You may object to legitimate-interest processing for reasons relating to your particular situation. Where consent applies, you may withdraw it for the future without affecting prior lawful processing. You may complain to a supervisory authority, particularly where you live or LDI North Rhine-Westphalia: https://www.ldi.nrw.de/. Send requests to the email address above. No automated decisions produce legal or similarly significant effects. You do not have to give blanket consent to this notice to read the website.

Privacy policy for the Dimbreaki app

Updated September 15, 2026. Dimbreaki is intended for people aged 13 and over. This notice covers the app and game server. Available functions depend on the platform and installed version.

1. Controller

Mohamed Lakbir, trading as dimbreaki studio, Rotdornstraße 13, 40472 Düsseldorf, Germany. Contact: support@dimbreaki.com.

2. Plain-language summary and younger players

Saves and settings are stored on your device. Online features use a pseudonymous guest profile; pseudonymous does not mean anonymous. We do not use advertising networks or cross-app advertising tracking. Screenshots, log attachments and Creator codes are optional.

The 13+ audience is not an official content rating. Dimbreaki is not intended for under-13s. Minors need their parent or guardian's authorization for contracts where the law requires it. For consent-based processing in directly offered online services, Germany requires parental consent or authorization below age 16. Using the app or reading this notice is not blanket consent. Ask a parent if something is unclear.

3. Local data and technical connections

The app stores settings, saves, diagnostic logs and any exports locally. Credentials are protected using Android Keystore or iOS Keychain. Registration or recovery generates a random installation identifier for abuse prevention. The app needs internet access and may vibrate. It does not request location, camera, microphone, contacts or general photo-library permissions. A voluntary image picker uses only the selected files. Necessary device storage and access for requested functions rely on section 25(2)(2) TDDDG.

At startup the app checks the server for required updates for its platform. Online functions check availability. These requests involve IP address, time and technical request data to provide a safe and compatible service, under GDPR Article 6(1)(f). Production connections use HTTPS.

4. Online profile and gameplay

A guest profile is created for requested online features. The revised menu does not create a new profile merely to display a balance; existing sessions may be used. Older versions may create a profile for a balance request when the main menu first opens. Registration sends the installation identifier and creates a random Player ID and credentials. The server stores hashes of installation identifiers and credentials, cloud saves, Breaki ownership, loadouts, transformations, online match state and balances where used. Opponents receive the game and team information needed for a shared match. Requested game and account functions rely on Article 6(1)(b). Technical connection data and security events with pseudonymous player references support troubleshooting and abuse prevention under Article 6(1)(f), our interest in operating a safe, functioning service.

5. Optional purchases and Creator codes

Where an Android version offers purchases, Google Play handles payment. The app and server process Player ID, a derived obfuscated account identifier, product and transaction identifiers, purchase token, purchase and receipt times, country, Crystal amount, validation, credit and refund states, and price and currency provided by the store. An optional Creator code may be associated with a purchase. Personal player or purchase data is not shared with Creators. Purchase history, wallet and Crystal transactions stay with the same Player ID after recovery. A transaction is credited once. Recovery does not automatically transfer the local save to another device.

Google validates payments; purchase and cancellation states are reconciled with the server. The game server does not receive full payment-card or bank details. Contract and refund handling rely on Article 6(1)(b); fraud and duplicate-credit prevention on Article 6(1)(f); legally required records on Article 6(1)(c). Free development grants are labelled as tests and are not paid purchases. They use player, product and operation identifiers and the Crystal amount.

6. Bug reports, email and external links

You can send a bug report with text and explicitly selected screenshots or diagnostic logs to the game server. Log attachments are off by default in the revised app; check the selection before sending in older versions. Reports also contain technical app/device details and a player reference. Do not send passwords, recovery codes, payment details or unnecessary information about yourself or others. Local log export uses system sharing; you choose the recipient.

Email support processes sender address, message, attachments and correspondence. Account and contract support rely on Article 6(1)(b); general questions and voluntary bug reports on Article 6(1)(f), our interest in answering requests and fixing errors. Privacy requests rely on Article 6(1)(c).

For support@dimbreaki.com we use a business mailbox hosted in Microsoft Exchange Online (Plan 1), accessed through Outlook among other clients. The provider is Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland. Microsoft and its subprocessors process sender and recipient addresses, messages, attachments, and technical connection and security data to provide the email service. Customer Data are processed on our behalf to provide the service under the Microsoft contractual terms and the Microsoft Products and Services Data Protection Addendum (DPA). Game saves are not stored in this mailbox.

Processing outside the EEA, including by Microsoft Corporation in the USA, is possible in the circumstances described by Microsoft. The EU Data Boundary does not guarantee that all processing takes place exclusively within the EEA. Transfers to third countries are subject to the safeguards described in the DPA, including the EU standard contractual clauses incorporated there. Details of processing terms and access to these safeguards: https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA Information about continuing data transfers: https://learn.microsoft.com/en-us/privacy/eudb/eu-data-boundary-transfers-for-all-services

Discord, Twitch and Patreon community links open external services only when selected. Their providers' rules and privacy notices apply. They are not loaded as embedded app trackers. Opening a link sends the destination information such as your IP address and browser/app data.

7. Hosting and other recipients

Game servers and database are hosted by IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany. The operator and necessary service providers have access as required for operating the service. Google companies receive purchase and account-matching data for Google Play purchases and process payment under their own terms. Google describes international processing and transfer safeguards at https://policies.google.com/privacy?hl=en. We do not sell player data to advertising networks or data brokers.

8. Retention and backups

• Local diagnostic logs and exports: cleaned after 14 days when the app runs.
• Bug reports and attachments: expire after 30 days and are deleted at the next daily cleanup.
• Access tokens: 15 minutes; refresh tokens: 30 days. Revoked sessions are cleaned after 30 days and inactive expired sessions after 180 days. This does not erase the durable profile.
• Installation quotas: cleaned after 2 days; completed match journals after 24 hours through server cleanup jobs.
• Profile, cloud, ownership, purchase history and wallet: retained for profile use and removed on account deletion, unless a specific legal retention duty applies.
• Web access logs and system journals: rotated daily, including quiet days; archived logs are removed after 14 days through rotation. Including the active file, this is approximately up to 15 days in normal operation. Necessary incident evidence preserved separately may remain until the investigation is completed.
• Deletion receipts: pseudonymous Player-ID hash, reference and timestamps for 1,095 days, then the next daily cleanup. A hash is not automatically anonymous.
• Database backups: separate daily copies on the hosting server. Files whose age in complete days exceeds 14 are removed at the next successful daily run. They are not overwritten completely each day; in normal operation copies remain for approximately 15 to 16 days.
• Email support: removed after final resolution when correspondence is no longer needed for the request or specific legal claims. Mandatory business or purchase records are retained separately for the applicable statutory period. Exchange Online may additionally retain deleted mail in recovery areas and technical provider backups.

9. Deletion, recovery and your rights

Settings > Account & data > Delete account permanently erases the active online profile and associated game, cloud, match, purchase, wallet and uploaded support data after confirmation. Only after a confirmed server response does the app remove local credentials and saves and exit. An interrupted response leaves the status uncertain. Uninstalling alone does not delete a server account. Without the app, enter Player ID and recovery code only on the deletion page https://www.dimbreaki.com/delete-account. A Player ID alone cannot authorize deletion. Keep the recovery code safe and do not email it. Contact us if access is unavailable; reasonable doubts may require proportionate identity verification.

Email correspondence, technical logs, deletion evidence and backups follow their own retention periods and are not all removed by the account deletion button. Before restoring service from backups, intervening account deletions must be reapplied. Statutory refund, withdrawal and warranty rights remain. Account deletion is not withdrawal from a purchase contract.

Subject to legal conditions you have rights to access, rectification, erasure, restriction and portability. You may object to legitimate-interest processing for reasons relating to your particular situation. You may withdraw consent for the future without affecting prior lawful processing. Contact the email address above. We normally respond within one month and explain a legally permitted extension. You may complain to a supervisory authority, particularly where you live or to LDI North Rhine-Westphalia: https://www.ldi.nrw.de/. There are no automated decisions producing legal or similarly significant effects under Article 22. Required data is needed for the relevant online feature; optional attachments and Creator codes are not needed for the rest of the game.