Use the information for the review. Nothing broader.

Operalith uses contact details to answer a written request and, only after accepted scope, uses the minimum approved export needed to check one operational workflow.

The current product does not need a standing feed, customer credentials, or unrestricted system access.

01Contact data

A written inquiry is not an outreach permission slip.

Contact details are used to evaluate the request and respond directly
Contact details are not sold or repackaged into marketing lists
An inquiry is not permission for automated outreach or a live system action

There is no public web form or automated outreach. Direct written requests are reviewed by Dylan.

02Review material

An operational export belongs to one accepted scope.

Operalith requests only the columns and rows needed for the agreed check. Credentials, unrelated exports, broad archives, and records that do not support the decision question should not be sent.

03Your control

Retention and deletion are named before material moves.

The written scope should name the retention-review date and the instruction for returning or deleting private material. Questions or deletion requests can be sent directly to dylan@info.operalith.com.

Some records may need to be retained when required by an active engagement, payment, tax, dispute, or legal obligation.

04Accountability

A named person is responsible for the handling boundary.

Operalith is currently operated by Dylan Becchetti in Bethlehem, Pennsylvania. Privacy questions and requests go to dylan@info.operalith.com.

Public privacy record effective August 25, 2026.

Next record

Start with structure, not production records.

Describe the work first; existing column headers can help. You do not need to fabricate a sample or clean your export. We agree disclosure permission, a private handling route and retention before requesting existing records.

Request a fit check See what to send