Auto Secure LoginProve what happened on every recovery.
One defensible record for every vehicle recovery, from assignment through release, billing, and audit.
Built for: Owners of repossession and vehicle-recovery companies running the whole operation out of texts, spreadsheets, and a whiteboard · Dispatchers who need to know which driver has which case right now, and who is allowed to touch it · Field agents who want the assignment, the address, the instructions, and the photo upload in one place on a phone · Lot managers tracking spaces, keys, personal property, holds, releases, and transports
In one sentence
One defensible record for every vehicle recovery, from assignment through release, billing, and audit.
Compliance is the spine of the product, not a report you run at quarter end. Stop orders, breach-of-peace aborts, notice logs, retention, and legal holds are wired into the workflow at the moment the decision is actually made.
The problem
Repo Runner exists because of this.
You are running recovery work across tools that do not talk to each other. The assignment arrives by email or a lender portal. The driver gets it by text. The photos live on his phone until he remembers to send them. The condition notes are on paper in the truck. The keys are in a lockbox somebody wrote on a whiteboard. The invoice sits in accounting software that has never heard of the case. When a lender calls asking where the vehicle is and who signed for it, you are on three phones stitching the answer together, and the answer arrives an hour later than it should. The part that keeps you up at night is not the disorganization. It is the letter. Wrongful repossession. Breach of the peace. Personal property missing from the trunk. No notice, or the wrong notice. When that letter lands, you have to prove what your driver saw, what time he arrived and left, what the client told you and when, that you stopped the moment you were told to stop, and that nobody went back afterward and tidied up the file. A spreadsheet cannot prove any of that. Neither can a text thread that anyone can delete. And the obligations are not optional. Notice and right to cure. Servicemember protections. Law-enforcement notification. How you inventory and return personal property. How long you are allowed to keep location data on your own employees, and who inside your company is permitted to read their messages. Every one of those carries a real penalty, and most of them change from state to state. Software built for this business tends to either ignore the compliance side entirely or bury it three menus deep, and either way the risk stays parked on you.
What changes
- Compliance is the spine of the product, not a report you run at quarter end. Stop orders, breach-of-peace aborts, notice logs, retention, and legal holds are wired into the workflow at the moment the decision is actually made.
- The audit trail refuses edits by construction rather than by permission setting, and each entry is sealed to the one before it, so tampering shows up as a break instead of a gap nobody would ever notice.
- Role separation goes all the way down to a law-enforcement viewer who sees case status and nothing else, with no location and no messages. Most systems in this category stop at admin and non-admin.
- Employee location is treated as a duty workflow, not surveillance. There is no background location permission, points are rejected off-shift, and a case-linked point is refused unless the case is genuinely assigned to that person.
- The state-law reference desk ships marked as awaiting your counsel's approval, with a named-reviewer and effective-date workflow around every entry. It will not pretend to be legal advice, and it will not show proposed legislation as current law.
- The whole interface is bilingual English and Spanish, and that was verified by clicking through a real browser rather than by reading the code — which is how two genuine defects were caught that a code review had missed.
- The product documents its own open gaps in writing rather than hiding them, including the ten expansion gates it insists on before it will claim readiness for many companies at once. You find out what is unfinished from us, not from a demo that quietly fails in front of you.
What it does
How Repo Runner works, start to finish.
Repo Runner is one operating record for a recovery case, from the moment a lender assigns it to the day the vehicle is released and the invoice is settled. Everything hangs off the case: vehicle and account details, addresses, special instructions, who was assigned and when, every status change with the reason attached, photographs and client documents, the lot space and where the keys went, the personal-property inventory, the law-enforcement notice, the internal messages, the time entries, and the invoice. Sixteen work areas sit in one console with a single search across all of them, so nobody has to remember which system a fact lives in. The case moves through a lifecycle the software actually enforces. Fifteen defined states carry a file from new assignment through accepted, dispatched, in field, located, recovered, in transit, at lot, release pending, released or transported, and closed, with hold, cancelled, and breach-of-peace abort as control states alongside. You cannot jump a case forward to make the paperwork look tidier, and you cannot quietly reopen a closed one. Putting a case on hold, cancelling it, or aborting for breach of peace all require a written reason before the system will accept it, and bringing a case back to field work after a breach-of-peace abort requires a manager to approve it explicitly. A client stop order locks the case out of field activity, full stop. Nine role types see nine different versions of the same case. A field agent sees only the cases assigned to him. A dispatcher sees the board. A lot manager sees custody. An auditor can read everything and change nothing. Your lender and forwarder clients get their own login and see only the cases, invoices, and documents mapped to their account, with no view of your roster, your fleet, your lot, or any other client. A read-only law-enforcement account sees status and nothing more, with no location data and no messages. Those boundaries are enforced everywhere, including on live updates, so an unrelated colleague inside your own company does not even get a notification about a case they cannot open. Underneath all of it is a record built to survive being questioned. Photographs and documents are encrypted when stored, each one carries an integrity fingerprint, and that fingerprint is checked again before the file is handed back to you. Every material action lands in an audit trail that is sealed entry to entry, so an altered or removed record shows up as a break rather than disappearing quietly, and the system refuses edits and deletions of audit entries by construction rather than by policy setting. Eligible location points, messages, evidence, and encrypted backups age out on a thirty-day schedule, while unresolved cases, accounting records, and audit records are deliberately held back from routine cleanup. When something is likely to be disputed, an owner, manager, or auditor places a legal hold on the case or on one individual item. Holds never expire on their own: the system emails a reminder thirty days, seven days, and one day before the ninety-day review and again on the day, and a person has to look at it and either renew or explicitly release it. Every export is recorded with its size, its fingerprint, who asked for it, and when. The work itself happens where the work is. The web app installs to a phone or a desktop straight from the browser, runs in its own window, shows a readable offline screen with a retry control when the signal drops, and prompts you when an update is ready — that installed web app is what your field staff use today, and a separate mobile client is built and signed but is not yet in anyone's hands, which the honest limits below spell out. On-duty location is a deliberate workflow: an agent clocks in, the app asks for location only in the foreground and only after he takes an action, a case-linked point is rejected unless that case is genuinely assigned to him, and submissions stop the moment he clocks out. There is no background location permission and no hidden collection. The web app switches between English and Spanish from one toggle across every view. Routes and ordered stops can only be built from cases the assigned operator is actually allowed to work. Timekeeping, fleet maintenance work orders, a training library your management and counsel approve before drivers rely on it, a seventeen-article help center written for the people doing the work, and a state-law reference desk round out the day. Invoicing runs through QuickBooks Online or a hosted card and bank payment page, and raw card and account numbers never enter Repo Runner in either path. And if you want your lender's system to file assignments directly, there is a published contract covering sixty-two endpoints and seventy-six operations, with scoped keys you issue one per vendor and revoke in one click.
Features
Everything in the current release.
Each of these is built and working today. Nothing on this list is a roadmap item.
The case is the record
Vehicle, account reference, debtor details, addresses, instructions, priority, assignment, every status change, photographs, documents, lot space, keys, personal property, messages, time entries, and the invoice all attach to one case file. Sixteen work areas share one search box. Nobody has to remember which system a fact lives in, because there is only one.
A lifecycle the software enforces
Fifteen defined states carry a case from new assignment through recovery, transport, lot custody, release, and closure. The system will not let a case skip a step to make the file look neater, and a closed or cancelled case does not quietly reopen. Every move to hold, cancel, or abort requires a written reason before it is accepted.
Stop orders that actually stop the case
When a client pulls the assignment, the stop order locks the case out of field activity instead of leaving a note somebody might miss. A breach-of-peace abort does the same and goes further: the agent cannot resume on his own. A manager has to approve the return to field work and record why, and both the abort and the approval stay in the file permanently.
Nine roles, nine different views of the same case
Owner, manager, dispatcher, field agent, lot manager, mechanic, auditor, client, and read-only law enforcement each see a different slice. A field agent sees only his assigned cases. An auditor reads everything and changes nothing. The boundaries hold on live updates too, so an unrelated colleague never even gets pinged about a case they cannot open.
A login you can hand your lenders
Client users see only the cases, invoices, and documents mapped to their own account, and only the management contacts you approve for them to message. They cannot list your staff, your fleet, your lot inventory, or any other client's work. It takes the routine status call off your desk without opening the rest of your business up.
Routes tied to the assignment
Build an ordered run of stops from cases that are actually active and field-eligible, and assign the route only to the operator who holds every case on it. A case under a stop order, hold, cancellation, or abort cannot be routed at all. Agents mark stops arrived, completed, or skipped, and the route advances itself as they work.
On-duty location, on purpose
An agent clocks in, and the app asks for location in the foreground only after he takes an action. A point tied to a case is rejected unless that case is assigned to him, and submissions stop at clock-out. There is no background location permission and no hidden collection. Dispatch and management see a live duty map of the latest authorized position; nobody else does.
Evidence with a chain of custody
Recovery photographs, condition shots, and client documents are encrypted when stored and carry an integrity fingerprint that is verified again before the file is handed back. Sensitive responses are deliberately kept out of the offline cache on installed devices. Someone from another case, or another company, cannot pull a file they were never entitled to see. Single files are accepted up to 12 MiB.
Lot custody, keys, and personal property
Check a recovered vehicle in against a lot and a space, record where the keys went, log condition notes and intake photographs, and set the personal-property status and any hold. The connected case flips to at-lot in the same operation. Releases and transports capture the authorization and leave a custody history you can walk backward when someone disputes it.
A law-enforcement notice log, not a police shortcut
Record the agency, the type, how and when you notified them, who you spoke with, the confirmation reference, and the acknowledgement. It exists so you can show the notice was made where a state requires it. It is deliberately not a police lookup, not a dispatch channel, and not any suggestion that law enforcement should carry out a civil recovery.
Retention and legal holds with reminders that chase you
Eligible location points, messages, evidence, and encrypted backups age out on a thirty-day schedule, while unresolved cases, accounting records, and audit records are held back from routine cleanup. Put a legal hold on a case or a single item and it never releases itself. Reminders go out thirty days, seven days, and one day before the ninety-day review, and again on the day.
An audit trail nobody can quietly edit
Every material action is written to a trail where each entry is sealed to the one before it, so a changed or removed record shows up as a break in the chain rather than vanishing. Edits and deletions of audit entries are refused at the storage layer, not merely discouraged by a rule. Management searches are logged without copying the search phrase itself into the record.
Exports you can put in front of a lawyer
Any signed-in user can export their own account data, assignments, location points, messages, file details, and time entries. Owners, managers, and auditors can export a held item directly: evidence comes out in its original format after its integrity is re-verified, and a case export carries its vehicle, addresses, events, file list, messages, and location points. Each export records its size, fingerprint, requester, and timestamp.
Invoicing without touching card numbers
Create the invoice against the client, then let QuickBooks Online send its hosted invoice with card and bank options, or use the hosted card payment page directly. Raw card and bank-account numbers never enter Repo Runner in either path. Payment state flows back so the case and the invoice agree, and the accounting record stays put even if you later disconnect. Both paths need your provider credentials switched on first.
Bilingual for the people actually doing the work
One toggle switches the entire web interface between English and Spanish — dashboard, cases, team and clients, fleet, routes, lot, messages, chat, tickets, time clock, maintenance, billing, training, the state-law desk, help, and audit — backed by 708 translated entries. The legal-hold reminder email goes out with English and Spanish in the same message, because there is no stored language preference to guess from.
Updates that back themselves out
Every update records exactly which version is running, runs the full check-and-test gate before anything is installed, and takes a fresh encrypted backup that has to validate before the update is allowed to stand. The five previous versions stay on the machine, and a failed update restores the last working one on its own without anyone having to notice first.
Proof
Numbers we can stand behind.
Every figure below comes from the product's own release record or test suite, not from a marketing estimate.
Where it runs
Surfaces and status.
Status as of 2026-09-02. Re-verified live on 2026-09-02 at 12:17:55 UTC: https://repo.autosecurelogin.com/ returns the working sign-in portal (HTTP 200, 11,195 bytes) with all sixteen work areas present in the navigation, the liveness check reports version 0.4.1 running, and the readiness check reports both records storage and evidence storage available. Accounts are issued to approved companies rather than opened by public sign-up, which is why this is Early access rather than open availability. The label covers the web app and the API only. The mobile client is not included: its signed build sits on a closed distribution track that has no testers configured, so no one can install it today.
Works with
Worth more together.
Products on this platform share one sign-in, one support queue, and one engineering standard. These pair naturally with Repo Runner.
ASL Files
For sending a release authorization, a condition report, or a client document to someone outside your company with a password and an expiry date, instead of emailing it as an attachment and hoping.
Explore →ASL Messaging
The team chat already built into Repo Runner. If you run other software alongside it, the same chat follows your staff into those tools rather than becoming a second inbox nobody checks.
Explore →ASL Tickets
The support ticket queue already built into Repo Runner, for tracked requests inside your company and escalations to us, so a problem is not just a message somebody scrolled past.
Explore →What is new
Recent progress.
This product ships often. The most recent verified changes, newest first.
, English and Spanish coverage was finished across the entire web app rather than just the sign-in page: the dashboard, recovery cases, team and clients, fleet, routes and dispatch, lot inventory, messages, team chat, support tickets, time clock, maintenance, billing, training, the state-law desk, the help center, and audit and search all switch language from one toggle, backed by 708 translated entries, and the legal-hold reminder email now goes out in both languages in the same message. That work was checked by clicking through a real browser rather than reading the code, which caught two genuine defects a code review had missed, including one that broke the sign-in form in Spanish. On.
, the mobile client was rebuilt and its install evidence recorded with a published fingerprint for the exact build that was verified — an emulator install of a debug build, with the check on a physical handset still outstanding and the build not published to any distribution track. That rebuild is the most recent change in the codebase, dated.
. The live service was re-checked on.
at 12:17:55 UTC: it is responding on version 0.4.1, with records storage and evidence storage both reporting available.
Pricing
Pricing for Repo Runner 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.
Ask about pricingQuestions buyers ask
Straight answers.
What does it cost?
Pricing is not published. Repo Runner is set up per company rather than sold as a self-serve plan, so the conversation starts with how many field agents, dispatchers, and lot staff you have, how many lender logins you need, and whether you want the accounting connection turned on. Ask and you will get a number, not a form that disappears into a queue.
We already use a recovery network and a spreadsheet. Why change?
The network gives you assignments. It does not give you a defensible internal record of what your own people did with them. Repo Runner is the system of record on your side of that line: who was assigned, what time they arrived, what they photographed, when the stop order landed, where the keys went, and proof that none of it was edited afterward. You can keep taking assignments exactly the way you do now.
How hard is it to move our open cases in?
Open cases go in the way you would expect: one case per assignment, with the vehicle, account reference, addresses, client, and instructions. Closed history usually stays where it is, because re-keying old files buys you very little. If your lender or forwarder can push assignments over an API, they can file them directly and the case numbers stay identical on both sides, with duplicates rejected rather than silently doubled.
Will it tell me whether a repossession is legal?
No, and it would be dangerous if it did. The state-law desk is an operational reference with citations, plain-language summaries, effective dates, and named reviewers, and every entry ships marked as awaiting your counsel's approval until your attorney signs off. What the software does do is refuse to let a case move forward when a stop order, a breach-of-peace abort, or a hold is in place, and push the hard calls to a human instead of giving a driver a green light.
Where does our data live, and what happens if we stop paying?
Your records are yours. Every signed-in user can export their own data at any time, and owners, managers, and auditors can export cases, evidence, messages, and location records individually, with a file size and integrity fingerprint recorded on every export so you can prove the copy is intact. If you leave, you take a complete export with you. Nothing is held hostage behind a subscription.
Our drivers will call this a tracking app. What do I tell them?
Tell them it is not one, and that the design backs you up. Location is collected only in the foreground, only after the agent takes an action, only while he is clocked in, and only for a case actually assigned to him. There is no background location permission anywhere in the product, and submissions stop at clock-out. It also means you should put a written location and communications policy in front of them, and we will tell you the same thing.
Is it actually ready, or are we the first ones on it?
The web app and the API are deployed and running today. Every release has to pass thirty-five automated checks before it will install, takes a fresh encrypted backup that must validate as part of the update, and rolls itself back if anything fails. It is also in controlled release: accounts are issued to approved companies rather than opened to anyone with a card. Being early means direct access to us and real influence on what gets built next. It also means the honest limits on this page — the mobile app, the accounting connection, the payment paths, the legal content — are things to read before you sign, not after.
What happens if it goes down in the middle of a shift?
The installed app shows an offline screen with a retry control and reconnects rather than failing silently, and it deliberately does not cache case, evidence, location, message, or payment data on the device, so nothing sensitive is left sitting on a phone that went out of range. On our side, an encrypted backup runs daily and again on every update, the previous five versions stay ready to roll back to, and a failed update restores the last working version without waiting for someone to notice.
Do we need the phone app to use this in the field?
No, and today you should not wait for it. The web app installs to a phone straight from the browser, runs in its own window with its own icon, works offline with a recovery screen, and carries the full bilingual interface — that is the field surface we support and the one our own testing covers. The separate mobile client is signed but is not distributed to anyone yet, which is written into the limits on this page rather than left for you to discover.
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:
- Accounts are issued by us to approved companies. There is no public sign-up, and setting up a new company is done with you rather than by you — the in-product control for creating one has never had anything behind it, so we do it by hand.
- The state-law reference ships marked as awaiting counsel review, on purpose. Five reference entries come with it, covering the self-help possession rule, servicemember protection, notice and right to cure, and law-enforcement notice. Your attorney approves each one before your drivers rely on it, and five entries are a starting point, not a library.
- The training area ships as eight module outlines — a title, a category, and a one-line description each, covering breach of peace, stop orders, condition and personal property, location privacy, account security, law-enforcement notice, release authorization, and evidence handling. The teaching text itself is yours to write and your management and counsel to approve. We do not ship it pre-written.
- The QuickBooks Online accounting connection is built, documented, and covered by automated checks, but it has not yet been connected to a live QuickBooks company in production.
- Card and bank collection is wired at the payment boundary and needs your payment credentials switched on before a customer can pay that way. Neither payment path is carrying live traffic today.
- The mobile app is not in anyone's hands today. A signed build sits on a closed distribution track with no testers configured, Google Play has not reviewed it, and the client we rebuilt afterward has never been published to any track. Its install evidence is an emulator run, not a Play install on a physical handset. Use the installed web app on the phone in the meantime — that is the field surface we actually support.
- The web app is fully bilingual in English and Spanish, with two known cosmetic exceptions: a handful of dropdown labels whose visible text doubles as the value submitted to the server are still English, and the mobile client's own on-screen labels are English only.
- No pre-built connector to a recovery assignment network comes in the box. The API is open and documented, but connecting a network requires an agreement and credentials with that network first, and we will not claim a certification we do not have.
- Security review to date is our own, and we say so plainly. Independent penetration testing has not been performed, and we do not describe our internal review as an outside audit.
- Uploaded photographs and documents are encrypted and fingerprinted, but they are not scanned for malware. Treat files that arrive from outside your company accordingly until that scanning is in place.
Prove what happened on every recovery.
One defensible record for every vehicle recovery, from assignment through release, billing, and audit.
Prefer email? contact@autosecurelogin.com