ASL Meet — Source library
Public documentation snapshot: 2026-09-08
Your call stays between the people on it
Private video for up to four people. Guests join with a link. Nothing about the call is kept.
Your call stays between the people on it
Built for: A solo therapist or counselor who needs a private session room a client can open from a text message · A lawyer, accountant or advisor holding a confidential one-on-one with a client who will not install anything · A two- or three-person team that wants a quick face-to-face without adding another account for everyone · Anyone who needs to talk to one specific person and does not want that conversation sitting in a company's storage
ASL Meet exists because of this.
You need to talk to one person, or maybe two. A client. A patient. Your co-founder. Someone's attorney. The conversation is the entire point of the call, and it is nobody else's business. That is a simple thing to want and a surprisingly hard thing to actually get. What you get instead is friction on one side and exposure on the other. The person you are trying to reach has to make an account before they can say hello, or install something, or hunt for the small link that lets them join without doing either. Half of every first call is spent on that. Meanwhile the call itself is being carried by a company you have no relationship with, under terms you skimmed once. There is a recording toggle in there somewhere, and if you are honest, you are not certain who can flip it, where the resulting file lands, or how long it lives. The real problem is that you cannot check any of it. "We do not retain your calls" is a sentence in a policy document. Sentences get revised. If your conversation is being carried and held by someone else's equipment, then a policy change, a legal request, or a bad night for their security team is the only thing standing between that conversation and someone else. You are not asking for a promise. You are asking for a setup where there is nothing to hand over in the first place.
ASL Meet exists because of this.
The claim that nothing is kept is structural, not a policy sentence — the stored data model has no place to hold call content, so there is nothing to change your mind about later.
ASL Meet exists because of this.
Guests join with a link and a name. No account, no install, no organization membership. Most alternatives make the person you are trying to reach do the work.
ASL Meet exists because of this.
The four-person ceiling is stated up front on the landing page, on the join screen and in the terms — and it is the reason the privacy promise holds, rather than a limitation being hidden.
ASL Meet exists because of this.
Recording produces a file on your machine and shows everyone a notice when it starts and stops. There is no silent recording mode and no host-only capture — and we say plainly that a screenshot is the one action that does not announce itself.
ASL Meet exists because of this.
The full working interface is English and Spanish, with an automatic check that stops a new English string from shipping without its Spanish translation.
ASL Meet exists because of this.
Every change, including the defects found and what was and was not confirmed fixed, is written down and dated in the project's own record — including a real bug found on physical phone hardware that is recorded as still awaiting a confirming device run.
ASL Meet exists because of this.
Meeting links carry a randomly generated code rather than a guessable or sequential one, so nobody finds a room by trying codes.
How ASL Meet works, start to finish.
ASL Meet is a small, deliberately narrow video meeting tool. You sign in once and start a meeting. You get back a short link with a random code in it. You send that link to the person you want to talk to — text it, paste it in an email, read it out loud. They open it, type a display name, allow their camera and microphone, and they are in the call. They do not create an account. They do not install anything. A meeting holds up to four people in total, including you. While the call is running, the audio and video go straight between the devices in the call whenever the network allows it, encrypted the whole way. When a firewall or a restrictive network blocks that direct path, the encrypted stream is handed along by a relay that cannot open it, cannot read it, and does not keep it. Either way, nothing on our side ever holds your audio, video, screen share, chat messages, screenshots or recordings. There is no place in the system where those things could be stored. What is kept is a short administrative record of the meeting: the meeting code, an optional title, who hosted it, when it was created and ended, whether it was locked, whether a waiting room was switched on, any email address you sent an invite to, and a small list of host actions such as who was admitted, turned away or removed. That whole record is deleted thirty days after the meeting ends. Inside the call you get the controls you expect and a couple you might not. Mute and camera toggles. An audio-only mode that genuinely releases the camera rather than just freezing the picture, which matters when someone is on a weak connection. Screen sharing. Live text chat that is passed straight between the people in the room and is never written down anywhere. A recording button and a screenshot button — both produce a file that saves directly to your own machine, never to us. When anyone starts recording, everyone else in the room sees a notice naming them, and sees another when they stop. A screenshot is the one thing that does not announce itself, which is why the join screen asks everyone to record or screenshot only with the room's permission before they enter. As the host you control the door. You can turn on a waiting room, so guests are held outside until you look at the name and let them in or turn them away — and someone waiting is not using up one of the four places or hearing anything. You can lock the room once everyone has arrived, which stops any further guest joins even from someone holding the link. You can remove a participant. You can end the meeting for everyone at once. If you set a start time when you create the meeting, you can send a single email invite that carries the join link and a calendar attachment, so the appointment lands in the other person's calendar rather than in the pile of things they will forget. It runs in the browser on desktop and on Android phones, and it installs to a home screen or desktop like a normal app with its own icon and its own window. The entire working interface — the landing page, the join screen, the in-call toolbar, the status and error messages — is carried in English and Spanish, with a language selector that remembers your choice. Hosting a meeting uses a single Auto Secure Login sign-in that works across the other Auto Secure Login products, so a practice already using them does not add another password. ASL Therapy can also open a session room on a signed-in clinician's behalf through a protected connection that carries no client detail at all — the room comes back with a generic title and nothing else attached.
Everything in the current release.
Each of these is built and working today. Nothing on this list is a roadmap item.
Guests join with a link and a name
The person you are calling does not create an account, does not install anything, and does not need to be part of your organization. They open the link, type a display name, allow camera and microphone, and they are in. This is the single biggest reason first calls stop being a ten-minute support exercise. Hosting a meeting does require an account; joining one never does.
Nothing about the call is kept on our side
There is no storage anywhere in ASL Meet for call audio, video, screen shares, chat messages, screenshots or recordings. This is not a retention setting that could be changed later — the stored data model has nowhere to put those things. What exists afterward is a short administrative record of the meeting itself, and that is deleted after thirty days.
Recording saves to your own device
If you record a call or grab a screenshot, the file is produced on your own machine and saved there. It is never uploaded and we never receive a copy. That also means the file's safety is entirely yours to manage, and so is the legal responsibility for having made it.
Recording announces itself — screenshots do not
The moment anyone in the room starts a recording, a notice naming that person appears for every other participant, and another appears when they stop. There is no quiet recording mode and no host-only override. We are equally plain about the exception: a screenshot is taken entirely on that person's own device and does not announce itself, which is exactly why the join screen asks everyone to record or take screenshots only with the room's permission before they enter.
Waiting room with admit or deny
Turn on a waiting room and guests are held outside the call until you decide. You see the name each person entered and can let them in or turn them away one at a time. Someone waiting is not using up one of the four places and cannot see or hear anything until you admit them. If you refresh or reconnect, the list of people still waiting comes back with you rather than vanishing.
Lock the room once everyone is in
One click stops any further guest joins, even from someone holding a valid link. This is the practical answer to the fact that a link can be forwarded: once your two or three people have arrived, close the door behind them. You can unlock again if someone drops off and needs to come back.
Remove a participant, or end it for everyone
You can drop a specific person out of the call, or end the meeting for all participants at once. The remove control only becomes available once that person's video is actually on your screen, so you are never removing a name you have not seen. Both actions are written to the meeting's short administrative record.
Waiting-room decisions are recorded against the name you saw
When you admit or turn away someone waiting outside the call, what gets written into the meeting record is the display name that was actually in front of you when you decided — not only an internal reference. It is a small thing, and it is the difference between a record you can read back later and one that only proves a button was clicked.
Audio-only mode that actually saves bandwidth
This is separate from the ordinary camera toggle. Turning off your camera the usual way stops the picture but keeps the video stream running. Audio-only genuinely releases the camera and stops sending any video at all, which is the difference between a call that limps and a call that works on a bad connection or a metered phone plan. Switching back restores your camera without dropping anyone. Audio-only and screen sharing are one at a time — the app asks you to stop one before starting the other.
Screen sharing and in-call chat
Share your screen to walk someone through a document or a form. Type in the side chat when speaking out loud is awkward or the audio is struggling. Chat messages are passed straight between the people in the room and are never written to storage — when the call ends, they are gone.
Email invites with a calendar attachment
Give a meeting a start time and you can send one email invite straight from your meeting list. It carries the join link and, for scheduled meetings, a calendar file so the appointment lands in the recipient's calendar. Meetings without a start time send the plain join link. The start time is informational — the room is joinable the moment it exists, so nobody is ever locked out by a clock.
English and Spanish throughout
Not a translated brochure page — the working interface. Buttons, form labels, the in-call toolbar, error and status messages are all carried in both languages, with a language selector on the landing page and inside the room that remembers what you picked. The two dictionaries are checked against each other automatically before a release can go out, so a new English string cannot ship without its Spanish counterpart.
Meeting records expire on a schedule
Thirty days after a meeting ends, its code, title, timestamps, lock state, invite address and host-action trail are deleted. A meeting that was never formally ended expires thirty days after it was created. Rooms that are still live, including ones with someone still waiting to be admitted, are excluded from the sweep so an active call is never cleaned up out from under you.
Installs like an app, and works on a phone
Add it to a home screen or desktop and it opens with its own icon and its own window instead of a browser tab. The layout has been worked over on real phone hardware — the control bar, chat and participant list stay reachable rather than sliding off the bottom of a mobile screen, primary controls are at least 44 pixels across, and every form field has a label.
One sign-in, shared with the rest of the platform
Hosting uses the same Auto Secure Login account you use for the other Auto Secure Login products, so a practice already on the platform does not add a password or a second user list. ASL Therapy can also open a session room for a signed-in clinician through a protected connection that passes across no client name, diagnosis, appointment reason, note or payment detail — the room comes back with a generic title and no detail attached.
Numbers we can stand behind.
Every figure below comes from the product's own release record or test suite, not from a marketing estimate.
Numbers we can stand behind.
The tool is deliberately small. It does one thing — a private call between a few people — instead of becoming a meetings platform with a chat product and a whiteboard bolted on.
Surfaces and status.
Status as of 2026-09-02. Checked 2026-09-02: https://meet.autosecurelogin.com/ returns HTTP 200 with the full landing page (join-by-code form, four-person room notice, host sign-in), the service health check comes back healthy, and central sign-in and email invites both report as active. The last recorded production release is dated 2026-08-02 in the project's own change record, which also documents post-deploy verification of sign-in, meeting connection setup, relay connectivity and the health endpoint. The ASL Therapy room handoff has been live since 2026-07-30 with its own recorded acceptance. The Android app is separate and not generally available: it sits on a closed, invite-only track last recorded as in review.
Worth more together.
Products on this platform share one sign-in, one support queue, and one engineering standard. These pair naturally with ASL Meet.
ASL Therapy
A therapy practice can open a session room straight from the client portal. The handoff is built to carry no client name, diagnosis, appointment reason, note or payment detail — the room comes back with a generic title and nothing else attached.
ASL Intake
Run intake and practice records in one place, then take the conversation itself into a private room — without the conversation ever becoming another record to manage.
ASL Messaging
Keep day-to-day team chat in one place and use Meet when a thread needs to become a face-to-face call. Both work off the same platform sign-in.
ASL Municipal Utilities
Staff and residents can move a phone conversation into a short private call without either side setting up an account first.
Recent progress.
This product ships often. The most recent verified changes, newest first.
Recent progress.
2026-08-22 the Android client was rebuilt as a native launcher — it hands meeting links to the phone's own browser and never embeds the meeting page — and its tested build was recorded with a verified checksum; acceptance for that build was run on an emulator, with a physical-device rerun still pending, and the earlier client was kept only as a dated reference. Before that, on.
Recent progress.
2026-08-05 , a real navigation-bar layout defect found on a physical Pixel 8 — reproduced three times out of three, not a fluke — was traced to how the earlier phone build handled the edge-to-edge screen area on newer Android versions, and a fix was written in source; the record states plainly that the fix compiles but has not been confirmed on the same physical hardware, and that no new store release should be cut from it until it is. Android 1.0.0 went to a closed, invite-only early-access track on.
Recent progress.
2026-08-02 , along with the full store listing, an 18-and-over audience restriction, and a completed data-safety declaration stating no third-party sharing and no retained call content; that submission was last recorded as in review rather than approved. The browser service itself has been stable on its.
Recent progress.
2026-08-02 release: checked again on.
Recent progress.
2026-09-02 , the site loads, the health check is healthy, and sign-in and email invites are both active.
Recent progress.
Pricing for ASL Meet is quoted after a short conversation about your situation, because the right scope differs from one team to the next. There is no charge for that conversation.
What does it cost?
Pricing is not published. ASL Meet runs as part of the Auto Secure Login platform, and terms for an individual, a practice or an organization are arranged directly — write to contact@autosecurelogin.com and say roughly how many people would host meetings. Guests never pay and never need an account, so you are only ever talking about the people on your side who start meetings.
We already use a video tool that works. Why would we change?
For most calls you probably would not, and that is a fair answer. The case for ASL Meet is the specific call you would rather not have carried and held by someone else — a therapy session, a legal conversation, an HR discussion, a call with a source. Keep what you have for the all-hands and use ASL Meet for the conversations where "we do not retain this" needs to be a fact about the system rather than a line in a policy.
How hard is it to move over? What do we have to migrate?
Effectively nothing, because there is nothing to migrate. ASL Meet does not hold a contact list, a message history, a recording library or a room directory to move across. You sign in, start a meeting, and send someone a link. If your practice already uses other Auto Secure Login products, hosting works on the account you already have. The realistic transition cost is telling people the link now comes from a different place.
Do the people I am calling have to sign up or install something?
No. That is the point. A guest opens the link, types a display name, allows their camera and microphone, and is in the call. No account, no download, no organization membership, no waiting for an invitation to be provisioned. Only the person hosting the meeting needs an account.
Only four people? That seems small.
It is small, on purpose, and we would rather say so than bury it. Keeping the call between the participants' own devices is what makes the privacy claim true. Supporting bigger rooms would mean putting everyone's audio and video through equipment we run — a different product with a different promise. Four covers a one-on-one, a session with a partner or interpreter present, and a small working call. If you need a company all-hands, this is the wrong tool and we will tell you so.
How safe is our data really? What do you actually have?
For any given meeting we hold the meeting code, an optional title, who hosted it, when it was created and ended, whether it was locked, whether a waiting room was on, any address you emailed an invite to, and a short list of host actions such as who was admitted, turned away or removed. We do not hold the audio, the video, the screen share, the chat, the screenshots or any recording — there is no storage for those anywhere in the product. The administrative record we do hold is deleted thirty days after the meeting ends, and routine backup copies of it expire within the following fourteen days.
What happens if we stop paying, or just stop using it?
Your meetings stop working and your meeting records age out on the normal thirty-day schedule. There is no archive of calls to be held hostage, because there was never an archive — nothing was recorded on our side to begin with. Any recordings you made are already files on your own machines and are unaffected. You can also ask us to delete your ASL Meet access and data at any time by writing to contact@autosecurelogin.com from your account address; active data is removed as soon as reasonably practicable and no later than thirty days.
Is this actually ready, or are we the ones finding the problems?
The browser version is live and in daily use, and it has been through real-device acceptance testing rather than only automated checks — including a session on a physical Pixel 8 where the app's own test caught a genuine layout defect. That one is a fair example of how we report things: the cause was traced and a fix written, and the record still says plainly that the fix has not been confirmed on the same hardware. Twenty-six automated checks have to pass before any release goes out, and every change, including the failures, is written down and dated. The honest caveats are the ones listed openly: four people per room, Apple-device behavior not yet confirmed on real hardware, and an Android app that is not generally available.
Can I use it for a therapy session or another confidential appointment?
It was built with that in mind. The sensitive part of such an appointment is the conversation itself, and that never reaches us at all. The handoff from ASL Therapy is deliberately built to pass no client name, diagnosis, appointment reason, note or payment detail — the room comes back with a generic title. It is live today and was accepted end to end against a stand-in client portal; a representative real-user, two-device media run is still outstanding. For work under a regulatory obligation, put a written agreement in place and confirm the fit with your own compliance advisor, exactly as you would with any vendor. And keep identifying detail out of meeting titles and links.
What if someone records me without asking?
For a recording, you will see it. When any participant starts a recording, everyone else in the room gets a notice naming them, and another when they stop — there is no silent recording mode and no host override. A screenshot is the exception, and we would rather tell you than let you assume otherwise: it is taken entirely on that person's own device and does not announce itself. The join screen reminds everyone to record or screenshot only with the room's permission before they enter. Either way the resulting file lands on that person's own device, so the responsibility for consent, and for what happens to the file afterward, sits with them.
What should I know before I rely on it?
We would rather you hear this from us than discover it later. As of 2026-09-02:
What should I know before I rely on it?
Four people per room, host included. Going bigger would mean routing everyone's audio and video through equipment we run, which is exactly the thing this product avoids — so larger rooms are not offered rather than quietly added.
What should I know before I rely on it?
When a network blocks a direct connection between two participants, the encrypted stream is passed along by a relay. It cannot open, read or keep the call, but the path is no longer strictly device to device in that case.
What should I know before I rely on it?
The call is encrypted in transit between participants. We deliberately do not market this as end-to-end encryption, and the app store listing does not claim it either.
What should I know before I rely on it?
A recording announces itself to the room. A screenshot does not — it happens entirely on that person's own device. The join screen asks everyone to get permission first, but that is a request, not an enforcement.
What should I know before I rely on it?
Audio-only mode and screen sharing are one at a time. The app will ask you to stop one before you start the other.
What should I know before I rely on it?
If you send an email invite, the address you sent it to is kept in that meeting's administrative record and is deleted with the rest of it after thirty days.
What should I know before I rely on it?
The Android app is not generally available. It sits on a closed, invite-only early-access track, last recorded as in review, and it is a launcher that opens meeting links in the phone's own browser rather than carrying the call itself. The browser version is what everyone uses today, and it works on Android phones.
What should I know before I rely on it?
The verified device baseline is Chrome on Android plus desktop browsers. Current Safari on a real iPhone, iPad or Mac has not been through a full acceptance pass, so Apple-device camera and microphone behavior is not yet confirmed.
What should I know before I rely on it?
The ASL Therapy room handoff is live and was accepted end to end against a stand-in client portal. A representative real-user, two-device media and relay acceptance run is still outstanding and should be completed before use under a regulatory obligation.
What should I know before I rely on it?
The Privacy Notice and Terms pages are English only while a Spanish translation goes through legal review, and both supplement the platform's master policies rather than replacing them. Outside counsel review is recommended before a broad commercial rollout.
Your call stays between the people on it
Prefer email? contact@autosecurelogin.com