Skip to content

Privacy

Clear information about how USIMEX handles data.

USIMEX is designed around structured information, defined permissions, consent, owner review, and controlled use. This page explains the categories of information USIMEX may process, why it may be used, and the boundaries that apply.

Some public submission, upload, external-AI, communication, and owner-agent features are still being prepared and are not currently active.

Information may be collected when a person or organization chooses to interact with USIMEX.

  • Name and contact information
  • Organization name
  • Role or title
  • Website URL
  • Location
  • Preferred contact method
  • Industry
  • Service interests
  • Business problem or operational need
  • Desired outcome
  • Timeline
  • Budget range
  • Current tools or systems
  • Consent selections
  • Inquiry source
  • Website usage and successful email-registration events for site analytics
  • Technical request metadata when needed for security or troubleshooting

USIMEX should collect only information reasonably connected to the stated interaction or requested service. Not every category listed above is necessarily collected today. Our inquiry forms do not store visitor IP addresses or IP-derived identifiers; repeat-submission limits use signed-in accounts. Hosting and infrastructure providers may process request metadata under their own policies.

Information should have a defined purpose.

  • Responding to a project inquiry
  • Understanding an organization's needs
  • Determining whether USIMEX services may be relevant
  • Routing an inquiry for owner review
  • Preventing duplicate or abusive submissions
  • Maintaining consent evidence
  • Recording meaningful status changes
  • Improving system reliability
  • Meeting legal, security, or administrative obligations
  • Preparing a future proposal or scope
  • Supporting user-requested correction or deletion

Information should not be collected merely because it may be technically possible to collect it.

Consent should be specific, documented, and reviewable.

  • Contact consent

    Permission to contact a person in response to an inquiry or request.

  • Data-processing consent

    Permission to process submitted information for the stated interaction.

  • AI-assisted-review consent

    Optional permission for AI-assisted review where it is offered.

  • Marketing consent

    Optional permission for any marketing-related communication.

  • Required consent should be distinguished from optional consent.
  • Consent language and version may be recorded.
  • Marketing consent should remain optional.
  • Withdrawal should not retroactively make earlier lawful processing invalid.
  • A withdrawn consent record may be retained as evidence that consent was withdrawn.
  • No consent should be assumed from silence.

AI may assist with review. Human responsibility remains.

Future or controlled AI-assisted review may help with the following:

  • Classification
  • Summarization
  • Duplicate detection
  • Identifying missing context
  • Routing recommendations
  • Drafting internal recommendations
  • Highlighting policy or consent issues
  • AI-generated interpretations may be incomplete or incorrect.
  • Material decisions require authorized human review.
  • The owner-facing AI agent is not currently active.
  • Autonomous owner-agent actions are prohibited.
  • External AI autonomous submission is not active.
  • No automated decision should be presented as final authority.

AI-assisted inquiry drafts

For the Real Estate Website Review action, an external AI assistant may prepare a structured inquiry draft on a person’s behalf. USIMEX stores the draft temporarily for up to 30 minutes pending human confirmation. Unconfirmed drafts expire and are not submitted. Only after a person reviews, edits, and consents on a secure USIMEX page does the inquiry enter the normal contact workflow. Technical abuse-prevention data (such as a privacy-conscious IP hash) may be processed to protect the intake path. Unconfirmed or expired draft content is redacted or deleted within 7 days; security metadata is retained only under USIMEX’s approved security-retention policy.

Private operational information remains private by default.

  • Leads and inquiry records
  • Consent records
  • External AI request records
  • Owner notes
  • Owner-agent recommendations
  • Audit logs
  • Internal system settings
  • Permission rules
  • Policy-management records
  • Private business documents
  • Credentials or secrets
  • Internal identifiers
  • Security details
  • Private contact details
  • Sensitive personal information
  • Customer, patient, employee, buyer, supplier, or client records unless separately authorized
  • Uploaded files unless a controlled upload workflow is implemented

The public website should expose approved public information—not the internal records used to manage the system.

Records should be retained only for a defined operational, legal, security, or accountability purpose.

  • Lead records

    Owner review after approximately 730 days.

  • External AI request records

    Owner review after approximately 365 days.

  • Audit records

    Owner review after approximately 1,095 days.

  • Draft communications

    Approximately 180 days if applicable.

  • Consent records

    Retained with the related record or as necessary to preserve consent evidence.

  • Owner notes and recommendations

    Retained with the related operational record.

  • System settings

    Retained as system configuration.

These retention references describe review periods or intended lifecycle rules, not guaranteed automatic deletion dates. Automatic deletion is not currently implemented.

People may request review of information connected to them.

  • Correction of inaccurate information
  • Clarification of stored information
  • Withdrawal of optional consent
  • Review of marketing preferences
  • Deletion where appropriate
  • Restriction of future processing where appropriate
  • Requests may require identity verification.
  • Some information may need to be retained for legal, security, consent-evidence, fraud-prevention, contractual, or audit purposes.
  • Audit records should not be silently rewritten.
  • Withdrawal and deletion are not always the same action.
  • USIMEX does not currently provide a self-service privacy portal unless such a portal actually exists.

Privacy depends on permissions, boundaries, and honest feature status.

  • Public project intake

    Status: In preparation

  • External AI inquiry submission

    Status: In preparation

  • File uploads

    Status: In preparation

  • Owner-facing AI agent

    Status: In preparation

  • Autonomous owner-agent actions

    Status: Disabled

  • Outbound communications

    Status: In preparation

  • Public system status page

    Status: In preparation

  • Duplicate detection

    Status: Enabled

  • Manual owner review

    Status: Owner review required

  • Disabled features should not collect or process public submissions.
  • Consequential settings require confirmation and audit where implemented.
  • Manual owner review currently remains required.
  • Duplicate detection may operate when enabled.
  • No security or privacy system is perfect.
  • USIMEX does not claim independent certification, regulatory compliance, penetration testing, or guaranteed security unless documented.

Understand the system before sharing information.

Review what USIMEX builds, how it works, and the boundaries governing public and AI-assisted interaction before beginning a future project conversation.

Structured project intake and public contact channels are still being prepared.