Mestrio Studio

Mestrio Studio Privacy Policy

Effective date: August 7, 2026
Last updated: August 15, 2026

Welcome to Mestrio Studio (the “App”). This Privacy Policy explains how the individual developer/operator, Robin Wang (“we,” “us,” or “our”), processes personal information and related data when you use the Android application with package name com.mestrio.studio.

Development contact email: robinxdroid@gmail.com
Privacy Policy URL: https://mestrio-studio.web.app/privacy/

The current version of the App does not operate an App account system, cloud project storage, cloud hosting of project content, or live-content relay service. Projects, scenes, media references, recordings, and most settings that you create in the App are stored only on your device or in a location you choose. Some third-party account connections may use a minimal, stateless authorization relay when the provider requires a confidential client credential; that relay processes authorization codes and tokens only to exchange, refresh, or revoke authorization and does not receive project files or live audio/video. Unless you actively use a third-party feature, the App does not transmit this data to a network service. Read this policy together with the policies of the streaming platforms, payment services, websites, network-media services, and device manufacturers you choose to use.

1. Scope

This policy applies when you download, install, launch, or use the App’s recording, preview, audio mixing, streaming, scene editing, project import/export, external-device, and platform-authorization features.

It does not apply to independently provided third-party services, including any streaming service, account-authorization service, app-store or payment service, web source, network-media service, model-download site, or external-device service that you configure. Those third parties process data under their own terms and privacy policies, which we do not control.

2. Information We Process

The App primarily processes information on your device and only as needed to provide features that you actively use. It does not upload projects, recordings, captured content, or media libraries to an App server. Limited authorization credentials may be transmitted through the stateless authorization relay described below when required by a third-party provider. The information involved depends on the features you use.

2.1 Information you provide, select, or import

When you create or edit a project, the App may store locally on your device information that you enter or select, such as project and scene names; stream titles and descriptions; streaming server addresses and stream keys; source and canvas configuration; browser-source URLs; network-media addresses; selected devices; media file locations; model-download links; and preferences.

When you import media, projects, or archives, the App reads and processes the selected files on your device. When you export a project, recording, or archive, the App writes it to a location that you select or that Android manages. Do not include unnecessary sensitive information in project names, stream titles, stream notes, or archives that you share.

2.2 Audio, video, screen, and media content

After you actively enable a camera, microphone, screen capture, external video device, media file, browser source, or network-media source, the App accesses and processes the corresponding image, sound, or content only on your device to preview, compose, record, export, or stream it. You control that content, and it is not uploaded to any server. If you intentionally start streaming to a configured destination, share a file, or select a third-party network source, the relevant content or request goes directly from your device to the third-party service you select.

2.3 Platform authorization and account-related data

If you choose to connect a third-party streaming platform, account service, or another supported service, the App uses that service’s authorization flow on your device to request permissions required for the feature you selected. Depending on the service and scopes you grant, the App may process or display limited account/channel identifiers, display names, avatars, authorization state, stream configuration, or metadata needed to manage a stream locally on your device. The authorization flow communicates directly with the third-party service or, only where a confidential credential is required, through a stateless authorization relay that performs token exchange, refresh, or revocation.

Authorization tokens, refresh credentials, and stream keys are high-risk credentials. The App retains them only on the device, or has them managed by system/platform credential mechanisms, to the extent needed for authorized features. When a provider requires a confidential client credential, authorization codes and tokens pass transiently through the authorization relay over an encrypted connection; the relay is designed not to persist them or write them to application logs. Stream keys remain encrypted on the device and are not stored by the relay. You can disconnect a platform in the App and revoke authorization in that platform’s security settings. The platform’s own privacy policy governs its processing of account data and tokens.

2.4 Device, network, and diagnostic data

To operate properly, the App may access or process device and network information locally when relevant to the feature in use, such as Android version, device capability, display orientation, audio/video-device state, network availability, media devices or services discoverable on a local network, error information, and runtime logs.

The App automatically uses product analytics and crash/stability diagnostics. A third-party analytics processor may receive limited, content-free events describing feature requests and outcomes, internal feature categories, coarse duration/count buckets, App version and distribution channel, Android-version bucket, locale, theme, orientation, subscription tier, and Studio Mode state. A third-party diagnostics processor may receive crash, ANR, and native-failure reports together with the App version, affected internal subsystem, operation category, stack trace, an SDK-generated App-installation identifier, and limited device/runtime information needed to diagnose the fault.

These services are not used for targeted advertising, cross-app tracking, or data sales. The App disables advertising-ID collection, advertising-personalization signals, and automatic screen reporting. Analytics and diagnostics events are designed not to include projects, scene or Source names, captured audio/video, recordings, media-library content, speech transcripts, full URLs, stream keys, authorization tokens, passwords, file paths, email addresses, IP addresses, advertising IDs, or hardware device identifiers.

2.5 Purchases and subscriptions

If you purchase a subscription or in-app item through a third-party app store or payment service, that service and its payment partners process the payment. The App may read product identifiers, order/purchase tokens, purchase status, and entitlement or expiry information on your device as needed to verify, restore, or display purchases; that information is not uploaded to a server. We do not directly collect or store your full card, payment-account, or password information in the App.

3. How We Use Information

The App may use the information above on your device to:

We do not upload projects, captured content, recordings, or media libraries to an App server or use the above data for an unrelated purpose. Limited authorization credentials may be transmitted as described in Section 2.3. Other transmissions that occur when you actively use a third-party feature are governed by that third party’s rules.

4. Permissions and System Features

The App requests Android permissions or system authorization when you use the corresponding feature. Denying a permission may make that feature unavailable, but does not affect features that do not rely on it.

Permission or feature Purpose
Camera Capture camera video for preview, composition, recording, or streaming.
Microphone Capture audio for monitoring, mixing, recording, or streaming.
Screen capture Capture the screen you elect to share through Android’s MediaProjection authorization, which Android presents separately.
Network and Wi-Fi Connect to streaming services, platform-authorization pages, web sources, network-media addresses, and model-download URLs you configure.
Local network / Wi-Fi multicast Discover or connect to network-media or related services on your local network when you use those features.
USB / external video devices Recognize and use compatible UVC, HDMI, or other capture devices that you connect and select.
Display over other apps Show an App overlay only after you enable the relevant feature; Android manages this authorization separately.
Foreground service Keep continuous tasks such as recording, streaming, or media projection visible and stable.
Media and file access Use Android’s file picker or storage access that you grant to import, export, save recordings, and read files you select.

We do not secretly enable your camera, microphone, or screen capture without your action or Android authorization.

5. Storage, Retention, and Deletion

5.1 Location and retention

Project configuration, settings, covers, caches, and necessary local platform-connection data are generally stored in the App’s data area on your device or in a storage location you choose. Recordings, exports, and downloads are stored in a location you choose or that Android manages. The App does not operate a server or cloud database for aggregating, backing up, transmitting, or storing this content. The authorization relay described in Section 2.3 is not a content-storage or backup service.

We retain local data while it is needed for the applicable feature, until you delete a project, file, or cache; disconnect a platform; clear App data; or uninstall the App. System backups, file-manager recycle bins, third-party storage, and third-party platforms may retain copies under their independent rules.

5.2 Your controls

You can:

Deleting a local project or uninstalling the App may be irreversible. If content has already been streamed, shared, uploaded, or saved to a third-party service, delete it through that third party’s process.

6. Sharing, Transfers, and Public Disclosure

We do not sell, rent, trade, or share personal information or your content for targeted advertising. We do not collect project or live-content libraries on a server. The authorization relay processes only the limited credentials described in Section 2.3 and is not designed to retain them after completing the requested operation.

Information may be transmitted or disclosed as a result of your actions or where law requires it:

  1. Third-party services you choose. When you start a stream, complete OAuth authorization, access a browser source, download a model, connect network media, or use a third-party web service, relevant requests, content, and necessary identifiers go to the provider you specify. Streamed content goes directly to the platform or server you choose. Limited OAuth credentials may pass through the stateless authorization relay described in Section 2.3; project files and live audio/video do not.
  2. Third-party app stores or payment services. Necessary purchase information is processed between your device and the applicable service when you purchase, subscribe, restore purchases, or verify entitlements.
  3. Analytics and diagnostics processors. The limited events and fault reports described in Section 2.4 are transmitted to third-party processors acting for App analytics and stability diagnostics. These data flows are independent and are limited to their respective purposes.
  4. Legal and safety requirements. If you voluntarily contact us by email, we may process information that you include in the message and disclose the necessary part only when required by applicable law, court order, regulatory demand, or to protect safety, rights, or property.

7. Third-Party Services and International Transfers

Third-party platforms or network services that you choose may operate outside your country or transfer data to other countries or regions. International streaming platforms, third-party account or payment services, model-download sites, and URLs that you enter may be operated abroad. By actively using these features, you understand that relevant data is transmitted directly from your device and processed under the third party’s rules.

Review the applicable third party’s privacy policy, terms, and data-transfer information before connecting, and determine whether the service is appropriate for your use. We are not responsible for the availability, content, security, or data practices of third-party pages or services.

8. Security

We use reasonable measures appropriate to the App’s current scale and functionality to reduce risks of unauthorized access, use, disclosure, alteration, or loss. These include keeping projects and stream keys on-device, encrypting local credentials, minimizing the authorization relay to required token operations, configuring it not to persist or log credential bodies, avoiding authorization tokens and stream keys in ordinary App logs, and relying on Android’s app sandbox and permission model.

No device, network transmission, external storage, or third-party service can be absolutely secure. Protect your device unlock method, project archives, stream keys, platform accounts, and shared files. If you suspect credentials are exposed, change the relevant key promptly and revoke platform authorization.

9. Your Rights and Choices

To the extent provided by applicable law, you may have rights to access, correct, delete, withdraw consent, restrict processing, obtain a copy, or complain. Because most App data is stored on your device, you can generally exercise these choices directly through the App, your file manager, or Android Settings.

For assistance, email robinxdroid@gmail.com. Do not send passwords, authorization tokens, stream keys, or unnecessary personal information by email. Because we do not receive or retain the App’s user data, we cannot retrieve, restore, or delete projects or content on your device; use the App, your file manager, or Android Settings to do so directly.

10. Children

The App is not designed specifically for children under 14. Minors should use the App with a parent or guardian’s consent and guidance, especially before recording, sharing a screen, using a camera or microphone, streaming, or connecting to third-party platforms. If a guardian believes that a minor provided personal information without authorization, contact us at robinxdroid@gmail.com.

11. Changes to This Policy

We may update this policy because of feature, legal, or security changes. For material changes, we will provide notice through an in-app notice, an updated page, or another reasonable method. The revised effective date will appear at the top. Continuing to use the App after the effective date means that you understand and accept the updated policy. If you do not agree, stop using the relevant features and delete local data.

12. Governing Law, Disputes, and Contact

Unless mandatory law provides otherwise, the formation, validity, interpretation, performance, and dispute resolution of this policy are governed by the laws of mainland China, excluding the laws of the Hong Kong Special Administrative Region, the Macao Special Administrative Region, and Taiwan. If you use the App from another country or region, you are responsible for determining whether your use complies with local law.

For questions, comments, complaints, or requests concerning this policy or personal-information processing, contact: