Effective July 29, 2026

ASL MEET Privacy Notice

This notice supplements the Auto Secure Login Privacy Policy. The master policy governs Auto Secure Login generally; this notice explains how ASL MEET handles meeting information.

Information ASL MEET processes

• Host account information: the account identifier, email address, and display name supplied through Auto Secure Login, plus the signed-in session needed to manage meetings.
• Meeting metadata: a generated meeting code, optional title, host identifier, source application when applicable, four-person capacity, lock state, creation and end timestamps, and a limited audit trail of host actions.
• Live-only information: participant display names, room membership, chat messages, and WebRTC signaling messages are relayed in memory during the call and are not saved to the ASL MEET database.
• Operational information: limited request, security, and error information may be processed to operate the service, prevent abuse, investigate incidents, and comply with law.

Call content and recordings

ASL MEET does not record or store call audio, video, screen shares, chat, screenshots, or recordings on its application server. WebRTC encrypts media in transit and connects participants directly when possible. A TURN service may relay encrypted media when a direct connection is unavailable, but it does not decrypt or store that content.

If a participant starts a recording or takes a screenshot, the resulting file is created and saved on that participant’s own device. That participant controls the file and is responsible for obtaining any permission required by law or policy.

ASL Therapy handoff

An approved ASL Therapy server may request a meeting for an authenticated host through a protected service-to-service connection. ASL MEET receives the host's opaque Auto Secure Login account identifier and records that ASL Therapy created the room. The room title is always the generic "Therapy telehealth session." The handoff does not accept or store a client name, diagnosis, appointment reason, note, payment detail, or other clinical content.

Retention

Meeting metadata and its audit events are automatically removed 30 days after the meeting ends. If a meeting is never formally ended, its metadata is removed 30 days after creation. Live-only information disappears when connections close, the room empties, or the service restarts.

Daily operational database backups are normally kept for 14 days and may temporarily contain metadata that has since been removed from the active database. Account and security information may be retained longer when reasonably needed to provide the service, protect users, resolve disputes, or meet legal obligations, consistent with the master Privacy Policy.

Account and data deletion

To request deletion of your ASL MEET access and associated app data, email contact@autosecurelogin.com from the address connected to your account with the subject “ASL MEET account deletion.” We will verify the request before deleting data. You may request ASL MEET-only deletion or deletion of your full Auto Secure Login account; full account deletion also removes access to other Auto Secure Login services that use that identity.

You may instead request access, correction, or deletion of specific ASL MEET information without deleting your account. After a verified deletion request, associated ASL MEET meeting metadata is removed from the active service as soon as reasonably practicable and no later than 30 days, unless a legal or security exception applies. Residual copies in daily operational backups normally expire within the following 14 days. Limited security, fraud-prevention, dispute, or legal-compliance records may be retained only as reasonably necessary under the master Privacy Policy.

Choices and contact

Send privacy, deletion, or support requests to contact@autosecurelogin.com.

ASL MEET is not directed to children under 13. Do not use the service for unlawful surveillance, harassment, or recording without required permission.