Legal
Privacy Policy
Last updated: October 20, 2026
1. Who we are and what this policy covers
Luceryn is an AI-native platform for project and portfolio management, client relationship management and IT service management, together with the website at luceryn.com (together, the “Service”). The Service is provided by AQ Professional Services Inc., a corporation incorporated under the laws of Ontario, Canada. In this policy, “Luceryn”, “we”, “us” and “our” mean that company and the Service it provides.
This policy explains what personal information we collect, why we collect it, how we use and share it, where it is stored, how long we keep it, how we protect it, and the choices and rights you have. It applies to:
- Users: people who sign in to a Luceryn workspace, including people invited by their organization.
- Customers: the organizations that hold a Luceryn subscription, and their administrators and billing contacts.
- Visitors and prospects: people who visit our website, join our waitlist, request a demonstration, contact us or attend an event with us.
- People named in workspace content: for example a stakeholder listed in a project plan, a contact in the CRM, or a participant in a meeting transcript.
This policy forms part of our Terms of Service. If your organization has signed a separate agreement or Data Processing Agreement with us, that agreement governs how we process the content your organization puts into the Service, and it prevails over this policy where they differ.
2. The short version
- Your organization decides what goes into its workspace. For that content, your organization is in charge and we process it on its instructions (see section 16).
- We collect what we need to run the Service: account details, the content you create, usage and security logs, billing details and the messages you send us.
- Your stored data lives in Canada: the database, sign-in records and files are in Montréal, and the application servers run in Montréal. Some providers, including our AI provider, process specific data in the United States (section 8).
- We do not sell personal information, we do not share it for cross-context behavioural advertising, and we do not set advertising or cross-site tracking cookies.
- AI features send only the text needed for the task you start. That data is not used to train AI models, and administrators can switch AI off for the whole workspace (section 5).
- You can ask to access, correct, export or delete your personal information, and you can complain to a privacy regulator (sections 11 to 13).
3. Information we collect
We collect information in three ways: you give it to us, it is created as you use the Service, and it comes from third parties such as your organization or a service you connect.
3.1 Account and profile information
Your name, work email address, job title, department, role in the workspace, profile photo if you add one, time zone, language, working days and capacity, and your password (stored only as a one-way hash by our authentication provider) or your single sign-on identity. If you set up multi-factor authentication or a passkey, we store the information needed to verify it, never the secret itself in readable form.
3.2 Workspace content (Customer Data)
Everything your organization and its users put into the Service: projects, portfolios, plans and tasks, risks, actions, issues and decisions, status reports, documents and their versions, files, comments and messages, timesheets and expenses, budgets, contracts and change orders, CRM accounts, contacts and deals, IT service tickets and assets, intake forms, meeting minutes and transcripts, and anything else you enter or upload. This content can include personal information about people other than you, such as colleagues, clients, vendors or stakeholders.
3.3 Usage, device and log information
When you use the Service we record security and operational information: sign-in events, the IP address and browser used, the time and outcome of requests, administrative actions (for example changing a user's role), an activity history of changes to records, AI usage and actions, and error reports. Our hosting and network providers keep short-lived request logs containing similar technical details. We use this to operate, secure and support the Service and to understand, in aggregate, how features are used.
3.4 Billing information
The billing contact's name, email and company, the plan and number of seats, invoices and payment status. Card numbers and bank details are entered directly with our payment processor, Stripe, and are never stored by Luceryn.
3.5 Communications and support
Messages you send us by email, through forms or in support conversations, and the details needed to answer them. If you join our waitlist or request a demonstration we keep your name, work email, organization and what you told us about your needs.
3.6 Information from integrations you connect
If your organization connects another service, such as Microsoft 365, Google Workspace, Slack, Jira or Salesforce, we receive the information that service shares within the permissions your administrator grants. For example: calendar events to match meetings to projects, mail your organization chooses to share with a project, meeting transcripts for the AI notetaker, files from SharePoint, or issues from Jira. Access tokens for these connections are encrypted before they are stored.
3.7 Information from your organization and other third parties
Your organization may create your account, invite you, assign your role or provision you automatically through single sign-on or SCIM from its identity provider (for example Microsoft Entra ID or Okta). Colleagues may mention you in comments or name you in workspace content. If you sign in with Microsoft or Google, we receive your name, email address and a unique identifier from that provider.
3.8 Information we do not seek
The Service is not designed to hold sensitive categories of personal information, such as health, biometric or financial account information or government identification numbers. Please do not enter such information unless your organization has agreed this with us in writing.
4. How we use information, and our legal bases
We use personal information only for the purposes below. Where the law requires a legal basis (for example under the GDPR), the basis we rely on is listed for each purpose. Under Canadian law we rely on your knowledge and consent, which may be implied by your use of the Service for these purposes, or on the exceptions the law allows.
| Purpose | Examples | Legal basis |
|---|---|---|
| Provide the Service | Create and run your account and workspace, store and display content, deliver the features you use, sync connected integrations | Performance of our contract; your organization's instructions |
| Security and integrity | Authenticate users, enforce permissions, detect and stop fraud, abuse, attacks and bots, keep audit trails, investigate incidents | Legitimate interests in a secure service; legal obligations |
| AI features you start | Draft a plan, summarize a meeting, suggest risks, answer a question in Ask Luceryn (section 5) | Performance of our contract; your organization's instructions |
| Support and service communications | Answer questions, send invitations, notifications, security alerts, billing notices and changes to the Service or these terms | Performance of our contract; legitimate interests |
| Billing and administration | Manage subscriptions, invoices, taxes and accounting records | Performance of our contract; legal obligations |
| Improve the Service | Understand in aggregate which features are used, find and fix defects, measure performance | Legitimate interests in improving the product, using aggregated or de-identified data where possible |
| Marketing | Send product news to people who opted in or with whom we have an existing business relationship | Consent, or legitimate interests where the law allows; you can opt out at any time |
| Legal and compliance | Respond to lawful requests, enforce our terms, establish or defend legal claims, keep records the law requires | Legal obligations; legitimate interests |
We may create aggregated or de-identified information that no longer identifies any person or organization, and use it for any lawful business purpose, such as improving the Service or publishing aggregate trends. We will not try to re-identify it.
We do not use workspace content to build advertising profiles, and we do not use it to train AI models.
5. AI features and automated processing
Many Luceryn features use artificial intelligence. Here is how they handle your information.
- What is sent. When a user starts an AI feature, we send our AI provider, Anthropic, only the text needed for that task, for example the transcript being summarized or the details of the project being planned. We do not send your whole database.
- No training. Under Anthropic's commercial terms, data sent through its API is not used to train its models. Anthropic may keep request data for a limited period to detect misuse, under its own commercial terms and policies.
- Permissions apply. AI features work inside the requesting user's own workspace and permissions. They cannot reach another organization's data, and they cannot see records the user is not allowed to see.
- People stay in charge. AI output is marked as AI-drafted and remains editable. Consequential actions are proposed for a person to approve, and administrators set how much each AI action may do on its own.
- Off switch. Administrators can turn on No-AI mode, which stops all calls to the AI provider for the workspace. Workspace AI guardrails can also block or mask chosen kinds of content before it is sent.
- Semantic search. To find similar past projects and documents, project and document text is sent to Voyage AI to create numeric embeddings. Only the embeddings are stored, in your own database.
- Meeting notetaker. If your organization turns it on, the notetaker reads transcripts from your own Microsoft 365 tenant, or uses your organization's own Recall.ai account, to draft minutes, actions, risks and decisions. Retention of transcripts and minutes can be configured by your administrator.
We do not make decisions about individuals based solely on automated processing that produce legal or similarly significant effects on them. AI suggestions, such as a staffing recommendation or a risk score, are inputs for people at your organization to review.
7. Service providers
We use a small number of carefully chosen service providers (sub-processors). Each processes personal information only to provide its part of the Service, under a written agreement that requires it to protect the information. The current list is below and on our Security page; we update it before adding a provider that processes Customer Data.
Used to run the Service
| Provider | Purpose | Information processed | Location |
|---|---|---|---|
| Supabase (on Amazon Web Services) | Database, authentication and file storage | All stored Customer Data and account data: projects, plans, RAID items, documents, files, messages, users and sign-in records | Canada (AWS ca-central-1, Montréal) |
| Vercel | Application hosting and content delivery | Requests and responses as they are processed; short-lived request logs (IP address, browser, path). Holds no copy of the database | Canada (application functions in Montréal); static content is cached on Vercel's global network |
| Cloudflare | Domain 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 reset | Global network; traffic is handled at the data centre nearest the visitor |
| Anthropic | AI 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 models | United States |
| Voyage AI | Semantic search (finding similar projects and documents) | Project and document text, converted into numeric embeddings; only the embeddings are stored, in your own database | United States |
| Resend | Transactional email | Recipient name and address and the content of service emails (invitations, notifications, minutes) | United States |
| Stripe | Subscription billing and payments | Billing contact, company and subscription details. Card details go directly to Stripe and are never stored by Luceryn | United States and other Stripe locations |
Used only when your organization turns on the feature or integration
| Provider | Purpose | Information processed | Location |
|---|---|---|---|
| Microsoft (Microsoft 365, Entra ID, Teams, Outlook, SharePoint) | Sign-in, calendar, mail, meeting transcripts, Teams app and files, when your organization connects them | Only the items within the permissions your organization's administrator grants | Your organization's own Microsoft 365 region |
| Google (Google Workspace sign-in, Calendar, Gmail) | Sign-in and calendar or mail features, when connected | Only the items within the permissions granted | Google's locations under your organization's Google agreement |
| Slack, Atlassian (Jira), Salesforce, Asana, monday.com, ClickUp | Integrations your organization chooses to connect | The records exchanged with the connected tool, within the scope granted | Each provider's own locations |
| Recall.ai | Meeting notetaker bots, using your organization's own Recall.ai account | Meeting audio and transcripts for meetings the bot is invited to | The region your organization selects (United States or European Union) |
| Browser push services (Apple, Google, Mozilla, Microsoft) | Desktop and mobile push notifications, when a user turns them on | An encrypted notification payload and the device's push address | Each browser vendor's locations |
8. Where information is stored and processed
Stored in Canada. The Luceryn database, sign-in records and uploaded files are stored with Supabase on Amazon Web Services in Montréal, Canada (AWS ca-central-1), and the application servers that process your requests run in Montréal as well. Backups of the database are kept in the same Canadian region.
Processed elsewhere for specific purposes. Some providers process particular information outside Canada, mainly in the United States: AI requests (Anthropic), semantic-search embeddings (Voyage AI), email delivery (Resend) and payments (Stripe). Our network provider, Cloudflare, handles traffic at the data centre nearest each visitor. Integrations your organization connects process information in their own locations. Where information is processed in another country, it may be accessible to that country's courts, law enforcement and national security authorities under its laws.
Safeguards. We transfer personal information across borders only with contractual safeguards that require the recipient to protect it to a standard comparable to this policy and to the law that applies to it. For personal information from the European Economic Area, the United Kingdom or Switzerland, we rely on the adequacy decision for Canada where it applies and otherwise on the European Commission's Standard Contractual Clauses (with the UK addendum where relevant) or another lawful mechanism. Before transferring personal information of Québec residents outside Québec, we assess the privacy impact of the transfer as Québec law requires.
If your organization needs all processing, including AI, to remain in Canada, contact us about a dedicated deployment.
9. How long we keep information
We keep personal information only for as long as we need it for the purposes in this policy, or as long as the law requires. Specifically:
| Information | How long |
|---|---|
| Workspace content | For as long as your organization's subscription is active, or until it is deleted by a user or administrator. Your administrators control most deletion and can set retention for items such as meeting minutes and transcripts. |
| Deleted projects and documents | Held in an archive for 30 days so they can be restored, then permanently deleted. |
| Account and profile information | While the account exists. Deactivating a user removes their access and keeps the history of what they did, which your organization needs for its own records; the account is deleted with the workspace or on request. |
| Audit, activity and security logs | For as long as needed to secure the Service and meet your organization's audit needs, and no longer than the life of the workspace, except where a log is needed to investigate an incident or a legal claim. Provider request logs are kept for a short period by the provider. |
| After a subscription ends | Workspace content is deleted or de-identified within a reasonable period after the subscription ends and any export window has passed, unless the law requires us to keep it longer. Deleted data may remain in backups until those backups expire on their normal cycle. |
| Billing and tax records | For as long as tax and accounting law requires (in Canada, generally six years after the end of the relevant tax year). |
| Support and communications | For as long as needed to resolve the request and keep a reasonable record of it. |
| Waitlist, demo and marketing contacts | Until you unsubscribe or ask us to delete them, or when they are no longer relevant. |
10. How we protect information
We protect personal information with administrative, technical and physical safeguards appropriate to its sensitivity, including:
- Encryption in transit (TLS) and at rest, and separate encryption of stored integration credentials.
- Isolation of every organization's data at the database layer with row-level security, tested on every release by an automated cross-tenant check.
- Role-based permissions, multi-factor authentication that an organization can require for all its users, single sign-on (SAML and OIDC) and SCIM provisioning.
- Bot protection on sign-in and password reset, a check of new passwords against known breached passwords, and session controls.
- Administrative and financial audit logs, and optional streaming of security events to your organization's own security information and event management (SIEM) system.
- Restricted, logged access to production systems; recurring security testing; and providers chosen for their security practices.
No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If a breach of security safeguards involving personal information creates a real risk of significant harm, we will notify the affected organizations and, where the law requires, the affected individuals and the regulators, as soon as feasible, and keep a record of the breach as required by law. More detail is on our Security and Trust Center pages.
11. Your privacy rights
Depending on where you live, you may have some or all of the following rights over your personal information:
- Access: to know whether we hold personal information about you and to receive a copy of it, together with how it is used and to whom it has been disclosed.
- Correction: to have inaccurate or incomplete information corrected. You can update most profile information yourself in the Service.
- Deletion: to have personal information deleted, subject to the exceptions the law allows (for example records we must keep for tax purposes).
- Portability: to receive personal information you provided in a structured, commonly used and machine-readable format. Most registers in the Service also export to Excel or CSV.
- Withdraw consent: where we rely on consent, to withdraw it at any time, without affecting processing that already took place.
- Object or restrict: to object to, or ask us to limit, certain processing, including processing based on legitimate interests and direct marketing.
- Complain: to complain to a privacy regulator (section 12).
We will not discriminate against you for exercising any of these rights.
12. Additional information for your region
Canada
We handle personal information in line with the Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable provincial private-sector privacy laws. We have designated a Privacy Officer who is accountable for our compliance (section 20). If you are not satisfied with our response, you can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or, where it applies, to the privacy commissioner of your province.
Québec
If you are in Québec, you have the rights set out in the Act respecting the protection of personal information in the private sector, as amended by Law 25, including the right to be informed of the use of technology that can identify, locate or profile you (Luceryn does not use such technology to profile individuals), and the right to request portability of computerized personal information you provided. The person in charge of the protection of personal information is our Privacy Officer (section 20). You can complain to the Commission d'accès à l'information du Québec (cai.gouv.qc.ca).
European Economic Area, United Kingdom and Switzerland
Where the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection applies, Luceryn is the controller of account, billing, website and prospect information, and acts as a processor for Customer Data on behalf of your organization (section 16). The legal bases we rely on are in section 4, and international transfers are described in section 8. You have the rights in section 11 and you may also complain to the data protection authority in the country where you live, work or believe an infringement occurred.
United States
Residents of California and of other states with comprehensive privacy laws may have the right to know the categories and specific pieces of personal information we collect, use and disclose; to correct and delete it; to opt out of its sale, sharing for cross-context behavioural advertising, and certain profiling; and to limit the use of sensitive personal information. We do not sell or share personal information, we do not use sensitive personal information for purposes that require an opt-out, and we treat a browser's Global Privacy Control signal as a valid opt-out request. You may use an authorized agent; we will ask the agent for proof of your authorization and may ask you to verify your identity. If we deny your request, you may appeal by replying to our decision, and we will explain the outcome of the appeal.
During the past twelve months, Luceryn collected the following categories of personal information, for the purposes in section 4: identifiers (such as name, email address and IP address); professional or employment-related information (such as job title and role); commercial information (such as plan and billing history); internet or network activity (such as sign-in and usage logs); and the content of communications and files your organization places in the Service. We disclosed them only to the recipients described in sections 6 and 7, for business purposes.
13. How to make a request
Workspace content. Because your organization controls the content in its workspace, please send requests about that content to your organization's Luceryn administrator first. We will help your administrator respond, and if a request comes to us directly we will pass it to your organization where the law allows.
Everything else, including your account, billing, website and marketing information: email [email protected]. Tell us what you are asking for and how we can reach you.
We will confirm your identity before acting, usually by asking you to reply from the email address on the account. We aim to respond within 30 days, and will tell you if we need more time and why, as the law allows. Requests are free of charge unless they are clearly excessive or repetitive.
15. Communications from us
We send service communications, such as invitations, notifications you have turned on, security alerts, billing notices and important changes to the Service or our terms. These are part of operating your account and you cannot opt out of them while you hold one, though you can choose which notifications you receive in your settings.
Separately, we may send marketing messages about Luceryn to people who have agreed to receive them or with whom the law allows us to communicate. Every marketing message includes an unsubscribe link, and we honour opt-outs promptly in accordance with Canada's Anti-Spam Legislation (CASL), the CAN-SPAM Act and other applicable law.
16. Your organization's role and ours
For Customer Data (the content your organization and its users put into the Service), your organization is the controller (or the organization with control of the information), and we process it on your organization's behalf and on its documented instructions, as set out in our Terms of Service and any Data Processing Agreement. Your organization is responsible for having the right to collect that information and to put it into the Service, and for answering requests from the people it concerns.
For account and profile information used to run your account, billing information, website and prospect information, and information we need to secure and improve the Service, we decide how and why it is used and this policy applies directly.
Organizations can request our Data Processing Agreement by writing to [email protected].
17. Children
The Service is designed for business use by people aged 18 or over and is not directed at children. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will delete it.
18. Third-party sites and integrations
The Service and our website link to, and can connect with, services we do not operate. When you follow a link or your organization connects an integration, that provider's own privacy policy and terms apply to what it does with information. We are not responsible for their practices, so we encourage you to read their policies.
19. Changes to this policy
We may update this policy as the Service, the law or our practices change. We will post the new version here and change the date at the top. If a change is material, we will give notice by email or in the Service before it takes effect, and where the law requires your consent to a change, we will ask for it. Your continued use of the Service after a change takes effect means you accept the updated policy, to the extent the law allows.
20. Contact us
Questions, requests or complaints about this policy or our handling of personal information can be sent to our Privacy Officer, who is accountable for our compliance and is the person in charge of the protection of personal information under Québec law:
We will try to resolve any concern you raise with us. You also have the right to complain to the privacy regulator for your location, as described in section 12.