AttnomSolutions
Loading page
Bringing in the next surface without the heavy transition shell.
Loading page
Bringing in the next surface without the heavy transition shell.
Terms
This page now frames obligations, billing rules, dispute anchors, and role-aware summaries in plain language so people can understand the operating agreement before they commit to work or account use.
Commercial model
Quoted work, scoped delivery, and platform use are tied to written records rather than verbal assumptions.
Billing rules
Deposits, change requests, and on-chain payment finality are visible before money moves.
Support path
Questions and disputes should route through contact or workspace records before they escalate.
Contract navigator
The first pass should tell people what Attnom expects from them and what they should expect in return.
Obligation
Keep identity, credentials, and workspace records accurate. Do not impersonate others or bypass restricted areas.
Obligation
Use Attnom routes, tools, and account surfaces lawfully and without abuse, scraping, or deceptive workflow behavior.
Obligation
Provide scope, approvals, content, and feedback in time for the quoted project or operating lane to move forward.
Obligation
Third-party outages, exchange issues, blockchain congestion, and wallet compromise outside Attnom control are not guaranteed against.
Billing rules
Quotes and scope
Commercial terms follow the accepted quote, scoped request, or pricing lane attached to the work.
Deposits and timing
Deposits can be required before reserved work begins and may expire when pricing or delivery windows change.
On-chain finality
Blockchain payments are treated as final after confirmation unless Attnom agrees to another outcome in writing.
Change requests
Scope expansion can change delivery timing, billing, or acceptance boundaries before work continues.
Dispute anchors
Anchor 01
Raise the issue through contact or the relevant workspace thread before assuming the relationship has failed.
Anchor 02
Quotes, project notes, payment references, and route-specific records are the source of truth when terms are questioned.
Anchor 03
If an issue affects account safety, delivery integrity, or payment confidence, the related lane can be paused while reviewed.
Role-aware summary
Pick the role that best matches your use of Attnom and read the terms in the language that matters for that lane.
Clients
Best route
/workspace or /contact
Your main obligations are to give accurate scope, respond to approvals, and understand how deposits, change requests, and deliverable transfer are tied to the commercial agreement.
Delivery timing depends on the accepted scope and the client-side materials needed to move the work forward.
Client-specific deliverables transfer according to the commercial arrangement attached to the project.
Payment, billing, and dispute review rely on the written project and payment record, not a vague verbal summary.
Clarification lane
Route commercial, delivery, payment, or account questions through contact before you open a build request or send a deposit.