You can ask to see, correct or delete your data.
Use this route for personal data held through search project support or a company listing inquiry. Ask for access, correction, deletion or a copy without sending sensitive documents. Yondexy answers data requests within 5 days.
Effective October 10, 2026 · Last updated October 10, 2026 Send a data requestTell us which record or conversation your request concerns.
Identify your search project support record.
Start with the contact detail used for the original inquiry and describe what you want us to do. An inquiry reference, an approximate date or the subject of a conversation can help locate the record. You do not need to remember every field you completed.
For a company listing inquiry, distinguish the message you sent from any business directory records you are asking about. A request to change your contact email is not the same as asking us to revise a public company entry. If both are involved, say so in the message.
Do not paste passwords, card details or an entire private dataset into the form. There is no account to log into and no payment to make. A government identity document is not required to open a request. The form has no attachment field because the first step is to identify the issue, not collect more sensitive material.
You may use the form below or email [email protected]. Calling +1 (435) 555-4934 is another way to explain the request if typing it is difficult. See accessibility and barrier reporting if an interface prevents you continuing.
You can ask for access, correction, deletion or a copy.
Name the action you need.
- Access
- Ask whether we hold personal information about you and request an explanation of the records and their use. Identify the conversation or interaction if you can.
- Correction
- Identify the field you believe is wrong and give the replacement value. Explain whether it applies to a past message, current reply details or another record.
- Deletion
- Ask us to remove personal data associated with the interaction you name. If a legal exception affects part of the request, the response explains what cannot be removed and why.
- Copy
- Ask for a copy of personal data located for your request. You may describe a preferred readable format; we can clarify what is available for the records involved.
You can combine actions in one request. For example, you may want a copy before asking for deletion. State the intended order so we do not have to infer it. An access request does not automatically instruct us to erase the underlying conversation.
A correction to Yondexy's record does not automatically change information held independently by an external search engine or source publisher. If a request concerns business directory records rather than your own correspondence, include the public record reference and describe the part that relates to you. Do not send another person's private details to establish ownership of a listing.
Identity checks are proportionate to the record and the action.
We must not disclose a conversation to the wrong person.
We may ask questions before releasing a copy, changing a record or completing deletion. A reply from the contact route used for the original inquiry and a matching reference can help establish the connection. The information requested should relate to the record and the risk of acting on it.
Do not send identity documents in anticipation of a check. If the email or phone used originally is no longer available, explain that in your message. We can discuss another proportionate way to understand the request instead of treating an unavailable inbox as proof that you have no rights.
If you act for another person, state that relationship and the authority under which you are making the request. We may need to establish that authority before sharing their information. A request for one person's data is not permission to disclose a shared conversation in full where it would expose somebody else's personal information.
Where a record cannot be located or the request cannot yet be verified, we explain the obstacle rather than sending a speculative export. An inquiry number is useful context, but it does not by itself authorize access to every record associated with a name.
Your data request receives an answer within 5 days.
The reply explains the next action.
Yondexy answers a data request within 5 days. The answer addresses the request or explains what clarification is needed to identify the relevant records or act safely. This is not a promise that an unverified request causes immediate deletion.
After you send the form, a successful response includes a request reference. Keep it for follow-up. A confirmation that the message was saved means the request has been recorded; it does not mean a copy has already been prepared or a correction completed.
The response uses the contact route you provide. If some information is withheld or an action cannot be completed, the explanation should identify the reason and how you can question the decision. This page does not impose a requirement to buy a service or accept optional advertising storage before exercising a privacy right.
A technical failure is not a successful submission. If the form reports an error, use the message beside the affected field or contact [email protected]. If you are following up on a request already sent, include its reference instead of sending the same private material again.
The request route uses the same inquiry system, with a distinct request kind.
Know what this form records.
The form sends a data-request kind to ruli010.php. It records the name, phone, email and address supplied, along with the message, requested specification and consent tick. The IP address, browser user-agent string, referring URL and the times the form was rendered and sent are recorded automatically.
The hosting provider serves the website and stores the inquiry database. The mail provider carries the notification to the operator's inbox. These providers help deliver and retain the request; submitting the form does not make its contents a public company listing.
| Record type | Retention |
|---|---|
| Enquiries and email copies | 18 months |
| Chat transcripts | 12 months |
| Server and access logs | 60 days |
| Consent choice record | 12 months |
Support chat keeps the conversation and a token in your browser so you can return to it. The consent choice is stored separately under site_consent_v2. Removing browser storage can remove the local token or preference but does not send a deletion instruction for records on the server.
There is no account profile, password or payment record to export from this site's inquiry flow. If a requested record has already reached its retention limit and is no longer held, a request does not recreate it. The privacy statement explains the wider handling of submitted data and advertising attribution.
Changing advertising consent is separate from deleting an inquiry.
You can withdraw storage permission without a form.
Use Cookie choices in the footer to revisit optional storage. Google Ads, Microsoft Advertising and Meta Ads send traffic here. Their click identifiers are gclid, msclkid and fbclid. An identifier may arrive in the page URL; it is not treated as anonymous merely because it is not a name.
Consent Mode v2 keeps ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow storage. Declining or withdrawing sets all four back to denied immediately. Global Privacy Control, through the Sec-GPC header, is honoured as an opt-out without asking again. Denied storage is not a claim that no request reaches a platform.
Google Ireland Ltd / Google LLC receives Google Ads consent signals and handles Google attribution. Microsoft Ireland Operations Ltd handles Microsoft Advertising. Meta Platforms Ireland Ltd handles Meta Ads attribution. Their own handling is explained in Google's privacy information, the Microsoft privacy statement and Meta's privacy information.
We do not put names, message bodies, email addresses or phone numbers into advertising events. Asking us to delete an inquiry and withdrawing browser storage permission are different actions; use both routes if that is what you intend. See cookies and consent choices for storage details.
Applicable privacy law gives you routes to question a response.
A request does not waive your rights.
US state privacy law applies, including California's CCPA/CPRA and the other state laws in force. The rights available in a particular case depend on the applicable law and the information involved. You can use this route to describe an access, correction, deletion or copy request without having to cite a statute.
For visitors reaching the site from Europe, the GDPR sections of the privacy statement address access and related rights, including restriction, objection, portability and withdrawal of consent where applicable. You may describe one of those requests in the message rather than selecting a narrower action that does not fit.
If you disagree with a response, reply with the request reference and the part you want reviewed. You may complain to your state Attorney General and, in California, to the California Privacy Protection Agency. Visitors covered by the GDPR may raise a complaint with the relevant supervisory authority. Contacting Yondexy does not replace those complaint routes.
The operator is Yondexy, trading at yondexy.com, at 174 Mill Street, Apt 3, Austin, Texas 28536, Austin, Texas, United States. Questions about the use of the website itself are addressed in the service and website terms. An ordinary search project support question can go to the contact page instead.
Send a data request.
Say what you want done and provide either an email address or phone number for the reply. Neither contact field is required on its own. Do not include sensitive documents or someone else's private information.