Enterprise pack · security information
Evidence first, with the gaps named plainly.
These are application controls evidenced by this checkout. Lookpost is intended for authorised, unclassified commercial information. Do not send restricted or classified material through the public journey or demo.
Repository-evidenced controls
What the application demonstrates
Authenticated and role-scoped access
Better Auth sessions protect customer routes, and administrator routes independently check the authenticated administrator role.
Organisation-scoped reads and writes
Workspace APIs resolve the caller’s organisation permissions and scope queries and mutations to that organisation.
Rate limits
App-owned mutation and integration routes use database-backed abuse keys and bounded rate windows.
Append-only security audit entries
Security events are recorded as application audit entries; best-effort logging is designed not to turn a successful customer action into a 500.
Server-mediated private uploads
Document uploads are authenticated and handled by server routes that mediate storage operations; the browser does not receive storage credentials.
Framework security headers and CSP
The template owns security headers, a strict script policy and CSP composition; app code uses the provided seams rather than weakening them.
Proxy-routed AI, email and payments
AI, email and hosted payment operations go through the Polsia proxies/modules rather than provider SDK keys in the app.
Provider-managed or unverified
Questions to resolve in scope.
- At-rest encryption, backups and infrastructure hardening are provider-managed or not independently verified by this repository review.
- Cross-instance authentication limiting and the complete retention/purge lifecycle are not independently verified here; agree those controls and retention requirements during scope review.
- This page is not a certification, endorsement, compliance statement or claim of classified suitability. Customer-side configuration, lawful basis and operating procedures remain in scope.
Keep demo and customer data separate.
Demo accounts, sample records, namespaces, storage keys and audit views are labelled illustrative and are isolated to the demo account. They are not customer records or evidence.