Privacy policy
Version: 1.0 · Effective date:
1. Responsibility and contact
Valeriy Nekhaev / Валерий Нехаев, an individual, is responsible for the project's data processing. Good Vibes Point is the project name. Website: goodvibespoint.com. Contact for data questions and requests: vnehaev+gvp@gmail.com. This policy describes processing by the project; external services have their own rules.
2. Data and purposes
Registration requests first name, last name, date of birth, email, contact details, an optional DJ nickname and a password. The profile is linked to an account identifier and creation time. These details support accounts, communication and participation management. Firebase Authentication handles passwords; passwords are not stored in profile documents. Date of birth is currently required by the form and is collected to check age. A user-supplied date does not by itself verify identity or establish that the stated age is accurate. The 18+ audience described below applies only to courses; this policy does not set a general age limit for the website, residents or events.
Sign-in is available with email and password or Google. Google sign-in uses the identifier and account information supplied by the sign-in service. Guest bookings create an anonymous technical Firebase account linked to the booking.
Open Decks/Sessions records include DJ name, contact, genre, optional social link, chosen event and slot, user identifier and booking time. Open Decks booking confirmations store the email address and site language; messages are sent through the configured email service. DJ names appear in the lineup. Open Decks reserves a place without a performance time; Sessions also shows the performance time; contact details and the full booking are available to the organiser and relevant user under access rules.
Masterclass registration requests name, contact and an optional comment and records participant identifier, event, booking time and status. These support reservations and communication and are not published as an attendee list.
When you write by email or through an external social network, your message and supplied contact details are used to reply. Do not send passwords, verification codes or full card details.
3. Public profiles and photos
An enabled and published resident profile displays DJ nickname, biography and translations, music styles, photo, social links and like count. Email, birth date and contact from the private profile are not included in the public card. Likes are linked to accounts; the public view displays the total rather than a list of users.
Photos are uploaded to Firebase Storage or may be loaded by the browser from a permitted external HTTPS address. Visitors and search engines may copy published images and pages. Firebase image links include an access token: hiding a card does not guarantee revocation of a previously copied link. Photos of people are published with the depicted person’s permission. Do not upload a person’s photo for publication without their permission. Contact us by email to request removal. This publication rule does not mean the site technically verifies permission for every photo.
4. DJ School and messages
DJ School courses are intended only for adults aged 18 or over. This describes the course audience and does not assert that technical age verification is implemented: its presence and operation have not been confirmed.
When DJ School is used, account data is linked to roles, applications and waiting lists, enrolment, groups, schedules, teachers, attendance, trial lessons, charges, recorded payments and debt. Staff actions are recorded in an audit log. Access depends on role: students see their records, teachers see records within implemented permissions, and administrators see data needed to manage the school. This describes record keeping and does not announce active enrolment.
Schedule-change notifications and an email queue are implemented. When external email delivery is enabled, messages are sent through the configured SMTP service. If a personal calendar subscription is enabled, your calendar app receives a schedule through a secret link. Anyone holding that link can request the feed until it is revoked or replaced. The browser session stores the link token; the server stores its hash.
5. Technical data and browser storage
Firebase provides authentication, database, files and server functions; the site is deployed through Firebase Hosting. Infrastructure requests involve technical connection information, including IP address and browser information, under the provider's rules.
Resident profile saves generate limited diagnostics: request identifier, stage, result, controlled error code, duration, app version, indicators of a selected photo and multiline biography, time and a hash of the account identifier. Biography text and photo contents are not included in these diagnostic fields. Administration logs may include acting and affected account identifiers.
localStorage stores website language (gvp-language) and DJ School language (gvp-school-language); sessionStorage stores the generated calendar link information (school-calendar-…); Firebase stores sign-in state in the browser. The reviewed code contains no separate advertising tracker, Google Analytics or custom cookie-setting mechanism. External services may still use cookies or other storage. You can sign out and clear site data in your browser; this does not delete server records and may reset language and account access.
6. Services, links and support
Data is transferred to Google/Firebase to operate the site. Data may be processed by provider infrastructure in different countries; a server function's region does not determine the location of all data. This policy does not promise storage exclusively in one country.
The site links to social networks and maps. Following a link subjects your interaction to that service's rules. No embedded third-party videos or maps were found in the reviewed code; an external image loads from its server, which receives request information. The school email preview iframe uses the message's local content rather than a separate video service.
Code supports an external voluntary-support link to lava.top when configured. Checkout takes place on the platform and with the relevant payment provider under their rules; GVP implements no card-entry form. The lava.top notification handler is designed to retain event type, operation/product identifiers, amount, currency, time and processing status, without storing the full incoming payload or buyer identity in that record. This code does not establish that payments are active. Support does not purchase courses, tickets or services.
7. Retention, corrections and requests
We retain data while it is necessary for the stated purposes or mandatory retention under law. When we receive a deletion request, we review which data can be deleted and which must be retained. The site has no general time-based automatic deletion mechanism. Closing a tab, cancelling a booking, disabling a profile or deleting an account does not automatically delete all related data.
An administrator can delete the Firebase account, private profile, resident profile, its photos and some associated records. That operation does not cover all school, event, audit and payment records. To ask about your data, request corrections, unpublication or deletion, email vnehaev+gvp@gmail.com. Identify the relevant account or record without passwords or excessive documents. Any necessary identity check should be proportionate to the request. The response period for personal data requests is determined by applicable law. Whether and how a request can be fulfilled depends on actual data and applicable law; unconditional deletion of all related records is not promised.
8. Security and changes
The code implements role-based access, Firebase database and file rules, HTTPS and limited diagnostics. No system guarantees absolute security. Do not share private calendar links, passwords or codes. Material changes to the text and processing should be accompanied by an updated policy and date. Visiting the website or accepting the support terms does not replace separate consent where required. Applicable law and mandatory rights depend on the circumstances; this policy does not designate a specific jurisdiction.
