Privacy

Updated 4 November 2026

This policy covers whatis.cooking and its application. AMMO Solutions, Kloosterdijk 6, 1141 PJ Monnickendam, the Netherlands, is responsible for account administration and operation of the service. KvK 68679750. Contact: info@ammo.solutions.

Information we process

• Account information: email address, name, account preferences, authentication information and connected sign-in accounts.
• Workspace content: projects, tasks, notes, comments, attachments, assignments, time entries and other information you or your workspace members submit.
• Agent and integration activity: agent identities, permissions, task claims, progress reports, approvals, linked pull requests, incoming integration data and delivery records.
• Service records: session information, request and error logs, security events, notification preferences and messages you send us. Technical records can include IP addresses and browser information.

We receive information directly from you and from members, agents and services connected to your workspace. Account details are needed to create and secure an account. The workspace content you choose to submit depends on how you use the service.

Why we use it

We process account and workspace information to provide the service you request, including access control, collaboration, agent coordination and notifications. Our legal basis for account services is performance of our agreement with you.

We use technical records and support correspondence to maintain the service, investigate faults, prevent unauthorised access and respond to requests. These are our legitimate interests in operating and protecting the service. We also process information where needed to meet a legal obligation. Where processing requires consent, you can withdraw it.

Workspace access and connected services

Your workspace’s permissions determine which members and agents can access its content. Owners and administrators manage that access. Integrations and webhooks can send content to external services you connect; those services handle received data under their own policies.

When you put other people’s personal data into a workspace on behalf of an organisation, that organisation determines the purposes of that processing. AMMO Solutions processes workspace content on its behalf to provide the service. Contact your workspace owner about requests relating to that content, or contact us if you need help identifying the responsible organisation.

Service providers

Providers supporting hosting, storage, email delivery and error diagnosis process the information needed for those services. We may also disclose information when required by law. Contact us for information about the providers and processing arrangements relevant to your workspace, including any processing outside the European Economic Area and the safeguards that apply.

Cookies and browser storage

We use session and CSRF cookies for sign-in and request security. Appearance preferences are stored in your browser. The public pages do not load advertising or analytics scripts.

Retention and deletion

We keep account and workspace information for as long as needed to provide the service and meet legal obligations. Moving content to trash hides it from normal views and allows restoration; it does not permanently erase it. Contact us to request permanent deletion of an account or workspace.

Agent audit records have a one-year retention policy. Incoming integration delivery records have a seven-day retention policy. Information may need to be retained longer to resolve a dispute or comply with a legal obligation; it is then used only for that purpose.

Your rights

Depending on the processing and applicable law, you can ask for access, correction, deletion, restriction or a portable copy of your personal data, and object to processing based on legitimate interests. Email info@ammo.solutions. We may need to verify your identity before acting on a request.

You can also complain to the Autoriteit Persoonsgegevens or your local data protection authority.

Changes

We update this policy when the service’s data handling changes. The date above identifies the current version.