What this website covers
You can explore the product, pricing, policies, and contact options here on the website before anyone signs in.
Trust center
Trust you can verify
SayHex explains how our security, privacy, and access work in plain language, so you know exactly what to expect.
سیهکس به زبان قابل ارزیابی برای خریدار توضیح میدهد که راهنمایی عمومی وبسایت، برنامهریزی دسترسی بازبینیشده، حریم خصوصی و امنیت چگونه پیش از شروع کار محافظتشده کنار هم قرار میگیرند.
ClarityPlain, direct language
LanguagesEnglish and Persian
Your dataNot requested here
TransparencyClear on every page
Trust guidance
Clear information about SayHex
Here you will find our security, privacy, access, and publishing standards, with nothing about private systems or claims we cannot back up.
From demo to getting started
We set up access after a demo and a quick review, not through open sign-up. You never make your own admin account, and there is no instant approval.
Privacy and careful data handling
Our forms ask only for what is needed to contact you and plan a demo. Sensitive work data never goes on these public pages.
Plain-spoken security
We describe how we protect accounts and separate access in plain terms, without exposing private architecture or system details.
Quality in every language
Everything here is reviewed in every language you enable, with right-to-left layouts, so they read clearly and consistently.
What stays private
Real information you can rely on
We publish only information we have checked. Final contracts, approvals, and account setup happen directly with our team.
Data request contact workflow
Use the public contact form for website data requests
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.
Questions about trust?
Use the website for questions about trust, privacy, cookies, and terms. Book a demo when your team is ready to plan access.