Security / Trust & responsibility

Clarity is a security principle.

Understand the boundaries of this website, the controls that guide our product thinking and the steps to take if something looks wrong.

ARCLIGHT / PERSPECTIVE IN MOTION
Website scope

Know what happens here.

Clear expectations help visitors distinguish information, communication and financial activity.

01

Information & communication

This public website provides company information, educational perspectives, third-party market data, inquiry forms and career introductions.

02

No asset or account access

This website does not connect wallets, receive deposits, custody digital assets, execute trades or provide lending, staking or payment accounts.

Product design priorities

Responsibility should be visible.

These principles describe our development priorities. They are not a certification or a claim that a complete financial control environment is deployed.

01

Defined access

Design responsibilities around the work a person needs to perform, with clear ownership of access decisions.

02

Separated responsibilities

Distinguish preparation, review and authorization when the impact of an action calls for independent oversight.

03

Reviewable actions

Keep meaningful context around decisions: the source, the owner, the reason and the exceptions that were considered.

04

Prepared recovery

Identify dependencies, escalation paths and recovery questions before an interruption makes them urgent.

Visitor protection

Pause when a request crosses a boundary.

Use known contact details and independently verify the people and terms behind any proposed relationship.

01

Protect your credentials

Never enter a wallet seed phrase, private key, account password or payment-card details into this website’s forms.

02

Check the destination

Our website is arclightdigitalassets.com, including www.arclightdigitalassets.com. Look carefully for misspellings and unrelated domains.

03

Question unusual demands

Requests for recruitment fees, wallet transfers or remote access are reasons to stop and verify through our published contact route.

Operational perspective

Good handoffs reduce uncertainty.

Security questions often appear between systems and teams. A useful operating record explains what is known, what remains unresolved and who should make the next decision.

Read our perspective on continuous markets ↗
Reporting a concern

Give us enough context to investigate.

For a suspected impersonation, website problem or security concern, select “Security” on the contact form.

  1. Describe

    Include the affected page or message and explain what appeared unusual.

  2. Locate

    Provide the relevant URL and approximate time, including your time zone.

  3. Minimize

    Redact personal details. Do not include passwords, keys, account numbers or other people’s records.

  4. Contact

    Use our contact form or published email. Do not probe other users’ information or disrupt the service.

This contact route is not an emergency recovery service. Never transfer assets or share credentials to “verify” a report.

The next conversation

Transparency starts with clear boundaries.

Review the website scope, digital-asset risk notice and how information is handled.

Read disclosures