Loading Lithora...
Please wait
Loading Lithora...
Please wait
Security
Lithora holds your issues, your docs and a live connection to your code host. This page describes the controls that are actually implemented today — how sessions work, where the tenant boundary sits, what happens to deleted data, and which certifications we do not have.
Sessions & requests
The two most common ways a workspace gets taken over are a stolen token and a forged request. Both are closed at the transport layer, not by asking the interface to behave.
Browser sessions are carried in an HttpOnly, Secure, SameSite cookie. The session token is never written to localStorage, so it is not readable by page scripts and cannot be exfiltrated by a third-party snippet.
Every cookie-authenticated POST, PUT, PATCH and DELETE is checked against an Origin/Referer allowlist and rejected if it did not come from a Lithora front end. Token-authenticated calls from the API, CLI and SDK cannot be forged cross-site, so they pass through untouched.
Programmatic access uses personal access tokens you mint and revoke yourself. They are stored hashed, carry your own permissions, and never grant more than the account behind them.
All traffic runs over HTTPS. Integration credentials — OAuth tokens, webhook secrets, connector keys — are encrypted with an AES key held outside the database, and the server refuses to store them if that key is missing.
Boundaries
Access is decided per tenant, per role, and per link — and the read-only paths are as deliberate as the write ones.
Every read and write is scoped to the team it belongs to. Queries carry the tenant predicate at the data layer rather than relying on the UI to filter, so one workspace cannot see another’s work, files or activity.
Role-based access control governs who can administer a team, manage billing or change settings. The guest role is read-only and never billable — invite a client, an exec or a contractor without giving them write access or buying them a seat.
A public project link serves a read-only view with no login. It exposes project name, description and status plus task title, status, priority and due date — never member emails or internal ids. Links carry an optional expiry and can be revoked at any time.
Integrations
A work platform is only as safe as the traffic it accepts and the requests it makes on your behalf. Both directions are verified.
Inbound webhooks are signature-verified before a single byte is acted on — GitHub, GitLab, Bitbucket, Jira, Linear, Slack, Notion, Figma, Vercel, Cloudflare, deploy events and inbound email. A missing or wrong signature is a rejection, not a warning.
Any URL Lithora fetches on your behalf — an outbound webhook, an IdP metadata endpoint — is resolved and validated against private, loopback and link-local ranges first. The connection is then pinned to the validated address and redirects are refused, so a DNS rebind after the check cannot reach an internal host.
The AI agent stages write actions behind a confirmation gate and executes them under the permissions of the person who approved them. It cannot reach anything that person could not reach by hand.
Recovery & accountability
Deletion and automation are where trust is usually lost. Both leave a trail.
Deleting a task or a project is a soft delete. The item leaves every view immediately, stays restorable for 30 days, and is then hard-purged by a scheduled sweep. A mistake is recoverable; a deletion still means deletion.
Agent runs and administrative actions are recorded with what fired, when and what it proposed. Full audit logs are available on Scale.
Scale supports single sign-on over OIDC, plus SCIM 2.0 provisioning so joiners and leavers are handled by your identity provider instead of by hand.
Privacy
We do not sell or share your workspace data, and we do not use it for advertising. AI features send only the context needed to answer the request you made, and your content is not used to train models.
Read the full Privacy PolicyWe honour EU data-subject rights — access, export and deletion.
California privacy rights are honoured on the same request path.
Workspace data is separated per tenant at the query layer.
Export your workspace whenever you want. No exit tax, no hostage data.
What we do not claim
Plenty of products imply certifications they do not hold. Here is the honest list, so your security review does not have to discover it later.
Not certified. Lithora is in public beta and we will say so plainly until an audit is complete.
Not certified. We are not going to print a badge we have not earned.
Lithora is not designed for protected health information or cardholder data. Do not store it here.
Found something? Tell us directly. We read every report, we will not threaten you for disclosing responsibly, and we will tell you what we fixed.