Melodix web studio and API privacy notice
Version: 2026-11-04-web-v1. This notice covers the website at bekservice.uk/melodix/ and its web/API accounts. Native mobile apps have a separate retained notice below. Web accounts and payments are separate from Apple and Google purchases. During maintenance, new accounts, payments or generation may be unavailable.
Who is responsible
BEK SERVICE LTD, 20-22 Wenlock Road, London, N1 7GU, United Kingdom, is the controller of the personal information we use to operate Melodix. Contact support@bekservice.uk about privacy, service access or your rights. Web/API accounts are intended for adults aged 18 or over.
Information and purposes
We use your email address to verify account access and send sign-in links and transactional receipts. Account records include a protected identifier derived from the verified address, session and API-key metadata, accepted terms, usage and payment references. API keys are shown once; we retain keyed verifiers, not a recoverable copy of the key.
We process your prompts, lyrics, generation settings and private generated audio on company-controlled music infrastructure to fulfil your requests. We retain the references and usage records needed to show results, account for service units and recover interrupted work. Outputs are not a public gallery. This version does not accept audio uploads or offer voice cloning. Avoid including sensitive personal information or another person's private details in your inputs.
We also receive technical request information, including IP address, browser information and security signals. We use these to protect accounts, limit abuse and investigate faults. Payment eligibility records may include a reviewed country decision, policy version, evidence reference and review timestamps. A network signal alone does not permanently confiscate a paid balance; contact support to request review of a restriction. Support correspondence is used to investigate and answer your request.
We rely on performance of the requested service contract for necessary account, generation and payment processing; legitimate interests in protecting the service and users for proportionate security and abuse prevention; and legal obligations for required financial records. These purposes do not give us unrestricted permission to reuse your information. There is no advertising or marketing-analytics implementation in the web/API service, and contacting support does not subscribe you to marketing.
Cookies and service providers
First-party security cookies maintain sign-in, protect actions against forgery and limit abuse. The sign-in browser cookie lasts ten minutes. The session has a seven-day maximum and becomes unusable after thirty minutes idle. The antiforgery cookie is a session cookie. A first-party security identifier lasts thirty days and does not create additional free allowances when cleared. A separate thirty-day deletion receipt cookie can read only its matching deletion status after ordinary sessions have been revoked. Blocking necessary security cookies prevents the affected account actions.
Cloudflare delivers and protects the website. Its Turnstile check processes technical signals such as IP address, browser/TLS information and the site being visited. Cloudflare's addendum distinguishes processing on our behalf to protect the site from its own processing to improve bot detection. Its privacy information is linked below; this is not an anonymous check performed only on your device.
When web payments are available, Stripe processes payment details through Checkout. We do not receive your full card number or security code. We keep payment status and transaction, customer, invoice, refund and dispute references, together with amounts, currency, taxes and the applicable offer. Stripe also has independent processing purposes described in its privacy policy. Transactional email uses our configured mail service at mail.bekservice.uk. Receipt addresses are protected at rest in our service. Information you send to support is also handled through our mail systems.
Providers may process information internationally. We do not claim that all processing stays in the UK or that every provider arrangement has already been verified. Recipient, location and transfer-safeguard review must be completed before the dependent customer features are opened; public account registration remains closed while these launch requirements are unresolved. Contact us for information about the arrangements applicable to an enabled service.
Retention and deletion
Private audio is normally available for thirty days from verified completion; downloading does not extend that period. Expiry or deletion removes product access before physical cleanup finishes. Associated generation text is cleared after successful physical erasure. Unfinished or uncertain work retains the information needed for reconciliation until its outcome is established. Unused quote text is cleared thirty days after quote expiry. Completed account-export downloads expire after 24 hours.
Consumed sign-in email is cleared immediately from the token record; expired or consumed token metadata is cleared after 24 hours. Inactive session records are removed seven days after expiry, revocation or the idle deadline. Challenge intents and rate-limit records are cleared after their respective 48-hour cleanup periods. Compact operation and key-issuance identities and revoked-key metadata are retained to prevent replay; they do not contain a recoverable API key.
Account deletion immediately freezes new work and revokes ordinary sessions and keys. Already-sent or uncertain work must be reconciled before its content can be erased. After completed deletion, the verified-identity binding is retained for 35 days to prevent allowance resets, then unlinked. An unresolved transactional receipt may retain its protected recipient for up to thirty days after deletion. Necessary financial records remain separate: tax/accounting records normally need six years from the relevant financial-year end, and an applicable legal hold may require longer retention. That is not permission to retain music indefinitely.
Encrypted offhost backup snapshots expire within 35 days. Deletion records are preserved independently and reapplied before a restored service permits access; completion of a deletion requires independent backup acknowledgement. This does not mean every old backup block disappears immediately. The backup period does not apply to accounting, support or operational logs. Operational logs currently have no verified finite automatic expiry; an application-specific retention limit must be established before public registration opens. Support or incident material that must remain for an unresolved matter is assessed separately, rather than represented as already erased.
Your rights and contact
Where applicable, you can request access, correction, erasure, restriction, portability or object to processing based on legitimate interests. Account privacy tools provide export and deletion when available. You can also email support@bekservice.uk, including if you cannot sign in; no particular legal phrase is required. We may request proportionate identity verification. Never send an API key, sign-in link, session cookie or full payment-card details.
We normally respond to rights requests within one calendar month. If the law permits an extension or requires information to verify identity, we will explain. Necessary legal retention or unresolved work can affect what may be erased, but does not remove your right to ask or receive an explanation. You can complain to the UK Information Commissioner's Office using the link below. Changes to this notice are dated and versioned, with a document hash shown on this page.
Document SHA-256: 8d27084a258ea25e0dae51ce5a86b8555942ff1f34216ddfac87d5ef4ee17ad5