Privacy Policy
1. Controller and scope
Giovanni Emanuele Spina (also shown as Spina Giovanni Emanuele), developer of DJ Club 3D, is the data controller for the processing described here. Contact creo.app.app@gmail.com for privacy questions and requests. This notice covers the Android and iOS game, its online challenge service, remote configuration and this privacy page. Advertising and purchase provisions apply to versions and platforms that include those features.
DJ Club 3D does not offer registration for a game account. Technical identifiers used for online rooms and purchase verification are still personal data where they can relate to a user or installation.
2. Music, local files and settings
The game stores audio and visual settings, language, performance preferences, career progress, room settings, Deck queues, Cue points, nickname, selected built-in avatar and other preferences on your device. Device capabilities, including memory, performance and screen resolution, help adapt graphics.
You choose music with the operating system file picker. Selected files are read or copied into the app’s local storage; duration, waveform and rhythm analysis run locally. Imported music, audio analysis and mixer saves are not uploaded to our game servers, RevenueCat or opponents. The game does not use your music for advertising or profiling.
These features do not require access to contacts, precise location, camera or microphone. Any file-access permission or file selection is managed by the operating system. System or user-selected backup services may back up local app data under their own settings.
3. Online rooms, chat and challenges
When you use online functions, the game sends an app-generated random identifier, technical session credentials, nickname, selected built-in avatar, room name and invitation code, lobby messages, presence and connection-quality information to the game service. It also sends selected room and challenge, relevant career unlock progress, scores, judgements, crowd mood, timing and match results. The server receives your IP address to communicate with your device and protect the service from abuse.
Participants in the same room can see your nickname, avatar, messages, presence, connection quality and challenge information. These data provide saved rooms, synchronisation, results and service security. The game’s random online identifier is not your IMEI, phone number or advertising ID. Do not enter confidential information in nicknames, room names or messages.
Online play is optional. Practice and career gameplay can operate offline; online rooms and matches need a connection. Leaving a room or closing the app is different from deleting its stored information.
4. Remote configuration and technical connections
When a network connection is available, the app requests a configuration file from the developer’s HTTPS service at startup and periodically while running. It uses this file to retrieve game settings and availability rules, including advertising settings, and stores a local copy for fallback. A configuration request can occur without entering an online match.
The hosting infrastructure necessarily receives the connecting IP address and request metadata such as requested address, time and client information. Technical access or security logs may be processed to deliver configuration, maintain availability and prevent abuse. These configuration requests do not upload your music, audio analysis or chat contents.
5. Advertising and consent
Ad-supported versions use Google AdMob / Google Mobile Ads, with Google’s User Messaging Platform for applicable consent choices. Google may collect and share IP address, approximate location inferred from the IP address, app and device identifiers (including Android advertising ID, app set ID or iOS IDFA where applicable and permitted), app/ad interactions such as launches, taps and video views, and diagnostic/performance information. Purposes include advertising delivery and measurement, analytics, service security and fraud prevention. Approximate location inferred from an IP address does not mean the game accesses precise GPS location.
Ad personalisation and access to advertising or tracking identifiers depend on your choices, operating-system settings, service configuration and applicable rules. Where required, optional processing is subject to consent. On iOS, tracking across other companies’ apps and websites also requires App Tracking Transparency permission. Refusing tracking permission does not prevent gameplay. Non-personalised or limited ads can still involve technical data processing; they do not mean that no data are collected.
Use the consent controls displayed by the app and, when available, Settings → Ad privacy (“Privacy annunci”) to review or withdraw advertising choices. You can also use your device’s advertising-ID or tracking settings. Verified Pro access removes in-app advertising as described on the purchase screen; it does not erase data already processed by Google.
Provider information: Google Privacy Policy — https://policies.google.com/privacy ; Google advertising information — https://policies.google.com/technologies/ads ; Mobile Ads data disclosure — https://developers.google.com/admob/unity/privacy/play-data-disclosure .
6. Pro purchases and RevenueCat
Where Pro is offered, the purchase screen describes the features, price and purchase type before you confirm. Payments are processed by Google Play Billing on Android and Apple App Store / StoreKit on iOS. The developer and game do not receive your full card number, bank credentials or store password.
The app uses RevenueCat as a service provider to verify purchases, maintain and restore Pro access and analyse purchase performance. This processing includes a pseudonymous app-user identifier, purchase history, product and transaction identifiers, receipts or purchase tokens, purchase dates, transaction status and entitlement information. Requests also expose connection metadata such as IP address and technical app/device information needed for the service. Purchase verification may connect when the app starts or checks existing access, as well as when you buy or restore.
The current RevenueCat integration does not send your nickname, email, room chat or imported music as customer attributes. Automatic collection of advertising/device identifiers through RevenueCat is disabled in the integration. This does not disable the separate AdMob processing described above. Purchase verification uses its own pseudonymous identifier even though there is no game-account registration.
Buying Pro, deleting game data or removing advertising does not automatically delete previous transaction records or request a refund. For data handled by the developer through RevenueCat, contact us using section 9. Google Play and Apple manage their own payment records and any refunds under their rules.
Provider information: RevenueCat privacy and processor information — https://www.revenuecat.com/privacy ; RevenueCat Google Play data disclosure — https://www.revenuecat.com/docs/platform-resources/google-platform-resources/google-plays-data-safety ; Apple privacy — https://www.apple.com/legal/privacy/ .
7. Support, hosting and recipients
If you email us, we process your email address, message and attachments you choose to provide in order to answer. Do not send passwords, full payment details or unnecessary personal files.
This static privacy page is hosted through IONOS. The page itself contains no advertising scripts, analytics scripts, external fonts, registration forms or tracking cookies. Hosting access/security logs can include IP address, requested URL, timestamp and browser information to deliver and protect the website. Following an external provider link takes you to a service with its own privacy practices. IONOS information: https://www.ionos.it/terms-gtc/terms-privacy/ .
Recipients include other participants in your room, hosting/infrastructure and email providers needed to run the service, Google for advertising and consent services, RevenueCat for purchase verification, the purchase stores, and authorities where disclosure is legally required. Technical providers process data needed for their services under the applicable contracts and notices. The developer does not directly sell your personal data or use imported music for marketing. Google advertising processing, including data sharing, is described separately above.
8. Purposes and legal bases
Where GDPR applies, processing necessary to provide requested gameplay, online matches, purchase verification and restoration relies on performance of the requested service or contract. Optional advertising processing and tracking rely on consent where required. Maintaining secure infrastructure, configuration delivery, abuse prevention, support and proportionate service/purchase analysis rely on legitimate interests, balanced against your rights. Processing required by law relies on legal obligations.
Online play and purchases are optional. Declining the information necessary to connect or verify a purchase can prevent the corresponding online or Pro feature from working. Withdrawing optional advertising consent does not withdraw consent retroactively. Game judgements and crowd mood are gameplay mechanics, not automated decisions about people with legal or similarly significant effects.
9. Retention and how to request deletion
Local data remain until you remove them, clear the app’s storage or uninstall. Uninstalling normally removes app-private local data; operating-system backups must be managed separately. Local-only music is not stored on our server for us to delete.
Online room information and the latest match state are retained to let participants return to saved rooms, until the owner deletes the room or the relevant data are erased following a valid request. Room chat keeps at most the latest 30 messages, replacing older ones. You can delete rooms you own or remove your participation in another room with game controls. Removing participation does not necessarily erase earlier messages; Home or closing the app does not delete a room.
Purchase and entitlement records handled through RevenueCat are retained while needed to verify/restore access, respond to support requests, protect against fraud or meet legal obligations. We can instruct RevenueCat to delete associated customer data after a valid request, subject to applicable retention exceptions. The stores and other providers can retain their own transaction/security records under their rules and legal duties. A later restore or purchase verification may create a new service record.
Support correspondence and technical/security logs are retained only as needed to handle the request, investigate incidents, operate a secure service or meet legal obligations. Retention depends on those purposes and the provider’s relevant retention cycles. Where an exception requires us to retain identifiable data after a deletion request, we will explain the applicable reason and retention period or criterion in our response.
To request deletion of online data, chat messages or data handled through RevenueCat, email creo.app.app@gmail.com with the subject “DJ Club 3D — data deletion”. State which data you want deleted and whether you use Android or iOS. For an online request, include the relevant room code and nickname if available; for a purchase-related request, include only a transaction reference or pseudonymous identifier if known. We may ask for minimal additional information to locate the correct record and verify your request. Never send a password or full payment-card details. You do not need to register or sign in on this website.
We assess requests without undue delay. Where GDPR applies, we normally respond within one month; permitted extensions will be explained. Data deletion is separate from a refund, and requesting deletion does not cancel store-managed billing or erase records the stores are legally required to keep.
10. Security and international transfers
Game-service, configuration and purchase-verification communications use HTTPS/TLS; Google Mobile Ads documents encryption in transit for its SDK data. Online rooms use invitation codes and technical credentials. We restrict access to information needed to operate the service, but no security measure can give an absolute guarantee.
Providers may process data outside your country or the European Economic Area, including in the United States. Transfers subject to GDPR must use an applicable adequacy decision, standard contractual clauses or another legally recognised safeguard. Contact us for information about safeguards relevant to your data; provider notices also describe their processing.
11. Your rights and choices
Depending on the law that applies to you, you may request access, correction, erasure, restriction or portability; object to processing based on legitimate interests; or withdraw consent without affecting the lawfulness of earlier processing. Contact creo.app.app@gmail.com. We may need minimal information to verify identity. You may complain to the Italian Data Protection Authority (https://www.garanteprivacy.it/) or your local supervisory authority.
You control selected local files, online participation, room deletion where available, and the advertising controls described above. Store payment and device-backup controls are managed through the relevant provider.
12. Minors and policy updates
The game does not ask for your legal name or date of birth and does not offer game-account registration. Minors should use online functions and purchases with parental or guardian assistance where required and follow local law and store age rules. Do not share private information in chat. Contact us if you believe a minor’s data were processed without required authorisation so we can investigate and erase them where required.
We update this policy when the app’s features, providers or processing change. The date at the top identifies this version. New processing will be accompanied by updated information and consent where required. This page does not change consent choices you already made in the app.