Privacy Policy

ARIA Records LLC ("ARIA Records", "we", "us") operates ariarecordsllc.com and DJ Studio 37 by ARIA Records in Ormond Beach, Florida, and hosts 3M Multimedia Group's crew network at /3M. This policy explains exactly what we collect, why, and who else touches it. We have tried to write it in plain language rather than legal padding.

What we collect

When you book a session or event

• Your name, email address, and phone number
• Your event or session details: date, start time, duration, service, venue, city, estimated guest count
• Any notes you choose to add
• The amount paid and a payment reference from Stripe

When you pay

Payments are processed by Stripe. Your card details are entered directly into Stripe's payment form and are never sent to, seen by, or stored on our servers. We receive only a payment confirmation, the amount, and a reference identifier.

Your ARIA account

One account covers the whole site: the Board, 3M, the store, the toolkit and the Credits Ledger.

• Your email address, used to sign you in and confirm you are a real person, and your password if you set one, stored hashed rather than in readable form
• The name you choose to display
• Anything you post on the Board: posts and replies are visible to everyone
• If you apply to be listed: your music link and what you tell us about yourself

When you send us your music

When you join through the Collective form, or put a song in the live review line: your name, your email, the link to your music, what you do, and anything you write to us. In the live line the public sees the song's title and the name you chose, never the link or your email.

On 3M

• A crew profile is public in the directory: your name, headline, roles, gear, certifications, city, how far you travel, years in the work, day rate if you give one, your bio and links, and whether you are available. A company profile is public too: the company's name, city, size, what it does and who it hires, how it pays and its website. A call for crew is public in the same way. The contact you give on a company or a call is shown only to people who are signed in.
• Reviews written after a booking. The writer chooses whether a review is public or private.
• Crew bookings: the event, the date, the venue, the crew on it and what was paid.
• Getting paid as crew: Stripe collects your ID, bank details and tax forms, and we never see them. We only ask Stripe whether you can be paid yet.
• A company's saved card is kept by Stripe, not by us. We keep only Stripe's reference for your account, and show you the card's brand, last four digits and expiry so you know which card it is.

Text alerts

If you ask us to text you, we keep your mobile number and, if you tell us, your carrier. Each text is sent as an email to your carrier's free text gateway, so your carrier receives the number and the message. If you do not name your carrier, the text goes to every carrier gateway still running, so each of those carriers receives it.

Purchases and monthly plans

What you buy from the store, a monthly plan, a skip in the live line or a 3M plan: what it was, the amount, when it was paid, and the Stripe references for the payment and any subscription. Stripe holds your card and sends your receipts.

Studio session files

For a paid studio booking we make a Google Drive folder for your session files and share it with the email address you booked with.

The Credits Ledger, the scorecard and the handbook

• Credits you enter, and credits other people enter about you: the work, the role and who confirmed it. A credit is public only once somebody other than its author confirms it. If you decline a credit about you, it comes off the public pages but stays on our record, so it cannot simply be added again.
• The scorecard keeps your answers in the result link it gives you, not on our servers. If you ask to be reminded to take it again, we keep your email, the name you give, your score and that link, to send the reminder.
• If you ask us to email you the handbook or to tell you when a release is out, we keep your email address, and the name you give, to send it.

Automatically

Our host, Cloudflare, records standard server request information including IP address, for security and abuse prevention, for example rate-limiting sign-in attempts and telling people from bots. Google measurement, described below, runs unless you decline it, and visitors in the European Economic Area, the United Kingdom and Switzerland are asked first. We do not sell your booking details to data brokers.

Site measurement

Our own site measurement runs on our servers and sends what it records to nobody else. Google Analytics measurement is separate and is described under Cookies below.

What it records: the pages you open, the links you press, the website that referred you (the site's address only, never the full link or any search terms in it), the country your connection reports, and whether you are on a phone or a computer. It also stores a random identifier in your own browser so that a returning visitor is not counted twice. That identifier is generated on your device, is meaningless anywhere else, and is never linked to your name or email address.

What it does not record: your IP address, your name or email, anything you type into a form, the contents of any page you are signed in to, your mouse movements or scrolling, and anything at all about your activity on other websites.

Turning it off: if your browser sends the Global Privacy Control signal, our measurement does not run on your visit at all. Several browsers and extensions send it by default and most others offer it as a setting. Clearing your site data also removes the identifier described above.

Cloudflare's count: Cloudflare, our host, also adds its own Web Analytics to every page. It counts page views, where visitors came from and how fast pages load, and it sets no cookie. It does not check for the Global Privacy Control signal, so it counts every visit.

Cookies

We set a small number of strictly necessary cookies to keep you signed in. Our own site measurement does not use cookies. These providers may set their own:

• Cloudflare may set a security cookie (cf_clearance) when it checks that a visitor is a person and not a bot.
• Stripe sets fraud-prevention cookies (__stripe_mid and __stripe_sid) once its payment form loads: on the booking page as you near the pay step, and on 3M once you open a payment or a card form.
• Google Analytics, unless you decline it, uses cookies such as _ga to measure visits and paid bookings and help connect them to our Google Ads.

Google measurement

Google measurement shows us which of our ads lead to real bookings, so we stop paying for the ones that do not. It covers our public marketing and booking pages, ad-click identifiers and campaign information, and a purchase event after our server verifies a successful live booking payment. The event contains a booking reference, the amount paid, currency and a general service label. We do not include your name, email, phone number, payment details, or Stripe payment secrets in these events. Google also receives connection information when its tag loads. Our linked Google Ads account uses this measurement to report and optimize advertising. Advertising personalization and Google signals are disabled.

It is on unless you decline. A box at the bottom of the page lets you accept or decline, and we remember your choice in this browser. Visitors in the European Economic Area, the United Kingdom and Switzerland, and visitors whose country we cannot tell, are asked first, and nothing is measured until they accept. If your browser sends Global Privacy Control, we do not load Google measurement at all. Declining does not affect booking. You can change your choice here: declining stops further Google measurement and removes Google Analytics cookies where this site can access them. It does not erase data already sent.

Change Google measurement choice

Learn how Google uses information at Google's partner sites policy.

How we use it

• To take, confirm, and deliver your booking
• To send you a confirmation and any details you need before your session or event
• To add your booking to our studio calendar so your time is held
• To send you an invoice for a remaining balance, where one applies
• To run your account and what it opens: the Board, 3M, the store, the toolkit and the Credits Ledger
• To operate the Board, take down posts that break the rules, and review applications
• To put a 3M crew together, take the company's payment and pay the crew
• To send the alerts you asked for, by email or by text
• To keep records required for accounting and tax

We do not send marketing email unless you have asked us to.

Who else is involved

We use a small number of established providers, and only for the purposes below:

• Stripe: payments, saved cards, monthly plans and paying 3M crew. Receives your name, email, and payment details, and, if you are paid as 3M crew, the ID, bank details and tax forms it asks you for.
• Google: Google Calendar holds your booked time so it is not double-sold, Gmail sends our email and the text alerts, and Google Drive holds the folder for your studio session files. These services receive your booking details, your email address and, for a text, your number. Unless you decline Google measurement, Analytics and our linked Ads account also receive the measurement information described above.
• Cloudflare: hosting, database and file storage, security checks, and its Web Analytics. Stores your booking record, your account and anything you upload.
• Mobile carriers: only if you ask for texts. Your carrier's text gateway receives your number and the message, as described above.

Some pages show something from another company: a music or video player from Spotify, Apple Music, SoundCloud, Vimeo or YouTube on pages that play music, such as a musician's page or a press kit, and a Google map on the contact page. When one loads, that company sees your visit, under its own privacy policy. YouTube players use its privacy-enhanced mode.

We do not sell, rent, or trade your personal information, and we do not share it with anyone beyond the providers above.

How long we keep it

Booking records are kept for as long as needed to run the business and meet accounting and tax obligations. An unpaid booking stops holding its time after 30 minutes, and we delete it if you ask. Your account and what you post are kept until you ask us to remove them.

Your choices

You can ask us to show you what we hold about you, correct anything wrong, or delete your information. Email ariarecordsofficial@gmail.com and we will respond within 30 days. Note that we may need to keep records of completed transactions where the law requires it.

Security

The site is served over HTTPS. Access to internal tools requires a passcode, and those passcodes are stored hashed rather than in readable form. No system is perfectly secure, but we do not hold card numbers, which removes the most sensitive category of data entirely.

Children

This site is not directed at children under 13, and we do not knowingly collect their information. If you believe a child has given us information, contact us and we will delete it.

Changes

If we change this policy we will update the date at the top. Material changes affecting how we use your information will be communicated directly where we can.

Contact

ARIA Records LLC
533 N. Nova Rd #113, Ormond Beach, FL 32174
ariarecordsofficial@gmail.com
(386) 331-8421