Privacy Policy

1. Who is responsible

BLOK is operated by ESTRELA RECORDS, a French SAS registered with RCS Manosque under number 948 002 902, at 34 Rue Ratavoux, 04130 Volx, France. ESTRELA RECORDS is the controller for the processing described here.

For privacy questions or requests, email estrela.mgmt@gmail.com, mentioning BLOK, or write to that postal address.

2. Data we use and why

• Accounts and access. Email address, name, password hash, account identifier, email verification, accepted terms and session records let us create and secure your account, recover access and provide service messages. The legal basis is performance of our contract or steps you request before entering it. Security and abuse prevention also rely on our legitimate interest in protecting the service.
• Google sign-in, if you choose it. Google supplies an account identifier and verified email address. We use these to authenticate you or connect Google to your existing BLOK account. We request identity and email access only, not access to Gmail, Drive, contacts or your files. The legal basis for BLOK's authentication processing is performance of the service you request. You may instead use email and a password; existing accounts are not merged solely because emails match.
• Software and devices. Product access, licence status, device identifiers, device names and platform information support activation, downloads, device limits and offline authorisation. These are necessary to perform the software agreement. Security records may include IP address, browser information, timestamps and failed access attempts, based on our legitimate interest in preventing misuse.
• Qualified plugin use. Depending on the application version, reports include product and account identifiers, qualifying month, event times, activity intervals, session identifiers, plugin version and format. These support licence verification and contractual usage accounting, including allocations to creators. They do not contain your recordings, audio, MIDI, project contents or presets. We use these records for performance of the agreement and, where applicable, legal accounting obligations.
• Subscriptions and payments. Selected plan, billing interval, provider identifiers, payment and subscription status, amounts, currency, cancellations, refunds and disputes let us deliver purchased access and handle billing. Stripe handles the payment form; BLOK does not receive your full card number or security code. Processing is based on the contract and applicable accounting obligations. The checkout identifies the seller and payment terms that apply.
• Duo invitations. The subscription owner supplies the invited email address. We use it to match acceptance to the intended person. Members' names and emails are visible within their Duo; billing management is reserved to its owner. The personal invitation link expires after 48 hours. The owner shares it; we do not automatically email it. This supports the requested Duo service and our legitimate interest in delivering invitations securely.
• Support. We use your messages and the information you choose to provide to resolve your request, based on the contract or our legitimate interest in assisting users. Please avoid sending passwords, payment credentials or unrelated private files.
• Optional application diagnostics. BLOK Manager asks separately for local diagnostic collection, transfer to BLOK support, and automatic failure reports. These choices are off by default and are based on your consent; refusing them does not remove your software access. Reports contain bounded technical information such as application and operating-system versions, error codes and diagnostic events. They exclude audio, MIDI, projects, presets, passwords and raw account sessions. You can preview a manual report, withdraw these choices and request deletion of sent reports from the application's Support panel. Withdrawal stops new collection or transfers; a pending remote deletion completes when the service is reachable. This production service uses a separate encrypted diagnostic store and pseudonymous account and installation identifiers. It does not send reports to an AI provider or automatically install changes.

Required form fields are marked in the interface. Without the necessary account or payment information we cannot create access or fulfil the requested purchase. Optional Google connection and appearance preferences are not required to use BLOK.

3. Who receives data

Access is limited to authorised ESTRELA RECORDS personnel and service providers needed to operate BLOK: OVHcloud for hosting, Google for optional sign-in and service email delivery, and Stripe and its payment partners for checkout and subscription management. The background film is hosted on estrela-records.fr; loading it sends normal connection information to that host.

We may disclose necessary records to our accounting or legal advisers and to authorities when required by law. Another Duo member receives only the membership information described above, not your password or payment details.

Google and Stripe also process information under their own policies: Google Privacy Policy and Stripe Privacy Policy.

4. International processing

Google and Stripe operate internationally, so relevant data may be processed outside the European Economic Area, including in the United States. Their published transfer information describes the applicable adequacy decisions, EU–US Data Privacy Framework participation and standard contractual clauses: Google transfer frameworks and Stripe international transfers. Contact us for information about safeguards applicable to your BLOK data or to request a copy where available.

5. How long we keep data

Account and licence information is retained while needed to provide your account, purchases and continuing software rights. You can request account closure and deletion through the contact above. Closure is handled on request, rather than by an automatic timer. Records still necessary for an outstanding obligation, dispute or statutory retention requirement are restricted to that purpose.

• Routine licence events are kept for 90 days and download events for 180 days. Usage delivery receipts are kept for 30 days and synchronisation health records for seven days. Routine administration audit records are kept for one year; foundational security records may remain necessary for the life of the relevant account.
• Processed service-email queue records are removed after 90 days; message bodies are removed after processing. Password-reset records are removed seven days after expiry. Expiry of a sign-in or verification link makes it unusable, but does not by itself delete all associated account records.
• Accounting documents, invoices and supporting accounting records are retained for ten years from the end of the relevant financial year. Contract evidence is kept for the applicable limitation period, generally five years, and electronic consumer contracts of at least €120 for the applicable ten-year period. A dispute can require necessary evidence to be retained until its final resolution.
• Detailed plugin usage records are reviewed for their accounting or licence purpose. Only records needed to substantiate allocations, contractual rights or legal obligations are retained for the relevant period above. These reviews and account-deletion requests require administrative handling; the system does not promise immediate automatic erasure of all historical records.
• For optional application diagnostics, report content expires after 30 days, incident and delivery metadata after 90 days, and diagnostic audit records after 180 days. The server checks these expirations hourly. A deletion request removes report content sooner; minimal deletion records are kept separately to prevent erased reports from reappearing after recovery. These periods concern the diagnostic service, not licence or accounting records.

Technical logs and backup copies are subject to operational rotation. Deleted records may remain in isolated backups until those copies are replaced; backups are used for recovery, not normal account access. Provider-held records are also subject to the provider's own retention obligations.

6. Cookies and preferences

This account journey uses necessary session and security cookies: an access cookie lasting up to 15 minutes, a refresh cookie lasting up to 30 days, and a Google sign-in flow cookie lasting up to 10 minutes when you start that flow. They protect authentication and are not advertising identifiers.

Your appearance choice is stored locally until you change it or clear browser storage. An invitation may be held for the current browser session while you sign in. The service uses no advertising or audience-measurement cookie in this journey. Stripe and Google explain the cookies used on their own pages.

7. Your rights and choices

Subject to the conditions in applicable law, you can request access, correction, erasure, restriction and portability of your data, and object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing. You can also provide instructions concerning your data after your death.

Send your request to estrela.mgmt@gmail.com. We may ask for proportionate information to confirm identity, but never your password. Some records cannot be erased immediately because they support existing rights, accounting duties or a dispute; we will explain any applicable restriction.

Subscription and licence checks can automatically allow or deny software access according to your entitlement. If you think a result is wrong, contact us for human review.

You may lodge a complaint with the CNIL or another competent data protection authority.

8. Changes and additional services

We update the date and version above when this notice changes and provide additional notice where required. Separate beta, publishing or optional diagnostic features may provide an additional notice at collection; this notice does not authorise unrelated data collection.