LulaBeat Privacy Policy

About this policy

LulaBeat is a body-percussion composing and practice app, published by DI.BI.EM IT. This policy covers version 1.0.0. Last updated: October 6, 2026.

For privacy questions or requests concerning information you send to us, contact contact@dibiem.site.

Information stored and used on your device

LulaBeat stores rhythm patterns, phrase names, tempo, meter, subdivisions, drafts and recent edit history, saved phrases and practice sets, queue snapshots, lesson progress, practice dates and duration, completed or interrupted status, notes, playback checkpoints, weekly goals, navigation and feedback preferences. Text you enter can contain personal information. Unfinished entries may be saved before you explicitly save an item.

This information is used to provide the app’s features, organize your work, remember preferences and restore your session. These features work offline and do not require an account or upload your local records to the publisher.

Android data is kept in the app’s private storage. Previous-save and recovery copies may retain earlier information. The browser preview uses separate browser local storage and does not synchronize with the Android app.

Device access and optional feedback

The app does not request camera, microphone, contacts, location or shared photo/storage access. Optional sound and haptic cues are off by default and use device output capabilities. Your settings and device controls determine whether cues play.

Practice time and dates are used to show your local journal and totals. The app does not listen to your performance or use sensors to assess it.

Connections, services and sharing

The app’s local features have no advertising, analytics, purchases, remote crash-reporting service or developer-operated cloud synchronization. They do not automatically transmit your creations, notes or activity to the publisher. Android, AndroidX, Kotlin and Compose components provide the interface and local device functions.

The Android application declares Internet permission and includes a separate web-page component. Version 1.0.0 opens the native app directly. If that component displays an external page, the website can receive connection information such as your IP address and browser request details. JavaScript is enabled in that component. The app does not attach your local records to the request; the website handles its own cookies, logs and other processing.

Support email

Choosing the support email action opens your email app addressed to contact@dibiem.site. It does not automatically send a message or attach local records. If you send it, DI.BI.EM IT receives your sender address and the message and attachments you choose to provide to handle your inquiry. Your email service also processes that communication.

Copy email writes the public support address to your clipboard. The app does not read existing clipboard contents. Other software can access clipboard contents subject to the operating system’s restrictions.

For information about retention of support correspondence or to request deletion of information you sent, contact contact@dibiem.site. A request regarding support correspondence does not erase copies retained by your own email provider.

Backups

Android backup is enabled. Depending on your device, system settings and backup service, app data may be copied to a system backup or device transfer and later restored. These copies are separate from an app-operated cloud account. Manage their retention and deletion through your device and backup provider.

Retention and deletion

Local records have no automatic expiration period. They remain until changed, deleted or cleared. Editing and deleting an active item may leave earlier information in drafts, Undo history, previous-save or recovery copies.

You can delete saved phrases, practice sets and journal entries. A composer draft, independent queue copy or current queue editor may remain after its saved item is deleted. Deleting a journal entry also removes its contribution to displayed progress.

To remove all local Android app data, use Clear storage in Android app settings. Uninstalling ordinarily removes local app storage. For the browser preview, clear its site data. These actions remove locally stored work and preferences. Manage system backups, email and shared copies separately.

DI.BI.EM IT cannot remotely erase data stored only on your device. For privacy assistance, contact contact@dibiem.site.

Security

The app relies on Android’s private-storage controls and does not add its own encryption to local saves. Save validation and recovery copies help detect or recover damaged data; they are not encryption. Technical failures may be written to local device logs, without an app-operated remote reporting service.

The configured web-page connection uses HTTPS. Security of email, shared copies and system backups depends on the services and device settings involved. No storage or transmission method guarantees complete security.

Children’s privacy

The app does not request age or date of birth. The local data practices above apply to all users. Parents or guardians can manage locally entered information through the app and device controls. If a child sent personal information directly by support email, contact contact@dibiem.site for assistance or a deletion request.

Changes and contact

This policy may be revised when LulaBeat or its data handling changes. The revision date appears above.

App: LulaBeat. Publisher: DI.BI.EM IT. Privacy and support: contact@dibiem.site.