Contact Analytiics

One address reaches us, and it is read by the people who build the product rather than a queue: [hello@analytiics.co](mailto:hello@analytiics.co).

What to send where

• Beta access. Email us, or join the list on the home page. We onboard a small number of teams at a time so the manifest and the agent skills get shaped by people actually shipping with them.
• Support for a live project. Email, with your project slug in the subject. If your dashboard is public, a link to it saves a round trip.
• Bugs and feature requests. Open an issue at github.com/charlieclark/analytiics. The product is developed in the open, so a public issue gets a public answer that helps the next person.
• Security reports. Email, with security in the subject line. Please do not open a public issue for a vulnerability; we will confirm receipt and give you a timeline for a fix.
• Privacy requests. Email, with privacy in the subject line. What we hold and how long we hold it is set out on the privacy page.
• Press and partnerships. Email; we are happy to talk about how manifest-driven instrumentation works and where it does not fit.

Response times

We answer during European and North American working hours, usually within one business day. Security reports are triaged the same day we see them.

The company

Analytiics is built by a small independent team. There is no sales organisation, no call centre and no chatbot in front of the inbox — the person who replies is the person who can change the code.