At a glance
A plain-language guide
This summary helps you navigate the policy. It does not replace the complete policy below.
- UseEventStack processes organisation-scoped operational event data and account information needed to provide the service.
- Do not send passwords, private keys, session tokens, full payment-card data, or other secrets in event payloads.
- Stripe-hosted pages handle payment-card entry. UseEventStack does not store full payment-card numbers.
- The current dashboard uses browser storage, including local storage, for session or organisation state.
1. Scope and service status
This Privacy Policy applies to useEventStack websites, dashboards, APIs, SDKs, support channels, and related services. UseEventStack is a SaaS platform under active development. Its available functionality can change as the product develops.
- Customer
- The organisation that creates a workspace or otherwise receives the service.
- Authorised user
- A person permitted by a Customer to use the service.
- Event data
- Operational facts, payloads, metadata, traces, graphs, projections, and workflow records submitted to or generated within the service.
2. Information we handle
We handle information you provide directly, information generated while operating the service, and limited technical information needed to secure and support the service.
| Category | Examples and purpose |
|---|---|
| Account and organisation data | Names, email addresses, organisation details, role and membership information used to provide access and support. |
| Service data | Custom event contracts, event payloads, workflow execution records, traces, event graphs, projections, sandbox activity, replay requests, API-key metadata, and dashboard settings. |
| Support and communications | Messages and context supplied when you contact us or request help. |
| Technical data | Browser, device, request, security, and diagnostic information used to operate, troubleshoot, and protect the service. |
| Billing data | Subscription and billing identifiers received from Stripe. Payment-card entry is handled by Stripe-hosted pages. |
3. How we use information
- Provide organisation-scoped event ingestion, custom event contracts, workflow execution, traces, event graphs, projections, sandbox testing, and replay features.
- Authenticate users, manage organisation access, issue and manage API keys, and maintain dashboard surfaces.
- Operate public status and changelog projections when a Customer has chosen to publish them.
- Provide support, investigate errors or abuse, meet legal obligations, and improve the service.
- Process billing through Stripe-hosted checkout and billing portal pages.
4. Browser storage and cookies
The current dashboard uses browser storage, including local storage, to retain session or organisation state and support the dashboard experience. Your browser may also store information needed to keep you signed in, remember preferences, or protect service interactions.
You can control browser storage through your browser settings. Removing it can sign you out, clear your selected organisation, or affect dashboard functionality.
5. When information is shared
We may share information with service providers that support hosting, email delivery, payment processing, diagnostics, and customer support, only as needed to operate the service. We may also disclose information when required by law, to protect the service and its users, or in connection with a business transaction.
We do not sell event payloads or personal information. Customers control whether their own public status and changelog projections are made public.
6. Retention and security
We retain information for as long as reasonably necessary to provide the service, meet legal or billing obligations, resolve disputes, and protect the service. Retention controls and deletion workflows may be available in dashboard governance surfaces, but UseEventStack does not represent the service as a complete compliance or enterprise retention solution.
We use measures intended to protect information, but no system is completely secure. Please report suspected security issues to security@useeventstack.com and do not include secrets in an initial report.
7. Your choices and contact
You may contact us about access, correction, deletion, export, or privacy questions. Requests may require verification and can be limited where applicable law permits. Organisation administrators should use dashboard governance controls where available before requesting assistance.
Email privacy supportFor privacy, export, or deletion questions, contact support@useeventstack.com.