Privacy policy

What DJFanz stores

When you register, DJFanz stores your email address, your account role, and session and recovery information. Password accounts also store a salted password hash. If you choose Apple or Google sign-in, we receive a provider account identifier, verified email address (including an Apple private relay address when selected), and any name you share. These identifiers link your sign-in method to DJFanz; existing accounts are linked only after you sign in to that account. Apple authorization credentials are encrypted and retained to support authorization revocation when your account is deleted. Your profile may include a name, handle, biography, location, musical interests, images, and links that you choose to provide.

Using DJFanz can create uploaded audio, images, and video proof, posts and comments, follows and saved items, messages, song requests, schedules, event reservations, notifications, and payment and transfer records. Server security and access logs may contain your IP address, request time, and basic device or browser information.

How it is used

Your information supports sign-in, account recovery, your profile and music library, communication between Artists and DJs, requests and events, and a consistent experience across your signed-in devices. Session, security, and transaction records help protect accounts, diagnose failures, and prevent duplicate operations.

Payments use DJFanz-designed screens with secure Stripe card fields. Card numbers and security codes go directly to Stripe, not to the DJFanz server. DJFanz processes the billing name, email, and address you submit for payment setup; the billing address is sent to Stripe to calculate applicable tax. The app retains matching fingerprints and calculation references rather than a saved copy of the billing address. Your bank or card issuer may require additional authentication to authorize a payment.

DJ payout setup also uses DJFanz-designed forms. Sensitive identity information, including date of birth and any required government identification, and bank details are sent directly to Stripe for tokenization. Verification documents are uploaded directly to Stripe. DJFanz receives token and document references and stores encrypted pending-operation inputs, public business details, verification requirements and status, and masked bank summaries to complete or reconcile your setup. Full card numbers, bank account numbers, and identity-document files are not stored by the DJFanz server.

DJFanz retains payment and payout-account references, itemized amounts, tax records, status, and links to the related request or campaign for reconciliation, refunds, disputes, and accounting. Earlier payment records continue to be reconciled under their original terms. Stripe separately processes payment, identity, bank, and document information under its own privacy notice.

What other people can see

A published, visible profile and content you publish to the community can be seen by other members. Messages and song requests are shared with their intended recipients; an attached private track is shared as part of that interaction. Event hosts can see reservations for their events. Hiding a profile removes it from the public directory; it does not recall messages, requests, or content already shared with others.

The service runs on hosted infrastructure that processes data to provide DJFanz. People operating the service may access information when needed for support, security, and maintenance. Apple separately processes App Store distribution and installation information, and TestFlight testing and feedback information, under Apple's terms and privacy notice.

Community reports, blocks, and moderation

Public profiles, posts, comments, and events enter manual review before other members can see them. DJFanz keeps reviewed content snapshots, status, reasons, and audit references so moderators can review the exact submitted material. Private reports include the content reference, your selected reason, and any explanation you supply. They are accessible to you and authorized moderators; your identity is not disclosed to the reported account.

Blocking records the accounts you choose to block. Blocks limit new interactions and signed-in visibility while preserving existing financial request and proof resolution. Moderation records may be retained for abuse prevention and accountability after content or accounts are removed. Contact support about retained records. Read the community rules or get support.

DJ applications and performance consent

DJ professional applications contain the legal and professional names, location, experience, evidence links, venue types, and policy acknowledgements the applicant supplies. Applications, submitted revisions, reviewer checks, decisions, and explanations are private to the applicant and authorized administrators. Artist performance-rights consent is recorded with the policy version and payment quote.

Account deletion removes private application details and submitted application snapshots from the active service. Minimal administrative audit references and financial consent records may remain for accountability and unresolved payment obligations. Professional review is a human process; submitting a link alone does not verify identity.

Private spin proof and review

A DJ can record or choose a 3–30 second video with audio for a specific accepted request. Camera and microphone access starts only after the DJ chooses to record and grants device permission. The DJ can preview and retake the clip before submitting it.

Submitted proof is shared privately with the request’s artist, its DJ, and authorized administrators reviewing the case. It does not become a public community post or ordinary library upload. Proof, captions, review decisions, and reasons remain attached to the participants’ request history. An artist receives a request-linked message and notification when proof is ready.

For Stripe-paid requests, payment is captured at checkout. Artist proof approval or an administrator’s release schedules the DJ’s net transfer to their Stripe balance. A transfer is distinct from a bank payout. Unfulfilled requests that are declined, cancelled, expired, or refunded by an administrator receive a full refund including the service fee and tax; completion is tracked separately. Historical requests retain their original payment terms and recorded status. Disputes and overdue artist reviews go to an administrator; they do not cause automatic payment. Historical requests paid under the earlier acceptance policy are not charged again. Video proof and human review are not independent detection or verification of airplay.

Sponsored DJ placements

DJFanz Spotlight is optional paid advertising for eligible DJs. Sponsored profiles are labeled and matched to the page, search, city, or genre you are exploring. These placements use reviewed public DJ profiles; private tracks and messages are not advertising content.

DJFanz records qualified placement views and profile clicks to report campaign activity and prevent repeated counting. Short-lived, rotating account-derived digests support deduplication; campaign reports show aggregate counts, not viewer identities. Spotlight billing references and transaction records support payment reconciliation, refunds, disputes, and accounting.

Address assistance and payout details

When address assistance is available and you use it, your address search or the address you choose to check is sent through DJFanz to Google Maps Platform for suggestions and validation. DJFanz does not store the lookup history or provider suggestions. You review suggested corrections before applying them. Manual entry remains available; a format check is not postal verification. Google processes these requests under the Google Privacy Policy and Google Maps terms.

When you open payout editing, DJFanz retrieves available account details from Stripe for your signed-in account so you can review and correct them. This private read response is not stored as a profile copy or browser history. Identity numbers and complete bank account numbers are not shown. Updated identity and bank details continue to be tokenized directly with Stripe.

Help Center and support conversations

If you open a support ticket, DJFanz stores its topic, subject, description, the supported page you came from, replies, timestamps, and case status. This lets you and authorized support staff follow the same conversation. Staff assignment and internal notes are not visible to members. Support notifications contain a generic alert rather than the content of your ticket. Do not include passwords, sign-in codes, full card numbers, or bank account numbers in a ticket. Active support records are removed with account erasure; operational backups may remain as described below.

Optional newsletter

If you sign up for DJFanz news, we store your email address, consent and subscription status, and signup, confirmation, and unsubscribe timestamps. We send a confirmation link before activating your subscription. Newsletter email uses our email delivery provider, Amazon SES. You can unsubscribe using the link in a newsletter email; essential account and service messages are separate. Account erasure removes newsletter records matching that account’s email address. Contact info@djfanz.com for help with an address that is not attached to an account.

Optional device notifications

Notifications use Apple Push Notification service (APNs) on supported iOS devices or your browser’s Web Push service. They require your opt-in and device or browser permission. DJFanz stores encrypted device tokens or browser subscription endpoints and encryption keys, with each registration tied to your account and current signed-in session. You can choose booking requests, proof reviews, messages, and payment alerts in notification settings, or turn notifications off on the device.

Alerts use a generic preview without message text, track names, or payment amounts. The delivery provider processes the destination and notification payload, including a notification reference and category, to deliver the alert. DJFanz records delivery attempts and provider status to handle retries; a queued alert or provider acceptance does not confirm that you received it. Open DJFanz to read the account details.

Signing out revokes that session’s notification registrations and pending deliveries. Account deletion removes registrations and preferences, and delivery stops while deletion is pending. These actions do not recall alerts already sent to a provider or device. You can also manage permissions in your browser or device settings.

Sessions and device storage

The website uses a session cookie and security tokens to keep you signed in and protect requests. The native app stores its sign-in token using secure device storage. Your browser or device may cache app files. DJ track playback uses protected in-app streaming with no persistent app audio cache. Temporary technical buffering is used only for authorized playback; downloading, retaining copies, and redistributing tracks are prohibited by the performance policy. These controls do not promise absolute prevention of recording. Signing out removes the active session from the app; removing locally cached files is managed through your browser or device settings.

Deleting your account

On the website, open Account & settings and choose Delete account. In the app, open your account and find Delete account in the Security section. You must confirm the deletion and verify your identity using your current password or a connected Apple or Google account. When deletion completes, it permanently removes your login, profile, authored community content, messages, uploaded media, and personal account state from the active service, and revokes your sessions.

Your deletion request is accepted even if proof review, an unsettled payment, or a financial dispute delays completion. Your public activity is hidden while deletion is pending. The status page lists remaining obligations and the next scheduled check; it does not promise a fixed completion time. You can resolve existing requests and payments, check status, sign out, or contact support. Deletion completes automatically when those obligations permit it. The deletion request cannot be cancelled. Eligible unfulfilled requests are cancelled and any required refunds are processed under their original payment terms. Other members' financial records may retain an anonymous transaction entry so their balances and history remain consistent. Any remaining technical references no longer provide a login or public profile. Deleting DJFanz does not delete records held independently by Apple or a checkout provider, or copies another person has already saved.

Account data is kept while your account is active. File removal is processed after the account deletion commits. A private receipt token can remain in the requesting browser tab to confirm pending or completed status after sign-out. It is sent in a request header, never a page URL, and reveals no profile, contact or blocker details. Completed receipts expire after 90 days. Security logs and infrastructure backups can outlast active account records; they are separate from the app's live account. Contact us about information in retained operational records.

Questions about your information

Contact Dosh Corp at info@djfanz.com for privacy questions, access or correction requests, or help if you cannot sign in to delete your account. Include your account email and the request, but never send your password or recovery codes.

This notice may be updated as DJFanz changes. The date above identifies the current version.