RazielReveal
Privacy Policy
Effective date: 3 September 2026
Last updated: 3 September 2026
This Privacy Policy explains how WANG PING-YAO (the “Developer,” “we,” “us,” or “our”) handles personal data when you use the RazielReveal mobile application (the “App”). It applies to our processing of information through the App, associated cloud-processing features, support, and account services.
The App can process audio either locally on your device or through cloud processing. That distinction is important: we do not collect audio content that is processed only locally on your device.
1. Summary
- We treat your account information, audio Content, and generated Outputs as private.
- We do not sell your personal data or your audio Content.
- We do not use your audio Content or Outputs to train our models, for advertising, or for unrelated purposes without your explicit, separate permission.
- When you choose local processing, your audio and locally generated Outputs remain on your device and are not sent to us by the App for processing.
- We use a guest or registered account to provide account-linked features, including cross-platform Premium-status synchronisation and Cloud HQ quota management.
- When you choose cloud processing, including Cloud HQ stem separation, we store and process the Content and Outputs needed to provide that feature in the cloud. Cloud HQ uses Google Firebase/Google Cloud and MVSep as service providers.
- If you separately opt in, we use Google Firebase services for reasonable, proportionate usage analytics, diagnostics, and performance monitoring to assess service quality and improve the user experience. We do not include audio recordings, lyrics, stems, filenames, or locally processed Outputs in ordinary analytics events.
- Payment credentials are handled by authorised third-party payment channels; we do not store your complete card, bank-account, or digital-wallet information.
- If the App displays ads, you can choose whether to allow tracking for more relevant ads. If you decline, you will receive contextual or less-personalised ads where ads are shown.
2. Definitions
“Content” means audio files and related material you import, upload, or submit for processing. “Outputs” means audio stems and recognised musical information generated by the App, including beats, chords, melodies, lyrics, timestamps, MIDI-style note information, and song structure. “Account Data” means the information used to create, authenticate, secure, and administer a guest or registered account, synchronise Premium status, and administer Cloud HQ access and quota. “Personal data” means information that identifies, relates to, describes, or can reasonably be linked to you or your device.
3. Information we collect and why
A. Account, authentication, Premium status, and quota information
After you accept the legal documents, the App may create or use a pseudonymous guest account so that account-linked features can work. If you create or sign in to a permanent account, we may process your email address, display name if supplied by you or your sign-in provider, account identifier, sign-in-provider identifier, authentication and account-security records, and account settings. We do not receive or store your plain-text password. Authentication is provided through Google Firebase Authentication.
We use Account Data to authenticate and secure your account; link a guest account to a permanent account where you choose; support account access on supported iOS and Android devices; detect fraud, abuse, and unauthorised access; and respond to account or support requests.
To synchronise and administer Premium status and Cloud HQ access, we may process your Firebase account identifier, RevenueCat app-user identifier, active entitlement status, product and store identifiers, purchase or restore status, subscription/lifetime status, billing-conflict status, and server-calculated Cloud HQ quota information, including available, reserved, used, and accrued song units and the next quota-accrual time. We use this information only to provide, validate, reconcile, secure, and support purchases, Premium access, cross-platform entitlement status, and Cloud HQ quota. We do not use it for advertising based on your musical Content.
B. Audio Content and Outputs
Local processing. If you choose on-device processing, the App processes the selected audio and generates Outputs on your device. The App does not upload or collect that locally processed Content or those local Outputs for our processing. The App may keep them locally until you delete them, remove the App, or use a device or operating-system feature that removes them.
Cloud processing. If you choose cloud processing, we collect, transmit, store, and process the Content, relevant technical metadata, and the Outputs necessary to perform the requested service and make the results available to you. We treat these items as private. We do not sell them, use them to train models, publish them, or disclose them to advertising partners.
Cloud HQ stem separation. When you select Cloud HQ stem separation, we upload your selected audio file, a sanitised filename, file type and size, account and job identifiers, processing status and timestamps, and the resulting stems and ZIP archive to Google Firebase/Google Cloud services used to operate the feature. We may provide MVSep with a time-limited, signed URL that lets it retrieve the selected audio and process the requested separation. MVSep returns the resulting files to our cloud-processing workflow so that we can deliver them to you. MVSep does not receive your App account password or payment credentials from us.
Cloud storage may include the input file, generated stems, ZIP archive, recognised musical information where generated, processing status, filenames you provide, file metadata, account identifier, job identifier, quota status, and timestamps. We use this information only to provide cloud processing, maintain and secure the service, troubleshoot a request you make, enforce our Terms, and comply with law. We do not use your Content or Outputs for model training, unrelated model evaluation, advertising, marketing, or sale to others without your explicit, separate permission.
C. Usage analytics, service quality, and user-experience improvement
We collect only reasonable and proportionate usage analytics, diagnostics, and performance data to assess and improve service quality and the user experience. This information helps us understand whether features work as intended, identify crashes or slow processing, resolve errors, prioritise improvements, and make the App easier and more reliable to use.
Your choice. These services are optional. We keep Firebase observability data collection disabled and do not send this information unless you separately enable usage analytics and/or diagnostics and performance monitoring in the legal-acceptance screen or later in About & Legal. Declining or withdrawing either choice does not affect access to the App's core features.
Google Firebase services. If you opt in, we use Google Firebase services provided by Google LLC: Google Analytics for Firebase for usage analytics, Firebase Crashlytics for crash and non-fatal diagnostic reports, and Firebase Performance Monitoring for performance data. The selected services may process:
- feature-use events, such as whether a separation, recognition, export, cloud-processing request, purchase screen, or ad display was started, completed, cancelled, or failed;
- app version, operating-system version, device family or model, language or region setting, app configuration relevant to compatibility, session duration, and general device, network, and performance characteristics;
- pseudonymous app-installation, Firebase-installation, or analytics-instance identifiers; an IP address may be processed to derive country or region information;
- crash reports, non-fatal error categories, stack traces, error codes, performance measurements, timing data, CPU or memory information, and network/service diagnostics, including network request URLs without their parameters or payload content; and
- high-level, aggregated statistics, such as feature adoption and cloud-processing volume.
We design our analytics events, custom traces, and non-fatal diagnostic reports not to include the audio itself, separated stems, lyrics, recognised chords, generated musical information, file names, or the contents of locally processed files. We use this information solely to operate, secure, diagnose, measure, and improve service quality and the user experience; we do not use it to identify the musical content you process or to build advertising profiles from your Content.
We configure Firebase Analytics not to collect the Apple Identifier for Vendor (IDFV). Pseudonymous Firebase or analytics installation identifiers are different from the IDFV and may still be used by the selected Firebase services. Advertising identifiers and tracking for ads, if offered, are addressed separately in Section 3(E). Google processes Firebase information under its Privacy Policy and Firebase privacy and security information.
Where consent is required by law, we request it before collecting non-essential analytics, diagnostics, or performance data. You can withdraw consent at any time by turning off the relevant setting in About & Legal. Turning a setting off stops future collection by the corresponding service; it does not retroactively delete information collected before you withdrew consent.
D. Payment and transaction information
If you make a purchase, the relevant app store or other authorised payment processor handles the payment. We do not directly collect or store your full payment-card number, bank-account details, or digital-wallet credentials.
We may receive and keep the minimum transaction information needed to provide and reconcile your purchase, prevent fraud, provide support, and meet accounting or tax obligations. This may include your account or platform identifier, product purchased, transaction or order identifier, purchase date, amount, currency, country or region, tax status, subscription status, and receipt-validation result.
E. Advertising information and your tracking choice
If the App includes ads, an advertising provider may deliver ads using limited technical information, such as device or advertising identifiers, IP-address-derived approximate location, device type, operating-system version, language, ad interaction events, and other information that you allow it to use under its privacy terms and your device settings.
Where required, we will ask for your permission before tracking you across apps and websites owned by other companies for personalised advertising. On Apple devices, you can select Allow to permit tracking for more relevant advertising, or Ask App Not to Track to limit such tracking. If you decline, the App will not access the advertising identifier for cross-app tracking through the App and will show contextual or less-personalised ads where ads are available. You can change this choice later in your device privacy settings, subject to the operating system's controls.
We do not provide your audio Content, Outputs, or registration credentials to advertising providers. We do not knowingly use tracking for personalised advertising to users for whom such tracking is prohibited by applicable law.
F. Communications and support
If you contact us, we collect the information you choose to include, such as your name, contact details, screenshots, device information, and the substance of your request. Please do not send audio Content, passwords, or other sensitive information unless it is necessary and we specifically ask for it to resolve a support request.
4. How we use information
We use personal data only as reasonably necessary to:
- provide, operate, secure, maintain, and improve the App and the cloud-processing features you request;
- process Content and produce, store, retrieve, and deliver Outputs when you select cloud processing, including Cloud HQ stem separation;
- create and manage guest and registered accounts, authenticate users, synchronise and validate Premium status across supported platforms, administer Cloud HQ quota, process purchases, and provide customer support;
- monitor service performance, diagnose errors, prevent fraud, misuse, and security incidents, and enforce our Terms of Use;
- comply with legal obligations, respond to lawful requests, and protect rights, safety, and property; and
- serve advertising in accordance with your permissions and applicable law.
We do not use Content or Outputs for model training, model evaluation unrelated to your request, advertising, marketing, or sale to others unless you give us explicit, separate permission.
5. When information is disclosed
We do not sell or rent personal data, Content, or Outputs. We do not disclose Content or Outputs to third parties for their own independent marketing, advertising, or model-training purposes.
We may disclose limited information only in the following situations:
- Google Firebase and Google Cloud. Google LLC provides Firebase Authentication, Cloud Firestore, Cloud Functions, Cloud Storage, and related infrastructure for our account, entitlement, quota, and Cloud HQ features. Google may process Account Data, Cloud HQ job metadata, and, when you use Cloud HQ, the input and output files needed to provide the feature.
- MVSep Cloud HQ processing. When you choose Cloud HQ stem separation, we provide MVSep with the temporary access and information reasonably necessary to process the selected audio and return the resulting stems. MVSep's handling of the content is also subject to its Privacy Policy and Terms. We do not provide MVSep with your App account password or payment credentials.
- RevenueCat. RevenueCat, Inc. provides entitlement and purchase-status management. We provide it with an account identifier and it processes purchase, subscription, and entitlement information needed to validate and synchronise Premium status. We do not provide it with your audio Content or Outputs.
- Google Firebase observability services. If you opt in as described in Section 3(C), we share the listed usage, diagnostic, and performance information with Google LLC through Google Analytics for Firebase, Firebase Crashlytics, and Firebase Performance Monitoring. We do not send your audio Content or Outputs to these services.
- Payment channels. The relevant app store or payment processor receives information necessary to process and validate a transaction under its own privacy policy. We receive only the transaction information described above.
- Advertising providers. If ads are enabled, advertising providers may receive the limited technical and advertising information described in Section 3(E), subject to your permissions and their privacy terms. They do not receive your audio Content or Outputs from us.
- Legal, safety, and rights protection. We may disclose information where we reasonably believe disclosure is necessary to comply with law, a valid legal process, or a lawful request; protect the rights, privacy, safety, or property of you, the Developer, or others; investigate suspected wrongdoing; or enforce our agreements.
- Business transfer. If the App or the Developer's business is involved in a merger, acquisition, financing, reorganisation, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to applicable law and continued protection consistent with this Policy.
- With your direction or consent. We may disclose information when you ask us to do so or give your affirmative consent.
6. Legal bases for processing (EEA, UK, and similar regions)
Where applicable, we process personal data under one or more of these legal bases: performance of a contract with you (including providing account, Premium-status synchronisation, Cloud HQ quota, and cloud-processing features); our legitimate interests in operating, securing, improving, and protecting the App and preventing fraud or misuse, balanced against your rights; your consent (for example, where required for non-essential analytics or advertising tracking); and compliance with legal obligations.
You may withdraw consent at any time using the relevant App or device setting. Withdrawal does not affect processing that occurred before withdrawal and may prevent a consent-dependent feature from working.
7. Data retention and deletion
We retain personal data only for as long as reasonably necessary for the purposes described in this Policy, unless a longer period is required or permitted by law.
- Locally processed Content and Outputs: remain on your device under your control until you delete them, remove the App, or your device or operating system removes them. We do not retain a copy merely because you processed them locally.
- Cloud HQ Content and Outputs in our Firebase/Google Cloud services: are retained while needed to provide the Cloud HQ feature and, ordinarily, while the related account remains active, unless you request deletion or delete the account. Account deletion removes account-scoped Cloud HQ jobs and files from our active Firebase/Google Cloud storage. We may retain limited backups and information needed for security, fraud prevention, accounting, legal compliance, or dispute resolution for a limited or legally required period.
- MVSep Cloud HQ Content and Outputs: MVSep receives the source audio only to process the Cloud HQ request. MVSep currently states that it deletes the uploaded file after one day and working copies, generated outputs, and processing records after three days. MVSep may change its practices; see its Privacy Policy for its current terms.
- Account, entitlement, quota, and transaction information: is retained for the life of your account and afterward only as needed for support, security, fraud prevention, legal, accounting, tax, or dispute-resolution purposes. Account deletion removes the active Firebase account and account-scoped state, but does not necessarily delete transaction, billing, or audit records that a platform, RevenueCat, or we must retain for the listed purposes.
- Google Firebase observability data: Google Analytics event data is retained according to the data-retention setting configured for our Google Analytics property, which we will configure for no longer than 14 months. Google states that Firebase Crashlytics retains crash reports, extracted minidump data, and associated identifiers for 90 days before removal begins. Google states that Firebase Performance Monitoring retains IP-associated events for 30 days and installation-associated or de-identified performance data for 60 days before removal begins. Aggregated or de-identified reporting may remain available afterward. You may withdraw consent through About & Legal and may request deletion using the contact details below.
8. Security and limits of security
We use reasonable technical and organisational measures designed to protect personal data, including access controls, safeguards appropriate to the sensitivity of the data, and protection of cloud transmissions and storage where technically available. Access to cloud Content and Outputs is limited to persons and providers who need it to operate or support the requested service.
No method of transmission, storage, or security control is completely secure. Accordingly, we cannot guarantee absolute security or that data will never be lost, accessed, altered, disclosed, or destroyed despite our safeguards. You should keep your own backups of important Content and Outputs and protect your account credentials and device. To the maximum extent permitted by law, our liability for a data loss or security incident is limited as described in the Terms of Use.
9. International transfers
Cloud processing and service providers may process information in countries other than the one in which you live. In particular, Cloud HQ uses Google Firebase/Google Cloud and a MVSep regional service; MVSep states that processing is stored in the region where the job is created. Those countries may have data-protection laws that differ from your local laws. Where required, we will use appropriate safeguards for international transfers, such as contractual commitments recognised by applicable law.
10. Your privacy choices and rights
Depending on where you live and applicable law, you may have the right to request access to, correction of, deletion of, restriction of, or objection to processing of your personal data; to receive a portable copy of certain data; and to withdraw consent. You may also have a right to complain to your local data-protection authority.
You can generally:
- choose local processing rather than cloud processing when the App offers both options;
- create, sign in to, or sign out of an account using the account-management feature, understanding that sign-out does not delete the signed-in account;
- enable or disable the separate usage-analytics and diagnostics/performance-monitoring choices in About & Legal;
- delete locally stored Content and Outputs from the App or your device;
- request deletion of Cloud HQ Content, Outputs, or your account using the contact details below; deleting your account also removes active account-scoped Cloud HQ files and account state from our Firebase/Google Cloud services;
- control App permissions and advertising-tracking choices through your device settings;
- manage purchases or subscriptions through the applicable app-store account; and
- request account deletion or make a privacy request using the contact details below.
We may need to verify your identity before fulfilling a request and may retain or decline to delete information where law permits or requires us to do so. We will not discriminate against you for exercising a privacy right, except where a difference is reasonably related to the value or feasibility of providing a particular service or required by law.
California notice
We do not sell personal information. We do not share personal information for cross-context behavioural advertising unless you affirmatively allow tracking as described in Section 3(E). If applicable law grants you a right to opt out, you may use your device's tracking setting or contact us at bw.innovation.tw@gmail.com.
11. Children
The App is not directed to children under 13, or below the minimum age required to consent to data processing in their country. We do not knowingly collect personal data from such children without legally valid parental consent. If you believe a child has provided us personal data in violation of this Policy, contact us so that we can investigate and take appropriate action.
12. Changes to this Policy
We may update this Policy to reflect changes in our practices, the App, technology, or legal requirements. If we make a material change, we will provide notice through the App, an app-store listing, or another reasonable method where required by law. The updated Policy will display a new effective date. Your continued use of the App after the effective date is subject to the updated Policy, to the extent permitted by law.
13. Contact us
For privacy questions, requests, or complaints, contact:
WANG PING-YAO
Privacy email: bw.innovation.tw@gmail.com
Support email: bw.innovation.tw@gmail.com
Country: Singapore