Privacy, accessibility & support

Manage cookie choices, request assistance and suggest portal improvements.

Reviewed 16 October 2026. Available controls depend on your role, plan and service configuration.

Product Privacy Policy and data requests

Read the Privacy Policy at /privacy/ for account and workspace data, payment records, service providers, optional OpenAI guideline imports, international processing and retention. Cancellation keeps your data; account deletion is a separate action. Contact hey@cchora.com for access, correction, deletion or other applicable privacy requests. We may verify your identity before acting. Cookie settings only controls optional analytics, not all processing needed to deliver the service.

Cookie choices and analytics

Google Analytics remains blocked until Performance/analytics consent is accepted. The cookie widget and Cookie settings link open the preferences popup. Review Necessary, Functional, Performance and Targeting categories; targeting is labelled not used. Reject all declines optional tracking, while essential login/security functions remain available. Save my choices applies your selections. Withdrawing analytics consent removes accessible analytics cookies and refreshes the page to unload the tag. Read Cookie Policy for details.

Keep private content private

Use restricted sharing for confidential brand material and review permissions before publishing assets. Account, invitation, recovery and shared-portal pages are excluded from search indexing; the public website, login and signup pages are indexable. Noindex is not a substitute for access control. Avoid placing confidential data in public guidance, filenames, screenshots or support messages.

Accessibility and keyboard use

Use the Skip to content link, Tab to move through controls, visible focus indicators, Enter/Space to activate controls, and the available close button or Escape for dismissible dialogs. Browser zoom and narrow layouts are supported. Respect reduced-motion preferences where supported. Consult Accessibility statement for current limitations; a complete accessibility conformance audit has not been claimed. Describe any access barrier to support.

Send a support enquiry or request a demo

Open Contact, enter your name and email, optionally your company, select a topic and enter a plain-text message of 10–3,000 characters. Complete the security check and choose Send email. The form sends directly to hey@cchora.com; it does not open a draft in your email app. Attachments are not accepted. A success popup confirms sending; Done clears the form for a new enquiry. If sending fails, retain your text and retry later or email hey@cchora.com directly.

What to include in a support request

Include the page URL without secret tokens, affected brand, your role, the steps you tried, exact error message and approximate time. Explain the filename type/size for upload problems and transaction reference for billing problems. Do not send passwords, full card details, secret keys, authenticator codes or recovery links. If a screenshot is needed, use the direct email channel with sensitive information hidden; do not expect an attachment field on the contact form.

Suggest a feature

Choose Request Feature in the workspace or open Feature Board while signed in. Use a title of 5–160 characters, choose Portal, Assets, Collaboration, Billing, Security or Other, and describe the need in 20–3,000 characters. You can view your own submitted requests; it is not a public voting board or a guaranteed delivery roadmap. A success message means the request was saved, not that implementation is scheduled.