1. Scope and responsible party
This policy covers MelodyQR’s website, accounts, subscriptions and handling of public-link requests. The service operator’s identification, address and tax details are available in Account settings after you sign in. Contact support@melodyqr.com, Customer Service, Monday to Friday, 09:00–17:00 Argentina time, excluding local public holidays. Legal request deadlines remain applicable outside these hours.
For account administration, billing and support, MelodyQR determines the service-related processing. Workspace owners determine the contents and purposes of their own publications. Depending on the operation, MelodyQR may process personal data on their behalf. These roles, instructions and any processing agreement must be finalized for the actual service; visiting a published page does not transfer all responsibility to its visitor.
2. Account and workspace data
Signing in uses the enabled identity provider. MelodyQR receives its account identifier, email and verification state, and display name or avatar when supplied. We keep account identifiers, memberships, roles, sessions and resource metadata to authenticate users and enforce access. Supplying identity and workspace information needed for the service is required for those functions; optional profile fields remain optional. We do not ask for an identity-provider password.
3. Billing and integrations
Billing processes the selected plan, quote, currency, amounts, billing email, seller/provider references and payment/subscription status. Payment details are handled by the payment provider’s secure flow. The card flow uses a token, not stored plaintext card credentials. Do not send card numbers or security codes to support. Provider conditions and privacy apply to their own processing; enabling an integration may share the data needed for the action you request.
4. Content and public destinations
Workspace content can include URLs, text, images, files and contact details chosen by the publisher. Public pages, contact cards and files may be viewed, copied or shared by anyone with their address. A hidden field or hard-to-guess URL is not a privacy control. Only publish data you may lawfully disclose. External destinations, embedded services and the merchant’s own sales may have different controllers and policies.
5. Scan analytics
Scan events may include time, public link and destination identifiers, selected rule or experiment, outcome, approximate country/region/city, device class, browser/operating-system family, language, referring site origin (scheme, host and port when present) and technical performance. Location is inferred from network information, not a request for precise GPS access. These events do not prove a unique person or approved payment. Authorized workspace members can view analytics within their permissions.
Scan analytics are cookie-free by default and the application scan-event schema does not contain raw IP addresses or full user-agent strings. Infrastructure must still handle network requests and may process associated technical information under its own service arrangements. This is not a promise that no provider ever processes an IP address or that all statistics are irreversibly anonymous.
6. Website measurement and local storage
Marketing pages use Cloudflare website measurement on configured production hosts and aggregate events such as page visits and completed product actions. Optional campaign labels are restricted; that event dataset does not contain visitor, account or workspace identifiers, full referrers or destination URLs. The browser collection code skips measurement when Do Not Track or Global Privacy Control is enabled. Scan analytics are a separate system.
Authentication uses a session cookie on the web and protected session storage where applicable on native devices. Language, theme and interface preferences can use local device storage. Necessary session storage is different from marketing analytics; cookie-free scans do not mean the entire application uses no cookies. Any future optional advertising or tracking needs a separate disclosure and lawful permission before activation.
7. Purposes and lawful processing
We process necessary information to provide the requested service, authenticate and authorize access, publish content, manage subscriptions, protect availability, answer requests and comply with legal duties. Optional purposes requiring consent are explained and requested separately, with withdrawal available. We do not treat acceptance of service terms as blanket consent, and lawful grounds must be assessed for the applicable jurisdiction and operation.
8. Providers and international processing
Infrastructure, database, storage, email, identity and payment providers process information needed for their functions. The current technical inventory includes Cloudflare, Neon, Resend, the enabled login provider and Mercado Pago. Authorized workspace members, requested integrations and competent authorities may also receive data for their legitimate roles. We do not authorize advertising use of your content or sell personal data through this policy.
Processing may occur outside your country. The final list of contracting entities, regions, data categories, processor agreements and applicable international-transfer safeguards remains under review. We do not claim all data stay in Argentina or that mentioning a provider establishes a lawful transfer. This information must be completed before this draft becomes effective.
9. Security and confidentiality
Server-side permissions separate workspaces and actions; integrations use scoped credentials that can be revoked. The application does not store or log plaintext API credentials. Security and abuse controls can process audit records and pseudonymous rate-limit keys; pseudonymization is not anonymity. Protection must also include operational access, incident handling and provider arrangements. No certification, absolute security or universal pre-screening of uploaded files is claimed.
10. Retention and deletion
Scan history is separate from account, content, billing, support and audit records. The current analytics provider retains its events for three months; that is not a deletion deadline for all MelodyQR data. Cancelling a subscription does not automatically delete an account or public content. A final schedule for each category, legal retention, backups and deletion/export procedures remains to be completed. No instant deletion, universal period or indefinite reuse is promised.
11. Your rights and requests
Contact support@melodyqr.com to request access, correction or deletion and exercise other rights provided by the applicable law, including withdrawal of consent when relevant. We may verify identity and authority proportionately to protect your data and other workspace members. Do not send unnecessary sensitive documents. Requests follow mandatory deadlines, not a general support estimate; lawful retention or rights of others may affect deletion. You may also contact the competent data-protection authority or courts.
In Argentina, access requests must be answered within ten calendar days; correction, updating or deletion requests within five working days, subject to applicable statutory rules. The Agencia de Acceso a la Información Pública receives complaints through the official process linked below, including when a request is unanswered after the applicable deadline or rights are denied. Keep proof of your request and any response. This draft does not claim that a dedicated account-deletion or data-export workflow is already available in the application.
12. Age and policy changes
Creating and managing a MelodyQR account is intended for adults with contractual capacity. Public QR destinations can be visited without an account; that does not authorize publishers to collect children’s or sensitive data without a lawful basis. Material policy changes will be explained with their date, and any new consent will be obtained where required. Previous notices must remain available once published; browsing alone is not consent to a new optional purpose.