Skip to content

Legal

Privacy policy

What information Nidus handles, why, who helps us run the Service, and the choices you have. The short version: your company's data is your company's, we collect what the Service needs, and we never sell it.

1. Who we are and what this covers

Nidus ("Nidus", "we", "us") runs nidus.sh, the company sites at their own subdomains (such as acme.nidus.sh), and the Nidus app for iPhone, iPad, and Mac. Together these are the "Service". This policy explains what personal information we handle, why, and the choices you have.

Nidus is sold to organizations ("Customers"). Information a Customer and its people put into their company workspace, or sync into it from tools like Microsoft Entra, is Customer Data. For Customer Data, the Customer decides what is collected and why, and Nidus processes it on the Customer's behalf and under its instructions. If you use Nidus through your employer, your employer's own privacy notice also applies, and requests about that data are best sent to them first.

For information about our own website visitors, people who contact us, and Customer billing and account contacts, Nidus decides how it is used and is responsible for it.

2. Information we collect

Account information. Your name, work email, company, role, and sign-in details. Passwords are stored only as salted hashes. If you turn on two-step verification or add a passkey, we store what is needed to check them. For each signed-in session we keep the IP address, browser or device type, and times so you can see and end your sessions.

Workspace content. What your company records in Nidus: assets, serial numbers, stock, locations, categories, invoices, photos, custody and handoff records, signed receipts (including the signer's name and signature), projects, tasks, costs, mileage trips, time entries, vehicles, approvals, alerts, and the audit trail of who changed what and when.

Data from connected tools. When a company connects an integration, we receive what it provides:

  • Microsoft Entra ID: directory people (name, email, job title, department, office, employee ID, manager, cost center, license and account status) and security groups, plus Microsoft sign-in for single sign-on.
  • Microsoft Intune and Datto RMM: managed devices, their serial numbers, models, and assigned users.
  • Freshdesk: tickets linked to assets.
  • Microsoft Teams: the webhook a company sets up to receive alerts.

The iPhone, iPad, and Mac app. The app asks before using these, and you can turn each off in Settings:

  • Camera, to scan asset tags, serial numbers, SKUs, and location labels, and to take photos you choose to attach. Scanning happens on the device; only the photos you attach are uploaded.
  • Photo library, only for photos you pick to attach.
  • Location, only while the app is in use, to fill in where a trip started or ended and to count distance while you track a trip. The route stays on your device; Nidus receives only the places and distance you save with the trip.

Contact and support. When you use the contact form or email us: your name, email, company, team size, and message. We use your IP address briefly to limit abuse of the form.

Demo feedback. If you leave feedback when you exit the public demo: the email you enter, your answers, and the page you left from. We use them only to improve Nidus and, if you'd like, to follow up.

Billing. Payments are taken by Stripe through Link. We never see or store full card numbers. We receive the customer and subscription records we need to run your plan: plan, status, billing contact, and renewal dates.

Product analytics. On the web app we may send a small set of events to PostHog: page views (the path only), signups, successful sign-ins and the method used, and when an asset or user is added. You are identified only by an internal Nidus ID, and your company only by its subdomain. We never send names, emails, asset details, or anything you type. Automatic click capture and session recording are off, the platform console is never tracked, and we honor your browser's Do Not Track setting. The native app sends no analytics.

Error reports. When something fails, the app records an error code, the action that failed, and a short technical message, so we can fix it.

3. How we use information

  • To provide, secure, and support the Service, including sign-in, syncing, alerts, emails, and reports your company sets up.
  • To keep accounts safe: slowing repeated failed sign-ins, ending sessions, and sending notices when security settings change.
  • To bill Customers and manage plans, trials, and limits.
  • To answer questions and requests, and to tell account owners about important changes to the Service.
  • To understand, in aggregate, which features are used, and to find and fix errors.
  • To meet legal obligations and enforce our terms.

We do not sell personal information, we do not use it for advertising, and we do not share it for cross-context behavioral advertising. We do not use Customer Data to train AI models.

Where the law requires a legal basis, we rely on performing our contract with the Customer, our legitimate interests in running and securing the Service, your consent where we ask for it (such as camera or location access), and legal obligations.

4. AI features use your company's own provider

Nidus provides no AI service of its own. A company can choose to add its own Anthropic or OpenAI API key to read invoices. When it does, the invoice files a person chooses to read are sent to that provider under the company's own account and subject to the company's agreement with that provider. Nothing is created from the result until a person reviews and confirms it. Without a key, nothing is sent to an AI provider.

5. How information is shared

Within your company. People in your company can see workspace content according to the roles and location scopes their admins set. Each company's data is isolated from every other company.

Service providers. We use these providers to run Nidus. They process information only to provide their service to us, under contracts that protect it.

ProviderPurposeLocation
ConvexDatabase and backend that stores and processes workspace dataUnited States
CloudflareWebsite hosting, delivery, and encrypted storage for photos, invoices, and logos (R2)Global network
ResendSending account emails: invites, password resets, receipts, alerts, and scheduled reportsUnited States
Stripe and LinkCheckout, subscriptions, tax, and payment support; Link is the seller of recordUnited States and worldwide
PostHogLimited product analytics on the web app (see below)United States
AppleApple Maps driving distance for mileage, when a company uses itUnited States

Integrations your company connects. Microsoft, Datto, Freshdesk, Anthropic, and OpenAI receive or provide data only when your company connects them, under your company's own agreements with them.

Legal and safety. We may disclose information if the law requires it, to protect the rights, safety, or property of our users or others, or as part of a merger, acquisition, or sale of assets, in which case this policy continues to apply to the information transferred. We tell Customers about requests for their data where the law allows.

6. Cookies and local storage

We use a small number of cookies and browser storage, all for running the Service:

  • A session cookie that keeps you signed in, shared across nidus.sh and your company's subdomain.
  • A cookie that remembers which company you last signed in to.
  • Browser storage for preferences such as theme and colors, and for offline counts and drafts on your device.
  • PostHog storage for the limited analytics described above, only on the web app and only when analytics is enabled.

We do not use advertising or cross-site tracking cookies.

7. How long we keep information

  • Workspace content is kept while the Customer's account is open, until the Customer deletes it.
  • Exports and generated reports are deleted automatically after 7 days.
  • When a company is permanently deleted, its records, users, sessions, and stored files are deleted. Copies in backups expire on their normal schedule.
  • Contact and support messages are kept as long as needed to answer them and keep a record of the conversation.
  • Billing records are kept as long as tax and accounting law requires.

8. Security

Data travels over HTTPS. Uploaded photos, invoices, and logos are encrypted with AES-256 before they are stored. Access within a company is deny-by-default, integration keys cannot be read back once saved, and changes that matter are recorded in an audit trail. No system is perfectly secure; if we learn of a breach that affects your information, we will notify the affected Customers and people as the law requires. Read more on our security page.

9. Your rights and choices

Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal information, to object to or restrict some processing, and to withdraw consent. You can update your name, password, two-step verification, and passkeys yourself from your profile.

For information in a company workspace, contact that company's admins, who control it. If you contact us instead, we will pass your request to the Customer and help them respond. For anything else, email hello@nidus.sh. We may need to confirm your identity first, and we will not treat you differently for using these rights.

If you are in the European Economic Area, the United Kingdom, or Switzerland, you may also complain to your local data protection authority. California residents have the rights above under the CCPA; we do not sell or share personal information as that law defines it.

10. International transfers

Nidus and its main providers are based in the United States, so information may be processed there and in other countries where our providers operate. Where the law requires it, we rely on safeguards such as the European Commission's Standard Contractual Clauses for these transfers.

11. Children

Nidus is a business tool and is not directed to children under 16. We do not knowingly collect their personal information. If you believe a child has given us information, contact us and we will delete it.

12. Changes to this policy

We may update this policy as Nidus changes. The date at the top shows the latest version. If a change is significant, we will tell account owners by email or in the app before it takes effect.

13. Contact us

Questions or requests about privacy: hello@nidus.sh. For general help, see Support.