Website and demo terms

Terms for website and demo planning

These terms explain what this website and the demo request can do before any contract, license, or account setup is confirmed.

ClarityPlain, direct language
LanguagesEnglish and Persian
Your dataNot requested here
TransparencyClear on every page

What to expect

Here is how you can use this website and the demo request, in plain terms. It does not create service rights, grant protected access, or replace final legal review.

The website is here to inform you

This website explains what SayHex does and how to get started, and it does not grant portal access on its own, Customer Admin access, or production service commitments.

Demo requests start review, not access

Requesting a demo starts a conversation. It does not promise instant approval, instant sign-up, or an admin account right away.

Pricing and licensing are agreed with our team

We are happy to talk about pricing and licensing here, but final quotes and order terms are agreed with our team.

The admin area is set up after approval

The admin area is sign-in only and is set up for you after review and approval. Nothing on this website can create an admin account for you.

Final contracts are handled with our team

This helps you prepare legal and purchasing conversations. It does not replace the contract, order form, or legal approval.

What these terms cover

This helps you prepare website, demo, pricing, and purchasing conversations. Final contracts, service levels, order forms, and account setup happen in our secure commercial and onboarding process.

Data request contact workflow

For access, correction, deletion, consent, or privacy questions about information submitted through sayhex.com, start on the contact page with a short subject such as "Data request". Share only enough context for SayHex to route and verify the request; do not include passwords, secrets, payment details, private records, or log files.

Start with Contact SayHex

Open the contact page and use a clear subject such as "Data request" or "Privacy request" so Website Admin review can route it correctly.

Expect verification before action

SayHex may confirm the request and the reply path before taking action, especially when a request affects submitted form details or consent choices.

Keep sensitive details out

Public data requests should not include passwords, secrets, payment details, private records, protected account data, screenshots with credentials, or log files.

Use the contact page for terms questions about the public website. Use pricing and licensing for planning context, and request a demo when your team is ready to plan access.