Contact Arcarix
Use this page for privacy questions, content corrections, broken pages, reading feedback, or service inquiries.
Arcarix currently handles support by email so users can reach the operator without creating an account.
When you contact us, send only the information needed to understand the issue. For most reports, the page URL, language, selected reading path, browser, and a short description are enough.
You may say that a reading felt off, too certain, or culturally awkward, but the operator cannot decide a personal relationship, job, legal, financial, or health matter for you.
Primary contact: hello.arcarix@gmail.com
If your message is about a specific page, include the URL, language, and a short description.
For mobile layout problems, failed share-card saves, repeated result text, or a button that does not respond, include the browser you used and the approximate time of the issue.
What Arcarix can answer
Questions about privacy, terms, cookies, page behavior, content corrections, translation quality, and service feedback.
The contact channel cannot provide personal medical, legal, investment, or mental-health advice.
If a result sounded too absolute, if a reader voice felt unnatural, or if a phrase may be misunderstood in a specific culture, send that context. Those reports help improve public copy, generated-reading boundaries, and bilingual phrasing.
What not to send
Do not send identity documents, medical records, bank details, legal files, private conversations, or another person's sensitive information unless the operator specifically asks for a narrow support reason.
A useful report usually needs only the page URL, selected reading path, language, and a short explanation.
How feedback is reviewed
Content feedback may lead to clearer wording, stronger limitation notes, broken-link fixes, or public page improvements.
Generated reading feedback is reviewed for technical or wording issues, but Arcarix cannot guarantee that every reading will match a user's expectation.
The operator first checks whether the issue can be reproduced. If needed, the same screen's copy, input flow, and result template are reviewed together.
Requests are grouped by public pages, reading flow, generated wording, privacy guidance, and accessibility. If the same issue can affect many users, a product fix may come before an individual explanation.