Skip to content

Security & Trust

Built for confidential portfolio data.

Luceryn isolates every organisation's data at the database layer, encrypts it in transit and at rest, and keeps a deliberately small, transparent set of sub-processors. This page is a factual summary - including what's on our roadmap rather than already shipped.

One policy worth stating up front: we don't sell security as an upgrade. SAML SSO, SCIM, and MFA are included in every paid plan - Enterprise pricing covers data residency, dedicated infrastructure, and compliance work, never the lock on the door.

Tenant isolation

Every organisation is a separate tenant. All of it - projects, RAID, plans, documents and reports, CRM deals and contacts, RFP records, ITSM tickets and changes, meeting minutes, plus the user directory and templates - is isolated by PostgreSQL Row-Level Security (hundreds of policies enforced in the database, not just the UI). One customer can never see another's data.

Authentication & access

Sign-in via password or SSO (Microsoft / Google). Multi-factor authentication is supported and can be required per workspace. Inside the app, role-based permissions plus row-level security govern who can see and do what.

Data storage & encryption

Your data lives in a managed PostgreSQL database (Supabase, on AWS), with files in object storage, all in Canada. Everything is encrypted in transit (TLS) and at rest (AES-256), and the credentials for connected integrations are encrypted again before they are stored. The application servers (Vercel, also in Canada) run the code and hold no copy of your database.

Data residency

Luceryn runs in Canada. The database, sign-in records and uploaded files are stored in Supabase on AWS ca-central-1 (Montréal), and the application servers that process your requests run on Vercel in Montréal too. A few providers process specific data outside Canada: AI requests (Anthropic) and search embeddings (Voyage AI) in the United States, email delivery (Resend) and payments (Stripe), and Cloudflare at the network edge nearest each visitor. Integrations you connect run in their own locations. If your policy needs every step, including AI, to stay in Canada, ask us about a dedicated deployment.

AI transparency & your data

AI features are powered by Anthropic's Claude via its commercial API. We send only the specific text needed for the task you trigger - the transcript you paste, a proposal's fields, a project's details - never your whole database. Per Anthropic's commercial terms, your data is not used to train models or retained for training.

Semantic search (finding similar past projects and documents) sends project and document text to Voyage AI to generate vector embeddings; only the embeddings are stored, in your own database.

Every AI-written item is attributed to Luceryn and stays fully editable - you review and approve before anything is final. Admins can also switch a workspace to No-AI / manual mode, which turns off all AI calls entirely.

Confidential meetings

The AI Notetaker reads meeting transcripts from your own Microsoft 365 tenant via Microsoft Graph, only with the permissions your admin grants. The generated minutes are stored in your workspace, with configurable retention for minutes and transcripts.

No tracking

Luceryn wires in no analytics, advertising, or behavioural-tracking third parties. The complete sub-processor list is below - nothing else touches your data.

Sub-processors

ProviderPurposeData it processesLocation
Supabase (on Amazon Web Services)Database, authentication and file storageAll stored Customer Data and account data: projects, plans, RAID items, documents, files, messages, users and sign-in recordsCanada (AWS ca-central-1, Montréal)
VercelApplication hosting and content deliveryRequests and responses as they are processed; short-lived request logs (IP address, browser, path). Holds no copy of the databaseCanada (application functions in Montréal); static content is cached on Vercel's global network
CloudflareDomain name service, network protection and sign-in bot protection (Turnstile)Network traffic metadata (IP address, browser, request details) and the bot-protection challenge on sign-in and password resetGlobal network; traffic is handled at the data centre nearest the visitor
AnthropicAI features (Claude models)Only the specific text needed for the AI task a user starts (for example a pasted transcript or a project's details). Not used to train modelsUnited States
Voyage AISemantic search (finding similar projects and documents)Project and document text, converted into numeric embeddings; only the embeddings are stored, in your own databaseUnited States
ResendTransactional emailRecipient name and address and the content of service emails (invitations, notifications, minutes)United States
StripeSubscription billing and paymentsBilling contact, company and subscription details. Card details go directly to Stripe and are never stored by LucerynUnited States and other Stripe locations
Microsoft (Microsoft 365, Entra ID, Teams, Outlook, SharePoint)
Only when your organization turns it on
Sign-in, calendar, mail, meeting transcripts, Teams app and files, when your organization connects themOnly the items within the permissions your organization's administrator grantsYour organization's own Microsoft 365 region
Google (Google Workspace sign-in, Calendar, Gmail)
Only when your organization turns it on
Sign-in and calendar or mail features, when connectedOnly the items within the permissions grantedGoogle's locations under your organization's Google agreement
Slack, Atlassian (Jira), Salesforce, Asana, monday.com, ClickUp
Only when your organization turns it on
Integrations your organization chooses to connectThe records exchanged with the connected tool, within the scope grantedEach provider's own locations
Recall.ai
Only when your organization turns it on
Meeting notetaker bots, using your organization's own Recall.ai accountMeeting audio and transcripts for meetings the bot is invited toThe region your organization selects (United States or European Union)
Browser push services (Apple, Google, Mozilla, Microsoft)
Only when your organization turns it on
Desktop and mobile push notifications, when a user turns them onAn encrypted notification payload and the device's push addressEach browser vendor's locations

On our roadmap

We believe in being explicit about what is shipped versus in progress:

  • SOC 2 - pursuing Type I → II.
  • Independent penetration test + published report summary.
  • Data Processing Agreement (DPA) and signed sub-processor agreements.
  • Customer-managed encryption keys (BYOK) for enterprise.
  • Expanded regional data-residency options.

Already shipped: tenant isolation, encryption in transit + at rest, MFA, SSO, an admin audit log with CSV export, configurable data retention, a No-AI / manual mode, and Canadian hosting for every workspace.

Security questions or a vendor review? Contact us - we're glad to walk your team through the architecture.