Privacy Policy — Loud & Cle.ar

Who controls your data

Loud & Cle.ar is an early-stage automatic mastering product operated by Eli Briskin in Israel. Eli Briskin is the controller of the personal information described in this policy. You can contact the project at eli@loudandcle.ar or exercise a privacy right through the request form below.

Information we collect

Waitlist information: your email address and, when offered, your optional role or professional profile. If you join after a blind test, we also link your request to that completed test using its session identifier.
Reward reservations: after an accepted blind-test ballot, your email address, test-session identifier, offer and message variant, and campaign attribution needed to validate and fulfil a reserved free master when the beta opens.
Blind-test responses: master ratings, release preference, perceived origin, listener role, optional playback setup and basic interaction measures such as listening time and version switches. For all website forms and personal listening-test answers, we also record the approximate country, region and city supplied by our hosting provider, when available, to understand where submissions come from. Submission records do not store your IP address or precise location.
Campaign attribution: campaign parameters, advertising click identifiers, landing path and referrer information present when you submit a website form.
Measurement information: pages viewed, interaction events, session playback data, approximate location derived from IP address, browser and device information, campaign attribution and pseudonymous measurement identifiers. Measurement operates under the default and choices described below. We do not send your email address, ballot answers or audio content to Google, Microsoft Clarity or Reddit Pixel.
First-party interaction journal: button and link identifiers, form starts and outcomes, whether a field was filled (without email or message text), playback actions and durations, questionnaire steps and selected answers, including unfinished questionnaires. Public-page collection follows your analytics choice. Personal invitation tests associate these events with the original invitation as described on their privacy page. Events are stored privately with pseudonymous session identifiers and are not sent to advertising services.
Messages and privacy requests: your email address, request category and the details you choose to provide.
Technical information: hosting and security providers may process IP address, device, browser and request-log information needed to deliver and protect the site.

The public blind-test ballot does not require an email address and does not collect audio files, payment information or sensitive personal information. Reserving the promotional reward is optional and asks for an email only after the ballot has been accepted. Track upload becomes available after the beta opens and is governed by separate secure instructions.

Why we use it

To register and manage your requested access to listening tests or the closed beta.
To measure blind listening preferences and improve the mastering system. The ballot is accepted before any email is requested; research reporting remains aggregate or de-identified.
To validate, prevent duplicate use of and fulfil the free-master reward you reserve for the beta.
To understand which campaigns lead to genuine waitlist requests and measure campaign effectiveness.
To send service messages about the test or beta you asked to join.
To respond to questions and privacy requests.
To prevent abuse, diagnose failures and protect the website.
To comply with legal obligations and establish or defend legal claims.

Where applicable, we rely on your consent for beta and test communications, on steps you ask us to take before providing access, and on legitimate interests in operating and securing the service. You may withdraw consent at any time.

If you reserve a reward or join the waitlist after a blind test, the session identifier links your request to the accepted ballot so we can manage the requested access, understand your test feedback and, for rewards, verify eligibility. Providing an email is optional. Public research reports remain aggregate or de-identified. We do not send that link, your ballot answers or your email address to Google.

Service providers and transfers

We use Vercel to host the website, run serverless functions and privately store waitlist and contact submissions. We use Google Tag Manager, Google Analytics 4 and Google Ads to administer measurement tags, understand website use and attribute advertising outcomes. We use Microsoft Clarity for heatmaps, interaction analytics and session playback. On Reddit campaign visits, Reddit Pixel can measure ad-driven page visits, test starts, accepted ballots and optional reward or beta sign-ups after you allow advertising measurement. We use Telegram to notify our team in a restricted group when forms are submitted. These notifications may include your submitted email address, request details, blind-test responses and available campaign attribution, so we can review and respond to your submission. We use Notion as our restricted-access CRM to review beta and mastering requests, general inquiries and listening-test responses. These cards contain the corresponding submission details and approximate geography; links to the cards are included in our team notifications. We also record data access, deletion, correction, consent withdrawal and privacy questions in Notion as Privacy requests to track their handling history. They are not treated as sales leads. These providers process information under their own security and data-protection commitments. Information may be processed in countries other than your own; where required, we rely on appropriate transfer safeguards.

We do not sell or rent personal information. We do not share waitlist data with data brokers or use it to build third-party advertising profiles. We may disclose information when required by law, to protect rights and safety, or as part of a genuine business reorganisation subject to appropriate protections.

Retention and security

The first-party journal is reviewed and removed when no longer needed for test follow-up and funnel analysis, and included in applicable deletion requests. Browser-only questionnaire drafts are cleared after successful submission or when the browser tab session ends.

Waitlist and reward-claim submissions, including their links to ballots, are kept until the relevant private-test, reward fulfilment or beta programme ends, you withdraw, or a maximum of 24 months after submission, whichever comes first, unless continued retention is required by law or you separately join the product. Blind-test ballots may be retained in aggregate or de-identified form to compare product quality over time. Privacy requests may be retained for up to 24 months so we can document how they were handled. Copies sent to our team through Telegram and stored in Notion are subject to the same submission retention periods and are included when we process an applicable deletion request. Infrastructure logs follow the hosting provider's configured retention periods.

We use access controls and private storage intended to protect submissions. No internet service can guarantee absolute security, so please do not send confidential audio, passwords or sensitive personal information through the contact form.

Cookies and similar technology

We use Google Tag Manager to administer tags, Google Analytics 4 to understand site and funnel performance, the Google Ads tag to attribute meaningful actions such as starting or completing a blind test, and Microsoft Clarity to create heatmaps and session playbacks. Clarity records page structure and interactions such as clicks, scrolling and pointer movement; text entered into input fields is masked. On visits tagged as Reddit campaigns, Reddit Pixel can receive the page URL and campaign parameters, a pseudonymous browser identifier and these event types: page visit, test start, accepted ballot and optional sign-up. We do not pass ballot answers, audio or email addresses as event metadata or matching keys; automated email and phone matching and enhanced page metadata sharing are disabled in the Reddit account.

On ordinary site visits, analytics and advertising measurement storage are enabled when the page opens unless you have already saved a different choice. Ad personalisation remains disabled. On visits tagged as Reddit campaigns, measurement storage is denied by default and you are asked to choose before Reddit Pixel loads. If you choose Analytics only, analytics providers may use analytics cookies and receive page, campaign, device and interaction information. If you choose Allow measurement, analytics storage, advertising storage and advertising user data are granted for analytics and conversion attribution. If you decline, tags remain in limited or cookieless modes.

Google, Microsoft and Reddit act as independent providers under their own privacy terms. We do not use this Pixel for retargeting or send ballot answers, email addresses or audio to them. We store your general measurement choice in your browser under loud-clear-measurement-consent-v2 and your specific Reddit Pixel choice under loud-clear-reddit-pixel-consent-v1. The Reddit Pixel is not loaded until you choose Allow measurement; a prior choice for Google alone does not turn it on. You can opt out, withdraw or change your choice at any time using ; an existing opt-out is respected on every page. A change stops future Pixel events on the current page, and a reload prevents the Pixel from loading again.

Your choices and rights

Depending on where you live, you may have the right to access, correct, delete, restrict or receive a copy of your personal information; object to certain processing; withdraw consent; and complain to your local data-protection authority. You may also opt out of beta and listening-test emails at any time.

Submit a request below. We may need to verify that you control the email address involved before completing it.

Children and changes

The website and beta waitlist are not directed to children under 16, and we do not knowingly collect their information. We may update this policy as the product changes. The date at the top shows the latest revision; material changes will be highlighted on the website or communicated to affected participants.