Tie / Revenue Roll Opt Out: Privacy Form and Verification
Request a Tie or Revenue Roll opt out through its privacy form or email. Check required declarations, verification, timing and cookie-control limits.

To opt out of Tie, formerly Revenue Roll, use the privacy-request form linked from meettie.com or email info@meettie.com with the action and personal information concerned. Tie's current policy identifies the company as Revenue Roll Inc DBA Tie.
The form requires a name, email, requester role, legal basis and declarations, including email validation. Cookie preferences and Global Privacy Control address separate advertising choices; they do not by themselves confirm deletion of every stored record.
What information and choices does Tie cover?

Tie describes shopper-intelligence and marketing services. Its official privacy policy covers information supplied directly, collected automatically and obtained from other sources.
The relevant record may concern website use, contact details, an account or marketing-related information. Describe the actual context instead of assuming that a public people-search listing exists.
Revenue Roll and Tie are identified as the same company in the current notice. This guide therefore uses one request workflow for that controller. A name change alone is not a reason to send duplicate requests or create two separate removal campaigns.
| Your goal | Published route | What the result would need to confirm |
|---|---|---|
| Delete applicable personal information | Linked data-subject request form or info@meettie.com | Data addressed, exceptions and retained information |
| Opt out of sale or targeted advertising | Policy-described choices and an explicit request where needed | Which identifiers, uses and contexts are covered |
| Change browser preferences | Cookie Preference Settings and recognized GPC signal | Browser choice, rather than universal database deletion |
| Correct or access information | Request form or policy contact | Matching record and verified requester |
| Stop marketing emails | Unsubscribe or contact the company | Communication preference, not all stored data |
The policy says rights vary by location and applicable law. This guide describes available channels and observed controls, not an individual legal determination. For a broader understanding of records across separate businesses, see how to remove yourself from data brokers.
How to submit a Tie privacy request
1. Follow the current policy's request link
Open the policy and follow “Your Privacy Choices” or the data-subject request link. The linked Termly request form identifies Revenue Roll Inc DBA Tie in its declarations. Check that organization name before entering personal information.
During our November 19, 2026 inspection, the form displayed usable fields and a submit button. No personal details were entered and no request was submitted. A functioning public form is evidence of an intake route; it is not evidence that a later request was approved or completed.
2. Enter only relevant identifying information
The observed form asks for your name and the email address used to access the website or application. It also displays a website field.
Use a genuine email address you control, since the form says the request must be validated by email. If the relevant record uses an older address, explain that relationship rather than silently replacing it.
Choose whether you are the person or parent/guardian, or an authorized agent. The form asks under which law the request is made.
Select a basis that actually applies to you; do not claim a different residence simply to unlock an option. If you cannot identify an appropriate selection, use the policy email to ask how to proceed.
3. Explain the action and scope
The details field has a displayed limit of 1,024 characters. Use that space for the action, the record or interaction involved, and any relevant matching information. For example, explain that you want applicable personal information deleted and sale or targeted-advertising uses stopped, and ask for confirmation of any retained information.
That example is a request outline rather than a legal template. You may want only a correction, an access response or an opt-out.
Avoid packing every possible request into the form if it would obscure the issue. A concise description of the known record is more useful than unsupported claims about hidden data.
4. Read the declarations before submitting
The form requires declarations about accuracy, the consequences of deletion or restriction, and email validation. It warns that deleting or restricting personal data may be irreversible and can terminate services with the company. Read those statements in the context of any account or service you use.
If an agent is submitting, the policy says proof of authority can be required, including written and signed permission. Additional identity verification may also be requested. Do not use the representative route to submit another person's information without the necessary authority.
- Keep a copy of your request wording and the date.
- Retain any acknowledgment and reference number.
- Complete the email-validation step if you choose the form route.
- Check that follow-up questions relate to your actual request.
- Ask for the final action and any retention exception in writing.
The policy separately lists info@meettie.com for exercising rights. If the form fails or its required choices do not fit, explain the problem there and ask for the appropriate process. We verified the published address but did not test email delivery.
Verification and timing: avoid two common misreadings
The Termly form says the website administrator or data-protection officer will be notified within 24 hours and will need an appropriate amount of time to respond. This describes notification to the organization. It is not a promise that your personal information will be deleted within a day.
Tie's policy says identity verification may compare request information with data it already holds. It may seek further information if existing details are insufficient.
Answer only through the verified request channel and ask why any additional information is needed. A request for identity matching should not be treated as permission to send unrelated sensitive documents.
The policy's Nevada section says it aims to respond to a verified request within 60 days, with up to 30 additional days when needed and notice of extension. That language belongs to the Nevada section. It should not be generalized into a universal deadline for every resident, every form choice or every type of deletion.
For your own request, ask which response period applies and whether verification is complete. Save the acknowledgment and later verification date separately. If the stated response date passes, follow up using the original reference and identify the action still unresolved.
The notice also contains historical request metrics. Those figures are not a forecast for a new request and are not evidence of a completed consumer-request trial. We did not submit a consumer request, measure response times or verify an end-to-end removal outcome for this guide.
What can remain, and what needs a separate request?
The policy describes retention connected to legitimate operational needs and legal obligations. It also states that rights can be limited in some circumstances.
If a response says information remains, ask which categories, why they are retained and which processing has stopped. A precise explanation is more useful than treating every response as either complete erasure or total refusal.
Browser controls have another scope. Tie says it honors the Global Privacy Control signal and describes cookie preference settings for certain advertising choices.
Those choices should not be presented as confirmation that all named or account-related data was deleted. The browser tracking protection comparison explains why preventing tracking and removing stored records solve different problems.
A retailer or other business that collected information independently may need its own request. Ask who controls the record if Tie says it acts for another organization in your situation. Do not infer that all businesses using related marketing technology are legally or operationally one provider.
For separately identified advertising-data sources, the Mogean guide and VentiveIQ guide describe different request workflows. Their existence does not establish that those companies hold your information or share a dataset with Tie. Use them only when the next source is actually relevant.
You can also use the free privacy scan to investigate supported exposure sources. It is not a complete test of every nonpublic marketing dataset. Keep individual confirmations and matching details alongside scan results so a later recurrence can be tied to the correct source.
Frequently asked questions
Are Tie and Revenue Roll separate removal targets?
The current policy identifies Revenue Roll Inc DBA Tie, and the linked form uses that same company name. For this documented workflow, treat them as one controller and identify both names in your correspondence if useful. Avoid duplicate submissions solely because the branding changed.
Does the form's 24-hour statement mean deletion is complete?
No. It concerns notification to the website administrator or data-protection officer.
The same form says the organization needs time to respond. Wait for an actual decision or completion message before recording the outcome as removal.
Is the 60-day response language applicable to everyone?
It appears in the policy's Nevada section, with a possible additional 30 days and notice. Ask which timing applies to your location and request. Do not present that section as a universal processing rule or a tested completion promise.
Can I appeal a refusal?
The policy describes appeals under certain US state laws by emailing info@meettie.com. Eligibility depends on the applicable law and circumstances. Include the original request reference and the decision you are questioning rather than submitting an unexplained duplicate.
Will deleting cookies remove stored personal data?
Clearing cookies changes information in your browser. It does not establish deletion from Tie's systems. Use the published privacy-request process for stored data and retain any browser preference as a separate action in your records.
What if I cannot choose an applicable law in the form?
Do not make an inaccurate declaration. Contact the policy email and ask how to submit your request in your actual circumstances. The opt-out guide hub can help identify separate providers, but their procedures do not replace Tie's request requirements.
Sources checked November 19, 2026: Tie's official privacy notice and linked Termly data-subject request form. We inspected the public controls and declarations without submitting data. This guide documents the available process and its limits; it does not claim individual legal guidance, a paid-account trial or completed deletion.
Continue reading
Related privacy guides
Data Removal vs Credit Freezes: What Is Worth Paying For?
Compare free credit freezes with paid data removal. See current annual prices, temporary-lift rules, broker cleanup limits and when each action helps.
Read articleWINR Data Opt Out: DPO Email and Privacy Request Steps
Contact WINR Data’s privacy officer to request an opt out or deletion. Check verification, regional timing, portal access limits and follow-up steps.
Read articleApollo Interactive Opt Out: Data Rights Form and Removal
Use Apollo Interactive’s data-rights form to request an opt out or deletion. Check matching fields, verification, agent rules and retained-data limits.
Read article