Skip to content
Nimlits
Meet your teamSee them workTeach a Nim
Create a Team ↗
Nimlits/Privacy Policy

How Nimlits handles your data

Privacy Policy

Effective November 9, 2026

This Privacy Policy explains what information Nimlits collects, how we use it, who we share it with, and the rights you have over it. It applies to the Nimlits mobile apps, web app, the marketing sites at nimlits.com and lydo.chat, and any related services we offer (together, the "Service").

Nimlits is operated by Wisr Labs Inc., a Delaware corporation ("Nimlits," "we," "our," or "us"). When your employer or team operates a Nimlits workspace ("Space"), they are the controller of the data your team puts into that Space; we process that data on their behalf as described below.

The short version We collect only what we need to run the Service. We don't sell your data. We don't train external AI models on your team's content. We give you a thorough erasure feature in your Personal chats (Confidential), and we use it on ourselves too.

1. Information we collect

1.1 Account information

  • Phone number, email, display name, profile photo when you create an account.
  • Password (hashed) or third-party identity tokens if you sign in with Google, Apple, or another provider.
  • Verification codes used to prove ownership of your account.
  • Workspace and role information — which Spaces you belong to, what role you hold, what channels you've joined.

1.2 Communications and content

  • Messages — text, images, video, audio, files, polls, and reactions you send in any channel, group, or direct message.
  • Voice and video calls — connection metadata, and, where the Space owner has enabled it, recordings and transcripts.
  • Transcripts — when transcription is enabled, we generate a written record of voice/video calls; transcripts can be searched by Nims, approved connected agents, and the team's authorized members.
  • Wiki, Notes, Action Board, Calendar, Broadcast — anything your team writes, schedules, captures, or pins inside a Space.
  • AI agent interactions — questions you ask a Nim or an approved connected agent, the answers returned, and the source citations.

1.3 Device and usage information

  • Device type, OS, app version, language, timezone, and a device identifier we generate.
  • Approximate location derived from IP. We do not collect precise GPS unless you attach it to a message.
  • Usage events for product analytics and abuse prevention.
  • Crash reports, latency metrics, and similar diagnostic data.

1.4 Permissions you grant

  • Microphone for voice messages, voice calls, video calls.
  • Camera for video calls, attached photos, avatars.
  • Photo library for sending images and videos.
  • Contacts to help you find people you already know on Nimlits. When you allow access, the app uploads the names and phone numbers from your device's contacts to your account, and adds new ones periodically while access stays on. We store these entries in readable form (phone numbers are not hashed), including entries that don't match a Nimlits account. Only you can see them in the app; we use them to show which of your contacts are on Nimlits, to let you know when one of them joins, and in aggregate counts for product analytics.
  • Push notifications for incoming messages, calls, reminders.
  • Calendar on devices where a Nim or an approved connected agent is asked to schedule reminders.

1.5 Payment and billing information

If you subscribe to a paid plan or purchase prepaid usage credits, payments are processed by our payment processor. Your card or bank details are collected and stored by the payment processor and never touch Nimlits’ servers. We keep a payment token that lets us charge you, plus billing metadata we need for accounting and support — invoices, wallet balances, and usage and settlement records for metered AI features. Sales tax, VAT, and similar taxes are calculated and handled through our payment processor’s tax service.

2. How we use information

  • To provide, maintain, and improve the Service.
  • To deliver messages, calls, and notifications.
  • To power AI features inside your Space (see Section 3).
  • To operate billing, send receipts, and prevent fraud.
  • To detect, investigate, and prevent abuse and Terms violations.
  • To respond to support requests and operational notices.
  • To comply with applicable law.

We do not sell your personal information. We do not share your messages, calls, or AI agent interactions with advertisers, brokers, or third parties for their own marketing.

3. AI features and agents

Members of a Space can add Nims, our AI teammates, to a Space, and Space admins can connect approved AI agents built on models from third-party providers (the model providers you can choose in the app), as well as custom agents. Some managed requests are routed through a model-routing provider to reach the selected model. To answer questions, summarize conversations, extract action items, translate messages, and remember decisions, Nims and approved connected agents process the content your Space permits.

3.1 What AI agents can read

Nims and approved connected agents read only the content inside the Space, channel, conversation, or tool scope they are allowed to access. An agent in one Space cannot read content from another Space unless your organization has explicitly connected those Spaces. Direct messages between two users are not visible to an agent unless those users have asked that agent into the conversation.

If you turn on AI features for your personal notes (Settings → Notes for Nims), Nims and approved connected agents may also process the content of notes you own — and notes shared with you — to power semantic search, in-editor AI actions, related-note suggestions, and similar features. The free-text "Personal context" field, when set, is included with each request so responses better reflect your preferences. You can turn any of this off at any time, which stops further AI processing of personal content.

3.2 Third-party AI processors

Nims and connected AI features use large language models and supporting AI services hosted by third-party providers to generate responses, transcribe audio, produce embeddings used for search and ranking, and route real-time media. When you send content to an AI agent, that content is processed by the provider whose model you (or your Space) selected, under that provider's data-processing terms. Retention and training-use terms vary by provider; see the applicable provider's policies, linked from our subprocessor page, for specifics. Where a provider offers reduced-retention or no-training processing modes, we enable them where available. Section 5 lists the categories of these providers; the named list is available to customers on request, and it may change as we improve the Service. We use provider agreements and provider-level settings designed to prevent your content from being used to train public foundation models; specific commitments vary by provider — see the provider's data-processing terms.

3.3 Bring your own key (BYOK)

Where the Service supports it, you can connect your own API key for a supported AI provider. When you do, requests made with that key run under the key owner's provider account and that provider's terms — not under Nimlits’ provider agreements. A key's owner can make it usable by other members in shared contexts (for example, group chats or Spaces); the key owner remains the provider-account holder for all requests made with the key and should only share a key where they are comfortable with that.

3.4 AI-derived data

To power search, retrieval, and related features, we generate and store vector representations ("embeddings") of notes and knowledge content via managed embedding models. Where a workspace has enabled team knowledge features, we may also synthesize team knowledge (for example, distilled summaries of decisions and recurring topics) from that workspace's content; synthesized knowledge is scoped to the workspace that owns the source content and is not shared across workspaces.

3.5 Training

We do not train external foundation models on your team's content. We may use aggregated, de-identified usage signals (e.g. how long an answer is, what percentage of users mark a summary as helpful) to improve our own product.

3.6 External integrations

Third-party integrations and Model Context Protocol (MCP) connections let Nims and approved connected agents connect to tools like Notion, Linear, GitHub, Google Calendar, and CRMs. When an agent calls a tool on your behalf, the data needed to fulfill the request is sent to that tool's provider, and that provider's privacy policy applies. Space admins can disable specific integrations at any time.

3.7 Accuracy

AI outputs may be wrong. Verify before acting on anything an AI agent tells you, especially anything involving money, health, legal exposure, or harm to others.

4. How we share information

  • Inside your Space — content is visible according to channel and role rules.
  • With subprocessors we use to run the Service (see Section 5).
  • With Space owners — if you use the Service through a Space operated by your employer or another organization, that Space owner has access to the content posted in that Space.
  • For corporate transactions — in connection with a merger, acquisition, financing, or asset sale.
  • For legal reasons — when we believe in good faith disclosure is required by law or to prevent imminent harm.
  • With your consent.

5. Subprocessors

To run the Service we use a small set of third-party providers ("subprocessors") for hosting, real-time media, transcription, AI inference, payment processing, crash reporting, and push delivery. We have written agreements with each binding them to confidentiality and security, and — for the AI vendors — we use provider agreements and provider-level settings designed to prevent your team's content from being used to train public foundation models; specific commitments vary by provider — see the provider's data-processing terms.

The current list of named subprocessors, with each vendor's purpose and data-processing region, is available to customers on request at team@nimlits.com and is provided with our Data Processing Agreement.

Enterprise customers receive at least 30 days' advance notice of new subprocessors. Email team@nimlits.com with subject "Subprocessor notice" to subscribe.

6. Confidential and disappearing messages

6.1 Confidential

Confidential is available in Personal chats (direct messages and groups outside a Space). It is not currently available in Spaces (Teams), including Space channels and Space direct messages; we will update this policy before it is offered there. When you tap Confidential on a message, we erase it from sender and recipient device caches, the Nimlits cloud database, cloud file storage, search and AI indexes, and active backup snapshots (within 30 days). What remains is a tombstone showing a message was sent and erased. We do not maintain a hidden recoverable copy.

6.2 Disappearing messages

In Personal chats you can set a per-conversation timer that automatically erases messages a fixed time after they're sent. The same erasure pipeline as Confidential applies when the timer fires. Timers are not offered in Spaces (Teams); any timer previously set on a Space direct message is being turned off, and messages already sent with a timer are still erased on schedule.

6.3 End-to-end encrypted content (Confidential Mode)

Personal conversations protected by Confidential Mode, where enabled, use end-to-end encryption (MLS). End-to-end encrypted messages are not readable by Nimlits: we cannot decrypt them, and they are excluded from AI processing and search indexing. Confidential Mode is not currently available in Spaces (Teams); Space channels and Space direct messages are not end-to-end encrypted and are processed as described in this policy. Metadata needed to deliver encrypted messages (such as sender, recipients, and timestamps) is still processed as described in this policy.

6.4 What we cannot guarantee

We can erase messages from systems we control. We cannot prevent another participant from screenshotting, photographing their screen, or copying text into another tool before erasure.

7. Data retention

  • Active workspace content — kept while the Space is active. Owners can set a per-channel retention window.
  • Closed accounts — profile, settings, and DMs deleted within 30 days. Messages in shared Spaces remain owned by the Space.
  • Closed Spaces — content scheduled for deletion within 30 days, with a 7-day grace period.
  • Confidential — erased per Section 6.1; tombstone retained as long as the parent conversation exists.
  • Logs — retained up to 90 days.
  • Billing — retained 7 years for tax/accounting.
  • Legal holds — may suspend deletion only as required.

8. Backups

Encrypted backups are retained up to 30 days then permanently destroyed. When you trigger an erasure, deletion propagates to active databases immediately and to backup snapshots within the 30-day window as snapshots roll over.

9. Security

  • TLS 1.2+ in transit.
  • Encryption at rest using cloud-provider managed keys.
  • Voice/video encrypted in transit between participants and our media servers.
  • Least-privilege employee access; multi-factor auth on production.
  • Production access logged and reviewed.
  • Enterprise MLS encrypted Spaces are planned for private rollouts with teams that need human members and approved AI agents operating inside the same encrypted boundary.
  • Working toward SOC 2 Type II. Enterprise customers may request our latest security questionnaire under NDA.

10. International transfers

Nimlits is operated from the United States. If you're in the EEA, U.K., or Switzerland, your information will be transferred to and processed in countries with different data-protection laws. We rely on Standard Contractual Clauses for these transfers. Enterprise customers may request a Data Processing Addendum.

11. Your rights

Depending on where you live, you may have the right to access, correct, delete, export, object to processing, restrict processing, withdraw consent, and lodge a complaint with your data-protection authority. Contact team@nimlits.com. California residents have additional CCPA/CPRA rights. We do not sell or share personal information for cross-context behavioral advertising.

12. Age requirement

Nimlits is intended for adults. You must be at least 18 years old to use the Service; the Service is not directed to, and may not be used by, anyone under 18. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us with personal information, contact team@nimlits.com and we will delete it.

13. Cookies and SDKs

We use cookies and browser storage to keep you signed in, preserve drafts and unread state, and remember your theme. We do not use advertising cookies. We use first-party analytics and do not embed third-party advertising or behavioral-tracking SDKs in the apps.

14. Push and SMS

If you grant permission, we send push notifications. SMS is sent only for verification during sign-up or password reset; standard rates may apply. We do not send marketing SMS without separate consent.

15. Export and deletion

  • Export — Settings → Privacy → Export my data. Delivered as a JSON archive within 7 days.
  • Account deletion — Settings → Account → Delete account. Irreversible after a 7-day grace period.
  • Space deletion — Space settings → Danger zone → Delete Space.

16. Changes

For material changes, we'll give notice in-app or by email at least 30 days before the change takes effect.

17. Contact

All inquiries go to team@nimlits.com. Use a descriptive subject line — for example, "Privacy question," "Data subject request," "DPO matter," or "Security disclosure."

Postal — Wisr Labs Inc., Delaware, United States.

NimlitsBig intelligence. A little personality.
Skills at workIntegrationsQuestions & accessPricingPrivacyTermsSupport
Follow @nimlitsX↗Instagram↗TikTok↗Reddit↗YouTube↗LinkedIn↗Discord↗