Privacy Policy

Effective Date: January 28, 2026 | Last Updated: October 6, 2026

Inchambers and the website inchambers.ai are operated by Northbench Labs Inc., a corporation incorporated under the Business Corporations Act (Ontario), Canada (Ontario Corporation Number 1001736991), with its registered office at Office 923, 145 1/2 Church Street, Unit 5, Toronto, Ontario M5B 1Y4, Canada (“Northbench,” “we,” “our,” or “us”). Northbench Labs Inc. is the organization accountable for, and the controller of, the personal information described in this policy. We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our web application, Microsoft Word add-in, and related services (collectively, the “Service”). For more details on our privacy architecture, see our Privacy Architecture page. This policy complies with Microsoft Office Add-in Store requirements, Google OAuth requirements, and Microsoft Azure OAuth requirements. Inchambers is built on a zero-knowledge architecture. Your documents, AI prompts, AI responses, API keys, templates, chat history, and analysis results never touch our servers. All document processing happens entirely on your device.

1. Information We Collect

Information You Provide: When you register, we collect your name, email address, profile picture URL, and country (via Google OAuth or Microsoft Azure OAuth). Payment information is processed by Stripe or Razorpay; we store only your customer and subscription identifiers. Contact form submissions include name, email, message, and IP address for spam prevention. Newsletter subscriptions collect your email address.

Information Collected Automatically: We collect aggregate feature usage data (feature name, AI provider/model selected, success/failure status, per-user request count). We record session duration and activity count. Your IP address is used by our rate limiter and is recorded with your sign-in sessions and security audit events, to protect your account against misuse.

Information We Do Not Collect: Consistent with our zero-knowledge architecture, we do not collect, store, transmit, or have access to: document content, AI prompts and responses, API keys, templates, chat history, analysis results, device information, page views or browsing patterns, or client/case information.

2. How We Use Your Information

We use collected information to: provide, maintain, and improve the Service; process transactions and manage subscriptions; authenticate your identity; send technical notices, updates, and support messages; respond to inquiries; monitor aggregate usage trends; enforce rate limits; detect and prevent fraud; and comply with legal obligations.

3. Google and Microsoft Account Access (OAuth Scopes)

Sign-in: When you sign in with Google or Microsoft we request only openid, email and profile, to identify you.

Optional connectors: If you choose to connect your Google or Microsoft account inside the Service, we request the permissions below. Each is used only for the user-facing feature named, and only when you use it.

Permission	What it is used for
Google gmail.modify; Microsoft Mail.Read, Mail.ReadWrite, Mail.Send	The in-app email client: reading, searching and labelling your mail, saving drafts, and sending messages you write or approve.
Google calendar; Microsoft Calendars.ReadWrite	Showing your calendar and adding hearing dates, deadlines and meetings you create.
Google contacts.readonly, contacts.other.readonly; Microsoft Contacts.Read, People.Read	Suggesting recipients as you type an email address.
Google drive	Opening, editing and saving back the Drive documents you choose to work on in the Files module and the document editor.
Microsoft Files.ReadWrite.All, Sites.ReadWrite.All	Opening, searching, editing and saving back the OneDrive and SharePoint documents you choose to work on, including files shared with you.
Google drive.appdata; Microsoft Files.ReadWrite.AppFolder	Optional encrypted cross-device sync, stored in a hidden app-specific folder in your own storage.

How this data is handled: Your mail, calendar, contacts and files are read by the Inchambers app running in your browser, directly from Google’s or Microsoft’s servers. They are not sent to, stored on, or logged by Inchambers servers. Your Google and Microsoft access tokens are stored only on your own device, encrypted with AES-256-GCM (in your browser’s storage, and for Microsoft also in the Inchambers desktop app’s encrypted vault if you use it). They are never stored on our servers. Google requires our app’s secret key to issue and renew its tokens, so those two requests pass through our server, which adds the key and returns the tokens directly to your browser without storing or logging them. For a few optional connectors (Notion, Asana, HubSpot), a newly issued token is held on our server for at most two minutes, used once, to pass it to your browser. Content from these services is sent to an AI model only when you ask the Service to act on it (for example, to summarise an email or draft a reply). It then goes to the AI provider you selected, directly from your device when you use your own API key, and is not stored by us. We do not use this data for advertising, do not sell it, and do not allow humans to read it, except with your explicit consent for a specific message, where necessary for security, or to comply with law.

Google API Services User Data Policy: Inchambers’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google Workspace data obtained through Google APIs is not used to develop, improve or train generalized artificial intelligence or machine learning models.

Revoking access: You can disconnect a connector at any time in the Service, which revokes the Google grant and deletes the stored tokens. Deleting your Inchambers account also revokes the Google access connected in the browser you delete it from. You can also remove access at myaccount.google.com/permissions or account.microsoft.com.

4. Zero-Knowledge Architecture and Data Security

Inchambers operates across four isolated layers: (1) Authentication Layer: validates identity and subscription only, no document data; (2) Processing Layer: all document analysis happens on your device; (3) AI Layer: if you use your own API key, requests go directly from your device to the AI provider; otherwise they pass through our relay, which forwards them to the AI provider without storing or logging content; (4) Storage Layer: only account, billing metadata and aggregate usage counts.

API keys are encrypted with AES-256-GCM using the WebCrypto API. Templates, chat history and analysis results are stored in your browser’s IndexedDB. Optional Cloud Sync encrypts all data on your device with AES-256-GCM before uploading to your Google Drive or OneDrive; we cannot decrypt your cloud-synced data.

Security measures include: TLS 1.2+ encryption in transit, AES-256-GCM encryption for local and cloud-synced data, origin-isolated IndexedDB storage, OAuth 2.0 with PKCE, short-lived RS256-signed sessions bound to your device, a strict Content Security Policy, and regular security assessments. No method of transmission or storage is 100% secure.

5. Data Sharing and Disclosure

We do not sell your personal information. Service providers (subprocessors) that process account or billing data on our behalf: Amazon Web Services (application hosting in Canada, and transactional email through Amazon SES), Cloudflare (DNS, CDN and web security, and encrypted database backups stored in Cloudflare R2), Stripe and Razorpay (payment processing; we store only customer and subscription identifiers), and AI model providers (only the content of AI requests you make, relayed without storage when you do not use your own key). Our databases and rate limiting run on our own hosted infrastructure.

MCP integrations transmit data directly from your device to third-party services. Data shared with third parties is subject to their privacy policies. Authentication credentials for MCP services are stored locally with AES-256-GCM encryption. Some MCP integrations may use unofficial APIs or methods and may not have the same privacy and security guarantees as official integrations. We may disclose information if required by law. In a merger or acquisition, your information may be transferred.

6. Your Rights and Choices

You can access and export your account information and locally stored data at any time, and update account information in settings. You can delete your account yourself under Profile, Delete account: this cancels any subscription, signs out every device, deletes your account record immediately and revokes the Google access connected in that browser. To be certain no access remains, also remove Inchambers at myaccount.google.com/permissions. You can also request deletion by contacting [email protected]. Local data can be cleared through browser settings or the “Clear Data” option. Cloud Sync data can be deleted through Settings or directly from your Google Drive/OneDrive. You can opt out of marketing communications and revoke OAuth permissions at any time.

7. Data Retention

Account data is retained while your account is active. When you delete your account, your account record is deleted immediately and copies in encrypted database backups expire within 35 days. Billing records may be retained longer where tax or accounting law requires. Usage metrics are retained for the lifetime of your account. Rate-limiting data is transient. Session records, including IP addresses, are deleted with your account. Security audit records may be retained longer where needed to investigate misuse or meet legal obligations. Data from Google or Microsoft connectors is never stored on our servers; OAuth tokens on your device are deleted when you disconnect or delete your account. Local data is stored on your device until you clear it.

8. Children’s Privacy

Inchambers is not intended for use by individuals under 18. We do not knowingly collect personal information from children.

9. International Data Transfers

Your account information may be transferred to and processed in countries other than your country of residence. We ensure appropriate safeguards are in place for such transfers.

10. Microsoft Office Add-in Compliance

Document content is processed entirely client-side and never reaches our servers. We do not transmit, store, or use document content for advertising. When AI features are used, content is relayed on-the-fly (never stored) or sent directly to the AI provider for BYOK users.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. For material changes, we will provide additional notice such as email notification.

12. Contact Us

Inchambers is operated by:

Northbench Labs Inc.
Office 923, 145 1/2 Church Street, Unit 5
Toronto, Ontario M5B 1Y4, Canada
Ontario Corporation Number 1001736991 (incorporated under the Business Corporations Act (Ontario))

Privacy inquiries: [email protected]. Data Protection Officer: [email protected]. You may also write to us by post at the address above.

13. Jurisdiction-Specific Rights

EEA (GDPR): We process personal data under Contract Performance (Art. 6(1)(b)), Legitimate Interests (Art. 6(1)(f)), and Consent (Art. 6(1)(a)). You have rights to access, rectify, erase, restrict processing, data portability, and to lodge complaints with a supervisory authority.

California (CCPA): You have the right to know, right to delete, and right to non-discrimination. We do not sell your personal information or share it for cross-context behavioral advertising.

Canada (PIPEDA): Northbench Labs Inc. is an Ontario corporation and is accountable for personal information under its control under the Personal Information Protection and Electronic Documents Act (PIPEDA). You have rights to access and correct your personal information under PIPEDA. Complaints may be directed to our Privacy Officer at [email protected] and, if unresolved, to the Office of the Privacy Commissioner of Canada.

India (IT Act): Your information is subject to the Information Technology Act, 2000. Grievance Officer: [email protected]. We will acknowledge complaints within 48 hours and resolve within 30 days.

Legal Research and Citation Sources

When you use legal research, citation checking, or docket features, queries to public court sources (for example CourtListener / the Free Law Project and the Caselaw Access Project) are made directly from your browser to those third parties. For recent or unpublished opinions, full text may be retrieved through the Inchambers relay or, for firm customers, your firm’s own deployment. Inchambers does not store the content of these queries. Your use of third-party sources is subject to their own terms and privacy practices.

By using Inchambers, you acknowledge that you have read and understood this Privacy Policy. See also: Terms of Service · Disclaimer