Last Updated: August 19, 2026
This Privacy Policy describes how RQS Studio processes personal and technical data related to use of the platform. It describes the current Public Beta and is not a statement of absolute legal compliance or certification.
This Policy applies to RQS Studio and explains key data categories, purposes, relevant providers, retention, security, privacy rights and contact channels.
The service is operated by RaQuel Synths / RQS Studio. For privacy, personal-data requests, support or Terms questions, use our support channel.
Depending on the features you use, RQS Studio may process:
RQS Studio does not describe CPF/tax ID, postal address, phone number, precise location or biometrics as part of its current standard workflow.
Data may be processed to:
RQS Studio uses Supabase infrastructure for functions such as authentication, profile/account data and the application database. If you choose Google or GitHub login, data needed for authentication may be received from the selected provider. RQS Studio does not need to receive your Google or GitHub password for this login flow.
Processing carried out by the identity provider itself is also governed by that provider's policies.
Audio may be processed in ephemeral local storage while a job runs and in Amazon Web Services (AWS) object storage, including infrastructure in the São Paulo region where applicable to the audio workflow.
Temporary audio objects are configured for automatic expiration approximately 24 hours after upload under technical lifecycle policies. Effective physical removal may occur later depending on provider processing. The service should not be treated as permanent storage or backup.
RQS Uplink processes public music/media URLs supplied by users, generated redirect/deep links and related metadata needed to operate and manage the feature. Uplink is not a contact form and is not described as collecting a support name, subject and message.
When you voluntarily submit your email to an interest list, it may be stored/processed using Google/Firestore infrastructure and a communications provider such as Brevo to record interest in future RQS Studio offerings and send communications directly related to that interest.
Joining the waitlist is not treated as unrestricted consent for unrelated marketing.
We may process logs, technical identifiers, error responses, event times and operational data needed for diagnostics, security, abuse prevention and service stability. The content and duration of these records depend on the relevant service and operational need.
The Studio may use browser local storage and similar technologies for functions such as language preference, session handling and application state needed for the service.
The current Studio frontend audit did not find active Google AdSense implementation, publisher tags or ad units; this Policy therefore does not describe AdSense/DoubleClick advertising cookies or personalized ads as active RQS Studio processing. If advertising is introduced in the future, this Policy and, where required, consent mechanisms will be reviewed before the relevant use.
Relevant providers for current or prepared operation include:
The backend contains a prepared Stripe payment integration, but monetization is disabled in the current product state. If paid services are enabled, payment data may be processed by Stripe or another provider disclosed at checkout. When payment is handled by the payment provider, RQS Studio does not need to store complete payment-card data directly.
Some providers operate infrastructure across multiple countries. Accordingly, certain data may be processed outside Brazil depending on the service and provider used. Where applicable, processing should observe relevant legal requirements and safeguards. We do not state that all RQS Studio data remains exclusively in Brazil.
Retention varies by category:
RQS Studio uses technical and operational controls intended to reduce risks of unauthorized access, loss and abuse. No Internet-connected system can guarantee absolute security, and measures are adjusted as the architecture and product stage evolve.
Depending on applicable law and the specific situation, you may have rights such as confirmation of processing, access, correction, information about sharing, anonymization/blocking/deletion where applicable, withdrawal of consent where consent is the legal basis, deletion of consent-based data where applicable, and review of automated decisions where applicable.
To exercise rights or make a personal-data request, use the contact channel in this Policy. Some requests may require reasonable identity verification and may be subject to exceptions provided by law.
RQS Studio is not specifically directed to children. Where applicable law requires consent or authorization from a parent or guardian for a user, the service should be used only with that authorization.
This Policy may be updated to reflect changes in the product, providers, data practices or applicable requirements. The update date will be shown on this page.
For privacy, personal-data requests, support or questions about this Policy: Contact Us