Last updated: 2026-06-03
This page explains what personal data amoskalets.com processes while handling enquiries, client portal accounts, managed pilots, workflow automations, and platform operations. It is a practical operating notice, not a claim that every future compliance requirement is already implemented.
When you contact us, we collect the details you submit, such as name, email address, company name, and message content.
We use this information to reply, qualify the request, prepare a pilot or onboarding conversation, prevent abuse, and keep a basic record of the discussion.
If you create or use a client portal account, we process account identifiers, email address, authentication state, workspace membership, onboarding answers, tasks, artifacts, and related portal activity.
This data is used to provide the portal, show task status, manage workspace access, and keep project delivery records.
Managed pilots may process workflow inputs, webhook payloads, task instructions, integration metadata, uploaded or generated artifacts, and automation events needed to run the agreed workflow.
The exact data depends on the workflow scope agreed during onboarding. Do not send secrets or sensitive production data unless the workflow scope explicitly requires it and the handling approach has been agreed.
The platform records operational logs such as timestamps, route status, task and workflow events, error messages, IP-level request metadata, browser or session identifiers where used, and security or abuse-prevention signals.
Logs are used for reliability, debugging, security review, abuse prevention, backup verification, and operational health checks.
The platform may use infrastructure hosting, database, email delivery, monitoring, analytics, automation/orchestration, and AI model providers as processors or service providers.
For managed workflows, the specific processors can vary by implementation. We avoid publishing secrets, webhook URLs, and credentials, and we scope processor use around the agreed workflow.
Contact messages are kept while the enquiry is active and for a reasonable follow-up period after that.
Account, workspace, workflow, task, artifact, and log records are kept while needed to operate the service, support the client relationship, debug issues, preserve audit history, maintain backups, and meet operational or legal obligations.
Backups and logs may persist for a limited period after deletion from live systems because they are part of platform recovery and security operations.
You can ask for a copy, correction, or deletion of personal data associated with your contact request or account.
Some records may need to be retained where they are required for security, fraud prevention, operational audit, backup integrity, active service delivery, or legal obligations.
The site may use local storage, cookies, or analytics events to understand site usage and improve the product. The cookie banner lets visitors accept or decline non-essential tracking where the browser can store that preference.
For privacy, access, correction, or deletion requests, email andriimoskalec@gmail.com or use the contact form. Include the email address or workspace connected to the request so it can be located.