Law Enforcement Request Guidelines

Version 2.0 · Effective 24 October 2026

How Vision Makers Technologies Inc. handles requests from law enforcement and government agencies for user information.

1 · Principles

We comply with valid legal process and we protect user privacy. Both. A request must be lawful, properly served, and specific before we act on it, and we will challenge requests that are overbroad, defective, or inconsistent with applicable law.

2 · What we hold

We do not hold: private keys; seed phrases; user funds; or the ability to freeze, seize or reverse assets in a user's own wallet. No legal process can compel us to produce what does not exist.

We may hold: account registration data; email addresses; KYC records where verification was performed; connected wallet addresses; platform activity and agent logs; IP and device metadata; support correspondence; and subscription and payment records.

Retention periods are at Privacy Policy §8.

3 · Making a request

Submit to admin@visionmakers.io, subject "Law enforcement request", on official letterhead from an official government email address, including:

  • the issuing agency, officer name, badge or ID, and direct contact details;
  • the legal authority relied upon;
  • the specific user identifier, email, account ID or wallet address;
  • the precise data categories sought and the date range;
  • whether a non-disclosure obligation applies, and its legal basis and duration.

Requests lacking these will be returned for clarification.

4 · What we require

Request type Standard required
Basic subscriber information Valid legal process, subpoena or local equivalent
Activity and transaction logs Court order or equivalent
Content of communications Warrant or equivalent judicial authorisation
Preservation request Written request; we preserve for 90 days, extendable once

Requests from outside Panama should ordinarily proceed through mutual legal assistance or letters rogatory. We may respond to a foreign request voluntarily only where permitted by applicable law.

5 · Emergencies

Where there is a good-faith belief of an imminent risk of death or serious physical injury, we may disclose the minimum information necessary without full legal process. Mark the request "Emergency disclosure request" and state the nature and immediacy of the risk.

6 · User notification

Our default is to notify the affected user before disclosing, giving them an opportunity to object, unless:

  • we are legally prohibited from doing so;
  • there is a credible risk of death, serious injury, destruction of evidence or witness interference;
  • notification would be futile, for example, the account is already known to be compromised.

Where a non-disclosure order is time-limited, we notify the user on expiry.

7 · Transparency reporting

Commitment to establish We intend to publish a periodic transparency report covering the number of requests received by type and jurisdiction, and the proportion where data was produced, in full or in part. Cadence and first publication date to be confirmed; an unmet commitment is worse than none, so confirm feasibility before publishing this as a promise.

8 · Costs

We may seek reimbursement of reasonable costs of compliance where law permits.

9 · No endorsement of circumvention

Nothing here authorises informal access. Agencies must use proper process. Employees are prohibited from disclosing user data outside this policy.

Contact

admin@visionmakers.io