Privacy Policy
Last updated:
- We use your information to run Crewdle for you, keep it secure and bill for it. We do not sell it, and we do not use your content to train AI models.
- The Crewdle website and platform are hosted in Canada. Your organization's data is stored in the region chosen when it was created: Canada, the United States or the European Union. Some services, including the AI models, run outside that region; this page lists them.
- We count visits with our own cookieless counter, and we do not use Google Analytics or advertising pixels. The few browser items we use are listed in Cookies and browser storage (section 10).
- You can access, correct, export or delete your information. Write to support@crewdle.com.
1. Who we are
Crewdle is operated by Crewdle Technologies Inc. ("Crewdle", "we", "us"), 3 Place Ville Marie #400, Montreal, Quebec, H3B 2E3. This policy covers the website crewdle.com, the sign-in portal auth.crewdle.ai, the Crewdle apps (including Connect, Chat, Build, Create, Forge, Arena and Admin), the Crewdle desktop app and the Crewdle API (the "Services").
Person in charge of the protection of personal information: Vincent Lamanna, CEO, support@crewdle.com, 3 Place Ville Marie #400, Montreal, Quebec, H3B 2E3.
2. Our role
- We decide how your information is used (we are the "controller") for your account, the website, sign-up, billing, security and our own analytics.
- For the content an organization puts into Crewdle (conversations, files, memory, data from connected services), we act on that organization's behalf and according to its instructions (we are its "service provider" or "processor"). The organization decides what goes in and who can see it. If you are a member of an organization, its administrators can access the organization's content, and you may want to read its own privacy notice. Our data processing terms are available on request.
3. What we collect
| Category | Examples | Where it comes from |
|---|---|---|
| Account | Name, email address, profile photo, password (stored by our sign-in provider, never readable by us), sign-in method (email, Google, Microsoft), language and theme, the organizations you belong to, the date you accepted these terms. | You, or Google or Microsoft if you sign in with them |
| Phone number | The mobile number you verify by SMS before creating an organization. | You |
| Organization | Organization name, region, members and their roles, budgets, settings, billing address and tax number. | Administrators |
| Content | Messages, chats, files, instructions, agent outputs and deliverables, apps built with Build, recordings and transcripts, and the personal information these may contain about you or other people. | You, your organization and your agents |
| Memory | Notes that you, your organization or a project keep so agents remember context, and the search vectors computed from them. | You, your agents, and an automatic pass after replies (see section 5) |
| Agent email | Emails sent to an agent's address (sender, recipients, subject, body, attachments). | The people who write to your agents |
| Connected services | Access tokens and the data agents read or write in the services you connect (for example email, calendar, files, CRM, online store, accounting). | The services you connect |
| Payment | Payment card type, last four digits and expiry date, purchases, invoices, balance. The full card number is held only by Stripe. | You and Stripe |
| Usage and billing | For each AI request: which agent and product, the model, the amount of work (for example tokens) and its cost. These records never contain the text of prompts or replies. | The Services |
| Sign-up attribution and referrals | How you first found Crewdle: campaign (for example utm_source), referring website, landing page, and the referral code you used. Never the full referring address or advertising click identifiers. | Your browser, when you sign up |
| Technical and security data | IP address, browser and device type, pages viewed, approximate location derived from the IP address (country, region and city), bot and fraud signals, error and performance data, server logs. | Your device and our servers |
| Communications | Messages you send to our support, to the website chat or through our contact forms. | You |
| Feedback | Your answers to short in-product surveys (for example about your first result) and, if you stop paying, the reasons you give. Stored without your name. | You |
Do not put sensitive information (for example health, financial account or government identification data) into Crewdle unless it is needed and your organization allows it. Memory is designed to refuse passwords and personal, health, HR and legal details.
4. How we use it
| Purpose | Information used | Legal basis (GDPR) |
|---|---|---|
| Provide the Services: sign-in, run agents and chats, store content, connect services, send the emails the product needs | Account, organization, content, memory, agent email, connected services | Contract |
| Bill and collect payment, apply taxes, keep accounting records | Organization, payment, usage and billing | Contract; legal obligation |
| Prevent abuse and fraud: phone verification, one free sign-up grant per person, referral checks, bot protection, rate limits | Phone number, email address, IP address, technical and security data | Legitimate interests (protecting the Services and our users) |
| Keep the Services secure and working, investigate problems | Technical and security data, usage records, logs | Legitimate interests; legal obligation |
| Measure and improve the website and the Services | Our cookieless counts and experiments; survey answers and stop-paying reasons; with your consent where required, the attribution items in section 10 | Legitimate interests; consent (attribution cookies) |
| Know which channels bring sign-ups and pay referral rewards | Sign-up attribution and referral data | Legitimate interests; contract (referral program) |
| Send product updates, tips and offers | Name, email address, language, product use | Consent or legitimate interests, as the law allows; you can unsubscribe at any time |
| Answer you and provide support | Communications, account | Contract; legitimate interests |
| Comply with the law and enforce our terms | Any relevant category | Legal obligation; legitimate interests |
We do not sell your personal information, and we do not share it for targeted advertising.
5. AI and your content
- No training. We do not use your content to train AI models. We use AI providers' business APIs, whose terms exclude training on the data they receive.
- What the model receives. When you or an agent ask for an answer, our AI gateway sends the model provider the context needed for that request: the message, relevant history, files and memory. It checks budgets and permissions first. Nothing is sent in the background or in bulk.
- Private AI mode. An agent or workflow in private AI mode can only use models the provider runs with zero data retention. The model still runs on the provider's infrastructure. Image, video and speech tools are not covered.
- AI guardrails. If your organization turns on AI guardrails, the text of messages and replies is checked by Fireraven, in Canada, whatever your region. Fireraven keeps the checked text for monitoring and does not train on it.
- Memory. After a reply, an automatic pass may save useful facts to memory. Memory refuses passwords and personal, health, HR, legal and client-confidential details. You can review, edit and delete notes; administrators cannot see members' personal notes.
- Automated decisions. Crewdle does not make decisions about you that have legal or similarly significant effects based solely on automated processing. If your organization uses agents to make decisions about people, it is responsible for informing them and providing human review.
6. Where your information is stored
The Crewdle website and platform are hosted in Canada. When an organization is created, it chooses a region for its data: Canada, the United States or the European Union. The region cannot be changed later. See also Data residency.
| Region | Database, files and back-end | Agents, AI gateway and knowledge search |
|---|---|---|
| Canada (default) | Montréal | Montréal |
| United States | Database: several US data centres; files and back-end: Northern Virginia | Northern Virginia |
| European Union | Frankfurt | Frankfurt |
Some information is processed outside your organization's region:
- Global, in Canada: your sign-in identity and profile (name, email, phone, preferences), sign-up attribution, referral and anti-abuse records, survey answers and stop-paying reasons (stored without names), our cookieless analytics, and a directory entry per organization (name and region).
- AI models: run on the providers' infrastructure, mostly in the United States, whatever your region.
- Real-time connection service: presence and file-transfer signals for organizations in Canada and the United States are processed in the United States (Iowa).
- AI guardrails: Canada, for every region.
- Other services: email delivery, payments, web browsing for agents and server logs run where those providers operate, mostly in the United States.
Transfers. When information leaves Quebec, Canada or the European Union, we first assess the risks, and we require the recipient to protect it by contract (for transfers from the EU: the European Commission's standard contractual clauses or an equivalent mechanism). Information processed in another country may be accessible to that country's authorities under its laws.
7. The companies we work with
We share information only with service providers that need it to run the Services, under contracts that limit their use of it to that purpose, and as required by law. The current list:
| Provider | What it does for us | Location |
|---|---|---|
| Google Cloud and Firebase | Hosting, database, file storage, back-end, sign-in, SMS verification, bot protection (reCAPTCHA), push notifications, logs | Your region; sign-in and logs global |
| Amazon Web Services | Agent runtime, AI gateway, knowledge search, encrypted agent storage; AI models through Amazon Bedrock (Anthropic Claude, OpenAI, Cohere embeddings) | Your region; Bedrock models may run in other AWS regions |
| Anthropic | Claude models | United States |
| OpenAI | GPT models, embeddings, transcription, images | United States |
| Google (Vertex AI) | Gemini models, images, video | Global |
| OpenRouter | Access to other models you choose (for example Mistral, Meta, xAI, DeepSeek) | United States; the model's provider may be elsewhere |
| Perplexity, Brave | Web search for agents | United States |
| Browserbase, Firecrawl | Web browsing and page reading for agents, saved website logins you choose to keep | United States |
| ElevenLabs | Text-to-speech | United States |
| Runway | Video generation | United States |
| Google Maps Platform | Places and maps for agents | Global |
| Fireraven | AI guardrails, if your organization turns them on | Canada |
| Twilio SendGrid | Sending email, and receiving email for agent addresses | United States |
| Twilio | Call connectivity in Connect, phone calls handled by agents | United States |
| Stripe | Payments, invoices, sales tax, partner payouts | United States |
| Microsoft | Microsoft sign-in and Microsoft Teams integration | Global |
| GitHub | Code hosting and deployment of our apps | United States |
We may also disclose information: to a successor if Crewdle is merged or sold, with notice to you; to professional advisers under confidentiality; or when the law requires it, to protect someone's safety, or to defend our rights. If you belong to an organization managed by a Crewdle partner (reseller), the partner can see and manage that organization, and Crewdle staff can access an organization to provide support; every such access is logged.
8. Services you connect
When you connect a service (for example Google, Microsoft 365, Slack, Shopify, HubSpot, Zoho or Xero), we store an access token and your agents read or write data in that service as you instruct. That data stays subject to the service's own privacy policy. You can disconnect at any time; we then revoke the access where the service allows it and delete the token.
Google user data. Crewdle's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features you request, we do not use it for advertising, we do not sell it, and we do not use it to train AI models.
9. Analytics and experiments
- Our own cookieless analytics. We count page views and visits with our own counter. It stores nothing on your device and uses no third-party analytics service. We explain how we count visits without cookies on our blog.
- Visitor number: computed from your IP address and browser type with a key that changes and is deleted every day, so visits cannot be linked from one day to the next.
- Location: when a visit is recorded, we look up its approximate location (country, region such as a province or state, and city) in the DB-IP Lite database. The IP address itself is never stored, and city locations are rounded to about 10 km (0.1°). IP geolocation by DB-IP, licensed under CC BY 4.0.
- Who sees it: Crewdle administrators only. The real-time view can show a city with a single visitor; views over a period hide places with fewer than 5 visitors.
- Where and how long: in Canada. Individual visit records are kept for 13 months; totals by day, page or place are kept without a time limit and contain no information about individuals.
- Experiments. When we test two versions of a website page, our server picks the version from the daily visitor number above; nothing is stored on your device. If you then sign up, the experiment's id and the name of the version you saw (nothing else) travel with the record of how you first found Crewdle.
- Feedback. Answers to our short in-product surveys (for example about your first result) and the reasons you give when you stop paying are stored without your name, in Canada, whatever your organization's region.
- We do not use Google Analytics, session recording or advertising pixels. The browser items we do use, and your choices, are in section 10.
10. Cookies and browser storage
- Most of what we store in your browser keeps you signed in, keeps you secure or remembers a choice you made, such as your language or theme. These are strictly necessary.
- A few items measure how our website and apps are used. We ask for your consent before using those where the law requires it.
- We do not use advertising cookies, and we do not sell your personal information.
This section explains the cookies and similar technologies (local storage, session storage and IndexedDB) used by Crewdle on crewdle.com, on the sign-in portal auth.crewdle.ai and in the Crewdle apps on *.crewdle.ai.
What these technologies are
A cookie is a small text file a website stores in your browser. Local storage, session storage and IndexedDB are similar places in your browser where a site can keep data. Session storage is erased when you close the tab. "First party" means the item belongs to the site you are visiting; "third party" means it belongs to another company.
The categories we use
- Strictly necessary: sign-in, security, fraud and bot protection, and features you asked for. The service does not work without them, so they do not require consent.
- Preferences: remember choices you made, such as language and theme.
- Measurement and testing: help us understand where visitors come from and attribute sign-ups to the people who refer them. These are not necessary, and we ask for your consent where the law requires it.
We do not use advertising or cross-site profiling cookies, Google Analytics or session recording.
crewdle.com (our website)
crewdle.com shows no cookie banner because it sets no non-essential cookies: our website sets no cookies at all. What it keeps in your browser is strictly necessary (resending a form) or functional (your language, blog and venue preferences), plus two session-storage items that remember the campaign you arrived from and are erased when you close the tab.
| Name | Type and party | Purpose | Duration | Category |
|---|---|---|---|---|
crewdle_lang | Local storage, first party | Remembers the language you chose (English or French). | Until you clear it | Preferences |
crewdle_blog_prefs, crewdle_blog_full_article | Local storage, first party | Remembers your reading settings on the blog. | Until you clear it | Preferences |
crewdle-venue-profile, crewdle-venue-look-hint, crewdle-venue-chatter | Local storage, first party | Remembers the name, colour and hints you chose in the 3D venue. | Until you clear it | Preferences |
crewdle_intake_queue | Local storage, first party | Keeps a form you submitted so it can be sent again if the connection failed. | Up to 3 days | Strictly necessary |
crewdle_campaign | Session storage, first party | Remembers the campaign link you arrived from (for example utm_source) so we know which campaigns bring visitors. | Until you close the tab | Measurement and testing |
crewdle_src | Session storage, first party | Remembers how you first found Crewdle (campaign, referring site, landing page), so that if you create an account we know which channel brought you. It never contains your name or email. | Until you close the tab | Measurement and testing |
Website experiments (testing two versions of a page) use a variant chosen on our server from the daily visitor number described in section 9 above, with no cookie or storage on your device.
Our page counter (/pulse.js) counts page views without any cookie, storage or identifier on your
device. See "Our own cookieless analytics" in section 9 above.
The chat window on the website sends your messages to our servers to generate an answer. It does not store anything in your browser.
auth.crewdle.ai (sign-in) and the Crewdle apps (*.crewdle.ai)
| Name | Type and party | Purpose | Duration | Category |
|---|---|---|---|---|
__session | Cookie, first party, HTTP-only, on auth.crewdle.ai | Keeps you signed in to Crewdle, so one sign-in works for every Crewdle app. | Up to 14 days | Strictly necessary |
__session (store link) | Cookie, first party, HTTP-only | When you connect a Shopify store, links the installation to your Crewdle account. It holds a random single-use key. | 30 minutes | Strictly necessary |
crewdle_known | Cookie, first party, on .crewdle.ai | Remembers that someone has already signed in from this browser, so we show "Sign in" instead of "Sign up". It does not identify you. | 400 days | Strictly necessary |
crewdle_ms_tid, crewdle_ms_oid | Cookies, first party, on .crewdle.ai | After you sign in with Microsoft, passes your Microsoft organization to the app so you can join your team's Crewdle organization. | 5 minutes | Strictly necessary |
crewdle_auth_pkce:* | Session storage, first party | Protects the sign-in hand-off between the sign-in portal and an app (a one-time security code). | Deleted after sign-in, or when you close the tab | Strictly necessary |
firebaseLocalStorageDb | IndexedDB, first party (Google Firebase) | Keeps you signed in to an app. | Until you sign out | Strictly necessary |
firebase-app-check-database, _grecaptcha; _GRECAPTCHA on google.com | IndexedDB and local storage, first party; cookie, third party (Google reCAPTCHA) | Protects sign-up, phone verification and our servers against bots and abuse. | Up to 6 months | Strictly necessary |
__stripe_mid, __stripe_sid | Cookies, first party (set by Stripe) | Fraud prevention for payments, set by Stripe's payment library. | 1 year and 30 minutes | Strictly necessary |
msal.* | Session storage, first party (Microsoft) | Used when you connect a Microsoft account. | Until you close the tab | Strictly necessary |
crewdle_pending_email_code, crewdle:chunk-reload-at, crewdle_white_label*, crewdle_partner_home:* and other interface keys | Session and local storage, first party | Keep a sign-up in progress, recover from an app update, show your organization's branding, and remember interface settings such as open panels and default models. | Until you close the tab or clear it (branding return links: 24 hours) | Strictly necessary or preferences |
crewdle_theme, crewdle_lang (and theme, lang) | Cookies on .crewdle.ai, and local storage, first party | Remember your theme (light or dark) and language across Crewdle apps. | 365 days | Preferences |
crewdle_ref | Cookie, first party, on .crewdle.ai | Remembers the partner referral link you followed, so the sign-up is attributed to that partner. | 7 days | Measurement and testing |
crewdle_src | Session storage, first party; a cookie on .crewdle.ai only with your consent | Remembers how you first found Crewdle (campaign, referring site, referral code), so we know which channel brought you when you create an account. | Session storage: until you close the tab. Cookie: 90 days | Measurement and testing |
Your choices
- Consent: where the law requires it, we ask before using measurement and testing items, and you can change your choice at any time. There's nothing to set: crewdle.com doesn't use optional cookies. You can clear what's stored in your browser's settings at any time.
- Your browser: you can block or delete cookies and site data in your browser settings. If you block strictly necessary items, signing in will not work.
We update this section when we add, change or remove a cookie or storage item.
11. How long we keep information
| Information | How long |
|---|---|
| Account and profile | Until you delete your account |
| Organization content (conversations, files, agents, memory, agent email) | Until it is deleted by a user, by the organization, or with the organization; deleted 1 year after the organization's last activity |
| Personal chats | Until you delete them or your account |
| Shared links | Until they expire or are revoked |
| Build: inactive prototype projects; build logs | Deleted after 180 days without activity; 30 days |
| Meeting recording working files | 14 days |
| Pending approval and memory suggestion cards | Expire after 3 to 14 days |
| Email verification codes | 10 minutes |
| Usage and billing records, invoices | 7 years for tax and accounting records; deleted with the organization except invoices and a summary of totals kept for accounting |
| Anti-abuse records (phone number, email address, IP address used for a free grant or sign-up limits) | 3 years; kept after account deletion to prevent repeat abuse of free balance |
| Referral records | 2 years after the reward is paid or refused |
| Sign-up attribution | Until you delete your account |
| Cookieless analytics events | 13 months; aggregated totals without a time limit |
| Survey answers and stop-paying reasons | 2 years |
| Server logs | 90 days |
| Backups | Up to 35 days, then overwritten |
When you delete your account, we delete your profile, your agents, your personal chats, conversations where you were the only participant, your files, your connections and your Build projects. Messages you wrote in shared conversations stay with the organization and are shown as written by "Deleted user". You must first delete any organization you own, or transfer it.
12. Security
Data is encrypted in transit and at rest; agent storage is encrypted, and knowledge indexes use a dedicated key in each region. Organizations are separated by access rules on every record, and each agent runs in its own container. Agents ask before sensitive actions. Server logs are designed to keep metadata only, not the content of prompts, replies or emails. Access by Crewdle staff is limited to what is needed and logged. No system is perfectly secure: if an incident creates a risk of serious harm to you, we will notify you and the competent authorities as the law requires, and we keep a register of incidents.
13. Your rights
Depending on where you live, you can:
- know whether we hold information about you, and get a copy of it;
- have it corrected, or completed;
- have it deleted (you can delete your account yourself under Account, Danger zone);
- get it in a structured, commonly used format (portability);
- withdraw your consent, for example to cookies or marketing emails;
- object to or restrict some uses, including processing based on our legitimate interests;
- be informed about, and submit observations on, a decision based solely on automated processing.
Write to support@crewdle.com. We answer within 30 days. We may need to confirm your identity. If your request concerns content held by an organization, we will forward it to that organization or help it answer.
If you are not satisfied with our answer, you can complain to the Commission d’accès à l’information du Québec, the Office of the Privacy Commissioner of Canada, or, in the European Union or the United Kingdom, your local data protection authority.
California and other US states. We do not sell personal information or share it for cross-context behavioural advertising, and we do not use sensitive personal information to infer characteristics. You can exercise the rights above, and we will not treat you differently for doing so.
14. Children
The Services are not meant for children. You must be at least 18 years old to create an account. If you believe a child has given us personal information, contact us and we will delete it.
15. Emails we send
We send emails needed for the Services (sign-in codes, invitations, billing, security and important changes). With your consent or as the law allows, we also send product updates, tips and offers; every such email has an unsubscribe link, and you can manage your email preferences in your account.
16. Changes to this policy
We update this policy when our practices change. The date at the top shows the latest version. If a change is significant, we will tell you in the Services or by email before it takes effect.
17. Contact
Questions or requests: Vincent Lamanna, CEO, support@crewdle.com, Crewdle Technologies Inc., 3 Place Ville Marie #400, Montreal, Quebec, H3B 2E3.

