Request review, correction, or deletion of information connected to you.

What may be requested.

A person may ask USIMEX to take any of the following actions regarding information connected to them.

• Review of information connected to them
• Correction of inaccurate information
• Clarification of incomplete or misleading information
• Updating outdated contact or organization information
• Withdrawal of optional consent where applicable
• Restriction of certain future uses
• Deletion where appropriate
• Confirmation that a reviewed change was completed
• Explanation when a request cannot be completed as submitted

Requests may involve several kinds of records.

The following categories describe the types of records a request may touch. Actual records are never displayed publicly.

• Business inquiry information
• Contact and organization information
• Consent records
• Inquiry history and status activity
• Communications connected to a request
• Security and abuse-prevention records
• Audit and accountability records
• Owner review notes connected to the request
• System-generated identifiers and timestamps
• Records required to preserve system integrity
• Records required by law, contract, dispute, or security obligations

Public pages describe categories only. Leads, consent records, audit logs, owner notes, external AI requests, and operational data are not exposed on this website.

Requests follow a controlled review process.

1. 1

   Submit the request

2. 2

   Identify the information or interaction involved

3. 3

   Verify identity or authority where necessary

4. 4

   Locate and review relevant records

5. 5

   Determine the appropriate correction, restriction, retention, or deletion action

6. 6

   Communicate the outcome where a response channel is available

• No public automated identity-verification workflow exists
• No immediate or automatic deletion occurs
• Additional clarification may be requested
• Requests involving organizations may require proof of authority
• Requests submitted by agents may require authorization
• Related records may need to be reviewed together

Some information may need to be retained.

Information may be retained where reasonably necessary for the following purposes.

• Legal obligations
• Contractual obligations
• Fraud or abuse prevention
• Security investigations
• Dispute resolution
• Auditability and accountability
• Consent history
• Record integrity
• Preventing duplicate or conflicting records
• Protecting the rights of USIMEX or others
• Preserving evidence of significant actions
• Maintaining system reliability
• Enforcing policies or agreements
• Responding to regulatory or lawful requests

USIMEX does not claim a specific statutory retention period unless one is explicitly supported by existing approved records.

Requests must be connected to the correct person or organization.

• USIMEX may ask for enough information to locate the relevant record
• Identity verification should be proportionate to the request
• Sensitive information should not be submitted unnecessarily
• Government identification should not be requested by default
• File uploads are not accepted
• Passwords, access credentials, payment information, medical records, or highly sensitive documents must not be submitted
• A representative may need documented authority
• A request may be paused when identity or authority cannot be reasonably confirmed
• USIMEX may refuse requests that appear fraudulent, abusive, deceptive, or harmful

Consent choices and deletion requests are related, but not identical.

• Withdrawal of optional consent may stop certain future uses
• Withdrawal does not necessarily delete historical records
• Records proving that consent was granted or withdrawn may be retained
• Required processing may continue where necessary to respond to the request
• Marketing consent may be withdrawn separately
• Operational, security, legal, and audit records may follow different retention rules
• A deletion request does not automatically cancel contracts or other obligations
• Communications about the request may themselves become part of the review record

An automated consent-management portal does not currently exist. Consent choices are recorded through approved workflows and reviewed by USIMEX.

Human review governs the outcome.

• Material decisions require authorized human review
• Public requests do not grant access to private systems
• A requester cannot directly edit database records
• External AI systems cannot approve or execute deletion
• The owner-facing AI agent cannot independently delete records
• Automated actions are not enabled by default
• Auditability may require preserving evidence of the request and outcome
• Approved corrections should be traceable
• Denied or limited requests should have a documented reason
• Private operational records remain private
• No public deletion endpoint exists
• No webhook, API, chatbot, or autonomous deletion mechanism exists