Privacy policy

This policy explains how Anectico handles personal information when you visit our website, join our waitlist, contact us, or use our observability platform and its integrations.

1. Who handles your information

Anectico is operated by Anectico Limited (“we,” “us,” or “our”). We provide tools to investigate errors, traces, logs, session replays, and other application activity. For privacy questions and requests, contact hello@anectico.com.

We determine how information is used to manage our website, waitlist, accounts, support, and service security. For personal information that a customer sends from their application, the customer determines the purposes of processing, and Anectico processes that information to provide the service on their instructions. If your information comes from an application using Anectico, contact that application’s operator first; we can help route your request.

2. Information we handle

• Website and communications: your email address, messages you send us, waitlist signup and delivery records, and technical information such as IP address, browser information, requested pages, and security events processed by our hosting providers.
• Account information: sign-in identity, name, email address, organization and project memberships, permissions, and account activity.
• Customer application data: the events a customer chooses to send, which may include user identifiers, profile attributes, errors, stack traces, logs, traces, device information, URLs, session recordings, and AI prompts or responses. The information present depends on the customer’s instrumentation and content settings.
• Integration data: authorized workspace, organization, repository, project, channel, issue, and installation identifiers; ticket titles, descriptions, links and status; notification content; and webhook payloads, which can include user names or other personal information.
• Connection credentials: OAuth access and refresh tokens, installation credentials, and webhook verification secrets needed to operate authorized connections. Provider credentials stored in Anectico’s connection vault are encrypted.
• Agent activity and operations: the keys and approvals you give your own AI agents, a record of what each agent did through MCP, the CLI and the API, and of the skills the CLI reports it installed or removed, a separate record of which read-only proof pages a signed-in member of your organization opened in the Console (the kind of page, the object it showed, the project, the time and the member), saved definitions such as dashboards and alert rules, delivery history, and audit records of actions taken in the platform. The agent record and the record of opened proof pages are kept for 30 days on Free and Solo, 90 days on Pro and 180 days on Scale; a downgrade shortens readable history as soon as the plan changes and older rows are removed on the next retention pass, while an upgrade never restores deleted rows; when a member leaves the organization, their name is removed from the record of opened pages.

Customers are responsible for choosing appropriate collection, masking, consent, and access settings. Do not send passwords, payment-card details, or sensitive personal information that is unnecessary for an investigation.

3. Why we use information

We use this information to provide access, correlate telemetry, investigate application problems, deliver notifications, create and synchronize tickets, answer support requests, protect the service, and understand its reliability and use.

Where European or UK data-protection law applies, our bases for processing account and website information are performing a contract or taking requested steps before a contract; legitimate interests in operating, supporting, improving, and securing the service; and complying with legal obligations. We rely on consent for optional waitlist invitations and launch updates. You can withdraw that consent by emailing us, without affecting earlier lawful processing.

Providing a waitlist email is optional, but we cannot send updates without it. Account information is needed to provide authenticated access. Customers establish the appropriate legal basis for information collected from their own users.

4. Slack, GitHub, Jira, and Linear

A customer chooses whether to connect their own third-party account and authorizes the permissions shown by that provider. Anectico uses the connection to perform the configured workflow: for example, sending a Slack alert, handling an alert action, creating an issue in GitHub, Jira, or Linear, or synchronizing a linked ticket’s status.

Those workflows transmit relevant content to the selected destination. A ticket or alert can include an error summary, application details, and links to Anectico. People who can access that destination may see the transmitted content under the provider’s permissions. Providers send Anectico events needed to handle interactions and synchronize status.

You can disconnect an integration in Anectico and revoke its authorization in the provider’s settings. Disconnecting stops Anectico from using that connection; it does not automatically erase existing tickets, messages, stored connection records, or historical events. Remove Jira’s separately configured admin webhook in Jira as well. Contact us to request deletion of retained integration information. Copies held by the provider are subject to that provider’s controls and policies.

5. Service providers and other recipients

Information is available to authorized members of your Anectico organization and to the service providers needed for the features you use. The current setup includes:

• Cloudflare: website delivery, security, and waitlist record storage.
• DigitalOcean: platform hosting and storage.
• Your chosen sign-in provider (if you use social sign-in): account authentication. Email-code sign-in is handled by Anectico.
• Cloudflare Email Sending: transactional email, including waitlist confirmations.
• Telegram: internal notifications containing waitlist signup email addresses.
• Google Fonts: website font delivery, which sends your browser’s network request information to Google.
• Connected services: the destinations you choose for notifications and tickets, such as Slack, GitHub, Jira, and Linear.
• Model provider for scoring: the provider of the small scoring model described in section 6. Contact us for current provider details.

We may also disclose information when required by law or when necessary to address fraud, abuse, security incidents, or legal claims. We do not sell personal information or use customer telemetry for targeted advertising.

6. AI agents and scoring

Anectico has no assistant or chat of its own. If you connect an AI agent through MCP or the CLI, the agent reads the data its key allows, and it sends what it reads to the model provider you chose for that agent. That provider is your choice and your responsibility, and its handling and retention depend on your agreement with it. Use scoped keys and your project’s content policy to limit what an agent can read.

Anectico itself uses a small scoring model for a few measurements, such as ranking detected anomalies, labeling repeated log patterns and judging how urgent an Issue is. It returns a score or a category that is stored as data. It writes no text and takes no action. What it receives follows your project’s content policy. If you configure automatic quality checks on your own AI agent’s runs, the recorded content your policy allows may be sent to an evaluation model to score each run.

Provider handling and retention depend on the selected provider and its applicable service terms. Contact us for the current provider details before sending sensitive material. An agent’s output can be inaccurate and should be checked against the original evidence, for example on a proof page. Anectico’s tools are not intended to make decisions about people that have legal or similarly significant effects.

7. Storage, retention, and deletion

Service providers may process information in countries other than yours. The locations and applicable transfer arrangements depend on the deployment and feature. Contact us for the current hosting locations, recipient details, and applicable transfer safeguards before submitting data with location or transfer restrictions.

Retention depends on the information and its purpose. We keep waitlist information while managing invitations and launch communications, or until you request removal. Account, support, and security records are kept while needed to provide access, resolve requests, investigate incidents, or meet legal obligations.

Customer telemetry retention depends on the data type, deployment, and configured retention controls. A limit on what can be queried is not a guarantee that every stored copy has already been deleted. Integration history and previously stored connection credentials are not automatically erased by disconnecting. Ask us for the current retention behavior or to arrange deletion; we will explain any information that must be retained and why. Copies held in connected services must also be managed there.

8. Cookies and browser storage

The Console uses cookies for authentication and browser storage for interface preferences. Hosting and security providers may use cookies or similar mechanisms to operate and protect the website. You can manage cookies in your browser; blocking authentication cookies prevents sign-in. The waitlist confirmation email is configured without open or click tracking.

9. Your choices and rights

Depending on applicable law, you may have rights to access, correct, delete, restrict, or receive a portable copy of personal information, and to object to certain processing. You can also withdraw consent for optional communications. Send requests to hello@anectico.com; we may need to verify your identity and authority before acting.

If the information belongs to a customer’s application, we will coordinate with that customer where appropriate. You may complain to your local data-protection authority. In Ireland, this is the Data Protection Commission.

10. Children

Anectico’s website and accounts are intended for adults using developer and business tools. We do not invite children to create accounts. Customers must assess their own obligations before collecting information about children through their applications.

11. Changes and contact

We will update this page when our practices change and identify the updated date. Where required, we will provide additional notice before a material change applies. Questions about this policy or our terms of service can be sent to hello@anectico.com.