Drupe Opt Out: Remove Your Number With the Official Form

To opt out of Drupe, open its official Remove My Info page and enter your name, email address and phone number with the correct country code. The form states a 24-hour removal expectation. Account deletion and sale or sharing preferences have separate routes in Drupe's privacy notice, so specify those too if they are part of your goal.

We checked Drupe's public form and privacy notice on October 19, 2026. We did not submit personal information or request a verification message. The form was visible; its completion outcome was not tested. The policy still carries a June 30, 2022 revision date, which is distinct from our current access check.

Pick the request that matches your concern

Drupe combines phone and contact features with caller identification. The visible name associated with your number may be your main concern even if you have never used its app. Removing a public association, deleting an account and changing sharing preferences are related privacy choices, but one is not evidence that all the others were completed.

The official privacy notice identifies the operator as Sync.Me Ltd. That does not make the two branded public workflows interchangeable.

Use this Drupe form for Drupe information; the SyncMe opt-out guide describes its own route. Ask support to clarify scope if you are affected in both places.

Complete the public removal form

Open Remove My Info

Go to the Drupe unsubscribe page directly. Check the domain and the Remove My Info heading before entering data. It is a data-removal page despite the word unsubscribe in its URL; do not confuse it with an email newsletter unsubscribe link.

The public interface marks Name, Email and Phone Number with asterisks. Use an email address you can access for any follow-up. Choose the correct country in the telephone selector before entering the number. Check the final international number so a default country selection does not point to somebody else's record.

Handle the conditional checkbox accurately

The page includes a checkbox for requests under Daniel's Law. It is a conditional designation, not a general removal requirement. Select it only when that is the basis of your request. Leaving it unchecked is appropriate when you are making an ordinary request without asserting that status.

The page also uses a CAPTCHA component. Complete the controls presented to you and then use the submit button. We stopped before submission, so this guide does not promise a particular confirmation screen, code-delivery method or email sequence after the first step. Follow the actual instructions shown for your request.

Save a useful record

Record the date and the number submitted, plus any acknowledgement or case reference. A screenshot of the blank form explains the entry point; your own confirmation is what documents your submission. Store it privately rather than sharing personal details in a public support comment.

• Confirm the domain, heading and correct request type.
• Enter the requested name, email and country-specific number.
• Complete applicable controls without claiming an unsupported status.
• Save the confirmation and follow any identity-verification instructions.

If the form fails, do not repeatedly submit slightly different identities. Note the failure and use privacy@getdrupe.com, which the policy lists for rights requests.

Explain the form issue and provide only the information needed to identify the request. Ask for a secure, proportionate verification method if more evidence is required.

Account deletion and sharing are separate

The policy describes account deactivation through user settings and account deletion by email. If you no longer want an account, state that explicitly to the privacy contact. Removing your app from the phone is not itself a confirmation that an account or its server-side information has been deleted.

Drupe also provides a separate Do Not Sell My Info page. A sale/sharing preference and a deletion request have different scopes. If you want both, ask for both and retain the respective confirmations. Do not assume a choice on one form silently sets every privacy preference elsewhere.

Before account closure, consider whether you need information stored in the app or need to change your default calling workflow. This is a practical continuity check, not a reason to postpone privacy action indefinitely. Ask support what account deletion changes and keep billing questions separate if you have a paid subscription.

The opt-out hub groups other provider-specific routes. It can help when the same name-number association appears in multiple services. Each request should identify the actual service displaying the data so that a response from one company is not mistaken for a result everywhere.

Timing, verification and a persistent result

The form's 24-hour statement is a provider claim, not our measured turnaround. The policy allows identity checks and retained information in certain circumstances. Record when you submitted, when any verification was completed and when the operator confirmed an action. Those timestamps help explain a delay more clearly than a single sent date.

If the public result persists, compare the exact number, country code and source. Ask whether the request concerns the current caller-ID listing, an account association or information the company retains for another purpose. An incorrect country selector or incomplete verification can require a different remedy from a stale display.

A local address-book name can also differ from a database result. Check the original affected surface where you can legitimately access it, and describe what you see without claiming that all other users see the same thing. If another person's device is needed to verify a problem, obtain their permission and avoid exposing unrelated contacts.

The phone-number removal checklist can help organize these separate observations. Keep a record of the source, date and response rather than judging every removal by whether the phone rings less often. Call volume is affected by many things outside a public listing.

Reappearance and the limits of one request

Drupe's notice discusses information supplied by other users or available from other sources, alongside its opt-out route. It also describes retained public activity after account deletion. These statements make it important to request the outcome you want and ask what suppression applies if the same information is encountered again.

A later match is a reason to investigate, not proof of a particular cause. Save the new result and compare it with the earlier one.

If it is on Drupe, reference the existing request. If it is in a different app, use that app's route. Do not assume a related company name means a single email covers all products.

For wider broker exposure, a free data broker scan can reveal additional records to review. Specific managed coverage of Drupe is not established here. The direct form remains a useful manual route even if you use a service for other brokers.

The data-removal and call-blocking comparison explains why database cleanup and device-level filtering solve different problems. Choose the measure that matches your goal: a corrected or hidden record for privacy, and separate calling controls for incoming interruptions.

A number visible in ContactsPlus needs its own request. The ContactsPlus caller-ID guide covers its published email route and the distinction between caller-ID removal and wider privacy rights.

Frequently asked questions

Must I assert Daniel's Law to submit the form?

No general requirement of that kind is shown. The checkbox labels a specific basis for a request. Use it only when applicable and keep an ordinary removal request truthful.

Is the 24-hour statement a verified removal result?

No. It is the wording on the current public form. We did not submit a number or measure processing, and a verification or retention issue can require further handling.

Can a non-user use the public form?

The removal page is publicly accessible and does not require an account login at the entry step we inspected. That observation does not remove the need to follow any ownership or identity checks presented after submission.

Does one request cover SyncMe too?

This guide does not establish that. Drupe names Sync.Me Ltd. in its policy, but use each product's published route or obtain explicit confirmation of cross-product scope from the operator.