Privacy policy

Effective 3 November 2026 · Applies to the Nedim desktop app, the Nedim mobile app and nedim.app

Nedim is workplace software that an organization installs on its own server for its own members. This policy explains, in plain language, what the apps and this website process, where that data lives, who can see it and how long it is kept. The short version: the organization that runs your Nedim server holds your data; the makers of Nedim do not receive it.

1. Who is responsible for what

Nedim is not a hosted service. Each organization deploys the Nedim server on infrastructure it controls and invites its own members. For everything you do inside Nedim, your organization is the data controller: it decides who may join, which features are enabled, which AI provider the server uses, how long data is kept and who may see it. Questions about your workspace data go to your organization's Nedim administrator.

The makers of Nedim publish the apps and operate this website. They do not run your organization's server, do not have accounts on it and do not receive any data from the apps. The only data they process is described in section 10.

2. Account, sign-in and devices

Your account exists only on your organization's server. To operate it, the server stores:

• your e-mail address, display name and the invitation that created the account;
• a salted hash of your password (never the password itself) and your encrypted two-factor secret;
• one-time recovery codes, hashed;
• a record per signed-in device: a name you can edit, the platform, the app version, the time of the last sign-in and a public key the device uses to prove it is the same device on later requests;
• an audit log of security-relevant events (sign-ins, failed attempts, device changes, administrative actions) with the time and the IP address the request came from.

You can see and revoke your devices under Settings → Devices. Revoking a device signs it out and tells it to delete its local data the next time it connects.

3. Workspace content

Messages, attachments, files, documents, slide decks, sheets, notes, automation definitions and their run history are stored on your organization's server (database and object storage) so that your colleagues and your other devices can see them. This content is protected in transit and at rest by the server, but it is not end-to-end encrypted: your organization's administrators can access it, and it is searchable within the workspace according to the permissions your organization sets.

Presence (whether you are online) and read state are shared with the people you work with and are not kept as a history.

4. The vault

The vault holds logins, secrets, notes and files. Everything in it is encrypted on your device with a key derived from a passphrase that is separate from your account password. The passphrase and the derived key never leave your device. The server stores only ciphertext and can neither read it nor recover it for you: if you lose the passphrase, the vault cannot be opened. Administrators cannot read vault contents.

On the phone you may unlock the vault with Face ID, Touch ID or a fingerprint. That check is performed by the operating system; Nedim never receives, stores or transmits biometric data. The unlocked key is kept in the device's secure hardware store for a limited time and is invalidated when biometric enrolment changes.

5. AI features and agents

When you use an AI feature on the server (for example the AI composer or a server-side bot), the text you type and the content you attach are sent through your organization's server to the AI provider your administrator has configured (for example Anthropic). That provider processes the request under its own terms and the agreement your organization has with it. Your organization's administrator can tell you which provider is in use.

Coding agents on the desktop (Claude Code, Codex, Cursor and others) are separate programs that run on your own computer under your own account with that vendor. Nedim starts and displays them; what they send to their vendor is governed by that vendor's policy. Nedim does not add any of its own data collection to them.

Push-to-talk in the mobile AI composer records audio only while you hold the button, converts it to text and discards the audio. No audio is stored or sent elsewhere.

6. Notifications

If you allow notifications on the phone, the app registers a device push token with your organization's server. The server uses that token to deliver notifications through Apple's or Google's push service. The delivery message carries the minimum needed to show the notification; the full content is fetched from your organization's server when you open the app. You can turn notifications off in the system settings at any time.

7. Device permissions

Nedim does not request your location, contacts, calendar or health data.

8. What is stored on your device

• Sign-in state: a short-lived access token in memory and a refresh token in the operating system's keychain or keystore, bound to this device only.
• Cache: a local database with recent messages, contacts and settings so the app works offline. On the phone the database is encrypted and its key lives in the keychain; on the desktop it is stored under your user profile.
• Vault: encrypted as described in section 4.
• Logs and diagnostics: a local log file that you can inspect and export; it is never uploaded automatically.

Signing out, or an administrator revoking the device, removes the tokens, the cache and the vault copy from the device. On Android the app excludes its data from system backups.

9. Telemetry, analytics and crash reports

The Nedim apps contain no analytics, advertising or tracking SDKs and send no usage statistics. Crash reports and diagnostics stay on the device unless you export them yourself and choose to share them, for example with your administrator. The desktop app checks your organization's server for updates; that request carries the app version and platform, nothing more.

10. This website

nedim.app is a static site. It sets no cookies, runs no scripts, embeds nothing from third parties and has no accounts or forms. The web server and the content delivery network in front of it keep standard access logs (IP address, requested page, time, browser identification) for security and capacity purposes for up to 30 days. Nothing from the website is linked to a Nedim account.

11. Retention and deletion

Your organization decides how long workspace content, audit logs and backups are kept and deletes accounts when people leave. When an account is deleted, its devices are revoked and its personal data is removed from the server; messages you sent to others remain visible to them in the shared conversation unless your organization removes them. Backups age out on the schedule your organization sets.

12. Your rights

Depending on where you live, you may have the right to access, correct, export or delete personal data and to object to certain processing. For data inside a Nedim workspace, address your request to your organization's Nedim administrator, who holds the data and can act on it. For questions about this website or about the apps in general, contact the address in section 15. If you believe your request has not been handled properly, you may complain to your local data protection authority.

13. Children

Nedim is workplace software and is not directed at children. Organizations should not invite anyone under 16.

14. Changes to this policy

When this policy changes, the new version is published at this address with a new effective date. Material changes are also noted in the apps' release notes.

15. Contact

Questions about this policy, the website or the apps: [email protected]. Questions about your workspace data: your organization's Nedim administrator.