Reach the person behind the system.

01Operator

Arhan Canli reads the public contact channel.

Arhan Canli is the founder and lead engineer of TraceAxiom. Product, technical, evidence, privacy, and security questions currently go directly to him. The About page and public GitHub profile provide the canonical identity links.

TraceAxiom is an independent, pre-incorporation product project. The two-working-day reply target is an operating goal, not a contractual support or incident-response service level.

• Named founder and operator
• Public engineering profile
• Direct access-request mailbox
• Pre-incorporation status disclosed

02Product

Join the waitlist with a short description of your pull requests.

To join the waitlist, say which coding agents open pull requests in your repositories, roughly how many a week, and the stack at a high level. The homepage form stores the request and sends a confirmation. Arhan usually replies within two working days, but that target is not a contractual service level.

Do not paste private code, credentials, customer records, or regulated information into the first message. Verify is not installable yet; design partners are contacted when it can run on their repositories.

03Security

Report a suspected vulnerability without exposing the vulnerability.

Begin by emailing access@traceaxiom.com with the subject “Security report” or by using the public access form with the same label. Include a high-level description, the affected public URL, and a safe way to contact you. Do not include exploit code, credentials, personal data, or secrets in the first message.

TraceAxiom will reply to establish a more appropriate private channel when one is needed. There is no public bug-bounty promise today. Please act in good faith, avoid privacy violations and service disruption, and allow reasonable time to investigate before public disclosure.

• Stable route published in security.txt
• No secrets in the first message
• Good-faith reports welcomed
• No bug-bounty or response-time promise

04Privacy

Use the same channel for access, correction, or deletion requests.

Use the subject “Privacy request” and identify the email address used in the original access request. Do not send identity documents in the first message. TraceAxiom may need to verify control of the original email address before disclosing, correcting, or deleting a record.

The Privacy notice describes the submitted fields, salted IP hash, user-agent record, current processors, purposes, retention boundary, and open operational limitations. Questions about a future customer data path should be resolved before any confidential material is transferred.

05Evidence

Verification questions should name the exact claim or artifact.

If a public measurement, security statement, or product mechanism is unclear, include the page URL and exact language in question. TraceAxiom will distinguish what is implemented, what is measured, what is illustrative, and what remains open.

Requests for an audit, design-partner reference, production-readiness attestation, or customer outcome will not be answered with a substitute claim. If the requested authority does not exist yet, the response will say so.