Privacy notice

What we collect

We collect only what the pilot needs to answer you and to run the service:

• Pilot requests: email address, company or team name, and the workflow you describe
• Accounts: email address, organization name, a salted password hash, seat identifiers
• Operations: timestamps, seat identifiers, message metadata and error records needed to deliver work
• Billing: none. The pilot does not process payments

Why we hold it

Pilot requests are used to reply and to scope a first integration. Account data is used to authenticate you and to run your seats. Operational records exist so a message can be delivered, retried, or explained after an incident. We do not sell personal data and we do not use it to train models.

Cookies and tracking

The site sets one session cookie after sign-in. It is HttpOnly, SameSite=Lax, and is not used for advertising. The public pages load no third-party analytics or tracking scripts today. If that changes, this notice changes first.

Who else sees it

We use a hosting provider for the service and an email provider for verification and recovery messages. They process data on our instructions. We disclose data otherwise only when the law requires it, and we tell you unless we are barred from doing so.

Retention and your choices

Pilot requests are kept while the pilot conversation is active. Operational records are kept as long as needed to run and audit the service. You can ask for a copy, a correction, or deletion of your personal data at any time by writing to [email protected]; we answer within 30 days.

Where data is processed

The operator is based in the Republic of Korea and the pilot service is hosted in the European Union. Access is limited to the operator and the processors named above. If you need a specific region for a pilot, say so before the integration is scoped.

Contact

Privacy questions and requests: [email protected]. This notice was last updated on 3 November 2026.