L.S. Mobile Apps Opt Out: Phone Form and Deletion
Request L.S. Mobile Apps deletion or a sale opt-out with its phone-based form. Check country codes, non-user requests, verification and Lusha limits.

To opt out of L.S. Mobile Apps, open its current Data Subject Request form at lsmapps.com/opt-out.
Enter your name, reply email and the relevant phone number with its international country code, identify whether you use the app, then select your territory and available privacy right.
The US configuration includes separate deletion and sale opt-out choices. Non-users can also submit through the form.
The current page offers dpo@lsmapps.com as a contact and downloadable-form alternative.
Its older California notice uses privacy@lsmapps.com, so follow the current intake instructions when sending a completed form.
We checked these public pages on November 17, 2026 without entering personal identifiers, submitting a request or measuring removal results.
What the L.S. Mobile Apps request covers

| Situation | Relevant action | Important boundary |
|---|---|---|
| Your number appears in caller-ID or contact data | Use the Data Subject Request form | Identify the phone number with country code |
| You do not use the app | Choose No for app-user status | Another user may have supplied contact information |
| You want stored data deleted | Select the available deletion right | Retention exceptions may apply |
| You want sale restricted | Select the available sale opt-out right | Not the same as closing an app account |
| The form is inaccessible | Follow the current DPO email/download route | Do not send unsolicited identity documents |
The current opt-out page is an interactive request form, not merely a policy description. It accepts a user/non-user choice and displays rights after a territory is selected. The country-code requirement is explicit: the page says it cannot process a phone-related request without it.
The California notice describes L.S. Mobile Apps Holdings Ltd., caller-ID users and contacts who may never have used the app.
It also describes an affiliate relationship with Lusha. That relationship does not make this form interchangeable with Lusha’s professional-contact request process.
Complete the form step by step
1. Prepare the matching phone number
Use the number involved in the caller-ID or contact record. Include the international dialing code and check for transcription errors. A local number without its country context can match poorly or be rejected, which is why the form asks for international format.
Provide the name associated with the personal data and an email address where you can receive a response. The page distinguishes the reply address from the telephone number the request concerns. Do not assume an unrelated email alone will identify a phone-based record.
2. Choose user status, territory and right
The required app-user question offers Yes and No. Select the accurate status; creating an app account is not stated as a prerequisite for the non-user form. Territory options shown during inspection were EU, US and Other. Choose your real location, because the next menu depends on that selection.
After selecting US, we observed access/know, deletion, portability, non-discrimination, rectification, sensitive-information limitation and sale opt-out choices. That was an interface check with no consumer identifiers. Other selections may produce different choices, and a displayed option does not establish that every request must be granted.
3. Explain the request and retain a copy
- Select the right that matches your desired outcome.
- Use the optional details field to clarify the particular record or mismatch.
- If you want deletion and sale restriction, state both and ask whether separate submissions are needed.
- Read the accuracy and authority confirmation before submitting yourself.
- Complete the normal security check and save any acknowledgement.
Do not bypass the security challenge or fill unrelated hidden fields. If the form fails, preserve the error message without publishing your identifiers. Contact the DPO through the address on the current intake and ask for a suitable alternative. The identity-verification guide explains how to evaluate requests for more information.
Verification, agents and realistic timing
The form says the company may contact you to verify identity before processing. It also asks you to affirm that the information is accurate and that you are the requester or authorized to act. Having someone’s number in an address book is not sufficient authority to request action on their behalf.
The California notice describes additional agent requirements: signed permission or power of attorney, direct identity verification and confirmation that the consumer authorized the request. Follow the applicable instructions if you are representing someone. Do not attach broad personal records simply because the form offers an optional text field.
The current form promises a response within the timeframe required by applicable law rather than a single universal number of days.
Its older California notice displays historical request statistics from 2023. Those figures are not current service targets and are not a prediction for a request submitted today.
Ask for the response window that applies to your territory and action. Record submission, verification and the final decision separately. We inspected the form but did not send it, so there is no verified confirmation-email sequence or observed completion time in this guide.
Caller-ID suppression, account deletion and Lusha
The California notice describes names and phone numbers supplied by app users, as well as professional enrichment and other information sources. That explains how a non-user might be involved. Deleting an app from your own phone does not establish that contacts supplied by other people were deleted from the service.
Account deletion is also a separate scope question. If you have an app account and want both the account and contact data handled, describe both. Ask what remains for security, accounting or other permitted purposes, and whether any suppression identifier is retained to honor your request.
The existing Lusha opt-out guide covers professional-contact suppression in Lusha’s B2B database. Use it when a separate Lusha record is involved. We keep the caller-ID phone workflow here because the live intake, required matching data and user/non-user distinction differ; we do not claim either request automatically completes the other.
For another caller-ID service, the Drupe removal guide provides its own route. A similar app category does not mean shared control of every record. The manual broker-removal workflow helps track those requests by provider and identifier.
Check the result and avoid false completion claims
Read the final response carefully: did the company delete information, restrict sales, correct a label or only acknowledge receipt? Ask for the affected phone number or record scope to be confirmed without unnecessarily repeating sensitive details. Keep any exception or inability-to-match explanation alongside the request.
If the original caller-ID display is lawfully accessible to you, check the same number after the provider’s stated period. A local contact label, cached result or another app may still show information independently. Identify the actual source before assuming that the completed request failed.
Changing a phone number, different formatting or a new contact upload may complicate matching. No reappearance frequency was established in this inspection. If the record returns, keep dated evidence and ask whether the original request covers the identifier now displayed.
A free exposure scan can identify other supported sources, but it is not a certification about this app’s internal records. Use the opt-out guide hub for another company’s process when the evidence points to a separate source.
Frequently asked questions
Can I request removal if I never installed the app?
Yes, the current form includes a No option for app-user status. The notice also discusses contact information about non-users. Supply the matching details requested rather than creating an unnecessary account.
Which email address should I use?
The live request page lists dpo@lsmapps.com for questions and the completed downloadable form. The older California notice lists privacy@lsmapps.com.
Follow the current intake and retain a copy of its instructions.
Is my local phone-number format enough?
The form explicitly requires a country code and international format. Use the number the request concerns and check the code carefully; do not substitute an unrelated number to pass validation.
Does a Lusha opt-out cover this app automatically?
That is not established by the inspected sources. The companies’ notices describe an affiliate relationship, but the caller-ID form and the B2B contact-removal workflow have different matching and scope requirements.
Can I rely on the old average response figures?
No. Historical statistics in the California notice describe earlier requests. The current form refers to applicable legal timeframes; ask for the window and status of your own request.
Continue reading
Related privacy guides
Real Intent Opt Out: Email Form and Suppression
Use Real Intent’s official opt-out form to request profile suppression. Check email retention, verification, timing and the separate SMS controls.
Read articleTrue Blue Analytics Opt Out: Form and Privacy Rights
Use True Blue Analytics’ privacy form or toll-free route. Check residence-based choices, identity checks, agent requests and political-data limits.
Read articleVistar Media Opt Out: Device ID, Form and Deletion
Use Vistar Media’s privacy form to opt out or request deletion. Check required device identifiers, verification, response terms and email alternatives.
Read article