AiBiBi Privacy Policy

1. Information we handle

Screen and audio session content

If you start screen sharing, the operating system presents its screen-capture authorization flow and AiBiBi processes the displayed screen to send it to the intended session participant. If you enable voice or microphone functionality, AiBiBi processes microphone audio for transmission. This information may reveal anything visible or audible during the session, including notifications and third-party personal information. Screen and audio sharing occur only when the relevant feature and system authorization are enabled.

Room, signaling, and connection information

We process room identifiers and participant roles to establish and coordinate sessions. Signaling rooms are transient and generally short-lived, although cleanup timing can vary due to session state, errors, infrastructure, or operational requirements. Connection and diagnostic logs may include the room identifier, participant role, relay or network-candidate metadata, app version, a device-derived identifier, IP address, timestamps, connection status, and error information. Network metadata can indicate an approximate location at a city or regional level even though AiBiBi does not request device location permission for this purpose.

Recent connections and local settings

On the audited Android implementation, AiBiBi keeps up to three recent room connections locally on your device and provides a delete control. Local settings and preferences are also stored on the device. Recent connections remain until you delete them, clear the app’s data, or uninstall the app, subject to device backup or restore behavior. iOS local storage and controls may differ and are described in the applicable app interface.

Analytics

On Android, if Firebase Analytics is configured and enabled, AiBiBi may send app-use events, app/device information, and a device-derived user identifier to Firebase to understand feature use, stability, and performance. This identifier is not the Android advertising ID in the audited implementation. Collection can depend on build configuration, consent choices, platform settings, and availability. On iOS, AiBiBi may use equivalent platform analytics or diagnostics only as disclosed in-app and in applicable App Store privacy labels. See Firebase Privacy and Security.

Feedback and support

If you submit feedback, we process the text, attachments or other content you choose to provide, your email address if provided, and related device and app metadata such as app version, operating system, device model, language, and diagnostic context. This is sent to our support endpoint so that we can respond, investigate, and improve AiBiBi. Do not include screen content, credentials, or another person’s information unless necessary and authorized.

Purchases and entitlements

If you purchase a subscription or one-time/lifetime product, Apple or Google processes your payment and payment credentials. AiBiBi receives or verifies limited transaction and entitlement data—such as product, purchase token or transaction reference, subscription state, expiration, and platform account/store response—needed to provide and restore access, prevent fraud, and handle support. We do not receive your complete payment-card number from the platform store.

No mandatory AiBiBi account

The audited Android app does not require you to create an AiBiBi account to use its core remote-assistance features. Your Apple or Google platform identity may still be used by the store for purchases, restoration, and platform services. If a future or platform-specific feature requires sign-in, the interface and updated disclosures will explain it.

2. Sources of information

We receive information:

• from you, when you enter a room identifier, start a session, share screen/audio, change settings, make a purchase, or contact support;
• from your device and app, through system permissions, local storage, connection telemetry, and diagnostics;
• from the other session participant, through signaling and session activity;
• from Apple or Google, for store transactions, entitlements, device/platform services, and applicable diagnostics; and
• from service providers, such as communications, hosting, relay, analytics, and support infrastructure.

3. How we use information

We use information to:

• create rooms, connect intended participants, and transmit screen and audio during sessions;
• operate, secure, troubleshoot, maintain, and improve AiBiBi and its connection quality;
• remember local settings and display recent connections;
• understand feature usage and app performance where analytics is configured and permitted;
• process, verify, restore, and support purchases and entitlements;
• respond to feedback and support requests;
• detect misuse, fraud, security incidents, and violations of our Terms of Service; and
• comply with law, protect rights and safety, and establish or defend legal claims.

Depending on where you live and the activity involved, our legal bases may include performing a contract you request, your consent, our legitimate interests in operating and securing AiBiBi, and compliance with legal obligations. You may withdraw consent where processing relies on it, without affecting prior lawful processing.

4. Recipients and processors

Information may be disclosed or made available as follows:

• Your session participant. The recipient receives the screen and audio you choose to transmit and may receive session status information. We cannot control what a recipient observes or independently records.
• Communications and infrastructure providers. Hosting, WebRTC signaling, STUN/TURN relay, network, security, and diagnostic providers process content or metadata as needed to establish and carry the session. When a direct peer-to-peer path is unavailable, encrypted media transport may pass through a relay.
• Analytics providers. On Android, Firebase/Google may process analytics data if configured and enabled. iOS analytics providers, if used, are disclosed through applicable in-app notices and store labels.
• Apple and Google. Platform stores process purchases, entitlements, refunds, and platform diagnostics under their own policies. See Google’s Privacy Policy and Apple’s Privacy Policy.
• Support and operational providers. Providers that host or process feedback, email, logs, and support requests act on our behalf and under appropriate obligations.
• Legal, safety, and corporate events. We may disclose information where reasonably necessary to comply with law or valid process, protect users and rights, investigate abuse, or complete a merger, financing, reorganization, or transfer of business, subject to applicable safeguards.

5. Advertising-related practices

The audited Android implementation does not use the Android advertising ID and does not use personal information for cross-context behavioral advertising. This statement is limited to the audited implementation and does not replace disclosures required by applicable law or platform store privacy forms. We will update this Policy and relevant platform disclosures before materially changing these practices.

6. Permissions and device controls

AiBiBi requests access only when relevant to a feature and subject to the operating system:

• Screen capture: Android uses the MediaProjection system prompt; iOS uses applicable system screen-broadcast or capture controls. You choose when to begin and can stop through the app or system interface.
• Microphone: used for voice/audio during an enabled session. You can deny or revoke access in device settings, but voice functionality will not work.
• Network access: required to connect participants and deliver the Service.
• Notifications or related platform permissions: may be requested where the operating system requires them to display active-session status or service notices.

The audited Android app does not request contacts, precise or approximate device location, SMS, or camera permissions. iOS permissions can differ based on system requirements and available features; review the system prompt and device settings before granting access. Denying optional access may limit the related feature but does not authorize collection by other means.

7. Retention

We retain personal information only as long as reasonably necessary for the purposes described here, including operation, security, support, legal compliance, dispute resolution, and enforcement. Retention depends on the data and context:

• screen and microphone content is transmitted for the session and is not intentionally stored by AiBiBi servers in the audited service design;
• signaling-room data is generally short-lived and removed after it is no longer needed to coordinate a session, subject to operational exceptions;
• connection and security logs may be retained for a limited period appropriate to troubleshooting, abuse prevention, and legal requirements;
• feedback and support records remain as needed to answer the request, maintain support history, and meet legal obligations;
• purchase and entitlement records remain as needed to provide purchased access and meet tax, accounting, fraud-prevention, and platform requirements; and
• local recent connections and settings remain until you delete them, clear app data, or uninstall, subject to device backup and restoration.

A recipient’s independent copy or recording is controlled by that recipient, not by AiBiBi.

8. Security

We use reasonable administrative, technical, and organizational measures designed to protect information, including transport security and restricted operational access where appropriate. WebRTC normally encrypts media in transit, but no device, network, transmission, or storage system is completely secure. Protect room identifiers, share only with trusted participants, keep your device updated, hide sensitive notifications, and stop a session if an unexpected person or activity appears.

9. International transfers

We are based in Singapore and operate with service providers and session participants that may be in other countries. Information may therefore be processed outside your country, where privacy laws may differ. Where required, we use recognized safeguards for international transfers, such as contractual protections, adequacy mechanisms, or other lawful transfer methods. A peer session also necessarily sends shared content to the location of the recipient you choose.

10. Children

AiBiBi is not directed to children under 13, or a higher minimum age where local law requires one, and we do not knowingly collect their personal information through the Service. A minor who is permitted to use AiBiBi must do so with the involvement of a parent or legal guardian. If you believe a child provided personal information contrary to these requirements, contact us so we can investigate and take appropriate action.

11. Your choices and regional privacy rights

Depending on your location, you may have rights to request access, correction, deletion, restriction, portability, or objection; withdraw consent; or appeal our response. You may also complain to your local privacy or data-protection authority. These rights can be subject to legal exceptions and identity verification.

• Stop screen sharing or microphone access through AiBiBi or operating-system controls.
• Delete recent connections using the in-app control where available, or clear app data/uninstall to remove local information, subject to backups.
• Adjust analytics or privacy controls offered in the app or device settings.
• Manage store subscriptions at Apple subscriptions or Google Play subscriptions.
• Request help or exercise a privacy right by emailing support@videoshowapps.com. Describe your request, country, platform, and enough transaction or support context for us to locate relevant records. Do not email passwords or full payment-card details.

Because core use does not require an AiBiBi account on the audited Android implementation and some identifiers are device-derived, we may not be able to link every record to you without additional verifiable context. We will explain if we cannot identify data or must retain it by law. Removing local data does not automatically delete server-side support, security, or transaction records; contact us for those requests.

12. Changes to this Policy

We may update this Policy to reflect changes in AiBiBi, law, or our service providers. We will publish the revised Policy and update the date above. If a change materially affects your privacy rights, we will provide additional notice or seek consent where required.

13. Contact us