Datasys Opt Out: Privacy Portal and Email Request Steps

To opt out of Datasys, open its Privacy Rights Center from Your Privacy Choices and select Opt-Out. Choose Delete My Data separately if you also want deletion. The public portal displays request and submitter-role choices, but our browser inspection did not reliably reach the final details screen. If the portal will not advance, the policy provides privacy@datasys.com as an alternative, with your state and the nature of the request.

This Datasys opt out guide is based on the official policy, privacy choices page and portal checked November 6, 2026. We did not submit a request, provide personal information or test a completed removal. The steps below distinguish observed controls, the published fallback and verification that may occur later.

Choose the Datasys privacy action

The official Your Privacy Choices page links to the Datasys Privacy Rights Center. The portal currently resolves to a request page on the privacy.datasys.com subdomain. Follow the link from the main site if an old bookmark stops working.

The company named in the privacy policy is Datasys Group, Inc. Keep that identity with your request log so it is not confused with unrelated businesses using a similar name. The opt-out guide hub lists separate workflows for other companies.

How to start the manual request

1. Select the actual action you want

The initial portal displays Opt-Out, Delete My Data and Access / Know My Data. Its descriptions distinguish stopping sale or sharing, requesting deletion and obtaining a copy of information. Choose the action that matches your goal rather than assuming that an access request also stops future use.

If you want both deletion and a restriction on future sale or sharing, explain both in your request or ask how Datasys wants the actions submitted. The initial screen presents distinct choices. It does not establish that selecting one automatically selects the others.

2. Identify the submitter accurately

During inspection, a later screen displayed Myself, Authorized Agent and Parent / Legal Guardian. Those roles affect who is requesting the action and what proof may be needed. An agent should have actual permission, and a guardian should follow the instructions that apply to the child and requested right.

The portal did not advance consistently in our browser checks. Some transitions changed the displayed step count, and a later Next control remained disabled. We therefore do not describe unobserved final fields or claim that a request can always be completed in four predictable screens.

If you encounter a similar problem, reopen the route from the official privacy choices page or try a current browser with the required site scripts available. Do not enter personal information into an unofficial copy of the form, and do not mistake a disabled button for a completed submission.

3. Use the documented email alternative when needed

The policy says that if you are unable to use the portal, you may email privacy@datasys.com. It specifies a subject in the format “[Your State] Privacy Request” and asks for your state of residence and the nature of the request. Replace the state label with your actual state rather than leaving it as template text.

For example, say you want Datasys to stop selling or sharing your personal information for targeted advertising, and separately say whether you request deletion. Ask which matching details or verification are necessary and how to provide them securely. Do not send an identity document before you understand why it is needed.

The policy also lists +1 954-949-9500 and toll-free 833-797-3282, plus a postal privacy administrator address in Boca Raton. Use the current policy to verify those details before calling or mailing. The email alternative is useful when you need to describe a portal issue and preserve a written request.

• Record the official route and requested action.
• State your location and role accurately.
• Keep a copy of your email or submission acknowledgement.
• Monitor replies for matching or verification questions.
• Ask for confirmation of each requested action.
• Retain any refusal and appeal instructions.

Matching, verification and response timing

Datasys says access, deletion and correction requests may require identity verification. Its privacy choices page says it asks for information needed to match the request to records it holds. An agent may need proof of authority, and Datasys may still need to verify the consumer directly.

The identity-verification guide explains how to assess that follow-up. Confirm the destination and purpose before sending sensitive information. A request for a matching detail is different from permission to collect an unlimited personal history.

The policy describes providing enough information to verify the requester and enough detail to understand the request. It also says making a verifiable consumer request does not require creating an account. Do not purchase a Datasys product or create a business account merely because a privacy form has a technical problem.

In its consumer-request section, Datasys says it endeavors to respond within 45 days and will explain an extension of up to 90 days in writing. The current privacy choices page more generally says timing depends on the request and jurisdiction. Treat those as published terms, not a tested completion time or one deadline for every action.

If a response says no record was found, ask what identifiers and scope were checked. If it says a request cannot be fulfilled, retain the reason and instructions for any available appeal. Avoid sending repeated, unexplained requests while the company is waiting for a specific verification response.

The policy includes state-specific appeal language, so use the deadline and route that apply to your actual situation. This guide does not determine your legal eligibility or replace advice about a particular dispute.

Opt-out, deletion and cookie settings are separate

Datasys's privacy choices page says an opt-out stops selling or sharing personal data with third parties for targeted advertising. It says this does not affect processing necessary to provide core services. Deletion is described separately and includes applicable exceptions and verified instructions to relevant service providers.

Those descriptions do not establish erasure from every independent client or source. If another organization collected the information directly from you, it may have a separate record and a separate reason for retaining it. Ask which entities and records the Datasys response actually covers.

The company also provides website cookie preferences and describes honoring Global Privacy Control as applicable to the transmitting browser or device. These controls can change browser-related choices without proving that an offline audience record or historical identifier has been deleted.

The data-broker overview explains why internal audience information can differ from a public people-search listing. A company can process marketing information even when there is no public profile page to search and remove.

For another marketing-data controller, the Allant opt-out guide illustrates a separate intake and verification process. It is related reading, not a claim that Allant and Datasys share your particular record or honor each other's requests.

Check the response and keep the scope clear

When you receive a response, identify whether it confirms an opt-out, deletion, a completed access request or only receipt of your message. Ask for clarification when a response addresses one action but leaves another unanswered.

Keep a private record of the matching identifiers used, especially if you later change address or email. A new identifier may require clarification about the scope of the earlier instruction. Repeated marketing from another company is not enough to show that Datasys failed to process the original request.

A free exposure scan can help identify supported public listings for a parallel cleanup. It cannot certify the contents of Datasys's internal systems. Use both forms of evidence for their actual purpose.

If you are comparing a service's progress report with your own requests, read how to interpret removal reports. Sending a request is an action; verified suppression or deletion is a result. That distinction prevents an unreliable portal from being mistaken for completed privacy work.

Frequently asked questions

Is a Datasys account required?

The policy says a verifiable consumer request does not require an account. Start from the public privacy route. If it fails, use the published alternative rather than signing up for an unrelated business product.

Can I ask for deletion and an opt-out together?

You can clearly state both goals, but the visible portal presents separate request choices. Ask Datasys whether it wants separate submissions and request confirmation of each action instead of assuming one selection covers everything.

What information should I email if the portal fails?

The documented fallback asks for your state and the nature of the request, with a state-specific privacy-request subject. Ask what additional matching information is needed. The guide does not prescribe unobserved final form fields.

Does rejecting website cookies delete the database record?

The privacy choices page separates cookie settings from opt-out and deletion requests. A cookie preference alone does not establish that Datasys identified and erased all information associated with you elsewhere.

What proves the request is finished?

A response should identify the action taken and its scope. An email sent, a selected radio button or a displayed Next button is not proof of completion. We inspected public routes only and did not test a personal removal outcome.