Trust and safety
SayHex separates public website information from protected work. The security page explains reviewed access, public form protection, and data boundaries without exposing private implementation detail.
SayHex اطلاعات عمومی وبسایت را از کار محافظتشده جدا میکند. این صفحه دسترسی بازبینیشده، محافظت فرمهای عمومی و مرزهای داده را بدون جزئیات خصوصی توضیح میدهد.
Public security copy
These sections give buyers and website visitors a high-level trust view while keeping private systems, account paths, event records, and implementation choices out of public copy.
Data handling
Public forms ask only for visitor-provided contact and planning fields. SayHex keeps security event records scoped to safe metadata such as challenge state and outcome, not message bodies, payment details, credentials, or private account data.
Privacy questions use the public contact path, and detailed notices stay owner-reviewed before publication.
Read the privacy pageAbuse defense
Contact, request-demo, and newsletter forms are protected by SayHex-owned challenge, timing, replay, and rate-limit checks before accepted submissions. The public page describes the control category, not the private steps behind it.
The website does not require third-party captcha services for the public security message.
Contact SayHexAdmin protection
Customer Admin access requires approved provisioning and protected login. Public security copy never creates admin accounts, opens self registration, or bypasses review for account changes.
Demo requests start an approval path; they do not grant Customer Admin access from the website.
Request Customer Admin DemoPublic boundary
The official website can explain security posture, privacy handling, and access expectations. It does not publish protected routes, environment values, infrastructure specifics, AI system labels, customer records, or event payloads.
Readers can review the trust and privacy pages for public context, then use contact or demo request for next steps.
Read the trust pageContact path
Public security, trust, privacy, and demo planning questions should use the SayHex contact or request-demo pages. The website does not accept private production details in public messages.
Visitors should avoid sending passwords, payment data, private account records, or infrastructure information through public forms.
Contact SayHexPublishing boundary
The SayHex website describes trust posture without revealing infrastructure specifics, protected configuration, unpublished event records, or implementation labels. No unsupported compliance claims are made on this page.
Use contact for public security or privacy questions, review the trust and privacy pages for public context, or request a Customer Admin demo when access planning is needed.
