ASL Support — Source library
Public documentation snapshot: 2026-09-08
Reach a real person without an account.
A no-login support form that becomes a real, tracked ticket a person actually answers.
Reach a real person without an account.
Built for: Anyone using an Auto Secure Login product who needs help and does not want to hunt for an email address · Someone locked out of a product, who cannot reach help that sits behind a login · A solo practitioner, shop owner, or small team who needs one dependable place to write when something breaks · Someone evaluating Auto Secure Login who wants to see what happens after the sale, not just before it
ASL Support exists because of this.
Something goes wrong and you go looking for help. The contact link opens a form that tells you nothing about where it lands. You type out the whole story, press send, and get a thank-you page. Then silence. A week later you still do not know whether a human ever read it. There is no reference, no reply, and nothing to follow up on. So you send it again, and now you are the person who emails twice. Or the help sits behind a login, and the reason you need help is that you cannot log in. You hunt around the website, find a generic address, and send your problem into an inbox that may or may not be watched by anyone. Meanwhile the thing you were trying to do this morning is still broken, and you have no idea whether to wait or start over somewhere else. There is a quieter worry underneath it. You have just typed your situation into a box on someone else's website. Where did that text go? Is it sitting in a log file, forwarded around in an email chain, or pasted into a chat room? Nobody tells you, and the form that asked for it rarely says. There is a second version of this problem if you are the one deciding whether to trust a company. Before you put your practice, your shop, or your records into someone else's software, you want to know what happens on the bad day. A support page that is a lone email address is an answer to that question, and not a reassuring one. You want to see that a request goes somewhere real, that it gets a number, and that a person is on the other end.
ASL Support exists because of this.
A submission becomes a tracked ticket with a status, an audit history, and its own reference in the platform's own queue, not a message in a mailbox nobody watches.
ASL Support exists because of this.
No account is required to reach a person, which is the only sensible design when the problem is that you cannot sign in.
ASL Support exists because of this.
Ticket subjects and bodies are encrypted at rest, and bodies stay out of logs, out of alert email, and out of web addresses.
ASL Support exists because of this.
One support address covers every Auto Secure Login product and responsible-disclosure reports, and you choose the routing yourself before you write.
ASL Support exists because of this.
The Android app asks for a single device permission and carries no trackers or advertising identifiers.
ASL Support exists because of this.
Intake fails loudly: a request that cannot be filed never gets a thank-you page.
ASL Support exists because of this.
What is not built yet is published as not built yet, including the self-service bilingual answer service that is still only a plan.
How ASL Support works, start to finish.
ASL Support is the public front door for every Auto Secure Login product. You open one page, choose the product you need help with, describe what is going on, and send. There is no account, no password, and no invitation to wait for. The email address you type is the address we reply to, so nothing depends on you having signed in anywhere. What makes it worth using is what happens after you press send. Your message does not land in a mailbox. It becomes a tracked support ticket in the same queue the rest of the platform runs on, with a status, an audit history, and its own reference. A real person reviews it and replies by email, and every email that ticket generates carries the reference in its subject line, so you can always point at the exact request. In the Android app the reference also appears on screen the moment the request is filed. On the website the confirmation is a plain acknowledgement, and the reference reaches you with the reply. Your words are handled with care on the way through. The ticket's subject and body are stored encrypted by the ticket service that holds them. The body is never written into a log file, never placed in a web address, and never copied into the alert that tells the team a request arrived. That alert carries the subject and the ticket reference only, and whoever answers reads the content inside the queue itself. Before you send, the form asks you not to include passwords, payment card numbers, or other credentials, because support never needs them and nobody legitimate will ask you for them. Because the front door is public and open to anyone, it is built to stay standing. Every field has a stated limit that both the website and the app enforce: 160 characters for your name, 200 for the subject, and 4,000 for the message itself, which is enough room to describe a real problem properly. Requests from a single network are capped at five a minute. And if the request cannot be filed for any reason, you are told on the spot and asked to try again shortly. It never shows a thank-you for a message that did not make it, because a form that quietly loses requests is worse than no form at all. There is also an Android app that gives you the same channel from your phone, and it is the more considerate of the two. It is a genuine app with its own screens rather than a web page in a shell. Each field counts down as you type, the five-a-minute limit is printed on the form instead of hidden, and a tick-box asks you to confirm you checked your message for secrets before it will send. It asks your device for one thing, internet access, and nothing else. It carries no trackers and no advertising identifier, keeps no draft once you close it, and can only talk to the real support service over an encrypted connection. A built-in Help and privacy screen walks through exactly how a request is handled and links straight to the privacy policy, the master terms, and the security and responsible-disclosure page. The app is finished and signed; it is not listed on Google Play yet.
Everything in the current release.
Each of these is built and working today. Nothing on this list is a roadmap item.
No login between you and a human
You do not need an Auto Secure Login account to ask for help. That matters most in the exact situation where help is needed: you cannot get in. Open the page, write what happened, send it. The email address you type is the only identity involved.
Say which product first
A picker lists fourteen Auto Secure Login products by name, plus a general option for when you are not sure which one is misbehaving and an Other option for anything else. Choosing it routes your request from the start instead of letting it bounce between people. The website and the Android app offer the same sixteen choices.
It becomes a real ticket, not an inbox item
Every submission is filed as a tracked support ticket in the same queue the rest of the platform uses. It carries a status, a priority, a reference, and an audit history from the moment it is created. There is no parallel mailbox that nobody tends.
A reference you can quote
Every ticket gets its own reference, and every email it generates carries that reference in the subject line, so a reply or a follow-up always points at the exact request. In the Android app the reference is shown on screen as soon as the request is filed; on the website it reaches you with the reply rather than on the confirmation.
A person reads it and replies by email
Every request is reviewed by a human, not sorted by an automatic responder. The reply goes to the address you typed. If your issue touches an account or billing, including the account email gets you matched faster.
Encrypted, and kept out of the plumbing
The ticket's subject and body are stored encrypted by the ticket service that holds them. The body is not written into logs, not placed in a web address, and not copied into notification email. The alert that reaches the team carries the subject and the ticket reference only, and the content is read inside the queue.
It tells you what not to send
The website form asks you, before you submit, not to include passwords, payment card numbers, or other sensitive credentials. The Android app goes further: it names private keys, recovery codes, authenticator codes and card details specifically, and will not send until you tick a box confirming you checked your message. Support never needs a secret to help you.
Limits that are stated, not discovered
Every field has a published size and both surfaces enforce it: 160 characters for your name, 200 for your email, 200 for the subject, 4,000 for the message. In the Android app each field counts down as you write, so you know where you stand before you send rather than after a rejection.
Abuse limits keep the door open
A public form with no account gate is exactly what someone would hammer, so requests from a single network are capped at five a minute. The Android app prints that cap on the form and says so plainly if you reach it. Wait a minute and send again.
It fails out loud
If your request cannot be filed, the page and the app say so on the spot and ask you to try again shortly. There is never a thank-you screen for a message that did not make it through. You always know whether your request actually landed.
The same channel from your phone
ASL Support for Android does one job well: send a support request from your phone. Same fields, same limits, same routing choices, and the ticket reference shown on success. It is a real app with native screens, not a website wrapped in an icon.
The app keeps nothing
It asks for one device permission, internet access, and no others. No trackers, no analytics, no advertising identifier, no contacts, no location, no files. Close it with a half-written request and that text is gone; nothing is left sitting on the phone.
The app cannot be misdirected
It talks to one fixed, encrypted address and will not fall back to an unprotected connection. Release testing confirmed it contains no service key or credential, so there is nothing useful to lift out of it. It has no staff view either: it is a customer app, and there is no internal queue hiding inside it.
Short path to the fine print
The privacy policy, the master terms, and the security and responsible-disclosure page are one click from the site and one tap from the app's Help and privacy screen. Account, privacy, and deletion requests are covered in the privacy policy, so you are never left guessing where to send them.
Where security reports go
The Auto Secure Login security page asks researchers to report through this same form, with "Security report" in the subject line and the affected page, steps, and impact in the message. One address covers ordinary help and responsible disclosure alike.
Numbers we can stand behind.
Every figure below comes from the product's own release record or test suite, not from a marketing estimate.
Surfaces and status.
Status as of 2026-09-02. support.autosecurelogin.com returned a normal, working request page when fetched directly on 2026-09-02; the page's own last-modified date is 2026-08-16. records the service live from 2026-08-01 and wired into the platform's ticket queue the same day. records the public site and the intake both confirmed responding on 2026-08-23, with the deployed service matching the source apart from line endings. The Android app is a separate surface and is not Live: a signed 1.0.0 release exists and passed acceptance on an emulator and a physical Pixel 8 on 2026-08-23, but records a Play lookup returning no result for the package, with no upload, track, or submission created.
Worth more together.
Products on this platform share one sign-in, one support queue, and one engineering standard. These pair naturally with ASL Support.
ASL Tickets
The ticket system this page files into. If you want the same kind of front door for your own users, with encrypted, tracked, referenced tickets instead of a shared inbox, that is the piece that provides it.
ASL Files
For when a support conversation needs a document and email is not a safe way to send one. It is encrypted-at-rest file storage with secure shares the recipient can open without an account.
ASL Meet
Some problems are faster to show than to type. Meet is the platform's own small-group meeting service for when a written thread stops being the quickest way through.
Recent progress.
This product ships often. The most recent verified changes, newest first.
Recent progress.
2026-08-23 as version 1.0.0, with release acceptance run on both an emulator and a physical Pixel 8 and every listed gate passing, including one real request filed end to end. Its store listing copy, data-safety worksheet, reviewer instructions, release notes, icon, banner, and eight screenshots were prepared at the same time. It has not been listed on Google Play, and one offline-behaviour run was recorded as still outstanding. The public support page itself was last updated on.
Recent progress.
2026-08-16 into the current Auto Secure Login look, stating the encrypted-ticket promise and linking to the privacy policy and the security and responsible-disclosure page. The live service was confirmed still responding during the.
Recent progress.
2026-08-23 release check, and again on.
Recent progress.
2026-09-02 . The Android release is the most recent change to the repository, dated.
Recent progress.
Pricing for ASL Support 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 to open a support request?
Nothing. There is no charge, no account, and no payment step anywhere in the flow. You give a name, an email we can reply to, the product, a subject, and a description of the problem.
We already have a help desk. Why would we use this?
Keep the desk you like. This exists so that anyone using an Auto Secure Login product always has one public address that reaches a human, including people who have no login with you and none with us. It sits alongside an internal desk rather than replacing it.
Is there anything to install, import, or set up?
No. Open the page, or the Android app, and send. Nothing on your side changes and nothing needs migrating. That is the whole point of a front door.
Who can read what I write, and where does it go?
The support team handling your ticket. The ticket's subject and body are stored encrypted, and the body is not copied into logs, into notification email, or into web addresses. The alert that tells us a request arrived carries the subject and the ticket reference, and the content is read inside the queue itself.
Do I get a confirmation email, and how do I quote my request later?
There is no automatic acknowledgement email. The website confirms on screen, and the Android app also shows the ticket reference there. The reference travels in the subject line of every email the ticket generates, so once a person replies you have it in writing and can quote it.
What happens if we stop paying for a product? Can we still get help?
Yes. The request form is not a paid add-on and is not tied to a subscription. If you are winding something down you can still write in about final billing, getting your data out, or having it deleted, and the privacy policy sets out those options.
Is this actually finished, or a placeholder page?
It has been live and taking real requests since 2026-08-01. Every submission is filed as a tracked ticket with a reference and answered by a person. The one part still unbuilt, the self-service bilingual answer service, is labelled as a plan rather than dressed up as working.
How fast will someone reply?
We do not publish a response-time promise. What we do commit to is that a real person reviews every request, that the reply goes to the address you provided, and that a request which fails to file tells you on the spot instead of disappearing.
Where do I report a security problem?
Here. The Auto Secure Login security page asks that reports come through this form with "Security report" in the subject line, and that you include the affected page or project, clear steps, and the likely impact. Please do not access data that is not yours or publish an unresolved issue before we have had a reasonable chance to look at it.
Should I include my password so you can check my account?
No. Never send passwords, payment card numbers, private keys, recovery codes, or authenticator codes. The form warns you and the Android app will not send until you confirm you checked your message. Anyone who asks you for those in the name of support is not us.
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?
Replies come by email. There is no phone line and no live chat today.
What should I know before I rely on it?
We do not publish a guaranteed response time, and we would rather say so than invent one.
What should I know before I rely on it?
Sending a request does not trigger an automatic acknowledgement email. The website confirms on screen, and the first email you receive is the reply.
What should I know before I rely on it?
On the website the confirmation does not display the ticket reference. The reference travels with the emails the ticket generates; the Android app shows it on screen.
What should I know before I rely on it?
The live character counters and the on-screen rate-limit notice are Android-app features. The website enforces the same limits but does not count down as you type, and its message on a rejected request is generic.
What should I know before I rely on it?
The website's pre-send warning is the short version. The full list of things never to send, and the confirmation tick-box, are in the Android app.
What should I know before I rely on it?
The product picker names fourteen products; not every Auto Secure Login product has its own entry yet, so some requests have to go in under General or Other.
What should I know before I rely on it?
The request form is in English today, and there is no Spanish version of it. A bilingual self-service answer experience is planned, not built.
What should I know before I rely on it?
You cannot attach a screenshot or a document to a request yet. If we need a file, we will tell you how to send it safely.
What should I know before I rely on it?
There is no customer login for browsing past tickets. You get a reference and an email thread.
Reach a real person without an account.
Prefer email? contact@autosecurelogin.com