Privacy notice

Scope

This notice covers Syllecta's public website, documentation, registration flow, customer console, and managed webhook/idempotency services. If a customer signs a separate agreement, that agreement controls where it conflicts with this public notice.

Information we collect

• Registration and contact details such as name, email, workspace name, provider stack, support context, referral/source fields, and internal follow-up status.
• Console account details such as user name, email, role, tenant, and authentication metadata.
• Operational product data such as webhook metadata, usage counters, callback status, and diagnostic logs.
• Tenant configuration such as callback URLs, provider names, API key metadata, webhook secret metadata, retention settings, and billing/support settings.
• Technical data such as IP address, user agent, timestamps, and security or rate-limit signals.

How we use information

We use this information to create and verify accounts, respond to contact requests, operate the product, protect accounts, investigate delivery failures, improve reliability workflows, and communicate about support.

Webhook and payload data

When a tenant configures Syllecta to receive webhook traffic, the service processes operational metadata such as provider, event id, delivery status, callback status, retry state, timing, error context, and correlation ids. Payload content may be processed and temporarily stored when needed to verify, deliver, replay, search, or debug the event flow.

Syllecta is designed to minimize customer data exposure. Sensitive fields such as card data, passwords, access tokens, session cookies, long-lived secrets, or unnecessary personal data should not be submitted unless they are required for the configured workflow.

Sharing and retention

We do not sell registration, contact, or product data. We may use service providers and internal operators who need access to run the product, support customers, send operational email, host infrastructure, maintain security, or investigate abuse.

Operational retention is documented in the Data retention guide. Financial ledger records, audit logs, tenant records, users, API keys, webhook secrets, settings, and plans are handled under separate legal/accounting or offboarding decisions.

Cookies and analytics

Syllecta uses necessary cookies for console authentication and session security. Analytics or marketing cookies should not be enabled without updating the Cookie notice and showing any consent controls required for the target launch region.

Requests and contact

To ask about deletion, access, correction, or privacy questions, contact support@syllecta.com. Security-sensitive reports can be sent to security@syllecta.com.