Guardrails before automation

Loresta is designed around least privilege, tenant isolation, and auditable actions.

Social access

Connections use provider OAuth. Access and refresh tokens are encrypted with AES-GCM, scopes are recorded, and capabilities are independently gated so a connection never implies unlimited action.

Workspace isolation

Every dashboard query and mutation is bound to an authenticated workspace membership. Sensitive changes require same-origin requests, CSRF validation, role checks, and rate limits. Delivery jobs use idempotency keys and conditional claims to prevent duplicate sends.

Automation safety

Automated messaging is inbound-only by default. Explicit, payment, legal, safety, minor-related, and other sensitive requests are handed to the owner. Automatic sends remain disabled until provider review and workspace approval are both confirmed.

Operational evidence

Publishing, replies, policy changes, connection changes, and handoffs produce audit records and delivery receipts without copying access tokens into logs.

Report an issue

Send security reports to security@loresta.co. Include the affected URL and a concise reproduction without sharing private fan data.