Skip to content

Privacy

What Luota stores, why it is processed, and how to leave cleanly.

Last updated: April 30, 2026. This notice is written for B2B use of Luota as an operational monitoring service. It is not a substitute for a signed DPA where your procurement or compliance process requires one.

Data matrix

What data exists, why it exists, and where a customer can verify it.

Current controls only. No customer logos, certification claims, or hidden enterprise promises are implied by this matrix.

Control

Account and workspace

Current posture

Email, workspace name, membership, plan, billing state, and support context needed to run the account.

Proof surface

Settings, billing, workspace controls, DPA request path.

Owner

Luota controller

Control

Workflow evidence

Current posture

Monitor definitions, schedules, heartbeats, runs, payload JSON, snippets, incidents, and timeline events.

Proof surface

Monitor detail, incident detail, export, retention policy.

Owner

Customer controller

Control

Alert routing

Current posture

Channel names, delivery preferences, target membership, encrypted sensitive destination fields, and delivery attempts.

Proof surface

Alert routing, incident alert attempts, audit/export surfaces.

Owner

Customer controller

Control

Billing records

Current posture

Stripe customer/subscription state, invoices, plan limits, renewal or cancellation state, and legal accounting records.

Proof surface

Billing page, Stripe customer portal, invoice records.

Owner

Luota/Stripe

Control

Operational logs

Current posture

Request metadata, rate-limit counters, error telemetry, privacy-constrained page views, and Core Web Vitals samples.

Proof surface

Security posture, subprocessors, service diagnostics.

Owner

Luota ops

Control

Exit and deletion

Current posture

Workspace export is available; live data deletion is handled first, while encrypted backup expiry follows the backup retention window.

Proof surface

Export page, privacy request, DPA, backup retention note.

Owner

Luota + customer

Buyer record

Privacy review should connect to product, controls, and billing evidence.

Luota is pre-customer, so the commercial site shows product behavior, public controls, and buying mechanics directly. No invented testimonials, logo walls, or compliance claims.

Product record

Actual surfaces, not borrowed credibility

Inspect the dashboard, monitor detail, incident record, demo workspace, and deliberate failure drill before trusting the product.

Public controls

Controls and limits are public

Review the current security posture, privacy terms, DPA, subprocessor list, disclosure path, and live service status.

Billing state

Buying rules match product limits

Confirm workflow limits, retention, Stripe responsibility, cancellation behavior, and what changes after checkout.

Who is responsible

Luota is a founder-operated workflow monitoring service. For account, billing, and service operations data, Luota acts as controller. For workflow payloads, run output, monitor events, alert routing, and incident evidence sent by a customer workspace, Luota acts as processor for that customer.

Privacy, deletion, export, DPA, and security requests go to support@luota.dev. Customers that need formal legal-entity details for procurement receive them through the signed DPA and invoice process.

What Luota stores

Account and workspace data: email address, workspace name, workspace membership, active plan, billing state, and support messages.

Product data: monitor definitions, schedules, owner labels, runbook URLs, alert-channel configuration, heartbeats, runs, incident state, timeline events, deploy SHA, host/environment metadata, payload JSON, and output snippets.

Operational data: request metadata, rate-limit counters, application logs, error telemetry, Core Web Vitals samples, and privacy-constrained public page-view analytics used to operate and improve the service.

Why Luota processes it

Service delivery: to detect missed, failed, late, stuck, slow, or stale workflow events and show the related incident evidence.

Billing and account administration: to keep Stripe subscription state, invoices, plan limits, account access, password reset, and customer support working.

Security and reliability: to prevent abuse, rate-limit ingest endpoints, investigate errors, verify backups, and maintain service integrity.

Legal bases

Contract: account access, monitor storage, alerts, billing, support, retention, and export/delete handling needed to provide the service.

Legitimate interests: abuse prevention, rate limiting, security logging, service diagnostics, and privacy-friendly performance measurement.

Legal obligation: invoice, tax, accounting, and compliance records that Luota or its processors must keep.

Retention and deletion

Monitor evidence follows the active plan: 7 days on Free and 30 days on Operator unless a written agreement says otherwise. Downgrades apply the shorter retention window on the next retention sweep.

Daily encrypted Postgres backups follow the documented backup cadence. Deletion requests remove live workspace data first; encrypted backup expiry follows the normal backup retention window.

Stripe billing records and legally required accounting records may be retained for the period required by payment, tax, and accounting obligations.

Transfers and subprocessors

Primary application and database hosting is in the EU. Some processors operate outside the EU; those transfers rely on the processor's published safeguards such as SCCs, the EU-US Data Privacy Framework, or equivalent contractual measures.

The canonical subprocessor list is published at /subprocessors. A signed DPA is available at /dpa for customers that need Article 28 processor terms.

Open subprocessor list

Your rights

Depending on your role and jurisdiction, you may request access, correction, deletion, restriction, portability, or objection. Workspace customers can also request export of the workspace evidence Luota controls.

If your employer or customer controls the workspace data, Luota may route the request through that customer as controller. You can also contact your local supervisory authority.

For security posture and operational controls, read the public security page.

Open security posture