Your screen, your control.

Screen and camera

The agent chooses and authorizes a window, screen or tab in the browser's source chooser. mdobe suggests windows by default; the browser confirms available options. The agent's camera is optional and requires authorization.

The client views the presentation. Their camera and microphone remain off, and they cannot control the agent's computer. Audio stays on the existing call. Pause hides the shared screen and camera; switching windows keeps the same link.

Invitation links

Each session supports one agent and one connected client for up to 90 minutes. Clients do not need to install an app or create an account to watch.

The link contains a private access key. Share it only with your client: anyone with the complete link can attempt to join. When a delivery service is connected, you can enter a client's phone number or email and send directly from the studio. The selected provider receives the recipient, message and complete URL, including its private key, to deliver the invitation. SMS and WhatsApp use Twilio; email uses Resend, under those providers' terms. Copy link remains available without these services.

Ending the session closes access. Closing or reloading the studio ends the presentation and requires a new link. The client view shows a logo and waiting status until the presentation begins. The agent's name, agency and follow-up link are not shown there; the profile name may identify invitations sent by the agent.

One-time SMS invitations

The mdobe SMS invitation program is being prepared for provider review. The agent must obtain permission for one invitation during the current call and explicitly confirm it before sending. There is no client signature or account requirement. Shared SMS remains disabled until its account model and campaign are approved.

Separate agent-attestation records contain the account, session identifier, destination hash, confirmation time, script version and provider reference. These records expire after 730 days and expired records are removed during later invitation processing. They do not contain the plain-text phone number or private link and are not audio recordings. They are separate from short-lived dispatch records.

Read the SMS Privacy Policy, SMS Terms of Service and verbal consent process. The existing messaging brand is littlenuvy; the product is now mdobe.

Client status and agent notifications

The studio reports when a client joins with a valid link, when their browser confirms video playback, and whether the page is visible or in the background. Brief status signals are sent while the session is open. A connection alone is not treated as proof of playback.

These states describe the browser; they do not measure attention or prove that a person read the content. Changes may take a few seconds. An unexpected disconnection is confirmed after missing connection signals, usually in about 25 seconds. Viewing status data is deleted when the room closes or expires.

To prevent duplicate invitations, the service stores an attempt reference, its status, and hashes of the destination and message. Records older than 24 hours are removed when new invitations are processed. These records do not store the phone number, email or complete link in plain text. Providers retain their own records under their policies. Accepted by the service does not confirm delivery or reading.

Send Keypad: private numeric requests

The agent can send a numeric keypad to request a number for the conversation. The field accepts one to thirty digits and preserves leading zeros. You can close the request without submitting. The value is sent only when you choose Send; typing or deleting digits does not transmit them to the agent. The app checks length and format, not the number's authenticity.

The response travels through an encrypted WebRTC data channel between the browsers, separately from HTTP signaling. The app does not add the response to its database, history, logs or local storage. The client's field is cleared on submission, cancellation or hiding the page. The studio holds the response temporarily in memory: it is masked by default, can be revealed for ten seconds and is cleared after 60 seconds, on manual deletion or on disconnection. Expiration is also checked when returning to the page.

Keypad responses cannot be requested during recording or pause. Recording cannot begin while a request or an uncleared response is present. These controls do not prevent external screenshots or device recordings. Share the value only when you recognize the agent and understand the request's purpose.

Functional checks are not an independent security audit. The service remains in its pilot phase.

Recording with consent

Recording is optional and requires client consent. It includes the shared screen and the agent's camera when enabled, without audio. It is prepared in the browser, with a limit of 20 minutes or 100 MB per file. Download it before closing the page.

This version does not store recordings in the cloud. The agent is responsible for downloaded files and their subsequent use. The client's camera and microphone remain off.

My profile, history and support

When you choose Google or ChatGPT sign-in, that provider verifies your identity. Google sign-in requests your account identifier, email and basic profile. Options become available once configured; the sign-in page shows which methods are enabled.

Independent sign-in, when enabled, uses Supabase to manage email, password and account sessions. Email code sign-in sends a one-time verification code and link to the address you provide. Only a successfully verified email can create a signed-in session. Supabase handles code expiry and one-time use; mdobe also limits requests and verification attempts. New accounts complete their profile before subscription setup. We do not store sign-in codes in account history, notes or local browser storage. Passwords are not stored in presentation history or shown to the agent. Authentication cookies are secure and cannot be read by page JavaScript. ChatGPT sign-in remains available during the pilot transition.

The agent's account stores their name, agency, follow-up link, preferences and history. Profile photos are stored privately and can be changed or removed under Home → My profile.

History records the session's internal name, start and end times, and whether a guest joined. Usage minutes estimate session duration; they do not prove that the client watched the entire presentation or measure attention.

Live help messages are stored so support staff can reply. Support availability is shown. Live help is not a chatbot, and an immediate reply is not guaranteed.

Private notes and meetings

Notes and meeting titles, dates, durations, and time zones are saved in the signed-in agent’s account. They are not included in the client or supervisor video connection. They remain stored until the agent deletes the item or requests account-data deletion through Support. Each account can hold up to 200 notes and 200 meetings.

Do not store medical records, government ID numbers, passwords, or other sensitive identifiers in notes or meeting titles. Notes are account-protected application data, not an end-to-end encrypted medical-record vault. Anything visibly opened inside a captured full screen or window can still appear in the presentation, including private notes.

Calendar export creates a downloadable .ics event with the meeting title and time. It does not include private notes, recipient addresses, or a client access key. It does not automatically send invitations or synchronize a calendar. Your calendar provider processes any file you choose to import.

Setter mode and supervisor access

The presenter can invite one supervisor using a separate private link bound to that supervisor’s account email. The client must explicitly allow the supervisor before the view starts. The supervisor must sign in with the invited account. The client can decline or remove permission, and the presenter can revoke the invitation.

The supervisor receives the same shared screen and enabled agent camera through a separate WebRTC connection. They cannot control the presenter’s device, operate presentation controls, or receive the private keypad data channel. They can still see anything visible within the captured source. Removing permission closes access after the connection status updates; ending the presentation invalidates the links. Access checks do not prevent an authorized participant from making an external screenshot or recording.

The invitation email, hashed access keys, consent state, and temporary supervisor connection status are stored for the active presentation and removed when the room is cleaned up. A new client must give their own permission; an earlier client’s choice is not reused.

Linked account devices

Existing linked devices may retain account access through a secure cookie for up to 7 days. Keep only devices you recognize and revoke their access from Home → Linked devices. New iPad pairing is not promoted in this version.

Clients can open a viewing link on an iPad. Presenting still requires a compatible desktop browser. mdobe does not provide an extended iPad monitor or a native iPad presenter app.

Pilot connections and operation

Hosting serves the app and coordinates session access. WebRTC uses STUN servers to discover network addresses needed for a connection; those servers may receive the browser's IP address, but not presentation content through that function. Some networks require an additional relay server. Check the client's connection before presenting.

The agent signs in using an available account method. Clients join through their private link and do not need a ChatGPT account. Existing linked account devices can be reviewed and revoked from the account.

Individual trial and subscription

The individual plan is $12.99 USD per agent per month, with a 7-day trial available once per account. Each agent has a separate account.

Starting the trial requires a payment method through Stripe's secure registration. The first 7 days are free; afterward, the subscription renews automatically at $12.99 USD per agent each month until canceled. Cancel from My account before the trial ends to avoid the first charge. The price and first charge date appear before confirmation. Existing pilot accounts that received access without a card retain their expiration date and are not charged automatically because of this change.

Help and product information

The Help Center searches reviewed product answers. It is not a generative AI assistant and does not send your notes, screen, or questions to an AI model. Support messages are stored for the support team as described above.

Questions about your information or a deletion request can be submitted through Support in your signed-in account. This pilot has not been independently certified as HIPAA compliant and does not replace your organization’s privacy or record-handling requirements.